HVX FinalCut users READ THIS

PUNCH

PUNCH

Active member
There is a fix in Final Cut 5.1.1 that resolves an issue with p2 imports of 720p/24PN footage. Rendering this footage (ie rendering dissolves) in earlier versions of Final cut will give you duplicate frames. You'll see a jump or a stutter.

You need to have Version 5.1 in order to upgrade to 5.1.1

If you do not have 5.1, you need to upgrade or crossgrade. THIS IS NOT A DOWNLOAD or an easy phone call or something you can have overnighted. Crossgrades for FCP studio 5 to Studio 5.1 run $59 and require that you mail in a form and send your disks with that form. No idea what the turn around time is, so I reccomend doing that quickly. The crossgrade offer expires December 06.

Here is a link to the late breaking news pdf:

http://manuals.info.apple.com/en/Final_Cut_Pro_5.0_lbn_z.pdf

Here is a link to the crossgrade form:

http://www.apple.com/ca/universal/crossgrade
 
Last edited:
I am running 5.1.1 universal and it still exhibits this problem. I am planning to use AE as a work around until they address the bug. It is very annoying and is so bad it almost makes FCP unusable. The problem seems to effect titles more than transitions most likely due to the shorter durations involved so the extra frames don't have time to accumulate.

Where did you find that 5.1.1 includes a fix? It does allow for removing the extra frames of 24PA in the new P2 Import Dialog so I wonder if that is what you've been reading about, if it is I can vouch for the fact that it does not correct the bug.

There is some discussion of this over at 2-pop but surprisingly not much fuss is being made over it.

-filmstox
 
holy crap...that's really bad news! I get duplicated frames on just about all of my transitions when I render them. Its awful and completey unacceptable.

Check out the pdf. link above. That's where I found the info.

I've already imported and written over my P2 cards, so I guess even if this did work, I'd still be screwed because it sounds like the fix is on import.

Yes lets make a big fuss here. It took me a week to get this far and I can't believe I haven't seen anything on this. I guess I'm going to just record out to a deck with as little rendered as possible (lots of green lines) and bring it back in so I can make a DVD that doesn't jump and stutter all over the place.
 
Huh? Is this only on 5.1? I'm still on 5.0 but got my crossgrade discs already. Planning on upgrading soon...should I wait? I'm not doing any 1080 24pa stuff anytime soon.
 
Hey Punch - what happens if you simply keyframe opacity rather than use a transition ?

Also - don't want to send you anywhere else but do ask across on Apples fcp discussion - likely you'll strike Shane Ross who has the workflow down as good or better than anyone.

If this is a true bug or v dependant then he'll know about it and be able to tell you what to do.
 
Last edited:
Keyframe opacity doesn't work. tried that.

Thanks, I'll try to find Shane Ross. I'll post what I find.
 
WTF? I dont think I have ever seen that problem. I started with 5.0.4 ->5.1 -> 5.1.1. I never noticed it and I have cut a lot of projects over the last couple months.
 
ohh - and the other thing that this looks like to me is that the transition is not rendered. Like it's an rt show. Definitely not to be trusted.
Yes, you've prolly got green bars or even dark green - but that's a software estimate/rt thing only despite what the manual says - that you don't need to render dark green.
Have you selected the transition and Cmnd-A or if you want to render the whole tl go opt-A.
 
Its specific to footage shot 720p/24PN

Maybe you're just lucky. I'm running accross more people who've encountered this problem.

I did post on Apples FCP Discussion. Shane is responding on that post, but he hasn't experienced the problem. His only input so far is to use FCP Rescue. It blows out the prefs, I guess. I used it...no fix.
 
robbo said:
ohh - and the other thing that this looks like to me is that the transition is not rendered. Like it's an rt show. Definitely not to be trusted.
Yes, you've prolly got green bars or even dark green - but that's a software estimate/rt thing only despite what the manual says - that you don't need to render dark green.
Have you selected the transition and Cmnd-A or if you want to render the whole tl go opt-A.
Click to expand...

It IS rendered, that's the ponit. It looks fine with a green line, the problem arises when you render it. Grey line...big problems
 
All my footage has been 720/24pN and ZERO stutter on transistion effects, and I used them A LOT for these projects (time-lapsed interviews) - started with 5.1 -> 5.1.1 and no problems.
 
robbo said:
ohh - and the other thing that this looks like to me is that the transition is not rendered. Like it's an rt show. Definitely not to be trusted.
Yes, you've prolly got green bars or even dark green - but that's a software estimate/rt thing only despite what the manual says - that you don't need to render dark green.
Have you selected the transition and Cmnd-A or if you want to render the whole tl go opt-A.
Click to expand...



But I am curious...why does it look like its not rendered? Other than the obvious stutter, is there anything else that leads you to that conclusion-maybe you're on to something.
 
In answer to your question above - sorry I was posting before I saw that - it looks like it hasn't been rendered. I mean if you've got grey then it has. It just looks like it hasn't ...


Bummer - sometimes you have to push Shane a little ... lol
He's a really busy guy - I wonder sometimes how he finds the time to post.

Is this for a film out ?
Because if it's not - try this one,
make a new seq this time using 29.97 - huh? yup, drop some 24 test stuff into that.
You'll have to render immediately - but how does it look ?

Not trying to be smart@ss here - just workarounds that may or may not help.
From what I understand it relates back to how it was recorded and that there are a couple of menu settings that need to be set properly before the correct flags are set for the nle to interpret the them correctly. AND the only reason why I know that is because Shane helped me !



Anyways - hope that might be a viable option for you.
cheers
 
Last edited:
robbo said:
Bummer - sometimes you have to push Shane a little ... lol
He's a really busy guy - I wonder sometimes how he finds the time to post.

Is this for a film out ?
Because if it's not - try this one,
make a new seq this time using 29.97 - huh? yup, drop some 24 test stuff into that.
You'll have to render immediately - but how does it look ?

Not trying to be smart@ss here - just workarounds that may or may not help.
From what I understand it relates back to how it was recorded and that there are a couple of menu settings that need to be set properly before the correct flags are set for the nle to interpret the them correctly. AND the only reason why I know that is because Shane helped me !

Anyways - hope that might be a viable option for you.
cheers
Click to expand...

Shane has already posted! Amazing. Guess I caught him on a good night.
I'll try your suggestion, no you're not being a smart@ss. Thanks for posting.
 
Heh - he's a night editor for one of the studio's in LA - very savvy.
Keep pushing him - tell him Robbosaur told you to. lol

There's a real limit to what i can suggest - I'm in NZ and that's PAL, baby.
Very occassionally I have to do some NTSC stuff - and I always have to relearn it all .

I gotta go look after kids now.
cheers - but do let us know how you get on.
 
robbo said:
In answer to your question above - sorry I was posting before I saw that - it looks like it hasn't been rendered. I mean if you've got grey then it has. It just looks like it hasn't ...


Bummer - sometimes you have to push Shane a little ... lol
He's a really busy guy - I wonder sometimes how he finds the time to post.

Is this for a film out ?
Because if it's not - try this one,
make a new seq this time using 29.97 - huh? yup, drop some 24 test stuff into that.
You'll have to render immediately - but how does it look ?

Not trying to be smart@ss here - just workarounds that may or may not help.
From what I understand it relates back to how it was recorded and that there are a couple of menu settings that need to be set properly before the correct flags are set for the nle to interpret the them correctly. AND the only reason why I know that is because Shane helped me !



Anyways - hope that might be a viable option for you.
cheers
Click to expand...


Hey Thanks Man! Looks like you have the work around. I actually pulled the project into a 59.94 Timebase and it looks great. Some of my slo-mo stuf is all messed up, but I can fix that. Yeah, this is not for film out so I'm good for now. I still don't think the problem is solved, but it looks like I can deliver this thing. Thanks!!
 
You must log in or register to reply here.
Back
Top