I've recently run into a problem where the MIDI message "reset all controllers" is forcing the Alchemy remix pad to start at pad #5.

I'm sure that Pete and Tim are aware of the messages that noatikl sends when it starts a piece. Hopefully, they will give us the option of sending these initialization messages or not (it's been mentioned in another thread). I may also contact Camel about this. If anything, the remix pad should default to pad #1.

I'll share more when I get the time. I just did not want you to think I disappeared or forgot about you...

I'm sure that Pete and Tim are aware of the messages that noatikl sends when it starts a piece. Hopefully, they will give us the option of sending these initialization messages or not (it's been mentioned in another thread).

Yes, we'll certainly do this at some stage. Many thanks for your patience - there is always too much to do.

I figured out why noatikl was "forcing" the remix pads to change to pad 5 on piece start. It's user error. There is nothing wrong with noatikl's initialization messages.

Do not use controllers 100 or 101 when automating Alchemy (or any synth for that matter). These controllers are reserved for RPN's (see http://www.midi.org/techspecs/midimessages.php#3 for details). I highly suggest only using controllers marked as undefined in the table.

noatikl sends out a pitch bend range message using controllers 100 and 101 on piece start. Following that with additional data using those same controllers confuses Alchemy. I believe that Ben at Camel Audio mentioned something about Alchemy doing weird things when sent a program change (I can confirm the behavior). It looks like certain controllers also do the same.

Long story short, don't use controllers 100 or 101 for MIDI automation (unless you really know what you're doing - see table 3a at the link I mentioned above).