02-05-2021, 11:32 AM
Hi Jesse,
I created an account to say that I would also buy one of these if it did the basic MIDI clock offset functionality of the E-RM multiclock.
That is, you can offset the clock signals that are being sent out by 1/10th of 1 ms offsets. For example, one MIDI output can be connected to an E-mu SP-1200 with -0.5 ms offset, and another can be connected to an Akai MPC-3000 with the clock delayed 2.1 ms, allowing the sequencers to be actually in sync with each other and a DAW, as opposed to having phasing issues.
The other part of how the multiclock achieves superior sync is that it can sync to a sync signal generated by an audio interface (DAC) originating from a DAW. Their plugin makes it really easy, but really only a DAC is needed to make the pulses. E-rm advertises +/-1 sample jitter at 48khz when syncing multiclock this way. It seems like this could be more difficult or impossible to achieve on the hardware you've designed as others have pointed out.
I hardly care about the other things the multiclock does, like prioritizing clock messages over other midi messages, allowing for clock division of or shuffle introduced to the midi clock outputs, or the transport controls for each midi output.
Please consider a clock offset feature like the multiclock's.
To put a finer point on it, I would be just ecstatic to buy the MRCC instead of a second and likely third multiclock which I would pick up just for this clock functionality (and certainly not for anything else it does).
Thanks!
I created an account to say that I would also buy one of these if it did the basic MIDI clock offset functionality of the E-RM multiclock.
That is, you can offset the clock signals that are being sent out by 1/10th of 1 ms offsets. For example, one MIDI output can be connected to an E-mu SP-1200 with -0.5 ms offset, and another can be connected to an Akai MPC-3000 with the clock delayed 2.1 ms, allowing the sequencers to be actually in sync with each other and a DAW, as opposed to having phasing issues.
The other part of how the multiclock achieves superior sync is that it can sync to a sync signal generated by an audio interface (DAC) originating from a DAW. Their plugin makes it really easy, but really only a DAC is needed to make the pulses. E-rm advertises +/-1 sample jitter at 48khz when syncing multiclock this way. It seems like this could be more difficult or impossible to achieve on the hardware you've designed as others have pointed out.
I hardly care about the other things the multiclock does, like prioritizing clock messages over other midi messages, allowing for clock division of or shuffle introduced to the midi clock outputs, or the transport controls for each midi output.
Please consider a clock offset feature like the multiclock's.
To put a finer point on it, I would be just ecstatic to buy the MRCC instead of a second and likely third multiclock which I would pick up just for this clock functionality (and certainly not for anything else it does).
Thanks!