Analogue-sequencer

been reading with interest the mails about midi loops & lockups.... 

what you need in a situation like this is some way to get y'r software
sequencer to send clock-only, & ignore any incoming clocks.

I wonder if these freezes are symptoms of the clock handling. my p3
had problems when it had a clock going back into it that had
originally come from it's own clock-only output. 
it senses the presence of midi clock & switches over to it, at which
point the clock-only output ceases to do anything useful. hence the
lockup.
perhaps a leaf from alesis' book? the mmt8 & hr16 have several clock
modes, including one that doesn't do any automatic switching & stays
instead on either "internal only" or "external only". 


I wish there was a way to distribute midi clocks & all other midi data
completely separately from each other. things like jam-mans, echo-pros
& various hardware sequencer jobbies use up midi channels
unnecessarily because they are listening for PC/CC/notes when all I
want them to do is follow a clock. the clock-only output on the p3 was
supposed to address this & let me run a maq with the p3 both as master
clock & FTS processor. but looping the maq back into the p3 causes the
aforementioned freezes.
can't really blame the p3 though- the maq is rather basic both in
hardware terms & in it's midi implementation, even the later version.

duncan.

> the clock-only output on the p3 was
> supposed to address this & let me run a maq with the p3 both as master
> clock & FTS processor. but looping the maq back into the p3 causes the
> aforementioned freezes.
> can't really blame the p3 though- the maq is rather basic both in
> hardware terms & in it's midi implementation, even the later version.

There shouldn't be any problem connecting the P3s clock output back to its
input.
The automatic switching of sync locks out the other source as soon as P3 is
started, whether manually or by incoming MIDI start.
I always have my 303 hooked up so that either P3 or 303 can be manually
started, each one sends sync to the other, and both pass it through.

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

ferrograph632 wrote:

>
>I wish there was a way to distribute midi clocks & all other midi data
>completely separately from each other. things like jam-mans, echo-pros
>& various hardware sequencer jobbies use up midi channels
>unnecessarily because they are listening for PC/CC/notes when all I
>want them to do is follow a clock. the clock-only output on the p3 was
>supposed to address this & let me run a maq with the p3 both as master
>clock & FTS processor. but looping the maq back into the p3 causes the
>aforementioned freezes.
>  
>
So you'd want to be able to send clock from the clock output but not the 
main MIDI output? You could get one of those little Anatek boxes and 
filter the clock from the outputs you want perhaps?

>can't really blame the p3 though- the maq is rather basic both in
>hardware terms & in it's midi implementation, even the later version.
>  
>
Oh yes. :)

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