Activity › Forums › Apple Final Cut Pro › Is this behaviour normal?
-
Is this behaviour normal?
Posted by Tony Sarafoski on May 19, 2012 at 11:38 amI jut finished editing a 2 hour multi-cam clip, and now need to export it to ProRes 422. It’s saying export time will the 2hr 11min. There’s no orange render line, and it’s being exported to ProRes 422. Is this normal?
Michael Garber replied 13 years, 12 months ago 4 Members · 11 Replies -
11 Replies
-
Carsten Orlt
May 19, 2012 at 12:50 pmThink of it as a file transfer. If I remember 1 hour of 1080 ProRes (not HQ) is about 60GB, so 2 hours is 120GB. If you copy 120GB from disk to disk it could take 2 hours depending on your disk speed.
So I think this is normal.
Could I be wrong? Any other takers?
Best
Carsten -
Tony Sarafoski
May 19, 2012 at 1:17 pmFunny thing is Carsten, I’ve never had the need to export to ProRes to transcode to another codec, I just normally send my project directly to compressor. However I experienced a really weird bug with multi cam, which I’ll post separately once I’ve extensively tested this found.
-
Tom Wolsky
May 19, 2012 at 2:46 pmIf you’re exporting to current settings, and ProRes is set as the render codec, then ProRes is what gets exported.
All the best,
Tom
“Final Cut Pro X for iMovie and Final Cut Express Users” from Focal Press
Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
Coming in 2012 “Complete Training for FCPX” from Class on Demand -
Carsten Orlt
May 20, 2012 at 12:18 amMea culpa, I misunderstood your question so Tom’s answer goes 🙂
Would be great to know what problems you had with multi cam.
Best
Carsten -
Michael Garber
May 20, 2012 at 1:30 amHey Tony,
Glad you posted this. I experienced similar behavior with my last export of a 20 minute PAL HD timeline. Perhaps it has something to do with PAL? I didn’t check how it was with my NTSC exports. Perhaps try something from 24p or in NTSC, if you have the footage.
Also, did you add any audio filters to your timeline? My PAL timeline had an audio filter which seemed to make the audio waveform take a really long time to render out. And it also said the export would take over 2 hours. But then it dropped down to just over real time. Which, as I mentioned was 20 minutes.
Perhaps it’s FCPX trouble ticket time? ;P
-Michael
Michael Garber
5th Wall – a post production company -
Tony Sarafoski
May 22, 2012 at 10:05 amTom, I’m we’ll aware this process, however correct me if I’m wrong, in FCP 7 providing the media in your timeline conformed to the timeline codec, exporting was a lot less than the length of the timeline, was it not? I no longer have 7 installed so I can’t test.
Anyone care to try this out. 2hrs of media on a timeline already transcoded to ProRes, Timeline coded needs to be ProRes, then export.
What’s the exporting time going to be in FCP 7?
-
Tom Wolsky
May 22, 2012 at 12:27 pmI think if you export a self-contained movie from FCP7 you will get similar performance going to ProRes.
All the best,
Tom
“Final Cut Pro X for iMovie and Final Cut Express Users” from Focal Press
Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
Coming in 2012 “Complete Training for FCPX” from Class on Demand -
Tony Sarafoski
May 22, 2012 at 12:56 pm[Carsten Orlt] “Would be great to know what problems you had with multi cam.”
Basically what happened, I was editing a 2hr long two camera edit (using multi cam), and when I finished the edit, I sent it directly to compressor so that I could encode it to MPEG-2.
As per normal once I send a project to compressor, I add the MPEG-2 and AC3 preset, adjust the bit rate and submit.
I’ve been working with FCPX since 10.0, and this workflow has worked flawless, till now.
When I authored the DVD and tested it back on a DVD player, there was no audio. I opened FCPX, and sure enough the audio was there. So where did I go wrong!
Well there seems to be a bug when you edit multi cam from a captured HDV or DV tape. By sending your project directly to compressor, for some reason the audio renders blank.
For my own sanity, I decided to test the same project, but this time added a H.264 & ProRes presets, and sure enough the audio rendered just fine.
This clearly is a bug, as I have been collaborating with Michael, and he too experienced this same problem last week when using multi cam on DV footage. What we are not sure of, if its a FCPX bug or compressor.
I believe Michael has already reported this to Apple and has had contact, so hopefully this gets sorted in the next release 🙂
-
Tony Sarafoski
May 22, 2012 at 12:57 pmHmm.. now you’ve got me curious, might re-install 7 and give it a go.
-
Michael Garber
May 22, 2012 at 4:03 pmI am testing it at work right now. If I export a 2 hr prores 1920×1080 timeline on my Mac Pro 3,1 to the same drive as the media, FCP7 is saying that it will take 36 minutes. I am going to leave it exporting and will report back if FCP7 is incorrect.
The files have no effects or filters on them, so no need to render anything. Export is set to make movie self contained. I am running a Mac Pro 3,1 with 16GB of RAM.
After this test, I’m going to set FCP to “re-render all frames” to see if that is more in line with FCPX. I agree with Tony on this that it seems to be a bug in X. Or, if not a bug, just a lousy thing that it should take this long to render.
Michael Garber
5th Wall – a post production company
Reply to this Discussion! Login or Sign Up