v4.53rc2 - September 29 2013

Devs, will this flood of MIDI messages sent to external devices with absolutely no good reason ever be fixed? It is EXTREMELY annoying. Happens when exiting Reaper as well - it sends default CC values to all CCs and all-notes-off. This is absolutely unnecessary - both when exiting Reaper, and when switching to another app. Why would anyone want this to happen!?

Just to let devs know that MIDI in Reaper still has ways to go, even after all these efforts. After MIDI editing in piano roll, it's time to fix MIDI interfacing with external hardware and all its niggles (and you might throw in ReaInsert fixes for good measure, to keep audio people happy)... Or even more users might follow that guy. He at least tried to make it work. Three months of trying is not insignificant at any rate. Other DAWs simply work when this is concerned - why can't Reaper? I'm currently at a point where I'm starting to get more hardware synths. Reaper is simply NOT GOOD ENOUGH for that yet. It needs fixes - ASAP.

The problem is that Reaper doesn't send INITIAL values (which you've set in the project), it zeroes them out (well, centers pan and maxes CC7). This is no good and is a constant annoyance when using my Kurzweil with Reaper. Please see jnif's GIF and . This flood of CC messages is ludicruous and unnecessary! No other DAW does this as a CONSTANT FLOOD. They send the messages ONCE and that's enough. The difference is very obvious.

If it does that continuously I'll agree that's a bug. However isn't a centered pan and maximum volume the default (so, a valid initial value)?

Not if you set it differently on your hardware device. Kurzweil is very detailed in this area - for every zone in a Setup (think of zone as a MIDI channel) I can set initial values for each CC! And Reaper doesn't know anything about it, because lack of bidirectional feedback to controller is another thing that's missing. And yes, try jnif's test. It does send a flood of messages for as long as the track that sends MIDI to another track is selected. If it's not selected, it stops - however it still sends resetting messages every time you click away from the track, or change cursor position, or play/stop/pause. EVEN IF "Reset CC on play/stop" IS DISABLED IN PROPERTIES!!! Does that make any sense? It makes none.

Bad idea or not, it would make working with my Kurzweil a lot easier. I don't want Reaper to guess what CC values are set on my external hardware (these values are stored in each patch - and are different for each patch). Ideally, if there's no CCs defined at the start of the project, Reaper shouldn't send any until it hits on a particular CC value change. It should only reset CCs depending on that option in Properties->Audio->MIDI Devices, or when you run "Reset all MIDI devices" action. This is currently not working in all cases, as illustrated by jnif's GIFs I linked to above (things get reset even if that option is disabled in Prefs). To ensure that CC values are always reproducible with external hardware, one should record their initial positions right at the start of the project. THAT is what Reaper should be using then, because now it has something to chase.

I can send this data from my Kurzweil - it's all sent to the MIDI out when you select a patch.