Analogue-sequencer

Colin,

Using the P3 to control a Roland MC-80(as midi slave), Func+Run works
ok as a Midi Continue BUT on first GBAR it seems to send out a Midi
Start because the MC-80 resets to Bar 1.  This only began occuring
after I upgraded from 3.1.06B10 to B18.

Is there a work round for this?

Thanks
Roger

> Using the P3 to control a Roland MC-80(as midi slave), Func+Run works
> ok as a Midi Continue BUT on first GBAR it seems to send out a Midi
> Start because the MC-80 resets to Bar 1.  This only began occuring
> after I upgraded from 3.1.06B10 to B18.
> 
> Is there a work round for this?

FUNC+RUN while stopped will CONTinue, FUNC+RUN while already running will
restart MIDI clock by sending a STOP then a START at the next GBar reset. 
The current build will need to ignore the held FUNC+RUN once it starts to
prevent it being treated as a restart.
I'll fix this and upload a new beta.

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

Roger wrote:

> Using the P3 to control a Roland MC-80(as midi slave), Func+Run works
> ok as a Midi Continue BUT on first GBAR it seems to send out a Midi
> Start because the MC-80 resets to Bar 1.  This only began occuring
> after I upgraded from 3.1.06B10 to B18.

This is fixed in beta 20, in files now, which also adds another slave 
restart option.

While P3 is running, if you press RUN again, a MIDI START message will 
be sent on the next GBar reset.
This can be used to restart manually stopped devices connected to the 
main P3 MIDI outputs. This option has no effect on the dedicated SYNC 
output for hardware reasons.

If you press FUNC+RUN while running, P3 will send a MIDI STOP message, 
followed immediately by a MIDI START on the next GBar reset.
This applies to both the main outputs, and the SYNC socket.
DIN sync can only START from STOPped, which is why the first option 
can't work on the SYNC output.


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