brundlefly

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.
 

Yes, this is almost certainly the problem. As mentioned earlier, you write automation on playback. If you record, any armed track will record wheel events as MIDI data instead of writing an automation envelope on the one write-enabled track.

nope. my other tracks were NOT armed.  Only the one doing pitch wheel changes on.   
 
 and why would " All Inputs - Omni" be the default?
 
seems kinda silly to have a pitch wheel change on one track effect others.

I don't think you've clarified whether you actual ever succeed in writing an automation envelope or whether you recorded Wheel events, and whether those wheel events were recorded on more than one track.
 
I'm fairly confident this is a configuration/procedural issue, but without being able to lay hands on the project, it's a little difficult to know what exactly went wrong.
 
If you don't set a specific MIDI input/channel SONAR defaults to All Inputs - Omni as the lesser of two weevils - recording nothing or recording everything. In most cases, recording everything will not be a problem, but recording nothing will always be a problem.

OK here is EXACTLY what I did...

1.  I have multiple simple instrument tracks with notes recorded on to them.  No wheel movements on any of them
2.  I decided i wanted a wheel movement on one track so I simply clicked the "W" for "write automation" and armed the track.  Then I simply moved the wheel while it was recording.  I see the wheel movement drawing ONLY in the one track I did the wheel movements on.
 
How that wheel movement on track 1 is effecting other tracks is beyond me.
 
According to your last statement, this sounds like default behavior?  Wheel movements will be captured on ALL tracks because of the MIDI-OMNI (all)?  How come the events dont SHOW these wheel movements on those tracks?

Sonar should be smart enough to keep the wheel movements contained to the track I recorded it on.

Adding a little pitch bend shouldn't be that hard.

SilverBlueMedallion
OK here is EXACTLY what I did...

1.  I have multiple simple instrument tracks with notes recorded on to them.  No wheel movements on any of them
2.  I decided i wanted a wheel movement on one track so I simply clicked the "W" for "write automation" and armed the track.  Then I simply moved the wheel while it was recording.  I see the wheel movement drawing ONLY in the one track I did the wheel movements on.
 
How that wheel movement on track 1 is effecting other tracks is beyond me.
 
According to your last statement, this sounds like default behavior?  Wheel movements will be captured on ALL tracks because of the MIDI-OMNI (all)?  How come the events dont SHOW these wheel movements on those tracks?

Sonar should be smart enough to keep the wheel movements contained to the track I recorded it on.

Adding a little pitch bend shouldn't be that hard.

If I have never seen this problem because I don't do it that way.
Meaning, I do not engage 'W' to record pitch-bend/modulation wheel movements.
In recording mode I have 'Sound-on-Sound' selected. Record enable that track. Start the engine, the wheel events are thus recorded, same as just adding notes by playing the keyboard.
 
Not saying that there might be a problem with Sonar or maybe just within this project template.

Personally I record pitch bend, modulation and any other CCs into a track as MIDI data, not as automation.

All tracks that have received a pitch-bend instruction will have passed it on to their linked synth. The synth will then adjust its pitch by the amount sent by the instruction. They will not reset their pitch to "standard" unless told to do so.

There won't be anything in the events list because although the synth has been sent pitch bend data the data has not been recorded into the track. Just like when you play a software synth without recording the MIDI the synth responds to your playing and retains whatever state it was in when you stopped playing until you tell it otherwise.

The simplest answer to all of this is to use Sonar's ability to recognise different MIDI ports if you have more than one controller so a single controller doesn't control everything amd synths only see what a particular controler is sending. And/or to use MIDI channels to set each synth to a different channel and then send data from the controller on the channel the track you want to respond is set to.

And no, this isn't a work-round. It's just how MIDI works. No different to using MIDI controlled hardware really. And at least Sonar can keep the MIDI traffic from different sources separate, some (e.g. Logic) combine all incoming MIDI into a single stream leaving the 16 MIDI channels as the only way to control where it ends up and what it affects.

The "MIDI omni" default on tracks is a nuisance at times, and catches people out once they get to using a few synths at a time. Though I suppose it prevents lots of support calls from beginners who don't understand what MIDI ports and channels are so find routing things correctly to be a problem or they load up a synth and it "won't work".

Disclaimer: the following is just thinking out loud:
 
The wrinkle seems to be the [W] along with record enable & recording. If there were a bug, I'd guess it to be related to this wrinkle.
 
And it seems clear that the pitch bend events or envelopes were not recorded to other tracks, but at some point got echoed to the synths on those tracks, leaving behind some non-zero final values in the synths which could then be cleared by various means of sending pitch bend of '0'. (This is assuming those other tracks did not vary in pitch bend amount during any playback after the offending incident but operated as if they had been left with a single pitch bend offset.) If that's the case, did those synths not sound like they had shifted pitch during the possibly offending recording phase?  If they did sound wrong then, it would be evidence of events weirdly leaking over to other tracks during [W] with recording. If they did not sound wrong then, the events must have been sent when the transport and all sound output was stopped, which would be even weirder.
 
Another weird thing is that those other tracks didn't receive a final '0' which would have been the most likely final event, given that the pitch wheel was most probably returned to 0 before [W] was cleared and recording was stopped.

tlw
Personally I record pitch bend, modulation and any other CCs into a track as MIDI data, not as automation.

All tracks that have received a pitch-bend instruction will have passed it on to their linked synth. The synth will then adjust its pitch by the amount sent by the instruction. They will not reset their pitch to "standard" unless told to do so.

There won't be anything in the events list because although the synth has been sent pitch bend data the data has not been recorded into the track. Just like when you play a software synth without recording the MIDI the synth responds to your playing and retains whatever state it was in when you stopped playing until you tell it otherwise.

The simplest answer to all of this is to use Sonar's ability to recognise different MIDI ports if you have more than one controller so a single controller doesn't control everything amd synths only see what a particular controler is sending. And/or to use MIDI channels to set each synth to a different channel and then send data from the controller on the channel the track you want to respond is set to.

And no, this isn't a work-round. It's just how MIDI works. No different to using MIDI controlled hardware really. And at least Sonar can keep the MIDI traffic from different sources separate, some (e.g. Logic) combine all incoming MIDI into a single stream leaving the 16 MIDI channels as the only way to control where it ends up and what it affects.

The "MIDI omni" default on tracks is a nuisance at times, and catches people out once they get to using a few synths at a time. Though I suppose it prevents lots of support calls from beginners who don't understand what MIDI ports and channels are so find routing things correctly to be a problem or they load up a synth and it "won't work".

 
 
what if i have more than 16 synth tracks?

bvideo
Disclaimer: the following is just thinking out loud:
 
The wrinkle seems to be the [W] along with record enable & recording. If there were a bug, I'd guess it to be related to this wrinkle.
 
And it seems clear that the pitch bend events or envelopes were not recorded to other tracks, but at some point got echoed to the synths on those tracks, leaving behind some non-zero final values in the synths which could then be cleared by various means of sending pitch bend of '0'. (This is assuming those other tracks did not vary in pitch bend amount during any playback after the offending incident but operated as if they had been left with a single pitch bend offset.) If that's the case, did those synths not sound like they had shifted pitch during the possibly offending recording phase?  If they did sound wrong then, it would be evidence of events weirdly leaking over to other tracks during [W] with recording. If they did not sound wrong then, the events must have been sent when the transport and all sound output was stopped, which would be even weirder.
 
Another weird thing is that those other tracks didn't receive a final '0' which would have been the most likely final event, given that the pitch wheel was most probably returned to 0 before [W] was cleared and recording was stopped.

THIS sounds like what is happening here....  

You are running the most recent version of SONAR, yes? There have been some MIDI fixes of late.

Anderton
You are running the most recent version of SONAR, yes? There have been some MIDI fixes of late.

Hi Anderton,
 
yes I am.  So I was able to resolve my issue this morning by changing the channel of the track with the wheel movements to Channel 2.  
 
I never have to change the channel, but for some reason this time i do.  Now the other synths aren't effected.
 
Strange.  Thank you everyone for trying to help me out!