John Pale
Forum Replies Created
-
Try the older XML versions. They should not contain anything specific to FCP 6.01.
-
You have to select in the bin the type of alpha you are using (there is a column for it). FCP often guesses wrong..though it supports all types of alphas.
-
Oh my. Sounds like you are introducing 3 different compression algorithms to your footage.
I’m not liking the sound of that. -
Re-read Walters posting.
USB 2 drives do not have the SUSTAINED throughput necessary for use with FCP, though their burst rate equals or exceeds that of FW400. Its the USB 2 interface thats the problem, not the drive (FW and USB 2 use the same drives)
This is likely to be the source of your problem.
-
In Avid your output settings in the Audio Tool are always global. In FCP, you can have different audio output settings for each sequence, because in FCP you can have multiple sequences open at the same time…not possible in Avid.
-
[mortimer heathcliff] “upon checking the file info on these clips, one rendered at 1280 x 1080 (the “Current Settings” version, which is what the sequence is), and the one where i chose the DVCPro HD rendered at 1920 x 1080. obvious discrepancy here, and just trying to nail down what will cause me the least amount of time and headache at the post house. again, starting with 1440 x 1080 HDV and 1280 x 1080 DVCPro HD (from HDCam original footage), also wondering if i really “gain” anything by rendering at 1920 x 1080 or should i leave it at 1280???”
I had this happen recently too. I was able to track it down to some animation files in the timeline….if I added a broadcast safe filter to them, thus causing FCP to read the render file instead of the original media, the timeline would export at the correct size. Not sure what was wrong with the original media..probably some weird Quicktime metadata bug…they were the correct size and codec.
-
Did you format the drive before using it?
Many drives come pre-formatted for PC using the FAT32 format. This is an old format and only supports files as large as 4GB.Erase and re-format the drive for MacOS Extended and you should be fine.
-
I read on another forum that MOTU is looking into ProRes support. It’s not due to be out for a while.
-
Check the audio output preferences for your sequence (not just your overall audio preferences).
If your sequence is set for multiple mono outputs (in Avid terminology “direct out” instead of stereo) you need to adjust the downmix settings or it will be very loud.
If your overall preferences differ from your sequence preferences you can expect different levels on output. Hope this makes sense.
On Avid, if you do your mix with your in direct out, but try to output in stereo, your levels will be very loud…similar concept.
-
Export Using Compressor does not use your FCP render files…it re-renders all your effects to directly to MPEG-2 (or whatever you are compressing to in Compressor), without first compressing to DVCPRO-HD.
This theoretically can produce a cleaner encode, but I have never been able to see a difference…certainly not enough of one to deal with the massively increased encode time.