Automation lane midi not working on render/bounce/freeze

I have an issue whereby if I use automation lanes for midi info (CC1, CC11, etc), everything works as expected within Sonar on playback, etc but when rendering, bouncing or freezing, the midi info in the automation lane is ignored. I'm using "real time" for render/bounce/freeze to eliminate any issue with the program not being able to keep up.
 
I've done this with both Hollywood Strings and Omnisphere but I'll reference HS for this purpose. Starting with an empty project, I create a new instance of Play and load up any articulation (say one of the Sustain violins). The audio and midi tracks are automatically created during that process. I record a series of notes. I create two automation lanes, one for CC1, another for CC11. I make something like a sine wave envelope in both, anything to generate CC1 and CC11 midi data. On playback I hear what I expect... CC1 controlling vibrato and CC11 controlling expression.

When I render, bounce, or freeze the track, Sonar ignores the automation lanes and the audio file is rendered, bounced, frozen without any of the results from the midi data in the automation lanes (no change in vibrato though CC1 and no change in expression in CC11).
 
I'm on the latest version of Sonar X2. 64 bit Win7 with the latest updates. My soundcard is an Audiophile 2496 set to appox 11ms buffer (it could be lower but it's liberally set to avoid any pops and hiccups and such) with the latest driver updates. Both HS and Omnisphere have the latest updates. Since the problem happened with both of those programs, I have to assume it's a Sonar problem. I just haven't tried it with a third program, I just used those as examples. 

So... does this happen to anyone else?

There are several check boxes in the Bounce To Track(s) function that deal with including/excluding automation.
 
I have not experienced your issues myself, and will try to do some research on your behalf in prior threads, but perhaps as posted above you can review the option check boxes to see what you have checked or not.
 
Bob Bone
 

Are these simple instrument tracks?
 
Bob Bone
 
 

Thanks very much for your reply and links. The first link is more or less my issue although my issue extends to creating an audio file through any process (freezing, bouncing, export). I have all the "automation" checkboxes checked, etc. 
 
I was wondering if anyone would mind trying this themselves just to see if it's reproducable outside of me. I've tried everything I can think of, have done it with multiple virtual instruments, etc. It just seems that there's a (huge) bug where Sonar ignores automation lane midi data when rending an audio file through bouncing, freezing or exporting.

Good to know, thanks for posting.    I usually do add CC's directly in the PRV anyway, but now I know that I probably shouldn't try it at the track level.   

Yes exactly. Apparently only happens during real-time or slow bounce. Cakewalk tech support said that fast bounce works as expected. I always use slow bounce only because I don't want any streaming-intensive instruments dropping out (like any of the East/West orchestral stuff).

The tech support email said that it's been "bugged up" so I'm assuming that means that it's submitted as a reproducible bug and will be addressed as part of an update (soon I hope!).

Guthrie Lowe
Did this ever get debugged in X2? Im running into the exact same situation....no dynamic control over PLAY libraries when exporting audio, though it's there in playback. I also use slow bounce because there'a a ton of midi info to process.   Exports the dynamic automation in Fast Bounce but then its a super glitchy render.

No, MIDI automation will not render on real-time bounce in X2; this wasn't fixed until sometime in X3 IIRC. You'll have to figure out how to eliminate whatever the problem is with Fast bounce. I suggest you start a new thread so that you don't get all kinds of irrelevant responses to the old posts in this one, and explain exactly what "super glitchy" means, which synths are affected, and what parameters you're automating.
 
In general, it's pretty unusual that real-time/online rendering works better than fast/offline.
 
 
 
 

Not sure about X3 (I think it was), but it works fine in Platinum.
 
Regards,
Dan

Noel Borthwick [Cakewalk]
IIRC this was fixed post X3. There were several MIDI tenderingissues fixed with CCs.

I have this exact issue and I'm running X3e, which is latest X3 update. Really, Cakewalk, is a bug this serious still unfixed? How can it be - I mean, isn't the ability to make a mixdown any DAW's core feature? This is seriously compromising the tight production schedule I'm on.
 
Edit: Removed the release date, which apparently was for the release notes only and not for the update patch itself.

Bristol_Jonesey
Can you provide some more information and the specific steps you're taking to expose the problem?

Sure. It's quite well documented in previous posts, but I made a video showing how it happens. As the forum doesn't let me link a Youtube video, you can find it in Youtube by searching for "Sonar X3 bug: ignores automation data when bouncing/rendering realtime".
 
 
 

AMH

Noel Borthwick [Cakewalk]
IIRC this was fixed post X3. There were several MIDI tenderingissues fixed with CCs.

I have this exact issue and I'm running X3e, which is latest X3 update. Really, Cakewalk, is a bug this serious still unfixed? How can it be - I mean, isn't the ability to make a mixdown any DAW's core feature? This is seriously compromising the tight production schedule I'm on.
 
Edit: Removed the release date, which apparently was for the release notes only and not for the update patch itself.

The post directly above yours has the CTO of Cakewalk stating this was fixed POST Sonar X3.