BUG: Losing rendered mulitcam audio

BUMP! SO many versions. So many problems that are constant throught all of them

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.

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.

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.

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.

I'm having the same issue too. This is honestly ridiculous. Please fix this.

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.

https://forums.creativecow.net/docs/forums/post.php?forumid=3&postid=958467&univpostid=958467&pview=t