Skip navigation
Currently Being Moderated

Adobe Media Encoder cs5 - No audio

Jul 24, 2011 3:56 PM

I am using Adobe Media Encoder cs5 version on a Windows XP Service Pack 3 32-bit machine.  None of the wmv or avi files I try to encode have the audio track encoded.  I have tried encoding with both the "F4V - Match Source Attributes" and "FLV - Web 640 x 480" presets.  Neither of these encode the audio output at all.  The audio track plays correctly in Windows Media Player.  Has anyone else had this problem?

  • Currently Being Moderated
    Jul 24, 2011 4:17 PM   in reply to wayne.allen

    If you're starting out with .wmv and .avi files, my best guess is that the audio codec in those files is one that AME simply can't work with.

    Mark as:
  • Currently Being Moderated
    Jul 24, 2011 10:37 PM   in reply to wayne.allen

    Yes, AME can read PCM audio inside of an AVI file.


    How are you playing back the F4V or FLV?  Can you post a sample for us to examine?

    Mark as:
  • Currently Being Moderated
    Jul 25, 2011 5:44 PM   in reply to wayne.allen

    Thanks for posting the clip.  That file transcodes to F4V and FLV successfully, audio included, on my Windows 7 x64 machine.  The resulting files play back audio as expected in After Effects, Adobe Media Player, and VLC.



    1. Do the resulting files report as containing an audio stream?  What are the parameters?  In VLC, choose Tools > Media Info, Codec Details tab.  The Project panel info in Premiere Pro or After Effects can also tell you this, as can applications like MediaInfo.

    2. Are you changing the Export Settings in AME at all, or are you only using the presets as described in your first post?

    3. Try a completely different file.  Try a different format, like QuickTime, WMV, or MPEG.  Does AME transcode the audio from that file?


    The goal of question #1 is to determine if AME is having problems writing the audio on your machine.  If isolated to this cause, there may be a system conflict or a problem with the AME application.  Removing competing codec packages or reinstalling AME may solve this problem.


    The goal of question #2 is to make sure that this problem is not user error.  User education may solve this problem.


    The goal of question #3 is to isolate the problem to a particular file type or file property.  This may indicate a problem similar to question #1.

    Mark as:
  • Currently Being Moderated
    Jul 26, 2011 11:53 AM   in reply to wayne.allen

    So if there is an audio track in the F4V file, let's take the next step and check to see if there's anything in it.  My preferred way to do this would be to drop the file into Premiere Pro and examine the waveform.  Do you have Premiere Pro CS4, or a comparable application that can read F4V files, installed?  Premiere Pro CS5 and CS5.5 require a 64-bit version of Windows 7 or Vista, and you're only on Windows XP 32-bit.  If you have access to a 64-bit machine, you could download the trial of Premiere Pro CS5.5.


    You could also use an audio editing application like Adobe Audition or maybe Audacity to look at the waveform. Worst-case scenario is to use the audio meters or audio visualizer in VLC or Windows Media Player to see if they are representing audio, but that doesn't give me as much confidence as viewing the waveform.


    Note that an M4V file, by definition, does not contain audio.  (M4V = MPEG-4 Video)  An MP4 file, on the other hand, should contain audio.


    Try an experiment: Pick one known good source file and use AME to export to a variety of outputs: AVI, QuickTime, H.264, and MPEG2 (the plain version, not the DVD or Blu-ray variants).  Also do audio-only formats, MP3 and WAV.  Which, if any, of these formats contain audio?


    Assuming that none of them do, because the direction this problem appears to be headed is an overall failure of AME to encode audio, let's look at remediation procedures:

    1. Clear the AME preferences.  Quit AME, then go to C:\Documents and Settings\username\Application Data\Adobe\Adobe Media Encoder\ and move the 5.0 folder to the desktop.  Start AME and test the problem.  If the problem is solved, trash that old folder.  If it is not solved, put the old folder back where it came from (replacing the fresh one that AME created).
    2. Clear the Adobe media cache files. Quit AME, then go to C:\Documents and Settings\username\Application Data\Adobe\Common\ and delete both the Media Cache and Media Cache Files folders.  Start AME and test the problem.
    3. Uninstall and reinstall AME.  For AME, actually, that means uninstalling and reinstalling the host application, such as Adobe Flash Pro.
    4. Uninstall any third-party codec packs, such as K-Lite.  Such multi-codec packs have been known to interefere with normal operation of the A/V codecs on the system.
    Mark as:
  • Currently Being Moderated
    Jul 28, 2011 11:18 AM   in reply to wayne.allen

    Very interesting data, Wayne.  Very interesting.


    > I am not sure how to encode to the other formats using AME, so I could not complete these tests.


    Sorry, that's my fault.  Ignore that test.  I didn't realize you are using the Web Premium suite.  The other formats I referred to are only available if you have Premiere Pro, After Effects, or the Production Premium suite installed.  (I knew this by subconscious deduction, actually, since those products require a 64-bit version of Windows 7 or Vista and you stated that you're on XP 32-bit.  It just didn't trickle out to my conscious brain.)


    Let's back off for a second and review what we know.  Please correct me if I'm wrong about any of these points.


    1. You have WMV and AVI source video files.  The audio in the AVI files is encoded as PCM or MP3.
    2. You can hear the audio in these files when you play them in Windows Media Player.
    3. Encoding these files to FLV, F4V, or H.264 appears to complete successfully in AME CS5.
    4. You can not hear the audio of the encoded files in Windows Media Player, Adobe Media Player, or VLC.
    5. Inspecting the encoded files in VLC and Audacity shows both that an audio track exists and that there is a waveform in that track.
    6. Using a different user account on the same machine does not exhibit the problem.
    7. Encoding your source files on a different machine using AME CS4 (your colleague) or AME CS5.5 (my computer, with the sample you posted) does not exhibit the problem.


    So, yes, this is most intriguing.  The difference in your ability to hear your source files but not the encoded files is most curious.


    I do wonder:

    • If you take one of your encoded files to a different machine, does the audio play? (If you post a sample, I'll try it here.)
    • Since Audacity shows a waveform for the encoded files, can your hear the audio in that application?


    The only thing I can think of that is unique about the formats that you are using AME to encode to (FLV, F4V, and H.264) is that those formats all use compressed audio.  MP3 in the FLV format, and AAC in F4V and H.264.  (FYI - F4V is simply H.264 insided of a Flash video wrapper.)  What could be unique under your user account related to that?  I don't know.  Possibly if there is a utility on your machine related to compressed audio, that might be intercepting the audio stream in some way.  Do you have any software designed for capturing compressed audio from the Internet?  Or it could be related to the audio card drivers on your machine.


    It might be worth sniffing around the %appdata% folder on your account and temporarily disposing of the folders for other programs.  If you can isolate something that way, you may be on the right path.


    You might also want to run msconfig (Start > Run > msconfig) to disable background applications and services that could be hijacking the audio.  Go to the Startup tab there, clear everything, reboot, and see what happens.  If that works, start putting the services back one-by-one until you find the culprit.


    Mark as:
  • Currently Being Moderated
    Jul 29, 2011 11:32 AM   in reply to wayne.allen

    Glad the problem is solved, Wayne.  Wish I had a good explanation, and I would be tempted to isolate the problem further, but if all is working now then best not to upset the spirits in the machine.  Just remember to occasionally sacrifice a floppy disk in their honor to keep your computer in good working order.

    Mark as:
  • Currently Being Moderated
    Aug 19, 2011 11:52 AM   in reply to Tim Kurkoski

    I am having the same issue. WIndows 7 64bit machine


    It is happening to both recently (today) encoded files and ones form more than a year ago. Those older files I know have sound on them.


    These file splay back fine on my laptop(same operating system) but not in my editing machine.


    I do have soud when playing wmv and avi source files in windows player.


    just no flash video sound

    Mark as:
  • Currently Being Moderated
    Dec 2, 2011 12:12 PM   in reply to wayne.allen

    I am having this same problem with the make version of the software. Is there any ideas on the Mac version? Most things I convert has no audio.

    Mark as:
  • Currently Being Moderated
    Mar 14, 2012 6:19 PM   in reply to creativemagma

    Has anyone come up with a solution, or any ideas, about this problem on Macs? I've upgraded to the latest version of Media Encoder. Starting with an .avi file. Video is fine, but no audio. I looked in VLC, as someone suggested earlier in the thread, and audio appears to be there. But the audio won't play, not even in VLC. I'm not sure what to use in place of Media Encoder, if this won't work.*

    Mark as:
  • Currently Being Moderated
    Mar 4, 2013 8:27 AM   in reply to teryg

    I have the same issue on my Mac with CS5 and CS6. Any answer yet?

    Mark as:
  • Currently Being Moderated
    Oct 1, 2013 11:12 PM   in reply to wayne.allen

    There seems to be an audio glitch in CC.


    I recently spent a few hours of headache trying to figure it out. When I exported the project, one of the audio layers WOULD NOT export. It wasn't muted, and there was nothing funny about it.


    There have been two work arounds noticed until this glitch is fixed. I can verify that both work for the time being. I'm not saying everyone here's problems is the same, but this worked for me and my export:


    1. Copy and pase all of your clips/media into a new sequence. It can be the exact same sequence settings, but for some odd reason, exporting from the new sequence doesn't have the problem.


    2. Do not use Adobe Media Encoder. Export directly from Premiere Pro. Seems to work.



    Here is a link to the other thread which helped me a lot:







    Hope this helps everyone!




    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (1)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points