Hi Obla,

I had thought of such a triggering idea myself, but I concluded that the way it would pan out would be even more complicated than the current method. There are two possibilities for triggering: MIDI notes trigger a particular pattern, interrupting that which is already playing; MIDI notes trigger a particular pattern, adding to that which is already playing. Of these, of course, the latter is more desirable, but would quickly lead to a maxing out of the channel polyphony - which would force me to cut reViSiT's 64 channels to a more reasonable 16 or so (allowing up to 4 patterns to be played simultaneously). If this was necessary, it would effectively limit reViSiT's capabilities as used in the conventional sense - i.e. with the order list.

The end decision was that I didn't want reViSiT to become like one of these Magic or eMagic DJ tools, which it ran the risk of becoming with such triggering - all songs would suddenly become based on 4 or 5 drum or bass loop patterns, and the only thing you could do with reViSiT would be Euro pop!

However, there is certainly a possibility of the first of the two options I mentioned - even with the current architecture. If you look at the Instrument List screens (F4), you'll notice that the keymap supports entire rows, rather than just pitch and samples. If a row effect was introduced (somehow extending IT's Cxx?), which caused a jump to a particular pattern, then you could still use MIDI notes to determine your pattern sequence. However, the big problem then is synchronisation - where will the tracker be at 2 minutes and 27 seconds in? With orders being created on the fly coupled with the forthcoming Variable Pattern lengths, this might engender some heavy calculations, which would interrupt playback.

I think, in any case, it'll have to wait until post v1.0, but is something I will look into.

All the best,
Chris