Eric Hansen.tv - Life at the Intersection of Color, Music and Beer
  • Facebook
  • Linkedin
  • Twitter
  • Rss
  • Blog
  • About
  • Services
    • Color Grading and Finishing
  • Clients & Press
  • Resources
    • Manuals
    • Misc Links
  • Research
  • Life
Search
Home» News » Upcoming H.264 Encoding Shoot Out

Upcoming H.264 Encoding Shoot Out

Posted by Eric Hansen - March 29, 2012 - News

I’m putting together a shootout between different software and hardware H.264 encoders. The planned line up:

Hardware:

– Elgato Turbo.264 HD

– Matrox MAX

– Blackmagic Design H.264 Pro Recorder

Software:

– Apple Compressor

– Adobe Media Encoder

– Telestream Episode

– Sorenson Squeeze

I’ll be looking for 2 things:

1. The fastest encoder with acceptable quality. This is a very frequent question I get, usually from editors and producers that need to get a rough cut on the web for review as fast as possible.

2. The best quality encoder, when time is not a factor.

Both of these will be weighed against cost.

As I run this test, what is most important to you? What formats do you typically have to deliver to your clients? Do you have to do a time code window burn? What specific things should I test or look at? Are there other encoders that I’m missing and should test?

Share this:

  • Facebook
  • Twitter
  • More
  • Google
  • Reddit
  • LinkedIn
  • Tumblr
  • Pinterest
  • Email

8 comments on “Upcoming H.264 Encoding Shoot Out”

  1. Dee says:
    June 14, 2012 at 6:06 pm

    I’m messing around with so many options out of these to try and figure out the easiest, fastest way to do a timecode burn with HD 1920×1080 footage. Please post results when you finish!

    • Hansen says:
      June 14, 2012 at 6:37 pm

      Hey Dee

      It’ll probably be a few more weeks until I post the test and results, but from my limited testing so far, I’ve had a lot of luck using Compressor along with the Elgato Turbo.264. Export the 1920×1080 file from Final Cut as a self-contained Quicktime file. Then in Compressor, use one of the Elgato presets and the Timecode Windowburn filter. Don’t use FCP to apply the windowburn – the export will take much longer than Compressor.

      This is one of the workflows I’m looking forward to testing more specifically, as it’s a very common deliverable. Also, I don’t typically deliver a 1920×1080 H.264 file. Even modern computers can choke on the playback. I usually give producers 720p files and they’re more than happy.

      • Dee says:
        June 14, 2012 at 8:42 pm

        Oh yeah, I’ve completely given up on FCP to burn the TC in a fast way. Nesting a sequence and exporting as H.264 still takes too long (faster faster! Instant gratification, yes please).

        I’ve tried self-contained export from FCP then -> Compressor with a TC filter on an H.264 setting (initially 1080p, then down to 360p. I could also Export using compressor with these settings and the TC), and I didn’t mind the time it took but for some reason compressor can’t deal with 23.976 (23.98) footage and starts the timecode burn at 00:59:56:10 (4 secs or so) before the actual TC start on my timeline which is 01:00:00:00. I haven’t figured out why that is yet, and I’m wondering if I export as 1080p50i it will correct.. Anyway, this is what led me to try TC burn other ways rather than from FCP or through Compressor.

        I’m going to try Elgato tomorrow. I have it, wasn’t able to test it out today. Will have to try what you suggested!

        • Dee says:
          June 14, 2012 at 8:46 pm

          Er I’m wondering if I export as 1080i50*** it will correct. Hopefully Elgato will be better, though I’d really like to know why Compressor does that!

          • Hansen says:
            June 14, 2012 at 10:33 pm

            I’ve never had an issue with the TC changing. Is your sequence 1080i50 or is it 1080p23.98? Export from FCP as “Current Settings”. if your sequence begins at 1:00:00:00, then the Quicktime in Compressor will begin at 1:00:00:00. If you’re changing the frame rate in Compressor, then it’s possible that the TC will change.

  2. Dee says:
    June 14, 2012 at 11:25 pm

    It’s an XDCAM EX 1080p24 sequence, start TC is at 01:00:00:00 in the Sequence Settings. The exports are all put out with “Current Settings”. TC on the sequence begins at 01:00:00:00, and shows as 01:00:00:00 when viewing the .mov with QT player 7. No framerate change in Compressor, I’ve set it both as Current framerate and 23.976.

    • Dee says:
      June 15, 2012 at 9:53 am

      Used Elgato through Compressor.. It took 45 minutes for a 45 minute interview. Nuts! I can’t even.. I’m so blown away. My Post Supervisor uses it, and I know it’s fast, but it’s one of those “see to believe” type situations. Still haveing the TC issue going through Compressor. Might lay down the TC in FCP then Export using Compressor Elgato settings.

      • Hansen says:
        June 15, 2012 at 10:13 am

        Hey Dee

        The Turbo.264 is an awesome device. Everyone has the same reaction the first time they use it. If you export a smaller resolution, it goes much faster. I’ve encoded 360p files at 300fps with it.

        If you’re using an AJA card, another option is to turn on the timecode windowburn output. It will place it over video live on output via SDI or Component. Then use something like the Blackmagic H.264 Pro Encoder to record the output live. FCP doesn’t have to render anything. It all goes real time in a single step. I used to do this all the time with DVD screeners using a DVD-R recorder. Many people don’t see the point of the BMD H.264 Pro Encoder, since they think software is better, but this is one of its great uses.

        All these options are part of the comparison article that’s coming.

Free Production Workflow Tips!

Popular Posts

Sorry. No data so far.

Categories

  • Apple, SANs and Post Production
  • Audio Sweetening
  • Clients
  • Color Grading
  • Featured
  • Movies Every Filmmaker Should Own
  • Music
  • Musings
  • News
  • Production
  • Rants
  • Reviews / Tests
  • SAN Installations
  • Super 8 Transfers
  • Travel
  • Tutorials

Latest Tweets

  • No public Tweets found

Statement of Use

Current Recommendations

Share this:

  • Facebook
  • Twitter
  • More
  • Google
  • Reddit
  • LinkedIn
  • Tumblr
  • Pinterest
  • Email

Get In Touch

  • Contact Us
  • flynsqurl
    • Twitter
    • Facebook
    • Email
    • Rss
(c) 2012 My Blog - Web Design by Jason Bobich
loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.