-
Any known issues with QT or FCP QT which may cause rendering???
Recently I’ve had two different client working FCP 5.1 and the QuickTime’s they’ve produced have sequence compatibility issues.
Let me explain
Client export a sequence using EXPORT/QUICKTIME MOVIE. They have selected “current setting”, “make movie movie self contained” and “recompress all frames” turned off.
Once they’ve exported their movie, the FCP QT wont drop back into their native sequence without rendering. All of the properties from “Clip Analyze” and QT file info appear matching to the sequence, but something in FCP wants to render.
Keep in mind they are using “Easy Setups” and they have Trashed Preferences.
Also this same issue would happen when using QuickTime Conversion.Has there been any known QT or FCP bugs which may contribute to this issue?
Thank You for Your Time
Marcus -
7 Replies
-
I have seen FCP make quicktimes on capture that aren’t the right frame rates… for example- easy setup for whatever compression at 23.98— I find the file on the drive and open it up in Quicktime. I then check its properties and see that it is 23.66 or 23.78… this is random and always changing- it can happen at 29.97 as well- This may or may not be your issue since I haven’t seen the sequence have problems- do a batch conform on the clip in cinema tools and see if everything is cool-
jw
Post Production Specialist
The DR Group
Los Angeles, CA -
[jordanwwoods] ” I then check its properties and see that it is 23.66 or 23.78″
This is the frame rate that Quicktime reports and is inaccurate. Only judge from the browser within FCP. Quicktime has some crappy frame rate code somewhere that has never been fixed.
For the original poster, there has to be some settings that you are missing on either your export or your timeline.
Jeremy
-
Thank you for the timely response
One client was working in 720p 23.98 and the other client 1080 29.97.
Separate clients on separate systems producing this QT issue when bring the footage back into FCP.
They both exported small clips and no issues, but when it came to exporting a larger sequence then this issue occurred.
The export QT wont drop back in without renderingThe clients are not performing any frame rate conversion in FCP.
All the QT properties appear correct and the sequence setting do match the exported QT.
But something is telling it to render.Any other ideas???
Marcus
-
[marcus] “but when it came to exporting a larger sequence then this issue occurred.”
How large is large?
I’d like to test this out.
Jeremy
-
First Client was working in 720p 23.98 DVCRPROHD and the program was about 10min in length.
No fance graphics or transistion, pretty basic.
Exported 30sec clip as a test and it worked fine in the sequence.
Full 10min program and you get the render bar of deathSecond Client was working in 1080i 29.97 Uncompress 10bit 20min length.
Some graphics and basic transistion.
Exported 40sec clip as a test and it worked fine the sequence
Full 20min program and you get the render bar of death.Would love to know your result.
Thank you for timeMarcus
-
Hey Marcus, am I wrong or did you not say that you’ve got “make self-contained” checked off? That’s what your post said, but the use of commas was suspect.
Anyway, the answer is pretty obvious. It must be self contained. Otherwise you’re importing a reference movie. A movie that links to other movies. There’s no limit to what it could be referencing. FCP doesn’t support realtime reference files. Too many layers of data for real time. It’d have to access not only the quicktime file itself, but on top of that QT would also have to access it’s own reference. A sequence is essentially a big reference file itself.
Here’s hoping this helps, but I may have misunderstood your post.
-
Make Self Contained was checked on…..my bad on the previous post.
Recompress was turned off.
The above problem hashappen recently with two client from two different systems.
I’m trying to see if it’s random FCP voodoo or a bug.
Thanks for your input.Marcus
Reply to this Discussion! Login or Sign Up