Paulo Jan
2
COW Coins
Forum Replies Created
-
Silly question: how do you know that the DV-PAL codec is horrid? Are you watching the result using Quicktime Player on the Mac? Because QT Player, by default, shows DV-encoded videos in low quality, and it indeed looks awful; you have to go to Window/Movie Properties/Video Track (the wording of the options might not be exact, I’m going from memory) and enable the “high quality” checkbox to see how it will really look like.
Excuse me if you already know this or it has nothing to do with your situation. It’s just that I’ve seen this mistake bite *a lot* of people.
-
Don’t know about FCP, but in the case of the 404 error, the HTTP spec describes several responses that the web server can send to the browser. The “OK” ones start with 2 (“200” = “OK, I’m sending you the page”), the 30x’s I don’t remember right now what they mean (though “302” is a redirect to another URL), and the errors start all with 4 (“401” = “access forbidden”). So… I don’t know: my hunch is that it would be very contrived if someone had carefully written the spec (including the organization above) just so that the 404 error matched a specific room number, but I don’t actually know one way or another.
-
720×486, 720×480 has lower-field first interlacing.
That would be if it’s DV, but not necessarily if it’s some other kind of SD format. For example, I thought that Betacam was always upper-field first?
-
You should have a folder called “Thumbnail cache files” (usually in the same place than your render files, autosaves, etc.). In it you’ll find 2 files called “Final Cut Pro Thumbnail Cache” and “Final Cut Pro Thumbnail Data”. He’s telling you to delete those (or move them to the desktop, if you’re scared of deleting stuff). Of course, do this with FCP closed.
-
The screenshot Shane posted is from the “Log and Transfer” window in FCP 6, not 5.
IIRC, FCP 5.0.4 had all kinds of trouble trying to import P2 files by itself. When we used it, we had to use P2 Log to log and export the files to Quicktime, then import the XML files into FCP.
-
Yes, no and no. However, I have read Mark Christensen’s “After Effects Studio Techniques”, which I’ve been told is the best book around for AE, and from which I learned the blur chroma channels technique I mentioned above. Since it wasn’t enough to solve my problem, I came here looking for further advice. I’ll now go and have a look at Andrew Kramer’s tutorial.
-
You can find those codecs at Avid’s website. Look for “Avid codecs LE”, or “Avid Quicktime codecs LE”, or something like that.
-
But Primatte RT, as it name says, is a simplified version of Primatte that is less processor-intensive, so that it can work in real-time. The tradeoff, of course, is that its keys aren’t much better in my experience than the ones using FCP’s own Chroma Keyer.
-
It’d had been better to rip them with uncompressed (PCM) sound. FCP needs to render sound when it comes in a compressed format like MP3.
-
In my experience, every time this has happened has been because the filename (the name you’re giving each clip while logging) was too long. It’s very frustrating because it’s not consistent: sometimes it will log and import happily clips with long names, and other times a name of just 20 characters will make it spit the red “!” sign. Personally, in those cases, I just give the clip a single-letter name, and then, once imported into FCP, I rename it.