My suggestion is a simple one, but I notice it every time I use the program:
 
In the FX rack context menus, I would love a selection for "Replace Effect."
 
Just like there is a selection for "Replace Synth" in the Instrument Track context menus.
 
We can replace a synth with one step, but must go through the extra step of deleting an effect and then adding another one all over again, when replacing effects is something I, and probably others, do way more often than replacing synths. It would be great to have that functionality.

Create more keyboard shortcut options in Preferences for some new features like for Piano Roll:

1. View -> Show Multiple Lanes
2. Transform tool

Puggles
*BUG*
I have a recorded video for better understanding. Video here
 
When you take two clips on the same track and move them together (and create a crossfade, if so desired) I try to drag one of the clips to make sure it is in sync with the metronome and when I move the clip, the part that is crossfaded now has a "cut", or "gap" in it after being moved.  Sonar 4,5,7, or 8 that I've used in the past has NEVER done this, so why now?  When I would drag one of those clips, it would just slide accordingly with the crossfade (if applicable).  I could not find any option in the preferences menu to change this from happening.

80% of the time this works how it SHOULD and does and this bug does not show it's ugly face.  I have to assume this is a bug in the software since I have ALWAYS edited in Sonar the exact same way since Sonar 4 and this editing bug happens MOST of, but not all the time.

I found doing anything with multiple selected clips is hit and miss (see http://forum.cakewalk.com/Issue-when-using-Normalize-in-multiselect-m3763740.aspx).
 
Sonar Platinum/CbB store multiple clips in the same file. It seems that performing multiple-clip operations which involve clips that are in a file shared by other clips just doesn't work properly. You either get corrupted or blank clips, or the contents of other clips affect the logic in whatever operation you're doing (certainly in the case of Normalize or Clip Gain).
 
The only way I found to stop it doing this is to:

• Ensure "Create One File Per Clip" is selected (this is in the "Save As" dialog)
• Select each clip individually and select "Bounce To Clip(s)" for each one.

This ensures that each clip is in its own file. Once this is the case, multiple clip operations should work as expected.
 
Seeing as I'm in the right thread for this...
(a) Can this bug be fixed; and/or
(b) Can we have some method of doing a bulk "Bounce to Clips" for all the clips in a track, so that each clip ends up in its own file?

Just wanted to repost my request (This could influence my choice of DAW a lot!) for AAF file import and export.
 
My Main reasons for requesting this feature are the following:
 
1) Several other DAWs including Pro Tools, Logic X, Presonus Studio One, and others, have included support for the AAF format, making it possible to move large sessions easily between different DAWs.
 
2) In a Multi-Daw environment (I play in a band with multiple members and DAWs) this makes working on projects from differing DAWs a total pleasure, as well as saving time and helping keep inspiration levels high!
 
3) OMF is dated, and currently not widely supported, AAF has a better track record and has a much wider layer of support.
 
4) This would be one of the ONLY reasons I would think another DAW would win out over Sonar, especially in Post Production and editing.
 
 
<----- Multiple posts here have also brought up this issue :)
 
I am sorry for posting multiple times in this thread, but I do believe that this would be a great asset to Cakewalk by Bandlab, and would help many musicians and engineer/ producers to work with production companies and post production facilities in a much easier manner.
 
P.S. Cakewalk For Life!
 

Sorry, my link to the forum post relating to AAF didn't post for some reason
 
but a simple forum search should bring up the relevant link :)

msmcleod

Puggles
*BUG*
I have a recorded video for better understanding. Video here
 
When you take two clips on the same track and move them together (and create a crossfade, if so desired) I try to drag one of the clips to make sure it is in sync with the metronome and when I move the clip, the part that is crossfaded now has a "cut", or "gap" in it after being moved.  Sonar 4,5,7, or 8 that I've used in the past has NEVER done this, so why now?  When I would drag one of those clips, it would just slide accordingly with the crossfade (if applicable).  I could not find any option in the preferences menu to change this from happening.

80% of the time this works how it SHOULD and does and this bug does not show it's ugly face.  I have to assume this is a bug in the software since I have ALWAYS edited in Sonar the exact same way since Sonar 4 and this editing bug happens MOST of, but not all the time.

I found doing anything with multiple selected clips is hit and miss (see http://forum.cakewalk.com/Issue-when-using-Normalize-in-multiselect-m3763740.aspx).
 
Sonar Platinum/CbB store multiple clips in the same file. It seems that performing multiple-clip operations which involve clips that are in a file shared by other clips just doesn't work properly. You either get corrupted or blank clips, or the contents of other clips affect the logic in whatever operation you're doing (certainly in the case of Normalize or Clip Gain).
 
The only way I found to stop it doing this is to:

• Ensure "Create One File Per Clip" is selected (this is in the "Save As" dialog)
• Select each clip individually and select "Bounce To Clip(s)" for each one.

This ensures that each clip is in its own file. Once this is the case, multiple clip operations should work as expected.
 
Seeing as I'm in the right thread for this...
(a) Can this bug be fixed; and/or
(b) Can we have some method of doing a bulk "Bounce to Clips" for all the clips in a track, so that each clip ends up in its own file?

This was NEVER an issue before when I would edit in Guitar Tracks, Sonar 4,5,7,8, X1 and X3, so why is this happening now?  It doesn't make sense.  I have exhausted the options menu (even in advanced settings) and I can't find anything that pertains to this.  I'm absolutely convinced that this is a bug.  And as far as bugs go, this is almost a deal breaker for me.  I have edited like this for YEARS with Cakewalk products and this has put a serious damper on my efficiency with editing.

Puggles

msmcleod

Puggles
*BUG*
I have a recorded video for better understanding.
 
When you take two clips on the same track and move them together (and create a crossfade, if so desired) I try to drag one of the clips to make sure it is in sync with the metronome and when I move the clip, the part that is crossfaded now has a "cut", or "gap" in it after being moved.  Sonar 4,5,7, or 8 that I've used in the past has NEVER done this, so why now?  When I would drag one of those clips, it would just slide accordingly with the crossfade (if applicable).  I could not find any option in the preferences menu to change this from happening.

80% of the time this works how it SHOULD and does and this bug does not show it's ugly face.  I have to assume this is a bug in the software since I have ALWAYS edited in Sonar the exact same way since Sonar 4 and this editing bug happens MOST of, but not all the time.

I found doing anything with multiple selected clips is hit and miss (see ).
 
Sonar Platinum/CbB store multiple clips in the same file. It seems that performing multiple-clip operations which involve clips that are in a file shared by other clips just doesn't work properly. You either get corrupted or blank clips, or the contents of other clips affect the logic in whatever operation you're doing (certainly in the case of Normalize or Clip Gain).
 
The only way I found to stop it doing this is to:

• Ensure "Create One File Per Clip" is selected (this is in the "Save As" dialog)
• Select each clip individually and select "Bounce To Clip(s)" for each one.

This ensures that each clip is in its own file. Once this is the case, multiple clip operations should work as expected.
 
Seeing as I'm in the right thread for this...
(a) Can this bug be fixed; and/or
(b) Can we have some method of doing a bulk "Bounce to Clips" for all the clips in a track, so that each clip ends up in its own file?

This was NEVER an issue before when I would edit in Guitar Tracks, Sonar 4,5,7,8, X1 and X3, so why is this happening now?  It doesn't make sense.  I have exhausted the options menu (even in advanced settings) and I can't find anything that pertains to this.  I'm absolutely convinced that this is a bug.  And as far as bugs go, this is almost a deal breaker for me.  I have edited like this for YEARS with Cakewalk products and this has put a serious damper on my efficiency with editing.

I've seen this on and off (raised a forum request about it), I've got no answers other than it seems to be something that happens to a project and once it's happened you can't roll it back, impossibly annoying

I had another feature request of sorts, which is that when there's a new release in the BLA, it should be really really really really easy to find out what changes have been made. I.e. release notes. Updating a sticky thread really isn't a good way to do it, especially when, with the last two updates, no new text seemed to be added.

Horsefight
I had another feature request of sorts, which is that when there's a new release in the BLA, it should be really really really really easy to find out what changes have been made. I.e. release notes. Updating a sticky thread really isn't a good way to do it, especially when, with the last two updates, no new text seemed to be added.

For the "Easy to find" part - on the BandLab Assistant, you can click the little down arrow bit next to the "Open" button for the app and choose "Learn More" which opens a web page. From there click the "What's New". But as you noticed, they didn't update the page with the last couple of updates to the app - which were bug fixes. That would have been nice... The Release Notes show for the (2018.05) release, but not the two bug fixes released in the mean time. 
 
And the page only shows the most recent update. I think a link to previous updates is in order, too. 

SandlinJohn

Horsefight
I had another feature request of sorts, which is that when there's a new release in the BLA, it should be really really really really easy to find out what changes have been made. I.e. release notes. Updating a sticky thread really isn't a good way to do it, especially when, with the last two updates, no new text seemed to be added.

For the "Easy to find" part - on the BandLab Assistant, you can click the little down arrow bit next to the "Open" button for the app and choose "Learn More" which opens a web page. From there click the "What's New". But as you noticed, they didn't update the page with the last couple of updates to the app - which were bug fixes. That would have been nice... The Release Notes show for the (2018.05) release, but not the two bug fixes released in the mean time. 
 
And the page only shows the most recent update. I think a link to previous updates is in order, too. 

Thanks, yeah I think I saw that with the last update but, like you said it didn't mention any new changes so it's not of any real value unless it's updated every time
 
Cheers