Analogue-sequencer

Colin f wrote:

> 
>  
>
>OK, I've implemented slave re-start in a test build, but it threw up a
>couple of questions...
>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.
>I tried sending the STOP on the last clock pulse of the Gbar, but that
>didn't give my 303 enough time to get its head around restarting...
>  
>
I would personally NOT want a stop command sent at all because I often 
have multiple synced devices and wish to be able to stop them manually 
but restart them smoothly and individually when needed. If the process 
sent stop first, devices that I didn't stop manually would stop too, out 
of my control.

>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
>?
>  
>
The "safe stop" function works fine now, I wouldn't personally tamper 
with it. If you want to resync stuff, it will be because you have 
manually stopped it (all devices should be manually stoppable, in my 
experience, so the P3 needn't worry about that aspect of things).

>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 ?
>  
>
Just doing the Func+Run thing during playback to send a Start on the 
next GBar would provide all the functionality I can currently dream up...

Paul

---
Paul Nagle / Soft Room Music / Bogus Focus Records / Binar / Headshock / The Joint Intelligence Committee
        www.softroom.co.uk / www.BogusFocus.com / www.JointIntelligenceCommittee.com