Analogue-sequencer

> i've just noticed something about the playlist-edit mode and part 
> selection: in play mode, say part# 9 is playing and global bar is set 
> to 32. if i hit the key for another part, this key's LED lights up 
> orange, indicating the part that will be switched to when the end of 
> the global bar is reached, as usual. but if i then enter playlist-
> edit by hitting FUNC+(1-8) before the end of the global bar the 
> switch to the next part is suspended until the end of the global bar 
> is reached after i leave playlist-edit...this doesn't happen when i 
> do the same, but enter pattern-edit mode instead of playlist-edit. 

That's by design...

> although it offers some nice possibilities for live use it struck me 
> as kinda weird, but when i think about it now it's probably because 
> memory-wise the playlists are linked to the parts, whereas the 
> patterns aren't...

Sort of. I always thought it was important to be able to edit a pattern
that wasn't active so you could set up a pattern in the background
before making it play. There are a couple of pointers used by the
pattern edit code to select which pattern in memory you are editing.
For playlist edit, the code just uses the current part and track
numbers.
When you enter playlist edit, a part_hold flag is set to prevent the
part changing. This was to prevent the playlist being edited switching
to another one.
IIRC the aux event for select part doesn't check the part_hold flag, so
there could be strangeness if a new part is selected by a pattern while
you're in playlist edit - I'll need to check that out.

> it also gave me the idea that i'd like to be able to edit playlists 
> for other parts than the one playing, and that i'd also like to be 
> able to switch to playlists for other tracks directly from playlist-
> edit...probably not really in the realm of the possible though, is it?

It is entirely possible - I'd just need to set up a separate pointer to
capture what the current part was at the time you enter playlist edit.
The reason I didn't do this is because I thought it would probably be
hellishly confusing.
Maybe not - what does anyone else thing ?

> o and btw i've got the problem with the tempo setting sorted. when 
> trying to set the BTempo the setting kept jumping back to "off" after 
> i'd turned the pot to the value i want. turns out you need to set the 
> value using the DATA-pot, not the TEMPO-pot. it's kind of confusing, 
> as the display reads "Init tempo = xxx" when you're setting the 
> BTempo and just "Tempo = xxx" when turning the TEMPO-pot, with the 
> word "tempo" in the exact same spot in both readouts. only difference 
> is the capital T. my bad...i'm blaming typically dutch "agricultural" 
> produce. :-)

I blame not R'ing The FM ;-)
I appreciate it may seem a little confusing, but imagine if you had
selected the new initial tempo and hit enter - the tempo woudl
immediately jump to the new position of the knob. I used the data knob
so that the tempo knob could remain dedicated to setting the current
tempo only.

Cheers,
Colin f