Skip navigation

Trying to shorten export time

385 Views 7 Replies Latest reply: Apr 8, 2013 2:49 AM by fox_m RSS
elmerlang Level 1 Level 1 (0 points)
Currently Being Moderated
Apr 6, 2013 9:41 AM

Been trying to export 1920x1080 using h.264 codec for posting on web. I first set up my own Export but took 8 hrs to finish 35%. Been looking at the Apple Devices 720 or 1080 options now. I switch options from Apple Device to Web Hosting but there's no indication of changes in size changes the size and therefore length of time to export (generally). Tho Apple Devices produces a "protected MPEG-4" movie and Web Hosting a "Quicktime" movie.


Any suggestions on choices for export?


Has anyone had problems withi export time and then solved them? If so, how?


Any other tips appreciated.

MacBook Pro 2.66 ghz, Mac OS X (10.6.4)
  • Russ H Level 6 Level 6 (12,880 points)
    Currently Being Moderated
    Apr 6, 2013 2:46 PM (in response to elmerlang)

    All things being equal, exporting the same format (including resolution) as your project should be fastest.( Pro Res exports faster than h.264, but when you say post to Web, I'm guessing you mean YouTube or Vimeo and PR may not be the best choice for them.) For an h.264 export. I'd choose one of the Vimeo or YT presets.


    If you are anticipating a full day for an export then I would say something is wrong …unless your project is in the range of say, 8 -10 hours long.


    What model is your MBP? And are you really running 10.6.4?



  • Russ H Level 6 Level 6 (12,880 points)
    Currently Being Moderated
    Apr 7, 2013 8:17 AM (in response to elmerlang)

    I have the same model MBP and I agree that 2 1/2 hours for a 40 minute h.264 export is reasonable. (The new MBP's, BTW, are considerably faster.)


    IMO, the most reliable way to export to Vimeo et al is to output a master file and use the video service's uploader.


    If you're planning to do a lot of these projects, consider Compressor, which gives much more control than FCP.


    Good  luck.



  • Ian R. Brown Level 6 Level 6 (17,460 points)
    Currently Being Moderated
    Apr 7, 2013 8:20 AM (in response to elmerlang)

    It's probably best to ignore Vimeo/Youtube and create a video on your desktop etc. whereupon you can decide exactly what you want to do with it.


    There is no advantage in using the Vimeo/YT settings but there are potential problems as you discovered.


    Incidentally, a couple of hours plus for a 40 minute project is probably the best you will achieve on your MBP.


    What was the quality like?

  • Ian R. Brown Level 6 Level 6 (17,460 points)
    Currently Being Moderated
    Apr 8, 2013 1:23 AM (in response to elmerlang)

    Not that it matters now, but the old legacy Compressor 3.5 and earlier can be used with FCP X.


    You can't access its presets directly from FCP X but you can export a project as a Master File and  manually drop it into legacy Compressor and encode using any of its presets.

  • fox_m Level 4 Level 4 (3,335 points)
    Currently Being Moderated
    Apr 8, 2013 2:49 AM (in response to elmerlang)

    My workflow for a YouTube project is:


    Completely render the project before exporting.


    Export to whatever the current codec is set for (so... just Export with current settings), typically ProRes 422(HQ) [my general preference established when creating a project] or sometimes ProRes LT and if necessary, ProRes 4444.  It really doesn't matter, when the project is completely rendered and exporting to a ProRes format, the export is about 1/5 to 1/2 run time (about 2 - 5 minutes for every 10 of video -- probably dependent on your storage bandwidth.)


    Exporting H.264 for YouTube of Vimeo straight out of FCPX is *absolutely pointless* since FCPX does not offer any quality options (always exports highest quality H.264) and YouTube and others are just going to recompress down to their limit anyway.  I never give YT that opportunity...


    I use Quicktime 7 Pro (about 100,000 times easier than compressor [hyperbole]) to transcode to YouTube specifications. The maximum bandwidth YT will "place" is 5Mbps... so I transcode to, at most, 5Mbps.  Turn on Auto Key Frames; Turn off Frame Reordering; Data Rate Restrict to 5000 kbits/sec; Optimize for Streaming; Compressor Quality (max available) to High; Encoding to Best Quality (Multi-pass).  For the Size options, I use the HD settings from the top section (anything below the start of NTSC will create broadcast tv "safe" video [overscan] and will not be completely compatible with digital targets such as YT [it will be smaller].) I also set Preserve Aspect Ratio Using Letterbox (YT used to have problems with 1920x1080 video being a little "squished" vertically to compensate for the transport controls... probably just habit now.)  Audio: Format AAC; Sample Rate 48000; Variable bit rate ~192kbps. And check the Prepare for Internet Streaming checkbox and select Fast Start.  Except for the variable bit rate audio and the letterboxing stuff, these are the specifications YT put down in its documention.


    Converting from the ProRes output from FCPX to the H.264 for YT in QT7Pro is actually faster than trying to export H.264 directly out of FCPX (and compressor for that matter...)




    I find if you simply change the m4v filletype to .mov, you don't need all the web page stuff that gets generated, you can simply load the video up in a browser from a direct URL.  Exporting to Apple Devices is a quick way to transcode 1080 out of FCPX to the smaller sized 720 video when necessary.


    Here's an example of an .m4v Apple Devices video with the filetype manually changed to .mov:

    Will it upload to YT? Yep: here's the proof: (but this one has no audio -- be very careful about the audio settings of what you upload to YT... they don't like Linear PCM [AIFF, WAV, etc... YT wants AAC])





More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.