BUG: Losing rendered mulitcam audio
I am losing rendered multicam audio in Premiere Pro every time I restart Premiere. I am running Premiere Pro 2018 12.1.1 on 10.12.6 Sierra, and every time I restart premiere I lose all the rendered audio and waveforms in Premiere Pro with multicam clips, all I see is a red line through the audio, and I have to render them again. This has to be a bug and is incredibly frustrating, especially when working with a significant amount of clips as it is a long render.
Philippa Byers commented
The disappearing waveforms from multiclips edited into a sequence continues in version 14.8.0. Well done Adobe. It's so exasperating, frustrating and a waste of precious time.
Matt Stegner commented
Deleting my previous, incorrect comment. I've created a bug for this with the number: DVAAU-4203910. You can use this bug number as reference when asking Adobe about the issue.
Paul Moore commented
I'm leaning towards Matt's analysis of the situation. While it may not be a "feature" per se, Premiere can't draw a mix-down waveform (like from a nested sequence) until it's rendered, and any change to that mixdown will reset the process. That's not unexpected bad behavior from the software; that's just how it works. They could add a feature to live-render under these circumstances, but I can imagine that eating up a huge chunk of memory. A few ways I've found to work around this problem are as follows.
1) If you only need one audio source once you've synced all your video angles, remove all the extraneous audio tracks.
2) Do not make cuts within a multicam sequence. Honestly, this is just a matter of best practices anyway. It causes a whole bunch of issues with project management down the line.
3) Don't apply audio effects to the source clip (at least not until Adobe makes Master Audio Effects a thing). Always apply to the multicam clip. It may take a little more time but, with the proper copy/paste procedure, not by much.
Maybe one day, somebody will work out a way to render mixdown waveforms in real-time, but until then, this at least somewhat solves the problem.
Matt Stegner commented
This might not be a bug.
If a nested sequence (multicams are a form of nested sequence under the hood) has to mix down audio, the waveforms are not displayed. Premiere has always worked like this. The only way to see waveforms in a nest is to have a direct 1:1 pass through. Even simple things like cuts or trims will cause the nested waveform to be not drawn.
Jason Decker commented
How is this still not fixed? There's a CreativeCow post about this issue from 2014 and this bug report was filed in 2018. WTF???
Image attached: One multicam has waveforms, one doesn't. Nothing I do changes that fact.
Lee Whitman commented
I'm having the same issue too. This is honestly ridiculous. Please fix this.
Luke Hart commented
Since this bug has existed for years and Adobe appears to have no inclination of fixing it, see the workaround I linked below. Fixed the issue for me in moments.
I felt its necessary to highlight the step-by-step instructions for the workflow that generates this issue.
1) Audio waveforms are generated, visible, and responsive to timeline re-sizing and usage
2) Change one parameter using "AUDynamics Processor.
3) Come back to timeline to find waveforms missing.
4) I could "Render Audio" - AND that has worked but I don't see why it should be necessary and would love an explanation or fix.
16Gb 2133 Mhz
Radeon Pro 460
Basically... Adobe REALLY needs to make fixing this whole render file issue that Premiere has a priority. It's so **** frustrating and time-wasting to have to re-render things JUST because Premiere decided to up and forget that those render files already exist. This should not be happening. It's been happening for years and Adobe still hasn't fixed it. Ridiculous.
FIX IT ADOBE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I'll add my concurrence. Working on a multicam project today... in just a few hours, I've lost my rendered audio four times. Ridiculous. Twice because Premiere crashed (another little bug that i've enjoyed having to deal with repeatedly...) and twice because it just up and... disappeared. One of the times I think it was because I tweaked ONE audio clip in the multi-cam sequence, which of course makes THE ENTIRE sequence unrender. Joy.
T. Baugh commented
Same problem... been going on for the last few versions. Glad to learn today that Resolve supports mutlicam editing!
Avinash Lobo commented
This is a bug I reported about 16 months ago, with a response that they're hoping to get it fixed "ASAP".