On Sunday 02 January 2011, zoinky420 wrote:
job, but you may have to use a designated input (often port 1) for the clock
source to get a stable timing.
original tempo plus an unrelated MIDI clock that is only seen downstream of
the merger.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
> hmm I have several mergers but never thought of using them that way.Most mergers don't handle real-time data well. Some do a reasonably good
job, but you may have to use a designated input (often port 1) for the clock
source to get a stable timing.
> Theoretically it should work but I've never seen it mentioned in anyNo, that's not how MIDI clock works. You'd get the two sequences at their
> manuals as an option. I've got a three-processor merger with midi
> filtering, so I could conceivably merge two different sequences at any
> tempo to one MIDI out, and control the tempo to both of them by merging
> a third channel of nothing but clock data?
original tempo plus an unrelated MIDI clock that is only seen downstream of
the merger.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds