Puggles
I have not found anyone else talking about this editing bug that I have and the program is being updated regularly, so am I the only one experiencing this?

 
In general, you can get around the clip editing bugs by using bounce-to-clips between edits.
 
Also, in your example you were moving the clip around a lot to get the right position. Before you try the second move, undo the first using CTRL+Z. When you're happy with it, bounce-to-clips.
 
The other thing I find helps, is to have the "create one clip per file" option checked in the save dialog.
 
Without this checked, Cakewalk/SONAR saves all its clip in the one file with internal references as to where each clip starts/stops. These internal references can get corrupted, although regular bounce-to-clips helps to refresh them.
 
I guess the idea behind having the one file was for performance reasons. This is less of a concern if you're using an SSD.
 
So in summary, use bounce-to-clips often - even if it's on each clip, bouncing to itself; and have the "create one clip per file" option checked.
 

You might try using Command Center to reinstall Sonar. This time make sure you have the shortcuts where you want them. In the meantime use Cakewalk by Bandlab. It is a very good version. 

msmcleod

Puggles
I have not found anyone else talking about this editing bug that I have and the program is being updated regularly, so am I the only one experiencing this?

 
In general, you can get around the clip editing bugs by using bounce-to-clips between edits.
 
Also, in your example you were moving the clip around a lot to get the right position. Before you try the second move, undo the first using CTRL+Z. When you're happy with it, bounce-to-clips.
 
The other thing I find helps, is to have the "create one clip per file" option checked in the save dialog.
 
Without this checked, Cakewalk/SONAR saves all its clip in the one file with internal references as to where each clip starts/stops. These internal references can get corrupted, although regular bounce-to-clips helps to refresh them.
 
I guess the idea behind having the one file was for performance reasons. This is less of a concern if you're using an SSD.
 
So in summary, use bounce-to-clips often - even if it's on each clip, bouncing to itself; and have the "create one clip per file" option checked.
 

To manipulate and fine tune the editing of the two clip to create perfect crossfades is a pain as it is when I have to click on them a certain way so the program doesn't make unwanted cuts every time is enough of a pain in the butt, but if I did and then bounced them, what if I want to come back and do something different to them later?  If they are bounced aren't they "one" and then merged together?  So they can't be reseparated and manipulated after they are bounced.  I used to just wait until I was finalizing my project and then bounce all drums together, all guitars together and etc... and then do any final compression to them as a bounced group before combining into one. 
 
So if I bounce each clip after I edit it quickly, doesn't that make it more difficult for me to do anything else to the "bounced slip" later on?  What if I change my mind later on in the project?
 
If this is happening to very few people, could someone take a screenshot of their preferences menus and show me?  Maybe there's some really deep hidden option that I'm not applying, or maybe it's in the smaller options menu at the top-ish left of the DAW (were crossfade options are at)?

Puggles

msmcleod

Puggles
I have not found anyone else talking about this editing bug that I have and the program is being updated regularly, so am I the only one experiencing this?

 
In general, you can get around the clip editing bugs by using bounce-to-clips between edits.
 
Also, in your example you were moving the clip around a lot to get the right position. Before you try the second move, undo the first using CTRL+Z. When you're happy with it, bounce-to-clips.
 
The other thing I find helps, is to have the "create one clip per file" option checked in the save dialog.
 
Without this checked, Cakewalk/SONAR saves all its clip in the one file with internal references as to where each clip starts/stops. These internal references can get corrupted, although regular bounce-to-clips helps to refresh them.
 
I guess the idea behind having the one file was for performance reasons. This is less of a concern if you're using an SSD.
 
So in summary, use bounce-to-clips often - even if it's on each clip, bouncing to itself; and have the "create one clip per file" option checked.
 

To manipulate and fine tune the editing of the two clip to create perfect crossfades is a pain as it is when I have to click on them a certain way so the program doesn't make unwanted cuts every time is enough of a pain in the butt, but if I did and then bounced them, what if I want to come back and do something different to them later?  If they are bounced aren't they "one" and then merged together?  So they can't be reseparated and manipulated after they are bounced.  I used to just wait until I was finalizing my project and then bounce all drums together, all guitars together and etc... and then do any final compression to them as a bounced group before combining into one. 
 
So if I bounce each clip after I edit it quickly, doesn't that make it more difficult for me to do anything else to the "bounced slip" later on?  What if I change my mind later on in the project?
 
If this is happening to very few people, could someone take a screenshot of their preferences menus and show me?  Maybe there's some really deep hidden option that I'm not applying, or maybe it's in the smaller options menu at the top-ish left of the DAW (were crossfade options are at)?

I meant bounce each clip to itself - so select each individual clip and bounce one at a time.
 
If you select more than one clip, then yes, it will merge them. But you don't want this. Just select the one clip at a time, and right click->bounce-to-clips.
 

msmcleod
This is less of a concern if you're using an SSD.

Oh dear.

I work with moving clips all the time and have never come across this problem. I just went into a project of mine and I had just got through editing (Spliting clips moveing them over and on top of each other) and went back in that same project and tried to repro this issue and could not.
 
CbB doesn't do this. Use it.

Grem
 
CbB doesn't do this. Use it.

Um, isn't that video in the OP of CbB (the upper left corner of the app is orange and says "Cakewalk")? It is almost like that move operation is baking in the fades on each iteration (the graphical representation), rather than working with the raw audio data representation throughout. Pulling apart two cross-faded overlapping clips should make them both grow (and they don't), so is like the algorithm only has subtraction in it. Each time he releases the mouse the "raw" representation is actually the faded values. The clip duration changing near the end is just "not good."
 
I have not used this functionality, but there is definitely something amiss with the cross-fade algorithm in it.

mettelus
 
Um, isn't that video in the OP of CbB 

 
Yes you are correct mettelus. Sorry about that Puggles. 
 
Puggles, if this happens to you often, which you indicate in your posts, that leads me to think something has to be wrong with your system. I mean, if this was a common problem, as much as I work with clips I would have seen it at least once by now, but I don't remember it happening. And again, if it was a common problem, people would be here screaming all about a big bug like that.
 
So let's look at your system. As a suggestion, what video card do you use and when was the last time t had it's drivers updated?