So normally when I'm in the piano roll view, if I select MIDI notes and type in a velocity in the Event Inspector (upper right in screenshot below), that velocity value propagates to the selected notes. For example, here I should be able to set the velocity of all the selected notes to "54."
 


For some reason, Sonar's Event-Inspector Velocity-Value is not propagating to the selected piano-roll notes when I change it anymore. Is Event Inspector propagation to selected notes a setting? Did I accidentally set something the wrong way? This is quite frustrating. 

( This is X2a build 351 on Win 7 64 by the way )

By any chance, is the MIDI clip locked? (Do you see a blue or white padlock icon on the clip?)

Yes, it sounds like the clip may be locked. Right-click the clip and choose Clip Lock from the menu to see if the data is locked.
 
And for those who don't know about the Event Inspector, check out this free video...
Cakewalk SONAR: Event Inspector Editing - http://www.garrigus.com/ (see video link)
 
Scott

--
Scott R. Garrigus - http://garrigus.com - SONAR X2 Power! - http://garrigus.com/?SonarX2Power
* Author of the Cakewalk Sonar and Sony Sound Forge Power book series: http://garrigus.com/?PowerBooks
* Author of the Cakewalk Sonar ProAudioTutor video tutorial series: http://garrigus.com/?ProAudioTutor
* Publisher of the DigiFreq free music technology newsletter: http://digifreq.com/?DigiFreq
* Publisher of the NewTechReview free consumer technology newsletter: http://newtechreview.com/?NewTechReview

Thanks for the replies! 
 
Nope, neither the data nor the position on the clip were locked (I lock clips pretty frequently). However, restarting Sonar and re-loading the project seemed to de-glitch it. 
 
I will try to pay attention to see if the phenomenon is reproducible. I may have found a bug. 

If I recall correctly, there's something of a bug in that if any note's velocity (or maybe just the first one) is already equal to the target value, none of them get changed.

brundlefly
If I recall correctly, there's something of a bug in that if any note's velocity (or maybe just the first one) is already equal to the target value, none of them get changed.

THAT would explain my exact experience. I was taking the sound of the sample at X velocity and selecting it with all other notes to try to set them to that same velocity. 

That issue has been there since a very early version of Sonar IIRC. Come to think of it, I've never reported it via Problem Reporter. I just got used to it but it's a bit inconvenient.