NRPNs in softsynths

NRPN is transfered with 4 MIDI CC messages and the speed of MIDI is limited.
What is wrong with simple CC and/or automations?

Part of CCs (as RPNs) have some proposed meaning (see tables at www.midi.org). Some equipment/synth follow that proposal. Some set default mapping to proposed or fixed with some (N)RPNs. Many allow "MIDI Learn" for parameters, in that case (N)RPNs can be unsupported (as ambiguous).
 
So particular parameter in particular plug-in can be controlled:
1) by automations. That is special not MIDI (at least not directly) related way to control VST parameters. No MIDI track pointing to that plug-in (in case that is Audio FX) required for that.
2) by MIDI. MIDI track is required and there are 2 variations:
2.a) MIDI signal (CC, RPN, NRPN, etc.) by which that parameter is controlled is predefined
2.b) MIDI signal can be learned within plug-in. The subset of MIDI messages which plug-in understand is plug-in specific. So some plug-ins can understand NRPNs, other not.
 
From the user perspective, (1) and (2) can be controlled "with mouse" or with MIDI controller. But routes from the MIDI controller to parameter are different:
1) for automations, Sonar has 3 approaches:
1.I) "Remote control..." (f.e. in the Synth rack)
2.II) Control Surface "ACT Dynamic mapping" (so call "ACT Learn")
3.III) Control Surface direct automation parameters steering (f.e. used by MackieControl)
2) for MIDI way the host is only involved as a MIDI provider, it has no influence what delivered to the plug-in MIDI message will do (play note, switch it off, control attack, etc.)
 
All methods have sufficient for any purpose time resolution. But it is up to the plug-in to support fast parameter changes. Some are not expecting more then one change for one parameter inside one audio buffer frame and can produce very strange results. But one buffer is usually no longer then 3-5ms so that is rarely a limitation.
Note that transferring one NRPN throw standard MIDI cable takes ~4ms. If that "worked fine", other methods should be fine to.

AAAHHHH! I just want to write music! I think that to save my simple artist's brain I will just stick with my idea of using a set of notes that are sent to an element or another example of the synth, then use the synth UI to control whatever. The whole plan seems to be to make it "simple" and dumb it down and control me and I can work with that for now, until I actually get some mucus written.
 
Otherwise I have to MIDI learn and all that. I have loaded heaps of synths and they just do not have a full CC implementation. When there is a standard set of CC#, why can't the synths just USE them?!

ARRRGHQ And then of course if I want to try a different version of the instrument (a new guitar) I lose all my settings and have to start again. The expression should be in the music, not the instrument. Read any score. The composer and the player make the expression, by manipulating the instrument note by note.
 

The MIDI CC spec is here. Keep in mind plug-ins may not follow the spec, refer to the plug-in documentation. How CC data is bound to features in the the plug-in depend on the developer. To create a CC for a value not listed in the "MIDI Envelope/Event Type" drop downs ln SONAR, enter the number in the Value field when type is set to Control.

The MIDI implementation often is not detailed in software documentation the way it was in hardware because the approaches vary. Some plug-ins are GM compliant. Some plug-ins use MIDI learn to bind CC to functions. Some use set up screens often referred to as a modulation matrix. Some don't mess with CC at all leaving it up the the DAW and plug-in automation. Plug-in automation in DAWs may be controlled by MIDI in one way or another. Some use a combination of methods.

According to page 116 of the user guide for Rapture Pro:

The following controllers are hard-wired:
• CC7 = Volume
• CC11 = Expression
• CC64 = Sustain (can be enabled/disabled per-Element using display control)
• CC66 = Sostenuto (can be enabled/disabled per-Element using display control)
• CC73 = Global Amplitude Attack
• CC72 = Global Amplitude Release

promidi
According to page 116 of the user guide for Rapture Pro:

The following controllers are hard-wired:
• CC7 = Volume
• CC11 = Expression
• CC64 = Sustain (can be enabled/disabled per-Element using display control)
• CC66 = Sostenuto (can be enabled/disabled per-Element using display control)
• CC73 = Global Amplitude Attack
• CC72 = Global Amplitude Release

OK. Thanks. Interestingly I can override CC#73 in Dim Pro. I have always assumed their architectures were pretty much the same.