Tag Archives: audio

FPS Bug in Adobe Media Encoder CS4

Adobe Media Encoder CS4 (AME) is a stand-alone app that comes with Flash CS4 and After Effects CS4. While it has the ability to do batch encoding and HD h264 .f4v’s (basically a .mp4 file in a flash wrapper), with its clunky interface, limited pre/post-processing options and odd bugs, you’re better off using full-featured encoders like Telestream’s Episode or Sorenson Squeeze. For those on a more limited budget though, AME  is usable. With that said, the most recent update to AME, (11.10.2009) introduced a bug where you can no longer properly encode .flv’s at 15fps on OS X systems.

It’s a bug, Jim

AME 4.2 supposedly fixed deinterlacing if Max Render Quality was set for interlaced sources. Instead, the clip looks like it was possibly encoded at 15fps but is playing at 29.97, interpolating “missing frames.” I thought it was a playback issue, but I had encoded a sample clip earlier with AME 4.1 and using the same flv player, in this case VLC, you could still see a difference between the two clips. Here are two sample clips, one encoded with AME 4.1 and the other with AME 4.2. Take a look and you decide:

Video encoded using AME 4.1[flv:/movies/1-ame-4_1.flv 382 288]

Video encoded using AME 4.2[flv:/movies/2-ame-4_2.flv 382 288]

Although it’s not as obvious at this frame size, at 640 x 480, you can see how much sharper the image looks in the 4.1-encoded clip and the weird interpolating in the 4.2-encoded clip.

Solution and Workarounds

The current solution is to stick with 4.1. Already updated AME to 4.2? You have a couple of options:

Uninstall AME – Unfortunately, this is easier said than done: AME is a shared component, which means you have to uninstall every Adobe software that uses it. This is a royal pain for those with tweaked out preferences and/or using a Creative Suite. And don’t bother using AppCleaner; you’ll still be forced to re-install the “main” software (Flash, After Effects, Premiere Pro, etc.).

Use Leopard’s Time Machine to restore from an earlier point – This is the easiest solution, assuming you’ve been maintaining regular backups of your system. I recommend renaming the current Adobe Media Encoder CS 4 and then restoring to a version before 11/10/2009.

Copy AME 4.1 from another system – Fortunately, the AME app contents is self-contained within the Adobe Media Encoder CS 4 folder, so you can copy it from a another system that hasn’t updated to 4.2 yet. Rename or delete the 4.2 folder before you copy it over though, to make sure that you’re not mixing 4.1 and 4.2 stuff.

Another option is to encode straight from one of the “main” programs, in my case, After Effects. The disadvantages of this is that you no longer have access to to 2-pass VBR and longer encode times as the file has to also get rendered, unless you pre-render the clips and then set up the render queue to then encode them.

I must be the only one that’s seeing this bug because I couldn’t find any related posts either on the Adobe site or from a Google search, but I’ve posted this stuff in the hopes that it may help someone else and reduce their frustration with Adobe support. Note to Adobe:

  • include a bug report link on your support pages.
  • include support pages for the shared components like AME. It’s not worth posting on the forums if I don’t know where to post it in the first place and reasonably get feedback.

Has anyone seen this bug? Leave a comment.