Sequence Audio Doesn't Play After Opening A Project Unless You Solo and Unsolo A Track
After opening a project, the audio will not play in any open sequences. In order to get it to start working, you have to solo and then unsolo any audio track. This has been an issue since Premiere Pro Version 12.1 for sure. It may have been introduced in version 12.0.
Please check 12.1.2. We have provided a fix that we believe resolves this issue.
Rakesh Parge commented
copying entire sequence to a new one will resolve the issue for me. But I want a correct fix
AdminMatt Stegner (Admin, Adobe DVA) commented
@Amanda Cole, You are using Premiere 14.2? Can you post an example .prproj so I can investigate?
Amanda Cole commented
These are brand new sequences... fyi
Amanda Cole commented
Hi, It's 2020 and I'm having the same issue. Maybe I don't understand how to solo and unsolo. I turned off and on S on one audio track, but still no audio. I can play audio in the source window, just not in the timeline. Help! It's been weeks of trying to figure this out!
Happening here too; soloing and unsoloing doesn't usually fix it. I keep closing out and re-opening. It is maddening and a huge time-waster.
The issue could occur when an audio track was muted in a sequence and then the v12.1.1 project was saved and closed. When you reopened the project, the UI for the sequence no longer showed the audio track as being muted as the UI reset the toggle to show it as on. When a user would play back the sequence , not all of the audio tracks would appear to play causing them to possibly think it was a caching issue or codec related issue. Premiere was actually playing the sequence back correctly as those tracks were muted from the previous save state but the UI bug caused the issue where there was no indication that the track was muted.
Solution: (the Fix)
Once a v12.1.1 project shows this UI behavior it needs to be corrected and resaved. **Note** v12.1.2 will not correct this issue simply by opening the project in V12.1.2 .
You need to follow these steps to repair the project.
1. Toggle the Solo button on/off and the Audio track will correct the playback state. To keep it simple, Solo/Unsolo each audio track.
2. Playback the Sequence to insure that all audio tracks can be heard and monitored.
3. Save the Project
4. Quit Premiere Pro
5. Relaunch and issue should now be fixed.
As stated, the fix for this issue is included in the recent update, v12.1.2. This update keeps the UI bug from occurring so the user should not run into the issue again.
Super annoying as I have nested audio so I need to check each level of nesting for correct audio mute and soloing...
Miss one and you're render will have someone randomly talking in it.. Very annoying.
Can't wait for the bug-fix..
Danielle Hobert commented
Nope. Still NOT resolved! Just updated to 12.1.2 and I never had this issue before, but I do now. Yes, solo-ing any track and then un-soloing it seems to resolve it, but I'm worried if it'll affect exports, etc. And no Reg Santo Tomas, it's not resolved.
Richard Hawkins commented
UNRESOLVED... problem still exists and cascaded into export unless workaround (solo/unsolo) is employed.
Kevin Lawrence commented
No it does not. UNRESOLVED This is most definitely an ongoing and unresolved issue. I have a film project I started working on in 2014. I have lived and breathed this material and know all the issues with the substance of the sequences.. There are 15 sub sequences (scenes) as well as a music score and some ambient/foley in the master timeline. Many times I open an edit session and have to go through each sub-sequence and the "solo the tracks" trick has to be executed to enable the sound. If I render audio (get the waveform "picture").and do any edit changes it zaps the render. I have developed a work pattern that allows me to get around this. Why am I living with this defect, for this long?
Darren Manden commented
Yup. Something like a basic project open and export should be as straight-forward and simple as that. We shouldn't have to go and sift through the project to make sure that the software hasn't gone and set the world on fire.
Well...one would think that at least. :-(
Ben Myrick commented
I wonder if this trailer was exported from Premiere:
Furthermore I wonder how many people have lost time, money, or a reputation because of bugs like this. I personally have sent a "final cut" with missing audio to one of my clients. All I did was open the project, change a tile, and re-export thinking nothing else would change. It didn't seem like I would have to take the time to play it through again. I made the mistake of thinking that the fundamental aspects of Premiere were solid.
@Reg, Thank you for your response!
However, I do not believe this has fixed the issue. In addition, audio is now dropping out after a few seconds of playback. Have to hit play/stop over and over to get through a sequence. Audio is also glitchy and garbled at multitrack edit points. Frustrating. Adobe, than you kindly for fixing this thoroughly ASAP. OSX10.12.6, VideoDesktop 10.11.1.
I've relisted this title in quotation marks "Sequence Audio Doesn't Play After Opening A Project Unless You Solo and Unsolo A Track", as it still doesn't seem to be fixed. Please vote for it as this listing is "Completed" according to Adobe and is probably closed.
Evan Munro-Smith commented
I've been having this issue for months, and it still happens even after today's update.
Ben Myrick commented
This fix didn't work when I opened my project for the first time in 12.1.2, but after saving it from there and opening it again, the solos/mutes seem to work properly.
Henry McLaren commented
Still not fixed. This is now beyond ridiculous!!!!!!!!!!!!!! Please get this sorted immediately.
Sadly this is not fixed in 12.1.2. It actually caught me out today as I opened a project, made a small vision change, then exported. I delivered to the client who then phoned to ask why the music was missing.
Darren Manden commented
@Dan, @ Henry
That's almost the worst part of all of this: The sheer radio silence on Adobe's part about what is happening with all of these genuinely terrible bugs. At least if there were some indication of "Hey, we're actively working on this, and we'll have a fix soon", with something resembling updates, we could live in the hope that soon we'll be sorted, but no. Nothing even resembling that.
Instead we've had the genuinely non-committal "We are looking to addressing this issue"...which is just...what? What does that even mean?
How not to build faith among your customers.
I second that Dan. This situation is absolutely ridiculous!