New INFO and Great News!


Hello all! Cakewalk has now recognize the problem and they going to fix it ASAP!

Hello Freddie.
The status of your problem report has updated to "Submitted to Development" with the following notes:
This is confirmation that your report is officially on file with our development team. At this time we do not require any further information from you to research the nature of your report. Should we require further information we will contact you using the email address you have provided in your report.
 
Best Regards,
Cakewalk Problem Tracker

Lanceindastudio


Hi Anderton.

After you get that automation you want in the separate synth output track, I copy a mid clip onto the syntyh output track (yes a midi clip, usually from the midi track as this is where the automation will actually be), and then, when I take that midi clip that is on the synth output track and copy it to another location on the synth output track, the automation goes with that clip.
The clip serves no purpose being on the synth output track and does not alter the output at all except the service of carrying all automation with it when it is copied and moved elsewhere on the track.

Thank you!

Lance Jones

Thanks for sharing the workaround Lance!
 
 
 

Milamber


The issue we may be dealing with on this is that nobody has contacted the bakers and formally opened an issue with a CWBRN number? Is anyone aware of any open documented issues with Cakewalk? Does a CWBRN already exist that any of you are aware of? Before I call it in I would like to know if this issue is already owned by someone and what the feedback was....Thanks!

As I stated in the post directly above yours, the issue has been formally reported through Cake's problem reporter by myself and others.  They've been aware of the issue for quite some time now.
 
I received the same email as Freddie a couple of days ago (though it was reported some months ago) that the problem has been "submitted to development".  What that means as far as actually getting the problem fixed, only time will tell.

font size malfunction.. can anyone confirm ?  

Welcome :)

Freddie H


New INFO and Great News!


Hello all! Cakewalk has now recognize the problem and they going to fix it ASAP!

Hello Freddie.
The status of your problem report has updated to "Submitted to Development" with the following notes:
This is confirmation that your report is officially on file with our development team. At this time we do not require any further information from you to research the nature of your report. Should we require further information we will contact you using the email address you have provided in your report.
 
Best Regards,
Cakewalk Problem Tracker

That does not mean cakewalk are going to fix it, necessarily.
I have CWBRN tickets from years ago that got to that stage but still haven't been fixed.
 

Lanceindastudio


Hi Anderton.

After you get that automation you want in the separate synth output track, I copy a mid clip onto the syntyh output track (yes a midi clip, usually from the midi track as this is where the automation will actually be), and then, when I take that midi clip that is on the synth output track and copy it to another location on the synth output track, the automation goes with that clip.
The clip serves no purpose being on the synth output track and does not alter the output at all except the service of carrying all automation with it when it is copied and moved elsewhere on the track.

Thank you!

Lance Jones

None of these workarounds did work on my computer with SONAR X1?
Thanks for trying!

Had the same problem myself - now on X1D (installing X2 in a few days - will post back if problem solved)
BUT Right now theres a big ambiguity that needs clearing up before any code fix - specifically what the automation belongs to -
Track, Layer or clip. An ideal might be that Track Automation, Layer Automation and Clip Automation each provide separate options (copy, paste assign envelope etc) and are accessible as separate entities. Currently only the clip automation is this clear cut and copying it generally works as expected. Skylight implies that copying a track that the automation belongs to the track - but the experiences above demonstrate that this isnt the case.
 
One solution is to put all automation in a separate stereo bus and output the track(s) to that bus - That way clips tracks and layers can then explicitly be 'attached to' the automation set - the down side is that this doesn't help with a template style automation (i.e copy, paste and modify for an individual track)

NickGavriel

(installing X2 in a few days - will post back if problem solved)

Hi Nick, and welcome to the forum.


X2 and Automation is a whole different ball game. If you are installing X2, as you say, then you will see that you now have Automation Lanes and manipulation the automation is a lot easier, and less buggy than before.


cheers


andy

This and numerous other automation issues were addressed as part of the automation and selection/edit commands overhaul in X2.  Many fixes were made to the way instrument track automation was handled. 

In X2 not only can you copy and paste instrument track automation on the same track, it now also works with multiple track copy paste and copying to a different instrument track as well.  Bus automation is now also consistent across copy/paste.

In X2 I think we have covered every common case (and more) that you might have with automation copy paste. If we missed something please let us know.