Sean Oneil
Forum Replies Created
-
[JeremyG] “If I were you I’d bite the bullet, rent a dv50 deck for the day and recapture. Save you soooo much work and rendering time.”
Thanks but its all good. We still have systems with version 5. Worked fine and just barely made FedEx.
Sean
-
I’ve done more testing and confirmed it. It has nothing to do with the project file, or the hardware.
Good news is that it looks like this only happens with DV50 footage captured in FCP5. Another good thing is that there is a workaround.
If you export the clips as self-contained and then re-import, the problem goes away.
I was using “Export -> Quicktime Movie”, “current settings”, “self-contained”, and did NOT have “recompress all frames” checked. So it was a lossless export of cuts-only video that did not re-compress anything. And it fixed it.
In additon to the actual movie, Quicktime files store metadata which contains information like timecode, field dominance, aspect ratio, etc. My theory is that the way FCP 5 creates this data is different than the way FCP 6 creates it. And of course that FCP 6 does not properly interpret what FCP 5 creates. At least not with DV50 NTSC footage captured from an AJ-1200A.
So be careful. It is very hard to see. You need to look carefully on a broadcast monitor and you might not even see it unless there is a smooth and slow camera pan.
Sean
-
[IndieSoon] “So I was glad to find a post that suggested that I go into system settings > effects handling > turn 8 and 10 bit uncompressed to “None” which is a great idea (why should FCP handle the Uncompressed BM files anyway?) After changing the effects handling for 8 and 10 bit to “None” it still didn’t end my final cut crashes. I guess this works with Decklinks, but I have a Multibrigde.”
Actually Uncompressed files are Apple, not BM. And you want FCP to handle them or else you won’t get RT Effects. Only the 4:4:4 codec is BM. Other than that BM codec is legacy.
I don’t know what your issue is. But after this an many other issues, I think its safe to say that people should not upgrade to FCS2 until they release an update that fixes the numerous issues.
Sean
-
Sorry I don’t know. Until FCP6/BMD6.2, I haven’t had any problems with any drivers since getting Final Cut 5.1.
Sean
-
[Jan Crittenden Livingston] “Horrible stuttering sounds like someone that is shooting video style with the camera set to 24P. What were the setting on the camera?”
No, the camera was not set to 24p, and that’s not what the problem is like. It’s like it skips a frame every few seconds. Even if it was that wouldn’t explain why it plays fine on Final Cut 5.
Sean
-
[CharlieX] ”
Don’t have 6 yet, but sounds like the fields are being displayed out of order? I’ve seen this when a Flame captured footage on Field 1 when it should have been capturing 2. The slightest, hard to nail down stuttering…. you think you’re crazy at first, but it’s there.”This sounds like the best description of it. It’s VERY subtle and very hard to see. But its not the kind of thing you could let go of either. No way could you deliver something with that issue going on.
I’ll check the field dominance tomorrow morning.
Sean
-
I’d love to test it out capturing w/ v.6, but we sold our 1200A.
I guess I could capture Kona/Blackmagic and encode to DV50. See if the problem is still there.
If someone reading this has DV50 footage on there Mac with FCP 6 installed, please check this out. If I’m the only one who sends them feedback over this, I’m sure it will be ignored.
Further info. It was captured using firewire option on a Panasonic 1200A to FCP 5.1.4. The footage was shot in 29.97 mode (no pulldown) and was anamorphic.
-
It’s a more than a speed bump. The Intel Core 2 is much more powerful than the G5.
You can connect another monitor to it if you don’t like the screen.
HDCP is required for playing copy protected Blu-ray and HD-DVD. The monitor must also be HDCP compliant (Apple Cinema Displays are not BTW). There’s no OSX software for playing back commercial HD discs (Leopard will have it), but if you wanted it right now you could run Windows and use an external BR or HDDVD drive. Without HDCP you could never do this.
Sean
-
[Borjis] “I have found after testing that the topmost ProRes is HQ
and the ProRes on bottom is non-hq.”Thanks, that’s good to know. I assumed they were the same codec, just a different setting on the quality slider.
Sean
-
[COW Articles] “Able to run on computers without FCP 6 installed. You can use ProRes in other current QuickTime-aware applications–as long as they’re on a machine that also has FCP 6.
I read this in quite a few posts. To which I say, Really? It’s not just a codec you can install on, say, your After Effects machine on the desk next to yours that doesn’t have FCP 6?
Or do I misunderstand? Perhaps you mean that the codec doesn’t work with earlier versions of FCP. I wouldn’t expect this, for the rest, maybe I’m missing something. I welcome your corrections and clarifications, posted in the COWmunications forum.
“
I copied the ProRes Quicktime Component to another G5 that did not have FCS2 installed. Long story short, it works but be careful.
It works just like any other QT component. You can encode and decode ProRes using any QT app.
I made a custom Easy Setup for Final Cut 5 using ProRes. NTSC. The machine had FCP 5.1.4 and a Decklink Extreme card. Capture and playback functioned just like any unsupported QT codec would in Final Cut. However, when playing back, the field order was screwed up on the broadcast monitor. There were nasty interlacing “artifacts”.
I could have messed up on the Easy Setup. I really don’t know what was going on. But it was ugly. The test machine was then upgraded to FCS2 so I didn’t test anything else (QT Pro Export, Compressor, etc.).
All I can say is that there are no restrictions locking it to FCP 6. But it still may not be usable.
Sean