FCP HVX200 720-24p dissolve issue

O

Orangemoon

Member
I found a thread that listed (as it appeared) my exact problem...but unfortunately, the thread ended with no resolution. So, I'm hoping someone can help!

I shot in 720/24pn via P2 and transferred to FCP5.1 Whenever I use a cross-fade or a single-clip fade, I get a 1 or 2 frame "jump" at the keyframe point (either at the start of the fade or the end...or both). I tried using the pen-tool as an alternative but it didn't help.

I tried a variety of sequence settings but nothing has fixed it. There are 4 of us fairly seasoned editors looking at this with no idea how to fix it. It's our first time editing footage from an HVX200 and we've never seen this before from any camera.

Your help is greatly appreciated!

Thanks!
 
ok - just need to clarify....

are you talking about a cross dissolve?

1-is this only happening on this one clip or is it across the board - all cross dissolves.
2-have you rendered your timeline - this may be because it is laggy since you are running it off the timeline without it being rendered.

If you are looking for another option :-

- run the two clips you want to dissolve into eachother - one over -one under.
- then go into your first (top)clip and key frame opacity on the to clip from 100 (start of fade) to 0 (end of fade)
- then go to the second(bottom) clip and key frame from 0(start of fade) to 100 (end of fade)

I find that this may be a cleaner solution and less likely to find artifacts or unwanted frames creeping in.

I hope I understood you correctly - if there is more questions - let me know
 
More information...

More information...

CONTINUED:

It's happening on all dissolves and wherever I mess with opacity. The problem is "not" seen in the timeline "until" I render....When I do a "full" render, I get the pops. I first noticed it when I made a small clip of my film by exporting about 15 seconds of some scene for review. When I shared it with a friend via DVD, there was a "jump" during the cross-dissolve (about 2 frames.)

So, I said, "What the hell was that?". I went back to the timeline and it was not there....then, I did a "full" render and the "jump" "was" there.

I can move around the "in" and the "out" of the dissolve and it doesn't matter; it always happens at the keyframe.

Thanks!
 
Oh right, well, then it's obvious you broke it! Next thing we'll see you post is that someone just lost an eye!

JUST KIDDING!

If you go to Seqeunce > Render or Render All, everything in that list must be checked. I'll have to check this out, I edit 720p24 all the time and have never noticed it. I'll try doing some experimenting tonight.
 
Am I remembering correctly that someone posted here that you need to re-ingest your footage after upgrading to solve this problem? Or did that have to do with something else?
 
To BenB

To BenB

Thanks for your help! yeah, this is a weird one. I'm sitting on an almost 2 hour film for a client (and it's due!) and I have about 50 spots where this problem occurs. I've tried all sorts of changes to my edits to alleviate the problem...I've moved clips around, changed the keyframes, etc., but nothing works...I only end up moving the "jump" around to new places.

Ironically, in an un-rendered state, the "one or two frame jump" is not there. When I do a "full" render (all render items checked), the jump appears in the timeline "and" on any exports.

It's probably happening on every dissolve but it's only noticable when the clip have movement in it. In my case, it's a 2 hour film about a musician. I have a lot of transitions on the slow songs and if the musician is moving his head or guitar, there's a 1 or 2 frame jump that is "very" noticable...

I'll be checking these posts from the mental home so please keep 'em coming!

Thanks!
 
I'd try this, delete all your render files using the Render Manager. Then save and quit the project. Use FCP Rescue 5 to trash prefs. Start the project back up and render everything from scratch.

Also, are you seeing this on an external monitor, or on your computer screen, or both?

Another question, just to help me rule stuff out, discribe in detail what you mean by "jump".

Now, I had one of my consulting clients today have this problem do to "editor error". They were putting transitions on parts of a clip where the extra footage, that the transition (cross fade) extends a clip by, covered a segment where the camera stopped and started recording different scenes. A little use of the slip tool fixed that.

I'll assume that if you double click the clip that has the frame jump, and look at the footage just before the in point (or just after the out point) is fine, right?
 
Thanks for the tip...I'll try it tonight.

As for your questions:

The "jump" occurs on the clip that "has" the dissolve. Somtimes I overlap clips and only apply a dissolve to the top clip and it dissolves down into the lower clip as it's played. I also use the cross-dissolve in the conventional way where I butt two clips together and apply the cross-dissolve. If I stretch the dissolve to make it longer or shorter, it doesn't matter...the jump follows the in or out keyframe

The "jump" is a 1 or sometimes 2 frame "skip". If I remove the dissolve and stretch the clip out, the "jump" is not there...It's not on the actual clip above, below, or beside....just when I apply the dissolve (at the keyframe at 100% Opacity. or 0% Op.) and then "render" it does the jump become visible...only after render...and of course, when I make an export of it to QT.

It even occurs when I put a "text" above a clip (like on a song intro) and apply a dissolve to the text clip....

Thanks for your help!
 
I thought it was a 5.0.4 issue, so if he loaded the footage with 5.1.1 it shouldn't be a problem. If you loaded footage with 5.0.4 then I believe you need to go to your backups and re-load footage in order to properly overcome the render glitch. At least that is what I recall from all the discussions in the HVX threads earlier this summer.

cheers.
 
Progress

Progress

Thanks, all.

Your suggestions have led me along a good path. You all referenced that this "was" an issue a couple months back and you were right. I'm hot on the trail of being able to fix this situation. I'll advise ...hopefully tonight, with the results. I have one beer left for a big celebration later!

...still wearing yesterday's clothes and smelling ripe...but I'm almost there!
 
Solution!

Solution!

Thanks all for your help!

It's a bit time consuming but it works! Since this issue never corrupted the original .mov files, the fix works.

I first captured these clips in FC5.1 (not 5.1.1). Below 5.1.1 is where the FC issue resided and was fixed on 5.1.1 or above. So bottom line:

1. I had to upgrade OS from 10.4.4 to 10.4.8
2. Upgrade FCP to 5.1.2
3. And then follow the Apple document pasted below.


http://docs.info.apple.com/article.html?artnum=303950

Thanks, all!!!
 
You must log in or register to reply here.
Back
Top