Always transmit MIDI clock - even when transport is stopped.

I would like to see Drambo always transmitting MIDI clock on the selected output ports. Starting clock at the same time as the transport can bring problems with some hardware synthesizers that need time for their clock oscillators to sync and lock on to the incoming MIDI clock. I can see two options to solve this:

  • Run the clock all the time and sync the start of the transport with the next clock pulse. This would mean a maximum delay of 1/24 quarter note between pressing play and the actual start.
  • To make this more battery saving the clock start could be done like a pre-roll: Play pressed, clock starts, start is sent after x number of bars.

Comments

  • If we're naming alternative MIDI clock sources, there's also the excellent MidiFire.

  • edited September 2022

    Thanks for the suggestions @gravitas and @uncleDave. I am already experimenting with MIDIFire and it works pretty well. You can even do tempo automation by controlling MIDIfire via CCs. I just would love to have everything in one box - Drambo. Less hassle and less single points of failure.

  • Sending MIDI clock always can make sense indeed. Should be in settings.

  • Doesn’t turning on Ableton link do this? You don’t have to be using Ableton to use link.

  • Not sure if that works with hardware, which seemed to be the OP's focus.

  • edited September 2022

    Ableton LINK is independent from MIDI clock. But indeed, the beat position is always updated between all LINK members and hardware can alternatively be added by using the MIDI Link Sync app.

    I've only been using a Digitakt and a KORG Electribe MX synced via MIDI clock and that worked well.

  • Found a workaround for this if you have Loopy Pro:

    • Add a Loopy Pro Audio Unit MIDI Processor module. The instance can be empty.
    • Enable Ableton Link, but not Start/Stop in Loopy.
    • Disable host sync in Loopy.
    • Set the clock out destination in Loopy.
    • Make sure there are no MIDI Clock Sources in Loopy.
    • Disconnect the Drambo track's midi output from the Loopy module to avoid possibly doubling the clock.
    • Enable Link in Drambo. (Start / stop can be what you like. Loopy will ignore it.)
    • Disable the Clock destination Drambo. (Clock will come direct from Loopy.)
    • Press play in the AU and keep it running.

    Loopy will stay reliably in sync with Drambo, sending out clock directly to the hardware, but will ignore Drambo's start and stop.

  • I have recently started to integrate Loopy Pro and Drambo - two of my favourite apps, and this works great. It even helps as a workaround for my other “Drambo MIDI clock grievance” - the way how Drambo disables all manual transport control when it is synced to another MIDI source: You can synchronise the hosted Loopy Pro to other MIDI clock sources and Drambo will follow the clock while still giving you full manual transport control.

    Thanks a lot for the detailed suggestion.

Sign In or Register to comment.