Analogue-sequencer

> No problem Chiel - I'll put it back in. I hadn't really had any 
> feedback from people using it - more complaints that it was hard to 
> predict the timing of repeats.

hi Colin,

thnx a lot for putting it back in in v3.973..it's different though. 
in some ways cooler than it was, in others less so. 
the cool bit is that the number of repeats that are now possible is 
much higher which gets some pretty freaky effects. the less cool side 
is that it works way differently to the way it used to. the way it 
used to work was that if i just turned the rep*N value up to max, i 
could vary the number of repeats with the note-length. so if the 
length value was 12 i'd get no repeats, if the length was 6 the 
number of evenly spaced repeats would be 2, if the length was 3 i'd 
get 4 evenly spaced repeats, a length of 4 would make it a triplet 
repeat, 2 made 6 repeats etc., and i could get nice sort of up-beat 
things before the following note with length values above 6. the new 
version still interacts with the length parameter, but the smallest 
number of repeats i can get, with note-length set to 12 (max) appears 
to be something like 4 or 5, in a pattern with tbase 4. the extended 
value is cool, being able to get more than 8 repeats, is cool, but 
i'd really like to see the old way of interacting with the length 
value back..
btw i had some weird stuff going on during sysex dumps back to the 
P3's after doing the bootloader update; during the upload of the 
latest FW after the bootloader update the display kept flickering BAD 
DATA through the usual 'send more data' routine. i did the whole 
thing twice on the first machine with identical results, then once on 
the other, again with the same result, so i figured it'd be ok. i got 
the same kind of flickering BAD BLOCK messages through the sysx-
memory dumps back to the P3's on both occasions too. but it all seems 
to be working fine so i guess it's allright.

grtz Chiel