LOL! 666!!!

This aggravates me constantly as I'm editing different parts so I find myself placing zero controllers all over the place to fix it.

Very true. What's even worse is when doing orchestral mockups with key switched articulations.

I'm having to put "dummy" switches all over the place just to get the correct sounds to play when playback is initiated at any point in the timeline other than 01:01:000

@BJ
One of the key things with keyswitches is to have separate midi tracks that represent the various switches for the sake of consistent playback as well as notation printing.  The other thing i do is add a meter change at the start of the file - set to either 1/8 or 1/4 and leave that for a bar to assign the initial keyswitches then change the meter to first assigned to the project.  

At the risk of hijacking the thread. Is anyone using Drum maps for key switch tracks. I always intend setting it up.

Having a "look back" option for controler data and key switches has been discussed in the past. I don't recall if anyone put in a feature request but it would be a nice feature to have.

You guys are geniuses!  Went back through with all you'd noted, found a few previous floating pitch bends that had not been zero'd back out.  So I guess it had floated off from there.  I put a zero pitch bend controller in after each of the offending events, and it seems to have fixed it.

What I don't understand -- prior to correcting this, when I closed the project then re-opened it, moved NOW time to mid-project and started from one of the mid-track points without passing any pitch bend, I was still getting the errant pitch.  Shouldn't it have started playing at that point without acknowledging a pitch bend prior in the midi track that it had not actually played?  Or does the audio engine look retrospectively and play as if everything prior had actually been played?

Thanks for the help!!

Have a look in Preferences-->Project--->MIDI--->Other options and uncheck "Patch/Controller Searchback Before Play Starts"

Sonar will then ignore any prior controllers, but you may end up with some strange patches playing depending on your setup and the project.

swamptooth


@BJ
One of the key things with keyswitches is to have separate midi tracks that represent the various switches for the sake of consistent playback as well as notation printing.  The other thing i do is add a meter change at the start of the file - set to either 1/8 or 1/4 and leave that for a bar to assign the initial keyswitches then change the meter to first assigned to the project.  

swamp - yep, all my keyswitch data is actually contained within a drum map which lives on the top row of the PRV. The 2nd row is for normal note data, 3rd row for velocity & 4th row for CC11 data

Glyn Barnes


At the risk of hijacking the thread. Is anyone using Drum maps for key switch tracks. I always intend setting it up.

Having a "look back" option for controler data and key switches has been discussed in the past. I don't recall if anyone put in a feature request but it would be a nice feature to have.

Yes! See my post above.

Using Drum Maps for keyswitch data and the normal PRV for note data makes it completely obvious what you're dealing with

Yeah and the cool thing about drum maps is that one big map can go to multiple synths which is awesome!

Karl -- thanks, that makes sense now.  Not understanding how things work creates a lot of problems -- that seem foolish once I have the understanding...