Freeze synth and move clip to a new track

Shouldn't be a problem. What happens when you try to Shift+drag?
 
Alternatively, you can bounce directly to the other track and then disconnect the synth or Archive the synth track.

Paul P
 
It looks like both drag move and drag copy were disabled as of Manchester.  Move didn't work properly anyway.  You could drag copy the frozen clip elsewhere at that worked ok, but drag moving it would cause the source track to go crazy if you then unfroze it.  I think they should just have disabled move, not copy.

Neither works! Shift+drag, the cursor moves but not the clip. Same with Shift+Ctrl+Drag (except that the cursor has the little plus next to it). 
 
If it has been disabled, that's a shame. I used it all the time and never had any problems with synths.
 
 

Strange. Works in X3. If I move it to another track, then press Ctrl before I drop, a little plus sign appears next to the "Move" cross and I get a copy.
 
In Newburyport, the plus sign also appears, but nothing happens.
 
And Copy Paste works in both. Weird.

 
I don't think moving made sense (what does it mean for the synth to be frozen but not have a clip ?) so I can see preventing that.  Regular copy works so why not drag copy as well since it's the same thing ?  Looks like a botched fix to me.

I did it with a midi and an instrument track.
The frozen audio in question was in the instrument track.

I'm getting unchanged odd results with Roland TTS (DXi), FM8 (Synth) and DimPro (Sample player).
 
The drag action does however cause fades or crossfades if I'm not careful.

Bristol_Jonesey: I can't get Dimension Pro to work . . .
 
Brundlefly: This works, and it will be a useful workaround for bouncing individual kit pieces in, say, AD2. But for a single bounce softsynth copy/paste is still as efficient. 
 
Paul P: I have not experienced any buggy behavior when using this technique, and I have been doing it for a long time! Perhaps your compositions are more intricate than mine ;).
 
Thanks everyone for your responses! I have never had much luck with forums, usually just answers like 'I don't know' (then don't waste my time!) but I believe Cakewalk users are the most knowledgeable and helpful out there! 

tenfoot
Due to this being buggy there is now no way to change the render bit depth of soft synths after the initial project setting.  Changing the render setting in preferences has no effect on bounce to track (broke in Sonar 2015).

The conditions for this issue still need clarification as I was not able to reproduce a problem other than that the project needed to be closed and re-opened for the render depth change to take effect. When last we left it, I was speculating that your case might be synth-specific, but that was never confirmed. For the benefit of others following along, here's that thread:
 
http://forum.cakewalk.com...to-track-m3374413.aspx
 
 

Paul P

ttaggart4
Paul P: I have not experienced any buggy behavior when using this technique, and I have been doing it for a long time! Perhaps your compositions are more intricate than mine ;).

It's not the move per se that causes the problem, it's the subsequent unfreezing and re-freezing of the synth that is problematic.  Maybe you don't do this ?  Watch was goes on in the transport window when you refreeze after having stolen the clip from a frozen synth and then unfrozen it.  The first time it will go through 2 freezing passes.  The next time it's 3, then 4, etc.  And often the resultant clip get longer and longer each time. 

I do exactly that. When I am ready to mix AD2, I 

1. Solo a drum kit piece
2. Freeze the synth
3. Copy the resulting clip to a new track solely for that kit piece's audio
4. Unfreeze the synth
5. Solo the next kit piece
6. Lather, rinse, repeat

I know there are ways to assign individual kit pieces to their own audio tracks, but I find that tedious and unreliable. I have not encountered the issue you mention, e.g. bugginess of this process.

brundlefly

tenfoot
Due to this being buggy there is now no way to change the render bit depth of soft synths after the initial project setting.  Changing the render setting in preferences has no effect on bounce to track (broke in Sonar 2015).

The conditions for this issue still need clarification as I was not able to reproduce a problem other than that the project needed to be closed and re-opened for the render depth change to take effect. When last we left it, I was speculating that your case might be synth-specific, but that was never confirmed. For the benefit of others following along, here's that thread:
 
http://forum.cakewalk.com...to-track-m3374413.aspx
 
 

I have tried tried this on every vst synth I have.  Yep.  It's certainly broken, and restarting the project or Sonar doesn't fix it.  

tenfoot

brundlefly

tenfoot
Due to this being buggy there is now no way to change the render bit depth of soft synths after the initial project setting.  Changing the render setting in preferences has no effect on bounce to track (broke in Sonar 2015).

The conditions for this issue still need clarification as I was not able to reproduce a problem other than that the project needed to be closed and re-opened for the render depth change to take effect. When last we left it, I was speculating that your case might be synth-specific, but that was never confirmed. For the benefit of others following along, here's that thread:
 
http://forum.cakewalk.com...to-track-m3374413.aspx
 

I have tried tried this on every vst synth I have.  Yep.  It's certainly broken, and restarting the project or Sonar doesn't fix it.  

I guess we'll just have to hope that the Bakers can reproduce it, then.