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!).

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.

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.
 
 
 
 

do we know for sure this is dealt with in X3?  im running two instances of PLAY 64 filled with Hollywood Diamond instruments, all triggered by staff notation.  The automation is CC1 and CC11 controlling volume and vibrato on the individual instrument tracks. When i fast bounce, notes will be clipped or disappear entirely.... even before i was using automation, i still had to real time render...fast bounce wasnt getting all the notes.....which was fine until i started using the automation...

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

IIRC this was fixed post X3. There were several MIDI tenderingissues fixed with CCs.

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.

I'm somewhat confused by your post which implies there was an update for X3 this year, when in fact there wasn't.
 
IIRC, I was running several instances of Play in X3e and did not see this particular problem - all automation was rendered faithfully.
 
Can you provide some more information and the specific steps you're taking to expose the problem?

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?

 
Under the old upgrade model each major release happened around the end of a year and one or more patches would be provided throughout the following year to address new issues and some outstanding issues carried over from previous releases, and sometimes to add new features. At a certain point, all development effort would go into the next release, and patching of the current release would cease.
 
This issue never got fixed in the X3 cycle, but was fixed some time back in 2015. I suspect that one reason it didn't have higher priority is that it has an easy workaround: use the default Fast Bounce mode to render. There are few cases where it's imperitive to do a real-time bounce of a soft synth so the impact is minimal, and of course, Fast bounce has the benefit of being faster (duh).
 
Also, since there's no such thing as 'real-time Freeze', I'm not sure why the OP said Freezing was affected. As I recall, this was only a problem with real-time bouncing. And it didn't affect MIDI sent to hardware ports, either.