When adding cross dissolves to a project that I'm working on, I've come across an odd problem. I say odd because this should be dirt simple, but Adobe seems to have messed this up. Please advise on any solution or work around, or perhaps simply see if you can recreate the issue so we can get Adobe to fix this.
Problem:
Cross dissolves transitions don't seem to work consistently in cs 5.5. Note: I know how transitions work, and I'm not doing something stupid like trying to apply a transition to a cut without actually removing any video between the two clips (assuming the clips came from the same source video.). I'm able to recreate this issue on two different systems with premiere pro cs 5.5 by doing the follwing:
- Create a new project and and sequence with the default settings.
- Enable the Mercury Playback Engine if it isn't already enabled.
- I import the Wildlife.wmv video that comes default with Windows 7 systems.
- Drop it the video into the sequence.
- Ripple delete about a 2 second section of the video. be sure to do this in the first half of the video, and make sure the the video changes the scene during this period so that you will notice the cross dissolve transition when it is applied.
- Apply the default cross dissolve transition to the edit.
- Review the edit. For my test, this edit always seems to work fine.
This is a screen capture of the working cross dissolve transition.
Now let me show you what happens when I do a similar edit somewhere in the second half of the video clip.
As you can see, for the duration of the transition, only the clip to the left is shown. At the end of the transition effect the program out preview jumps to displaying the clip to the right. There is no transition.
Additional notes:
This second transition works fine with MPE disabled, but because if of my other problem http://forums.adobe.com/message/3725642 that I have with MPE disable it is not a viable work around.
Help?
-Ted
27
Replies
Hi
Thi issue goes back till CS4: http://forums.adobe.com/message/2789016#2789016 - and still exists. Adobe have said they would take care of it over a year ago. But nothing seems to have happened with this issue. i was about to uograde from CS5 to CS5.5 in the hope that they had solved this issue - but it seems to be living well...sadly enough.
AdChoices