Happens with audio clips. Screwed up several of my projects. Had to go back and add them back in to about 50 clips. This has been going on for over a year. I have the latest version of Sonar Pro. 
 
Thanks in advance for fixing this sometime in the future.
 
Mike

I remember in Sonar 8 and X1, you would hit the "x" key to disable automatic crossfading of any clips.  When enabled and you move two clips over each other with any amount, they will crossfade accordingly.  Sometimes this can be beneficial, but personally, I find it unnecessary.

mleghorn
Happens with audio clips. Screwed up several of my projects. Had to go back and add them back in to about 50 clips. This has been going on for over a year. I have the latest version of Sonar Pro. 
 
Thanks in advance for fixing this sometime in the future.
 
Mike

Can you give a recipe to reproduce? I use zillions of crossfades due to working with narration, and they stay in place.

I'm not sure, but I think it happens when I work with two adjacent clips in the same track. Whatever the precise steps, the fades on the left side of all the clips in all the tracks disappeared. The first time this happened to me (a year or so ago) I was working with clips in the same track. Then I decided it would be safer to put each clip in a different track, and the problem seemed to go away. 

Sounds like take lanes trying to do some sort of automatic crossfading of 'comps' and messing it up. I've never seen this precise bug but I've seen a bunch of unwanted behaviour with clips in take lanes, such as crossfades being of mismatched types, fade handles being out beyond the end of the clip, etc.

mleghorn
I'm not sure, but I think it happens when I work with two adjacent clips in the same track. 

Unfold the Take Lanes and see if you actually have clips recorded in the Take Lanes. It's important to learn the different recording modes; don't select "Comping" (which is the defaut) if you don't want to comp.
 
That said, Cakewalk has prioritized overhauling Take Lanes along with plug-in load balancing and ripple editing, so I suspect we'll see some of the loose ends tightened. My biggest problem with Take Lanes isn't bugs, but inefficient workflow and editing constraints that can give the appearance of bugs. Hopefully that's what they're addressing.

I wasn't using take lanes.
 
Thanks,
Mike

You may think you're not using Take Lanes, but humor me and check whether any of the tracks where you have this issue reveal Take Lanes when you show them. If comping is selected as the default recording mode, it's entirely possible but you wouldn't know it if they're hidden - all you would see is the parent track.
 

I've had something similar happen every now and then. Sadly I cannot think of a recipe to reproduce but I have seen it occur on a track that had a lot of overlapping clips where I customized the cross-fades (manually overrode the default on a per clip basis). Everything is fine and then one day I'll notice that all the cross-fades have switched back to default and my manual changes are lost.

I guess I may be doing something wrong somewhere in the process, but suffice to say I've earned to just "bounce to clip" after backing up the pre-bounced project.

I noticed one error that occurs in cross-fading a "pair of clips" that are in the same group (e.g. two mono tracks that act as a stereo pair that I have placed into a group).

When cross fading these clips, the upper track loses its cross-fade but the lower track retains them. I had to keep manually fixing this but eventually rolled back to July's version from the (current) August update.