I'm working on a two camera interview in Production Premium CS5. Did the standard setup -- a source sequence with the two camera feeds, nested into a muiti-cam edit sequence where I pick the angles using the multi-cam monitor. Then I nest this into a target sequence where I slice and dice (to isolate just a part of the interview for a short web video, from a 25 minute interview down to 3 minutes or less).
In the process of making big cuts in my target sequence, I end up with a cut between two clips from the same camera. It's a clearly visible blip in continuity, and I typically use a cross dissolve to acknowledge that. When I apply the cross dissolve, I get a weird failure.
The first half of the dissolve works fine. But at the mid point it picks up *both* underlying camera feeds, not just the one that's actually in use. PPro is clearly going back up the nesting of sequences to get this from the source sequence. But why? And how do I stop it? If this a known bug in CS5, what's the workaround?
OK, tried a cross dissolve at a cut between two clips from the Bcam. Works perfectly. It's a cross dissolve between two Acam cuts that doesn't work. The only difference is where these tracks are located on the source sequence (nearly identical cameras, same AVCHD 1080p30, etc.). Acam is video 2, and Bcam is video 1.
Any ideas why one cross dissolve works and the other fails?
Since no one seems to have any idea what I'm talking about here, I think I can call this a bug in CS5. But since multi-cam editing has been overhauled in CS6, what's the point in filing a bug report? Bah.
Europe, Middle East and Africa