Major MIDI Problems

SilverBlueMedallion
First off, how do I revert back?

Secondly, why is this happening?

rlared

SilverBlueMedallion
to add one more piece of information - while one of those tracks is playing out of key - if I hilight that track and just move the pitch wheel a bit and then let it go back to the center, it then plays the correct pitch!   

When you do that, do all of the tracks play back in key or just the highlighted one?

gustabo
Edit > Preferences > Project > MIDI > Other Options > Patch/Controller Searchback Before Play Starts?

SilverBlueMedallion
 
(what happened with imgr linking, it no longer shows the picture in the thread?)
 

Anderton

SilverBlueMedallion
but now this breaks other things. Seriously, seems like Cakewalk still has a lot of MIDI issues to sort out.

You need to be specific about what "breaks." Also, what happens if you select searchback but not zero controllers? Are you clear about how continuous controllers aren't always continuous, in the sense that sending one value will cause that value to be retained until there's another value sent? This is why when you said "to add one more piece of information - while one of those tracks is playing out of key - if I hilight that track and just move the pitch wheel a bit and then let it go back to the center, it then plays the correct pitch!" it's really expected behavior...SONAR is reacting to a previous pitch bend message, and in this case, you're giving SONAR a new one that's what you wanted.
 
It seems that perhaps the problems you're experiencing may not involve SONAR, but stem from a lack of understanding about how MIDI works. If that's the case, you're looking for problems in the wrong place. Functions like zeroing controllers and searchback are common, so someone versed in MIDI would look at the status of those functions first if experiencing a project not following previous controller settings. If you can be more specific about what "breaks," perhaps we can sort this out for you.

SilverBlueMedallion

Anderton

SilverBlueMedallion
but now this breaks other things. Seriously, seems like Cakewalk still has a lot of MIDI issues to sort out.

You need to be specific about what "breaks." Also, what happens if you select searchback but not zero controllers? Are you clear about how continuous controllers aren't always continuous, in the sense that sending one value will cause that value to be retained until there's another value sent? This is why when you said "to add one more piece of information - while one of those tracks is playing out of key - if I hilight that track and just move the pitch wheel a bit and then let it go back to the center, it then plays the correct pitch!" it's really expected behavior...SONAR is reacting to a previous pitch bend message, and in this case, you're giving SONAR a new one that's what you wanted.
 
It seems that perhaps the problems you're experiencing may not involve SONAR, but stem from a lack of understanding about how MIDI works. If that's the case, you're looking for problems in the wrong place. Functions like zeroing controllers and searchback are common, so someone versed in MIDI would look at the status of those functions first if experiencing a project not following previous controller settings. If you can be more specific about what "breaks," perhaps we can sort this out for you.

Anderton,
 
How is that expected behavior?

Anderton

SilverBlueMedallion

Anderton

SilverBlueMedallion
but now this breaks other things. Seriously, seems like Cakewalk still has a lot of MIDI issues to sort out.

You need to be specific about what "breaks." Also, what happens if you select searchback but not zero controllers? Are you clear about how continuous controllers aren't always continuous, in the sense that sending one value will cause that value to be retained until there's another value sent? This is why when you said "to add one more piece of information - while one of those tracks is playing out of key - if I hilight that track and just move the pitch wheel a bit and then let it go back to the center, it then plays the correct pitch!" it's really expected behavior...SONAR is reacting to a previous pitch bend message, and in this case, you're giving SONAR a new one that's what you wanted.
 
It seems that perhaps the problems you're experiencing may not involve SONAR, but stem from a lack of understanding about how MIDI works. If that's the case, you're looking for problems in the wrong place. Functions like zeroing controllers and searchback are common, so someone versed in MIDI would look at the status of those functions first if experiencing a project not following previous controller settings. If you can be more specific about what "breaks," perhaps we can sort this out for you.

Anderton,
 
How is that expected behavior?

 
It's totally expected behavior if something has been offset by a previous message and you "just move the pitch wheel a bit and then let it go back to the center," as this gives it a new message. 
 

bvideo
To rephrase brundlefly's question that I haven't seen the answer yet:
what was the condition of the echo enable button [*)))] on all midi or instrument tracks tracks?
what was the input selection for all those tracks (e.g. your Akai)?
what was the setting in Edit -> Preferences -> MIDI -> Playback and Recording [] always echo current midi track?
 
There is a certain combination of these that could transmit wheel motions to multiple tracks. Depending on the last wheel motion transmitted, several tracks could have transmitted your performance of a wheel setting which then persists in the synths they were sent to. These settings could persist until "Zero Controllers ..." is put into effect or until a new wheel motion is performed into those tracks or until a recorded wheel event is encountered in the track.

Klaus

brundlefly
 
Also, make sure you don't have any MIDI track inputs set to All Inputs - Omni and no synths have MIDI Out enabled where not intended.

Did you check what brundlefly said above?
 
Because in combination with...:
 

SilverBlueMedallion
hello, it is an AKAI MPK 25 key.  I enabled write automation on ONE track... hit record and messed around with the pitch wheel on ONE track.  How could ALL my tracks be effected by the wheel changes I made on ONE track?
 
 

...this could be the reason why pitch wheel data is recorded on other tracks, too.