--- In
korgpolyex@yahoogroups.com, ASSI <Stromeko@...> wrote:
>
> On Sunday 02 January 2011, zoinky420 wrote:
> > 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.
The manual doesn't say anything about having to use a specific input for clock sources, but it does say that if you go overboard with midi data you can get buffer underruns.
>
> > Theoretically it should work but I've never seen it mentioned in any
> > 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?
>
> No, that's not how MIDI clock works. You'd get the two sequences at their
> original tempo plus an unrelated MIDI clock that is only seen downstream of
> the merger.
>
>
MIDI clock does control tempo, so I'm not sure what you're getting at.