HVX FinalCut users READ THIS

nsoltz said:
Just shot some 720pN footage today and captured to P2. Applied some filters and rendered. Absolutely no problems in FCP 5.1.1

Ned Soltz

I agree that that would be the case Ned. The problem I'm faced with and many others I bet is on footage imported on 5.0.4. There must be something wrong with those QT encodes. So, I'm still waiting for Apple to let us know:

1. It can be fixed retroactively with a software patch.:)
2. Tough luck. Reimport all your footage.:furious3:

I'd just like to know before I invest numerous hours reimporting P2 footage and hoping all my ongoing projects reconnect properly. I just don't know how to get a definitive answer on this, or could someone from Panasonic please ask someone at Apple to "render (without glitch frames)" a decision!
 
Punch...my condolences are offered. The production Gods seem to have ways of jumping in and testing patience ever now and again. We've all been there!!! Good Luck in your search for answers and in the meantime...cutaways!
 
Punch...
I wouldnt put much stock in a response that states that your problem is definitely related to a camera setting... when that response comes from a person who doesnt even have hands-on an hvx200.
 
Punch...If you want to truly isolate the origination of the problem. if, find out if the problem is camera based vs computer based... try reimporting your footage into an Avid system. if the problem does not occur, the problem is obviously not a camera issue, its an FCP issue. Id also try reimporting the footage into a different FCP system. If the problem doesnt exist on that system, then the problem is probably linked to some system conflict or setting issue on your paricular FCP staton. Finding the source of the problem is the first step to solving it.
 
Brentmeister said:
Punch...
I wouldnt put much stock in a response that states that your problem is definitely related to a camera setting... when that response comes from a person who doesnt even have hands-on an hvx200.

You're a funny comedian. I'm fairly certain the fix came with 5.1.1 and that upon reimporting the footage the production gods will give me a break. Yeah cutaways...its a client thing ya know?

I could NEVER hose my computer down with cold water...I have too many cool video games.

Anyway, I think the fix is in place. Upgrade to 5.1.1 reimport the footage. If you've written over your P2 cards learn a lesson and rethink the workflow/archive. And if you're stuck with a deadline and no new footage to import move the project over to a 30 drop timeline and render. Filmout people? dunno what they're going to do.
 
Starting your new project with 5.1.1 doesn't work.

I'm using a brand new MacBook Pro with a new install of FCP 5.1.1
 
so this means that we are pretty much forced to make the upgrade to use the p2/hvx workflow and shoot in 720pn? i was hoping to stick with an already paid for 5.0.4 for now. i've got enough bills with buying the camera. a simple patch for older systems would be nice, oui?
-jh
 
jwhammonds said:
so this means that we are pretty much forced to make the upgrade to use the p2/hvx workflow and shoot in 720pn? i was hoping to stick with an already paid for 5.0.4 for now. i've got enough bills with buying the camera. a simple patch for older systems would be nice, oui?
-jh

c'mon, its $50 to crossgrade.
 
By the way, 5.1.1 is a rock star for me. No more problems, I save the original files and when I go to import I check the box to remove duplicate frames. ...I guess that was the point of my original post..but hey the journey was fun..right?
 
I've been having this problem too and have not yet upgraded to 5.1. One workaround that I think I've found is to apply a meaningless non-realtime effect (ie "Levels") to the clip that is having the problem. This forces Final Cut to render the whole clip and seems to get rid of the issue. The problem is that any transitions on the other end of that clip inherit the same problem and you need to continuously apply the effect until you get to a cut.

That seems easier, though, within one job, than upgrading (fine, "crossgrading") and then re-importing all the media.

Hope someone finds this helpful,

- David
 
My editor just did a test on 5.1 and output to DVD and we do not see the problem. The current 5.1 has a checkbox on the P2 Import settings that says "Remove Duplicate Frames."

Does that mean that the current 5.1 does not have the problem? Or do we still need 5.1.1? And how much is it to upgrade to 5.1.1?

Kenneth
 
Kenneth said:
My editor just did a test on 5.1 and output to DVD and we do not see the problem. The current 5.1 has a checkbox on the P2 Import settings that says "Remove Duplicate Frames."

Does that mean that the current 5.1 does not have the problem? Or do we still need 5.1.1? And how much is it to upgrade to 5.1.1?

Kenneth


The upgrade is free from 5.1 tp 5.1.1

For those that need to upgrade to 5.1 its about $50 and you send your disks in. The turn around is very fast, like 2-3 days to get the new disks.
 
Back
Top