Can't EXPORT! "Rendering Required Audio Files"

[Ryan25575726vb6c]

I have a 1 minute video project. When I go to export it, it says "Rendering Required Audio Files" at 0%. I waited about 10 minutes and it was still at 0%

I have the original audio file and also an mp3 song for background music on this short and simple project. I tried converting it to a song to a WAV file but that didn't make a difference. Also my C and D drive are not close to being full, if that makes any difference.

I tried exporting the project without the music audio in it and it said the same thing. I then tried to export the project with out the original audio and then another time with no audio and the "Rendering Required Audio Files" still showed up and wouldn't export.

Any tips would be greatly appreciated!

Ryan

[Twerp85]

I realize I'm reviving a thread that has been inactive for a few years, but I've tried every single suggested solution offered on here for the same problem I'm suddenly haveing ona 75 minute rough cut of a feature film that I need to deliver, and boy am I frustated! Clearing the cache and making a new project did not work. Making everyything wav files doesnt help. Changing the input in audio hardware has no effect. As I try to identify where the issue is coming from, it appears that maybe some of my audio effects have randomly started bugging out. They were fine a few days ago when doing exports, but now, if I keep them on,   my test sections won't export. I have hundreds of music and SFX in this cut (it'sa thriller/horror film!), many of which have effects, so I can't fathrom re-creating it all from scratch. Any insight to fix this is appreciated! 

[blakejarvis]

usually this happens to me when my sequence settings don't match the footage. Idk if it would be helpful, but if you drag a piece of footage to the new sequence icon, the settings should align and the problem may subside. Also sending to Media Encoder has helped me too

[Twerp85]

thanks. my sequence settings match my footage, so that wouldn't be it. Also, this problem just started a couple days ago, after working on this project for 6 months which also makes it feel mysterious. Media Encoder makes exports soooo much slower, and it won't use my in and out points that I've designated in premiere. It also doesn't fix the underlying problem 😞 

[blakejarvis]

you could try exporting your audio so it's just one track, then putting it back in with the video and maybe having some luck? i've ripped some SFX from places before that gave my sequences some problems, but maybe if you can convert it to a simple mp3 or wav in Media encoder and drag it back in it would be solved?

Otherwise, ME might be best option and just wait a little longer. Hit export then take a long walk or something lol

[Twerp85]

trying to export just the audio gives the same issue, unfortunately. 

[Michael Grenadier]

never easy to diagnose these problems remotely. First, tell us your
sequence settings and your source audio formats and Premiere version, and
your computer specs. Then try and isolate the problem by exporting the
sequence in sections. You might try exporting "stems," individual audio
tracks which you could then merge together in a copy of the sequence. You
might try sending the audio to audition...

--
Michael Grenadier

[personal info deleted: forum rules]

[Twerp85]

Thanks! Sequence settings in screen grab below below.

Computer: MacBook Pro 16-inch 2021

Chip: Apple M1 Max

Memory: 64 GB

- Working in Premiere 25.1.0 (build 73) 

- Audio in my main multi cam clips are all recorded at 48000 Hx - 24 bit - 8 mono) some dialogue scenes have 3 lav/boom audio sources, other have anywhere between 4 and 9. All the same.

- Shot on 2 Panasonic S1 and SH1 cameras, close to 4K. The primary footage is from there and since we shot with anamorphic lenses, it was modified to be edited in 380 x 1606. 

- I have close to 100 different music and SFX throughout the 75 minute cut. Yes, some are .wav, some are mpr or mp4, but none have given me a problem in the last 6 months until this week. I suspect that some of the audio effects might be the culprit, but with so many different files and fx, narrowing it down is arduous.

- I've tried exporting in secctions, but the problem persists. I've also tried clearing the cache, starting a new project and copying and pasting the old sequence, exporting just the audio...still stuck at 0%

My other editor and I are using productions and lucid link to co-work, but both have been mostly smooth until now. 

No idea why premiere is suddenly doing this after 6 months of working mostly smoothly in this project with many different kinds of media, but I'm about to tear my hair out! 

[Twerp85]

update: as I try and go section by section to try exporting small chunks at a time, I definitely now think that it's the premiere audio effectson on some of my sound design that's causing the issue, because when i remove those audio effects in those sections, it exports fine. That said, there is weeks and weeks worth of work that was done on the sound design, and going through, identifying the faulty clips with effects and removing and recreating all of it feels unfathomable, especially when they'be been working fine and exporting normally up until now. 

[Joaquin27244073gxsw]

Hey there, 

thank you for posting your question. Due to your post  I was able to bypass a lot of troubleshooting. I also had the same issue with an MP3 imported at 44.1 kHz file to export as an H.264 video. 
The Soloution I found in my case was to change the rate from 48 kHz  to 44.1 kHz in the export menu under the audio tab.

Hence, the audio stayed at its original format. Although; it took about 5 minutes to render the audio files showing 0% movement. 

[Joaquin27244073gxsw]

I just wanted to update; once the audio file was exported at 44.1 kHz; I was now able to go back and successfully export the file as 48 kHz.

It seems Premiere only needs to do this once. Hope that helps. 

[amandac8733211]

Changing the audio from 48 kHz to 44.1 kHz fixed my stuck at 0% audio rendering issue. Thanks!

[lilyh76736360]

Yes - I had a full 1 hour cut of a film. I made a new sequence based off of 44.1hz audio and though it still had to do some audio renders it did move forward quicker (2 hrs export vs 4 hrs export...I'll take it)

[Wade22901579oomd]

This worked for me... I was getting so frustrated before. Thanks so much!

Adobe really needs to fix this.

[Squirrel Face]

That worked for me. Changed it to 44000 in sequence settings for that comp and now problem gone away entirely. 

[Amy_KLG]

I had the same issue and changed my audio from 48 to 44.1. that allowed it to export. Thanks!!

[chazd48838456]

Having same issue here. I'm not even using any mp3. Just the audio tracks linked to the video. Only audio corrections were to increase db, reduce reverb, clairty. 

anyone find a real solution. It's like they don't even use these programs before they release them. This should be a beta release issue worst case scenario. 

[Pablo272176547aql]

I'm not using MP3 either. I have used some additional sound effects but everything is wav/ 48000 and it does always have problems on projects I'm using more sound design on. It's utterly ridiculous that one of the most used editing suites has issues with audio files that make it unusable. 

[AndrewTheGreat]

Same here. Only a video with its own audio. Stuck. No FX used on any track

[Michael Grenadier]

what are the source properties?  codec, sampling rate and bit depth are probably the most relevant specs...   And always useful to tell us your system specs: OS version, Premiere version, amount of RAM, Hardware specs including graphics card... 

[AndrewTheGreat]

It goes on and on again, I name my specs, software versions and video
specs, you (not exactly you, but anyone) suggest updating PP, video
drivers, recoding the video to some other format, turning on or off
hardware decoding or changing the renderer, and on and on again. Maybe it's
better to start improving the software from the Adobe's site, and not
adding another "critically useful feature" like frame.io support? I've
already found a solution. But it's a workaround. Like taking painkillers
instead of curing the disease itself.

[Michael Grenadier]

and you don't want to share your workaround?  For the most part, we're just other premiere users trying to help others...  I've been working with NLE's since their birth and these kind of issues have always been part of the experience, even when the early systems were "turnkey" where Avid provided all hardware and software...  And the entry level expense was about $50,000...  

[chazd48838456]

It's nothing in settings or specs. It's clearly a software issue with so many people having the issue. I'm sure a majority of us aren't new. 

for this last fresh install of the most recent version it just doesn't work properly. Adobe support is horrible. All I do is share my screen and watch them ruin my project and then they hang up to let me reconnect all my videos that they managed to break the links to lol. 

I'm just one more step closer to davinci imo

[Michael Grenadier]

how many people?  in this thread maybe 10 or 12...    It's not easy to diagnose these problems from a distance.   Resolve is a superior color correction tool imho, but it's interface doesn't come close to Premiere's...    If you want to try and troubleshoot this issue, post back and I'm more the willing to help...  You said in an earlier post "Only audio corrections were to increase db, reduce reverb, clairty. "  What is "clairty?"  Is this a thirdparty plug-in?  I just searched the effects for clarity and clairty without any results... How did you increase db and how did you reduce reverb?  Try removing all these adjustments and see if you can export?     And then maybe we can figure out what the source of the problem is...

[chazd48838456]

In the audio tab. Not a 3rd party plug-in. Select audio and normalize to 0 for db level increase.

The issue also exists in mass but only 10-12 people here went deep enough into google and spent the effort to login and post about it.

If the word isn’t clarity it’s synonymous. I’m not by my computer at the moment but everything is the same I’ve been doing for 7-8 years before this update.

Sent from my iPhone

[AndrewTheGreat]

No, this doesn't fix it on my system. But changing the renderer from CUDA
to mercury and back does