MIDI clock in a multi-synth environment?

[jamos]

My band (C120 - http://c120.org) has decided to go from manual sync to using MIDI clock, and we're having a hell of a time with it. I should describe the problem I'm having, but it is so damned convoluted that I shudder at the thought of explaining it. Here goes.

The instruments are:

- 2 G2's (one of which is a synth, the other a master processor)
- An Alesis Ion and Alesis Fusion (respond to MIDI clock, but ignore Start and Stop messages)
- A Korg EM-1 (responds to MIDI clock and start/stop; can also be started and stopped when externally synced.)

We are an improvisational band, so we often start and stop our sequencers independently when playing. Unfortunately, because of the above mix of capabilities, I've found that it's impossible to have the sequencers all slave to the same clock, and yet still be able to independently start things.

The MIDI config I'm using at the moment is as follows: The Master G2 sends MIDI clock to all other instruments through a Thru chain. The Master G2 is set to internal sync, all others to external. This works well except for one problem: I have to start the sequencers in the second G2 using the Master G2's start/stop button; this also starts or stops the Korg as well.

Possible solutions that come to mind are:

- Find a way to filter the start/stop before they arrive at the Korg
- Find a way to start the second G2's sequencers independent of the first.

The first solution requires custom hardware or software, which is not an option at this point; so I'm looking into the second. The idea I've had is to remotely change the state of the G2's Clock module's Run buttons via MIDI, but that is a daunting prospect: I have many patches and performances with multiple clock modules, which adds up to a sh*tload of potentally messy patching.

Any suggestions?

[slave to this]

its kind of hard to conceptualize without actually seeing how you guys are doing your thing, so forgive me if you've already gone down this route. but have you tried getting fancy with assigning seperate midi channels to each of the synths? maybe you could waste a slot on your master g2 that toggled between doing different functions to seperate channels where only specific synths responded to the clock/other messages at a given time.

other than that, i know you said software isn't an option, but max/msp is your savior with this problem.

james

[jamos]

No, that won't help; MIDI clock and start/stop are not channelized.

Max/MSP might help here, but i could write a utility in C++ to do it in less time than I could learn Max. I just don't want to drag along a laptop and MIDI interface for that task.

[slave to this]

you said you needed to start the second g2's clock independent of the first?
i'm sure you could at least do that with sending midi to the seperate g2. wish i had a second to try it out on, but i don't see how that wouldn't be possible.

[slave to this]

to be more specific, i suppose i'm talking mainly more about sending triggers to start/stop sequencers on your 2nd g2, etc., but if that is what you meant about your potentially messy re-patching, i feel you.

[ian-s]

Hi Jim

I don't have any ideas about the MIDI clock issues, just wanted to say great site and excellent music.

Cheers

Ian

[jamos]

[deknow]

yes, use a single clock. these days i bring the evolver and use it as master clock (mostly because it is easy to set it to send midi clock and nothing else). ideally, i use a 707 for this, as it has a dedicated single large knob for controlling tempo. starting together is a problem when you have disparate devices...some do, some don't.

deknow

[dasz]

[jamos]

Yeah, single external clock is a no-brainer; what's tricky is that the G2 requres multiple clock modules for performances, and they can only be started in sync by the master clock switch.

I think things will work well now, we've got practice this afternnon and I'll try my new techniques then.

jim

[mosc]

Yes, nice music on that site. I'm not surprised.

[Antimon]