Problem controller midi in REAPER.

[yimianders]

Hi all,


I have a Problem with a midi controller in reaper.
The VSTi plugin works fine. Send hardware synthesizer presets and all controls work well, But The problem is when i want to record on track That. When I press the record button, Reaper VSTi plugin sends all controls with zero quantity. Sound Disappears, Because there is a volume control included.

That is, Reaper sends a message to all the controls on my MIDI Controller with zero quantity after pressing the record button or pressing the stop button or playback.

Can anyone help me with this? Or, is this misconfigured reaper? or, Is it problem of my SM project ?

Very thanks
Best regards

[trogluddite]

Hi there,
There are a couple o settings in Reaper that may be worth tweaking...
First call up the preferences panel (CTRL P) - then scroll down the list on the left and choose 'MIDI Devices' (listed under the 'Audio' category for some strange reason!).
At the bottom of the main panel, you will see tick boxes for "On stop/play..." followed by a few reset options. Clearing the 'Reset CC' should stop Reaper from sending those annoying messages (I think they are enabled by default).
Also look closely at the MIDI Input and Output panels above this to make sure that you have the right things selected; especially if you are using your plugin to edit external hardware. Particularly watch out for any inputs set to "Control" or "Enabled+Control" - this allows external MIDI CC to 'drive' the Reaper mix faders and pan pots, so can sometimes be a source of "rogue" mix changes. Likewise any output set to "Send Clock/SPP" will be sending extra messages that you probably don't want. Just right click on a line in the chart to change the setting.

Also, take a look in the toolkit I posted recently HERE - there is a MIDI Analyser display in there. Normally it is for use when testing schematics, so it doesn't show on the plugin front panel - but you can make it show up on your plugin's GUI by uncrossing the "Toggle Show in Parent" icon (the little 'eye' symbol on the bar that appears beneath a selected module). You can then pop it into your plugin temporarily so you can get a handle on what messages Reaper is sending.
Alternatively ,you could try my MagiMIDI tool - that too has MIDI displays, and can also filter and transform MIDI messages; but is probably a bit over the top for what you need to do, and has to be loaded as a separate plugin.
(BTW, those two gizmo's I just shamelessly plugged are total freebies - so if it helps with your design, feel free to pull them to bits and take anything that looks useful).

Hope that gets you up and running. If not, take a peek with one of those analysers and let us know what you see there; that may help give us some clues what the problem is.

[yimianders]

Hi there,
There are a couple o settings in Reaper that may be worth tweaking...
First call up the preferences panel (CTRL P) - then scroll down the list on the left and choose 'MIDI Devices' (listed under the 'Audio' category for some strange reason!).
At the bottom of the main panel, you will see tick boxes for "On stop/play..." followed by a few reset options. Clearing the 'Reset CC' should stop Reaper from sending those annoying messages (I think they are enabled by default).
Also look closely at the MIDI Input and Output panels above this to make sure that you have the right things selected; especially if you are using your plugin to edit external hardware. Particularly watch out for any inputs set to "Control" or "Enabled+Control" - this allows external MIDI CC to 'drive' the Reaper mix faders and pan pots, so can sometimes be a source of "rogue" mix changes. Likewise any output set to "Send Clock/SPP" will be sending extra messages that you probably don't want. Just right click on a line in the chart to change the setting.

Also, take a look in the toolkit I posted recently HERE - there is a MIDI Analyser display in there. Normally it is for use when testing schematics, so it doesn't show on the plugin front panel - but you can make it show up on your plugin's GUI by uncrossing the "Toggle Show in Parent" icon (the little 'eye' symbol on the bar that appears beneath a selected module). You can then pop it into your plugin temporarily so you can get a handle on what messages Reaper is sending.
Alternatively ,you could try my MagiMIDI tool - that too has MIDI displays, and can also filter and transform MIDI messages; but is probably a bit over the top for what you need to do, and has to be loaded as a separate plugin.
(BTW, those two gizmo's I just shamelessly plugged are total freebies - so if it helps with your design, feel free to pull them to bits and take anything that looks useful).

Hope that gets you up and running. If not, take a peek with one of those analysers and let us know what you see there; that may help give us some clues what the problem is.

Hi Trogludite,

I have solved the problem thanks to you.

The problem was in the box CCRESET.
Your explanation was very good, as always,

Thank you very much,

Best Regards

[trogluddite]

You're welcome

BTW) Just to let you know - there may be a side effect of unticking the "CC Reset box".
On an empty track, the reset value is probably zero - but if you have MIDI recorded it can be more useful...

Normally, recorded MIDI CC messages are played back as you would expect - each message is sent as the transport 'cursor' passes over it. But they are still individual events, not a continuous 'line' like an audio fade might be.
If you move the transport to a different place in the song, and press play, controllers can have the 'wrong' value for that point in the song - whatever value was last sent won't be updated until the cursor reaches the next MIDI message after you press play; which might not be for several bars.
The "Reset CC" function gets around this - it scans back through the song whenever you start playback, and finds the most appropriate value to send out for that point in the song - so that you hear exactly what you recorded as soon as you hit play.
It's not a major headache once you know what's happening - but I though I'd best let you know as I remember what confusion it caused me for ages - if you use lots of CC data, turning "Reset CC" off can make it seem like the track never plays back the same way twice!

[yimianders]

You're welcome

BTW) Just to let you know - there may be a side effect of unticking the "CC Reset box".
On an empty track, the reset value is probably zero - but if you have MIDI recorded it can be more useful...

Normally, recorded MIDI CC messages are played back as you would expect - each message is sent as the transport 'cursor' passes over it. But they are still individual events, not a continuous 'line' like an audio fade might be.
If you move the transport to a different place in the song, and press play, controllers can have the 'wrong' value for that point in the song - whatever value was last sent won't be updated until the cursor reaches the next MIDI message after you press play; which might not be for several bars.
The "Reset CC" function gets around this - it scans back through the song whenever you start playback, and finds the most appropriate value to send out for that point in the song - so that you hear exactly what you recorded as soon as you hit play.
It's not a major headache once you know what's happening - but I though I'd best let you know as I remember what confusion it caused me for ages - if you use lots of CC data, turning "Reset CC" off can make it seem like the track never plays back the same way twice!

Thank you very much again.

It's pretty much how it works with cubase. I will consider.