Analogue-sequencer

happened a couple of times this weekend, exactly as if I'd hit the stop button, & complete with an all-notes-off (so that a colleague at a nearby keyboard merged with the p3 had his notes choked off too).

I have low bar counts- a couple of tracks have four bars, but most were one or two. however, at least four tracks were poly-enabled to the max.

I am investigating the possibility that my motu box caused this, but I'm pretty sure that the p3 is upstream of it...
duncan.

> happened a couple of times this weekend, exactly as if I'd 
> hit the stop button, & complete with an all-notes-off (so 
> that a colleague at a nearby keyboard merged with the p3 had 
> his notes choked off too).
> 
> I have low bar counts- a couple of tracks have four bars, but 
> most were one or two. however, at least four tracks were 
> poly-enabled to the max.
> 
> I am investigating the possibility that my motu box caused 
> this, but I'm pretty sure that the p3 is upstream of it...

Did the P3 stop, or did it just send the stop and a-n-o messages ?
If it stopped itself, could it have received a stop message at its input ?

I would usually troubleshoot this sort of problem by capturing the MIDI
streams in and out of suspect devices with MIDI-Ox.
That has solved many a head-scratcher here.

Cheers,
Colin

>>Did the P3 stop<<  

yes, exactly as if I'd pushed "stop", which I didn't, but I was tweaking summat at the time... probably in mixer mode.

>>could it have received a stop message at its input ?<<

no- all there is upstream is an evolution keyboard, one of the basic ones with no transport facilities or clock o/p. the p3 is master clock these days. 

I'm wondering if the switch itself could've been set off by contaminant ingress of some sort. we weren't smoking, & it wasn't very humid. this happened three times in one piece (i.e. in the space of ten minutes) on saturday, then on sunday it was fine all day.

is there any way, under any circumstance, that the p3 could be programmed to stop on it's own? I don't think I've seen this....

downstream, however, is another story.... MOTU micro-express, maq, another keyboard... 
the maq has to receive clock from the p3 & remote control from the other keyboard, then it re-enters the MOTU as a source to be merged with both keyboards & the p3 & off to the various noise boxes. but I decided some time ago to run the p3 with FTS off at all times, & use custom patches in the emu modules for anti-bum-noting the maq.

the MOTU was fiddly to set up, but the pay-off is better merging & timing stability- previously I had three merge boxes cascaded & lots of clock problems.

duncan.