Embarrassing export times/computer performance

[James Cude]

From which format are you sourcing from and to what format are you exporting? Magic Bullet and stabilization often result in fairly long render times and also exporting to Compressor is slower because it’s 32-bit CPU rendering vs 64-bit GPU direct in FCPX. Also to what settings- if frame controls are cranked- will also take forever to render. More details please…

[Petter Stahre]

While I don’t know what causes the bad usage of your CPU I have found a way to use Compressor that is much faster (if using Compressor is an option for you?).

I first read about this here on the Cow and think this might be The Holy Grail of compression workflow. I started using it after I was annoyed with how long compression took when using the Keyer and other FCPX-effects.

Workflow: Send your job to Compressor, set up an export to ProRes, chose “Job/New Job With Target Output” and then choose the final format&compression you would like.

This means a ProRes is first created, and then Compressor is using it to calculate the next (final) job.

For me this has cut compression times with a factor between 3-6x, when the final format is using H.264.

It seems like if Compressor has to much to think about at a time everything goes slow instead 🙂 But if you let it concentrate on first building a proper full sized ProRes, and then compress&downsize&… it gets much faster.

Sorry if this isn’t a workflow you can use (or if you already know about it), it just made my life so much easier when I started using it I had to share 🙂

(I still would expect Magic Bullet effects to take some time to render though.)

Best,
Petter

[Adam Chesbrough]

Timeline: render settings
original: 29.97, H.264/MPEG-4 AVC format (from nikon D600)
compressor settings: H264, 1920×1080, settings are attached.

My normal encode process is to export master file (ProRes 422) and then encode in compressor afterwards, this drastically cuts down the time, that being said I was having relatively good export times using the built in share method. Below is some test settings that I ran in the past concerning export methods. I have never attacked the issue from a computer CPU/disk R/W stance before. Just built a new 6 core mac with GTX670 and RAID0 (250/300 R/W), will test the export with this and reply:

okay, just did some testing in the name of science/procrastination (what I thought was true held…true):
-Media: 15 second clip, H264 (5D)
-effect: FCPX loops_glory
-computer: MBP 2011 17″, 8GB RAM, 2.66GHz i7, NVIDIA GeForce GT 330M 512 MB
-software OS Lion, FCPX 10.0.3
-Encode settings: 1080 sharing preset

Processes
1. While in FCX, send project to compressor X and encode
Total Time: 12 minutes
2. Render in FCPX, export as contained/current settings (time is marginal), encode in compressor X.
Total Time: 4:40 (2:20 render and 2:20 encode)

okay, this might have something to do with the effect being graphics intensive (albeit nothing compared to some of the stuff that I use) and my graphics card is weak. I would be interested to see what times other people are getting with these two processes. I learned that the second was far faster in FCP7 on a blog awhile back and have never used process 1 again. This was only a 15 second clip!!! Also, having a render timeline is nice as I like to export as contained prores so that I can use the edited footage in another project later.Basically FCPX continues to disappoint on all levels with the exception of organization which is far superior, so much so that I am forcing myself to use it. It would be great if I could create a macro to run process #2, BUT THAT SHOULD BE APPLE’S JOB. Below is a link to download the clip I used if anyone else wants to give the test ago and share their results (I used the first 15 seconds)…faster GPU anyone?https://dl.dropbox.com/u/605116/MVI_9428.mov.zip

macbook pro 17″ i7, 8GB RAM
2 RAID 0 esata external HD 7200RPM

Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

OWC 4TB RAID0 (using esata)
Tempo SATA Pro ExpressCard/34 (6Gb/s)
Echo ExpressCard Pro Thunderbolt Adapter

[Adam Chesbrough]

Excellent. My normal process was to export master and then drag into compressor (same thing but two part process, also involved me waiting around the computer). Great insight that I will certainly use, thanks

Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

OWC 4TB RAID0 (using esata)
Tempo SATA Pro ExpressCard/34 (6Gb/s)
Echo ExpressCard Pro Thunderbolt Adapter

[Adam Chesbrough]

Is there anyway to save this process within the export settings or within compressor?

Macbook Pro Retina: 2.6GHZ i7, 16GB RAM 1600MHz DDR3, GT 650M 1GB RAM

Hackintosh (Sandy Bridge): i5 2500, 16GB 1333MHz DDR3, Nvidia GT640 2GB RAM

OWC 4TB RAID0 (using esata)
Tempo SATA Pro ExpressCard/34 (6Gb/s)
Echo ExpressCard Pro Thunderbolt Adapter