-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
host sync with clock+start/stop #2
Comments
I do not have a MOD Duo X, but when loading the plugin in Ardour it generates correct MIDI clock signals. The following show Ardour playing a temp-ramp, generating MIDIClock on a MIDI track. The output of the MIDI Clock generator is fed back into Ardour to show the difference between Ardour's transport and the generated clock signal. rec-2021-05-04_18.43.09.mp4So this seems to be an issue with the MOD system, and likely nothing I can do here. |
Yes, you're right, tried to wire it in Carla using Carla's host sync (jack transport), it seems like it's working just fine. Thnx anyway, and thnx for all your plugins in general, great work, using them in all I do both on the Duo and DAW's. |
Perhaps flag this up to the MOD as issue. The author of the MOD host (@falkTX)) is also the author of Carla, so it may be easy to address. |
Hi!
Seems like the clock gets messed'up when using host sync in mode
clock+start/stop
, it's somehow just set to 280bpm.I'm trying to sync a Duo Mod X to Bitwig for recording.
If I set mclk to
midi clock only
it works fine.Tried in Ardour, just to eliminate possible Bitwig problem, but same stuff happens.
Here is a video showing in details, hope this helps.
In the video you can see the Mod Duo transport, the mclk plugin and Bitwig transport.
The text was updated successfully, but these errors were encountered: