-
P2 Card issues
Hello Everyone,
I have a problem with capturing one of these shots that is panning across the ground. The problem is that the footage captures, but when I play it back it looks like it’s skipping. Has anyone experienced this problem and does anyone know the solution? Any help would be greatly appreciated. I have experienced other problems with the P2 card when footage comes in and looks like it was sped up, but I’ve already figured out how to resolve that problem. Unfortunately, that solution doesn’t work in this case.
Cheers,
Brad -
5 Replies
-
Perhaps you could post up an example with a link somewhere. That’s a little tricky to diagnose without seeing the footage.
-Noah
Unlock the secrets of the DVX100, Apple Color and now the HVX200!
https://www.callboxlive.com -
[wired2film] “I have a problem with capturing one of these shots that is panning across the ground. The problem is that the footage captures, but when I play it back it looks like it’s skipping. Has anyone experienced this problem and does anyone know the solution? Any help would be greatly appreciated. I have experienced other problems with the P2 card when footage comes in and looks like it was sped up, but I’ve already figured out how to resolve that problem. Unfortunately, that solution doesn’t work in this case.”
None of what you describe here is a P2 card issue. I’d bet fifty bucks you’re using FCP, right? What you’re describing is bugs in FCP, nothing to do with P2. Put the P2 card back in your camera and play the footage and it’ll play perfectly, right? Therefore it’s not a P2 issue, it’s an FCP issue.
Most people with complaints like this find that they can resolve them by un-clicking the “remove duplicate frames upon import” checkbox. If you really want to make all your problems go away, consider getting raylight from dvfilm.com; that’ll fix this and also make it so you never need to ingest footage again.
-
[Barry Green] “None of what you describe here is a P2 card issue. I’d bet fifty bucks you’re using FCP, right? What you’re describing is bugs in FCP, nothing to do with P2. Put the P2 card back in your camera and play the footage and it’ll play perfectly, right? Therefore it’s not a P2 issue, it’s an FCP issue.
Most people with complaints like this find that they can resolve them by un-clicking the “remove duplicate frames upon import” checkbox. “
Barry, if you’re going to make statements like this I think you really need to provide more detail. You know I respect your opinion and know you don’t make statements wildly, but for those with lesser experience this can be misinterpreted, and I don’t think it’s fair to FCP or the legions of FCP users that don’t experience these problems. I’m not saying FCP is perfect but I use it every day and shoot P2 every week and don’t seem to be encountering these issues on any of my four FCP systems…
[Barry Green] “If you really want to make all your problems go away, consider getting raylight from dvfilm.com; that’ll fix this and also make it so you never need to ingest footage again. “
good advice in general…
-
What he described is an FCP issue, plain and simple. FCP’s import window has caused issues over and over, and this wrong-frame-rate issue has been reported repeatedly. It’s well known, and as I said in the prior post, it is usually solved (AFAIK) by unclicking the “remove duplicate frames on import” button. What more info should I provide?
If FCP users don’t experience these problems, it’s because they’re going about things the “right way”; that’s all fine and dandy, but still — how can one characterize it as anything *but* an FCP issue, when the issue only occurs in FCP? You must identify the source of the problem before you can fix it. If someone thinks it’s a P2 problem, they’re barking up the wrong tree because the footage is solid.
This particular issue is a mistake on the user’s part only because it’s caused by the FCP import window not knowing intelligently as to when it should or shouldn’t remove duplicate frames. No other app even *has* an import window, nor do they even have an option to click or unclick anything about stripping duplicate frames upon import. Ergo, it is an FCP issue by default.
-
You can do what you just did and explain that this is a “user” issue… and that many users never experience this…
As for it being an FCP issue, we’re arguing semantics… what we do agree on is that it isn’t a P2 issue…
Reply to this Discussion! Login or Sign Up