Use NRPNs (For Accuracy)?

So I read somewhere that using NRPN's can yield much higher resolution of controller data.  This sound to me as pretty crucial if you want to control a softsynth's filter cutoff without it sounding to "steppy". I also noticed that using regular CC value range of 0 to 128 doesn't allow for fine tuning most parameters in software plugins.
 
I understand NRPN's are "bloated" and utilize more CPU, but I plan on freezing my synth tracks once recorded.   Does it utilize more CPU upon playback and/or just when moving the knobs on my controller?

But am I even on track with this whole NRPN thing to begin with?  I want to make sure my filter sweeps and other synth effects are as smooth as possible.

Am I correct in thinking I would need to use NRPN's from my controller instead of MIDI CC?
 
Thank You!
 

thanks!  what about my main question about it being more accurate?  Would that be true for softsynth parameters?  Will I get a smoother filter cutoff if I use NRPNs?

not really sure I understand what you just wrote.  
 
I just want to make sure I have the most smooth control of the parameters as possible.   As far as VST2's and VST3's are concerned, would I have a better chance at a smoother control with NRPN?
 
Thank You!

Sanderxpander
He is saying that the synth still has to support setting higher resolution values via NRPN. I haven't done a wide comparison but I would estimate that most don't. Most rely on "regular" midi for control input.
 
BUT, many synths (especially the ones from the last 5/10 years) have smoothing algorithms that prevent filter stepping, meaning internally they still use high resolution values and when the control input goes from, say, 63 to 64, they will calculate a few steps in between for a smooth glide rather than a sudden step. I'm sure that's oversimplifying it but I'm not a programmer. In any case, unless you're really zooming in on a sound and modulating a narrow range of filter cutoff values, it's usually not a problem.
 
Are you having specific issues with a synth and filter stepping? Be careful that you're not mistaking overtone resonance for filter stepping, even analog synths do that, it's simply a part of the way oscillators and filters interact.

Very helpful, thank you very much.  Actually, I havent found any issue with MIDI CC, but wanting to try out NRPN but I'm having issues with my Novation unit at the moment.
 
Thank you for your help!  Interpolated too!

There are 4 types of MIDI messages which have 14bit data precision: PithBend, CC14, (N)RPN and SysEx. PithBend is the only one which utilize just one standard 3 byte message. CC14 use 2 CC messages, RPN use 4 CC messages, SysEx is an arbitrary length message.
 
Hardware MIDI standard is extremely slow, sending one message takes ~1ms. That is why common practice is using PutchBend from hi resolution faders (f.e. on Mackie surfaces).
Inside modern computes there is no measurable difference in CPU consumption between such small data types (each message is stored/transfer within DAW in much bigger structures).
 
What can produce problems is the number of changes, not the resolution of each change. Sonar support crazy rates for such changes, but not only that is either ignored or crash synth, that can slow Sonar down to unusable level quickly. Such rates are not possible to achieve recording physical knobs, slow hardware within controllers does not send it so often, but when drawing by mouse it is good idea to use reasonable quantization.
 
Which maximum resolution is supported depends from particular parameter of particular synth. The same for supported MIDI messages. PitchBend, even when supported, is a bad choice in this case since it has special processing withing Sonar, leaving CC14 or (N)RPN for the purpose. If there is no documentation, "MIDI Learn" within plugin can quickly clarify supported message type. With maximum resolution that is more tricky, if there is some indication for parameter current value, it is possible to check weather tiny changes produce any effect on them.
 
Another way to increase the "resolution" while using standard CC is "assign matrix" within synth, in case it allows parameter subranges. F.e. fo frequency, if subrange is just 100Hz-200Hz, CC value have under 1 Hz resolution.
 
Common universal way to archive max supported by Synth resolution are already mentioned VST2/3 Automation parameters. They are 32 bit floats (for any parameter).
 
Another question is the possibility to enter these values using hardware controllers (entering by mouse is straightforward for all mentioned cases). I do not know any controller which produce hi resolution CC or (N)RPNs.
I have already mentioned hi resolution faders with PB, they are up to 10bit. So the solution is to use encoders and translate +- changes to coarse or fine changes. May be some Synths support Inc/Dec (N)RPNs, but universal approach is thru Automations. Organizing that practically in Sonar from my knowledge is only possible with AZ Controller.
 
PS. You are in my ban list, so probably you ignore all that. The information is for other users looking for extended answer on that (not unusual) question.
 
 

bitflipper
For most synth parameters, 127 discrete levels is more than sufficient. You can test this yourself within the PRV: create a MIDI track with one sustained note, and then add a CC and assign it to anything you like. Set the initial CC value to, say, 66. Manually edit the CC to change to 67 after some interval. Can you hear any change at all without watching the PRV for visual cues? Sometimes you can, sometimes you can't. Depends on the synth more than anything.

Where I find the limited number of values apparent is between 0 and 1 where you can definitely hear a difference as the control becomes an on/off switch.