Analogue-sequencer

--- In analogue-sequencer@yahoogroups.com, "Colin f" 
<colin@c...> wrote:
> Currently FUNC+RUN while running causes a STOP to be sent 
on the last beat
> of the current Gbar, followed by a START on the first beat of the 
next Gbar.

That would essentially automate how we were resyncing the 
other players at DS. But I think all we really needed was a start 
command on the Gbar. I can see why you might want to generate 
a stop command first; if the other machines are already running 
and you want to pull it together. 

> The first question is, should the FUNC+STOP send the STOP 
*immediately*,
> rather than trying to leave slaved devices running and reset 
them with Gbar
> ?

*Immediately* seems a little more flexible and intuitive.

> Second question is, should I require a second press of 
FUNC+STOP to arm the
> restart on the next Gbar - meaning you could stop slaved 
devices, and leave
> them stopped for several Gbars, before bringing them back in 
in sync ?

If I'm reading this correctly FUNC+RUN = Stop on last beat of 
Gbar, Start on 1st beat of next Gbar, while...
FUNC+STOP (1) = Immediate Stop
FUNC+STOP(2) = Start on 1st beat of next Gbar

That's useful and would work but I would probably just 
remember that FUNC+STOP is immediate stop and 
FUNC+RUN starts you at the next Gbar. What does midi gear do 
when receiving 2 stop commands in a row? 

Now that I think about it, I'd probably have to do the 2nd 
FUNC+STOP for the restart, otherwise the next time I'd think I 
was doing an immediate stop, the P3 would  actually send a 
start at the next Gbar.

OK, so FUNC+RUN is more panic mode, while FUNC+STOP is 
more musical breakdown mode. I can learn that;^)

-Jim

> 
> Best regards,
> Colin Fraser
> Sequentix Music Systems Ltd
> http://www.sequentix.com