Analogue-sequencer

I've installed a tweaked version of 4.5 in both of my P3s. the tweak makes it easier to enter polyphonic patterns by limiting the range of the aux notes to match the "base" note. so if you set the note range parameters to (say) C4 & two octaves, the aux notes will be similarly constrained. in the normal version of 4.5 & every earlier build, they had been unlimited, & this made dialling in the right value a choice from 127 instead of 24. tricky.

anyway, the new build is so much easier to use, but I have discovered what I think may be a bug, & wanted to see if anyone else is using polyphonic patterns often enough to have spotted this:
having arrived at a multi-bar chord sequence I like, & while the sequencer is running, I load the same saved pattern into another track.

("func" + the part key, btw.)

this is so I can quickly duplicate the chords on another instrument. but it's not in sync with its "parent" until I stop the P3 & start it again. I don't think it's a global bar thing- it has tended to be a matter of two or three beats, not a half-bar or anything one might expect.
anyone?

d.
d.

> having arrived at a multi-bar chord sequence I like, & while 
> the sequencer is running, I load the same saved pattern into 
> another track.

> but it's not in sync with its "parent" until I 
> stop the P3 & start it again. I don't think it's a global bar 
> thing- it has tended to be a matter of two or three beats, 
> not a half-bar or anything one might expect.
> anyone?

I think that will probably be a bug for any pattern, rather than just a
pattern using aux notes.
I'll check next time I have space and time to plug a P3 in.
It won't be hard to fix. There's a flag that should be set to tell the track
to sync the pattern on the gbar loop.
IIRC !


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

>>I think that will probably be a bug for any pattern, rather than just a pattern using aux notes.<<

I can't reproduce the symptom at home, using a very similar set-up with the same s/w on the P3 & an identical motu router. so I think maybe I imagined the whole thing, being as I had a mixture of attack times on the instruments concerned.

however... if I create a simple pattern in track one (mono or poly) & then load the same pattern into tracks two, three, &c., then delete the pattern in track one, the "there's some stuff here" lights stay lit on tracks two & three. is this intentional? damn clever... 

as soon as I make a new pattern in track one, tracks two & three start playing it as well. 

if I check the contents of these tracks, I'm told "---" & can't delete it. but if I reselect "---" using the +/- buttons, I can make the "stuff there" lights go out.

it's all logical enough- I just wondered how many people had seen this stuff. 

d.

> I can't reproduce the symptom at home, using a very similar 
> set-up with the same s/w on the P3 & an identical motu 
> router. so I think maybe I imagined the whole thing, being as 
> I had a mixture of attack times on the instruments concerned.

I think you'll find imaginary bugs are Paul's department (ducks)
 
> however... if I create a simple pattern in track one (mono or 
> poly) & then load the same pattern into tracks two, three, 
> &c., then delete the pattern in track one, the "there's some 
> stuff here" lights stay lit on tracks two & three. is this 
> intentional? damn clever... 

I don't remember that being intentional, but if it seems clever, it may have
been a subconscious decision.

In v4, each track could store a pattern for each part.
8 tracks by 8 parts gave 64 possible patterns for a bank.
Those could be 'ghosted' to any other location.

In v4.5, the patterns don't belong to a specific part/track location, but
there are still 64 of them.
The data structures are actually indentical, all that changed is the way
assignment and deletion is handled.
It makes them appear as a pool of freely assignable patterns, numbered 1 to
64, rather than the confusing part/track location and ghosting of v4.

When you are deleting a pattern that is assigned elsewhere, it must not be
checking those other tracks to de-assign the deleted pattern.
So they still appear to point to a pattern slot, but that slot is empty, so
nothing plays.
When you create the new pattern, it is being created in that empty slot, so
the tracks start playing it.
It would probably be more sensible to de-assign them, but maybe it does have
its uses not to.
 
Cheers,
Colin