First time to post.  Is there a way to disable pitch and bend events from a MIDI keyboard interface (like Novation Impulse 61) from warping the sound in MIDI tracks created in Sonar?  I have Sonar Producer 8.0.  There seems to be inadvertent noise on the USB link or maybe in the Impulse 61 pitch and bend wheels themselves which creeps into Sonar MIDI tracks as pitch or bend events, yet are not recorded into the tracks since I cannot see them in the Event List.  I can hear the sour notes during playback.  Is there a simple fix like adding a MIDI event command at the beginning of all Sonar MIDI tracts which will disable these effect?  Is there a global fix?  Any outline of steps necessary would be helpful.
 
Currently I use the VS700 as a control surface with VR700 as analog interface where all sample rates (VR700, Sonar *.ini and Sonar project files are equally set to 44,100 Hz).  The only way to disable the warbling, out-of-tune sound is to delete the Impulse 61 MIDI interface from Sonar altogether, which is how I know the MIDI interface is the culprit.
Thanks, --c

Go to Preferences then, under the MIDI options, go to the Recording and Playback menu, you will see the many options under Record and there, you will find the Pitch option you are looking for, uncheck the box and save.
 
Welcome to the forums. :)

Sh03e - Thanks.  Unchecking the Pitch box in Sonar seems to defeat inadvertent tuning in the playback!
 
... however, the pitch wheel on my Impulse 61 still controls detuning of whatever Sonar track has focus.  Impulse modulation wheel has no effect (which is good for now).  Maybe my Impulse mapping to Sonar is incorrect? 
 
Have noticed that a selected (or in focus) Sonar track maps MIDI kbd to whatever instrument patch that MIDI track points to even though I set their Inputs to None; i.e.,  Track 1 Input=None, Output to TPs.  Track 2 Input=None, Output to [effectively] Violin.  Track 3 Input=None [but says Omni?], Output = [effectively] cello, etc.  Depending which track has focus, its respective instrument patch is played with MIDI kbd strokes.  Also each track is set up as a unique instrument channel 1,2,3, ...
 
I'd like to say this post was answered to help other users who might have surely run into this issue, but until I know exactly what Novation's Automap software is doing, I cannot make a better report.

   I have a Novation Launchkey that does the exact same thing. My solution was to take it into the dinosaur exhibit in my garage and trade it out for my old Roland D-5. No knobs, no sliders and the mod "wheel" is practically useless. But it doesn't send erroneous controller data. If there is a better solution, I would love to have my knobs back.
 
   If I understand what I've read in other threads, selecting "none" as the input for a midi track is essentially All Ports Omni. If you want the track to actually have no input, you have to select an unused port/channel.

pacofat unfortunately i don't have the Impulse versión, i have a Launchkey 61 with his respective mapping through Cakewalk Generic Surface and from time to time it sends spurious pitch bend midi data, but long ago i've modified myself the Pitch Bend Wheel so now in my controller is more firm and tight, so it less frequent that behavior AFAIK in the forums from other sites, sometimes the AutoMap is a mess with the configuration and mapping, maybe you need to check extensively the AutoMap software or create a new template in case the previous version get corrupted.
 
Cheers.

Have discovered a problem when unchecking the pitch wheel box (Options>Global>MIDI>):  it deactivates my VS700C console's jog/shuttle wheel which I need for most any composition, recording and mixing sessions.  Assigning MIDI track channel inputs to unused ports/channels seems to help, though, FYI.  Thanks all!

As confirmed in another thread (about Mackie Control), it looks like these MIDI options affect not only track inputs but also Control Surfaces input. That is a bug...
 
Another solution can be Event filter as MIDI FX. That will not prevent the information recording, so the effect has to be applied on MIDI clips in "Processing mode" second time. But that should stop any influence from these events on synth, in play and in live mode.

azslow3
As confirmed in another thread (about Mackie Control), it looks like these MIDI options affect not only track inputs but also Control Surfaces input. That is a bug...

Also confirmed by the fact the Faderport will not work with aftertouch recording disabled in the same midi preferences.