Dave Smith Instruments SYNTHESIZERS

On Thu, Mar 04, 2004 at 08:36:03PM +0100, Stefan Weber wrote:
> > The evolver's sequencer is a slightly different beast though: it's not
> > (usually) used to play whole songs, but rather as one an element, and
> > hitting the start/stop button is not really the same thing as
> > starting/stopping a whole song -- you might very well do this many times
> > within a `song', and interrupting the clock sync doesn't seem all that
> > good idea then!
> 
> that makes sense, but the funny thing is that my nord modular sequences
> start playing, when I hit evolver's start button, and stops playing, when I
> hit the button again, despite the fact that, obviously, the midi clock is
> still streaming into the nord modular.

I have no idea about the NM (I'd _like_ to own one, but can't take the
windows requirement), but I assume this is because the NM is obeying the midi
start (continue?) and stop messages.  The evolver does send those regardless
of what it does with the midi clock.

I've occasionally run into this issue with multiple evolvers, and what I did
there was make the 2nd evolver just ignore midi control messages (I forget
exactly, but I think I just set the midi-recv parameter to `none').

Similarly, maybe you there's some way to make the NM ignore these incoming
messages.  My vague recollection is that the NL3 has a midi-recv parameter
similar to the evolver, so maybe the NM does too.  At worst, I suppose, you
could use some sort of midi filter to get rid of start/stop.

Also, try setting the evolver's midi-xmit parameter to `none' or `pro'
(program changes only); I think this parameter doesn't effect midi-clock
output (since that has its own control), so it might suffice to turn off the
start/stop messages.

-Miles
-- 
"1971 pickup truck; will trade for guns"