Analogue-sequencer

> 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