It's still in v7, too. I've learned to work around it by adding a keyframe to the other side of a dissolve if one of the sides already has one. But I just hit an instance 5 minutes ago actually where that didn't work and I had to move my B-side clip to another track and then put identical dissolves at the cut point on both tracks. 

I read somewhere that part of this behavior is intentional, but I don't understand why that would be since it worked as you expected it to in earlier versions

Evan Schiff:

I've learned to work around it by adding a keyframe to the other side of a dissolve if one of the sides already has one. But I just hit an instance 5 minutes ago actually where that didn't work and I had to move my B-side clip to another track and then put identical dissolves at the cut point on both tracks. 

I've used the split track method as well and adding the other keyframe but neither is ideal especially when you are trying to minimise tracks.

I can't believe it is an intentional change. We gained nothing by this new behaviour.

Agreed! This has been a "known bug" for too long now and it's incredibly frustrating (apparently since the v5 update 3 years ago).   At least with v6.5 and up, we have more tracks to 'waste' trying to work around this bug, but it's very annoying when you bump into it.  Each editor I've assisted has bumped into this bug and complained.

As I wrote earlier, it had been logged as a bug, I pinged MM to check the status of UDevC00172587.

I hear this issue is still on the list, folks. Hopefully in an upcoming patch.

Hello, I'm working with 7.0.4 and I still have issues with dissolves / audio keyframes. Sometimes render helps but sometimes not. It seems like the dissolve is ignoring the auto gain value. 

here you can see a demonstration of the behaviour:

http://vimeo.com/96235665

This is so annoying, is there any chance to see a bugfix pretty soon?

One thing I've noticed in recent versions is that if there are rubberbands on both the incoming and outgoing clip, MC seems to playback the dissolve correctly in real-time without editing.  Are you seeing that?

Unfortunately no, the dissolve seems to ignore both auto gain values on incoming and outgoing clip.

Has this bug been officially scheduled for a fix yet? It is incredibly bad that a pro editor can't do a simple crossfade correctly. it's been a bug for 4 generations of the software now.

I have to admit this thread has me scratching my head.  When I need the precision of cross fading while simultaneously changing clip volume it would never occur to me to not create an additional audio track.

With the limited amount of audio track you can't always split your audio, if it looks like that for example:

http://www.evanschiff.com/bd/wp-content/uploads/Reel-7-Full-timeline.jpg

And sometime I don't use dissolves as a precision of cross fading, but only as a dissolve to not hear the edit. For example if you have an atmo and you want to bring some variations with keyframes so it's not getting to boring and you want to loop it, I need the dissolve only to hide the edit at the loop point. Or you want 2-5 frames dissolves for the dialogue that you carefully prepared with audio keyframes. 

Bloersch:

With the limited amount of audio track you can't always split your audio, if it looks like that for example:

http://www.evanschiff.com/bd/wp-content/uploads/Reel-7-Full-timeline.jpg

Dude! You can still add 8 more tracks there!

You want to save some tracks to move some larger clips (Atmo, music etc.) there, so when you are trimming with sync locks enabled they don't get split and the rest of your timeline stays in sync.