No audio on export

I had the same problem in adobe media encoder. What helped me is to change folder in edit / preferences / media to folder, that is not full.

Issue solved in my case.

My workstation works for weeks non stop and it seems this issue happened every time there were windows updates waiting to be applied. Solution is simply turn the machine off, start again and let the updates run. After that everything seems to be back to normal.

Hope this helps!

[Move the All audios From  AUDIO TRACK 1 to  AUDIO TRACK 2 ] Its working!!!

I am having trouble with this issue.

Due to a catastrophic computer crash I had to buy a new MBP running El Capitain.

I'm running the current iteration of both Premiere Pro and Media Encoder

Media Encoder isn't exporting audio from a project (less that 2 minutes long with 2 tracks of audio) that I exported from 3 days ago.

This thread seems to be pretty old and I'm really stressing out about the fact that there doesn't seem to be a solution this problem.

MacbookPro

2.8 GHz Intel Core i7

16 GB 1600 MHz DDR3

AMD Radeon R9 M370X 2048 MB

I am experiencing this problem right now and the recommended "correct answer" doesn't fix the issue.

I am running Adobe Premiere Pro CC and have a music audio track and video track.

Part of the video audio is in slow motion and during editing and editing preview, the slow motion audio is perfect.

Upon exporting media, the finished video has no audio for the slow motion segment.

This is a small five minute video, so I don't understand the explanation that size of audio track may be an issue? If there is another fix, I need to get this finished asap... I have been using this system/software/work flow for hundreds of videos and this is the first time I have had any issue with slow motion sound.

Nothing in my cofiguration has changed.

If there is a better fix, please let me know.

In case there's any value to it, and hopefully it helps resolve this, I'm just adding my experience here.

On a PC, upgraded to Windows 10 from Windows 7 about 3 months ago, been using CS6 for ages without issues (on both 7 and 10).  A few days ago, I decided to finally take the plunge and buy CC given the increasing number of nice tools that CS6 didn't have, despite my reluctance to subscribe to the monthly model...  Still, Adobe seemed to show that they were constantly improving this product, so fine - I'm in.  (note that I still have CS6 installed)

Anyway, CC worked fine for about a day, and now (as above) AME is failing.  Half the time, if I "queue" something in Premiere, AME doesn't even notice (ie nothing is added to the queue), so I have to close AME and try again.  Even then, sometimes it doesn't work.  But the bigger issue is of course the audio bug.  Short music clips of ~5 minutes with mutliple audio tracks but only one not muted...  no audio.  And in fact you can see that AME doesn't even 'prepare the audio tracks' or whatever that first step is.  "Export"ing directly from Premiere DID work, but obviously that's a much less desirable workflow.

Finally, a (perhaps overdue) system restart has it working again.  Still took a few 'tries' to get the file to actually show up in the AME queue, but I've got three outputs with audio now...  I'll try to report back with any other updates.

Obviously this is a serious bug for a lot of people, but for what it's worth, if you haven't done a system restart lately (like me), maybe that'll help get AME going through at least one deadline or two?

Another option that fixed this for me was double-checking my source audio. I had an MP3 file being used as a temporary source for some VO. Once I swapped out the MP3 for an AIFF, all was fixed. Make sure you have no MP3 files in the timeline.

Well let's see of I have this right....

• There's a known issue with AME in that it can't output audio for large files - in my case even for a 30 minute video
• Although Adobe knew about this, they didn't;t think it was worth letting their customer know in advance (you have many ways to contact me and you are aware that I am using AME)
• Yes... perhaps I could cut and paste here and there and try this and that to see if I can get a work around. I don't feel inclined to do that primarily because when it comes to time to pay for my subscription each month it seems that no workaround I might use is acceptable
• I created my composition in AE having first created the video assets in PR
• Yes..... I can export my project out of AE back into PR - except that all that appears to do is to send back all of the assets within my project. It doesn't appear to regenerate the timeline in PR and it's that timeline which cost most of the many hours we have put into this video
• Yes.... I can actually render out of AE, but it seems only in AVI format, and since that isn't the required output format. no doubt we'll have to send that AVI file into AME in order to (hopefully) get the right format out with some audio
• The word on the street is that perhaps a shortage of disk space was responsible for causing AME to not perform properly - well how much workspace does AME need if the 414 GB free on my disk isn't enough? In fact the spec recommends 10 GB.
• Alternatively, do I have enough memory? Adobe specify 4 GB as minimum and 8 GB as recommended - I have 8 GB
• Perhaps my disk isn't fast enough? 7,200 rpm is recommended - and that's what I have
• But you must have 64 bit processing - and I do
• So what I have as a system exceeds the minimum required. If Adobe needed more than it should have said so
• But here is the most important point of all.... if the program runs into what could be considered a genuine resource issue, then stop the program and let the user know that there is a problem, preferably giving a message as to the nature of the problem. This has been good programming practice for at least the 48 years that I have been programming. The fact that the program didn't do this seems to indicate very poor program design (from a user interaction perspective) or the fact that what is causing this is simply a major bug that was not intentional design. Final testing of a large video file, e.g. 2 hours, would surely have shown up this error?
• So did Adobe know about this error before release? To say "no" would be to say testing wasn't done on a large file. To say "yes".... well I am sure that we will all have our own individual thoughts about that...
• Adobe makes super products and CC really is creative. Letting this issue escape the farm, not owning up to it and taking so long to fix it is also creative - but not in the manner that your customer might appreciate.
• I have wasted two days on this issue and missed a customer deadline.
• Adobe, please fix this quickly or I will be forced to drop using CC altogether. We must be able to rely upon our tools.
• Thank you.....  Ian

I'm facing this problem in After Effects. I've tried the solutions on this thread but nothing is working. Has anyone had success getting this to work in projects coming from AE to Encoder?