Generate Audio Waveform not working

[Michael_J_Titera]

Frequently the audio waveforms on my clips do not show so, I go to: Clip > Generate Audio Waveform

Unfortunately, nothing happens.

For example, I just created a New Sequence from a Multicam Source and the audio in A1 has no waveforms. I know that I can Render the Audio, which will produce the waveforms, but even that does not guarantee the waveforms won't disappear later. I am just wondering what is the purpose of the "Generate Audio Waveform" since it does nothing (not even an error message).

Cheers,

Michael J Titera

Adobe Premiere Pro CC

Version 13.0 (Build 255)

Windows 10 Pro

[R Neil Haugen]

How about a screen-grab of your screen with the audio waveforms missing?

Drag/drop the png file into your reply ... it would help to see your sequence area, including the header/control block on the left side.

Neil

[Michael_J_Titera]

Thanks for your help. Please let me know if you need any other information to resolve this Audio Waveform issue:

[PendragonTheNinja]

Almost 2 years later and they still haven't solved this problem. What the hey, Adobe?

[R Neil Haugen]

It's not that common and most of the time there's a local issue. What's the media involved, how did you import that into Premiere (and yes, this matters) ... and have you dumped the cache files so that Premiere will rebuild them? If not, I'd suggest doing that immediately.

Neil

[jasondecker]

It happens on literally every project I use Multicam clips in. At least one of them will randomly lose their waveforms and there is no way to get them back. the only solution which occasionally works is to dump the cache and let it rebuild. Then, a day or two later, another multicam will lose its waveforms. I just went to log a bug report and found one that's been sitting there since 2017 with multiple supporting comments and zero response from Adobe.

[R Neil Haugen]

It's (compared to the user base) a relatively small bug ... and they've had bigger fish to fry so to speak, sadly enough for those having toubles with this.

They've worked hard to knock off tons of long-lasting bugs, Patrick Palmer completely rebuilt the team when he took over a couple years back, bringing in Ivo Manalov to head bug-busting/stability. I'll give them credit for that.

Which leaves them with the many small bugs with only a few user with issues they can't repro in-house, which is why they also started the public beta program, to get the testing on more machines.

You went to the UserVoice system and checked on this ... please!!! ... go copy the link to that, and post it back in this thread so myself and others can go upvote it.

All posts/votes are seen by at least one engineer, and all posts/votes are collated and sent to the upper managers who decide budgets ... and they live by metrics. U-V is one of their biggest metrics. Let's give them some.

Neil

[jasondecker]

Would you like me to start a new post on UserVoice or copy/paste the links of all the posts I just upvoted? A quick search of "waveform" over there turned up at least 6 on the first page that touch on this issue from one angle or another, going back to 2018.

This is what I'm facing:

Pre-Cache Wipe:

Post-Cache Wipe

Post-Cache Wipe

Pre-Cache Wipe

And sometimes, if I'm really lucky, a thin red line appears with no explanation.

And sometimes, if I'm really lucky, a thin red line appears with no explanation.

[sethg12933769]

"It's (compared to the user base) a relatively small bug ... and they've had bigger fish to fry so to speak" I call BS on this. They never fix important issues, just care about charging like crazy month to month. You're always playing damage control for them? Lol.

[R Neil Haugen]

I call BS on your comment. It's rather ... well, lacking in depth. Knowledge. Nuance.

First, they have fixed a ton of major issues. Period. All of them? Oh Hades no. But a lot of issues, and on rather a constant basis. It's maddening when they hit us, yes, but ... saying they never fix any importantant issues off the bat makes your post rather uninformed. And shall we say, lacking in nuance?

Second ... no, I don't always carry water for ANYONE. I'm a totally practical dude, I simply do NOT get the whole 'brand allegiance' thing for any app. They're TOOLs ... period! Get over the emotions. Sheesh.

I've posted rather epic rants here about both buggy behavior and decisions I didn't agree with. Many, many times. I see some of the staffers annually at NAB and/or MAX, and they all know they'll get an earful from me.

Because I'll have a list of things, most of which aren't a problem for me but for other users! ... at any live meeting. And that will be long and specific, and yea, I'll take each point in detail. I don't get shrugged off easily.

And yet the staffers still smile when they see me coming, mostly. They're in for an often heated discussion, but they can handle that quite well.

And they can also tell me to my face that some of my issues are with a small enough group that it is highly unlikely they'll ever be fixed. Like the issue with control surfaces working only with the lowest/last instance of Lumetri on a clip, not the active instance. Whatever.

They know I'm both capable do doing about anything with Lumetri, including a lot of things most users say can't be done. And ... that I'm also gonna grill them on the painful limitations of that color correction panel. IN DETAIL. AGAIN!!!

I'll be after them on several things in a couple months. The Import page needs at the least the ability to Tab to the Create Project so we don't have to mouse over a frickin' huge monitor just to start the blasted project.

Export ... yea, that needs work. And options ...

The list currently has about 15 things. You're welcome to suggest things, btw. I'll write it down and bring it up.

Neil

[MyerPj]

I believe Jason is correct. Happens fairly regularly and scattered about when using multi-cam clips.

I can get most back by rendering audio also, but the next boot they are gone.

Post the UserVoice link here so we can upvote it, though I probably have...

[MyerPj]

If there is one (or more) specific enough that already has votes, then that would be good. Start another if they are not describing the issue we see. I know for sure it was doing it with 2019, and I think 2018 also.

[@gopysyk]

Try unlinking the audio then right-click> Render and Replace. This worked for me hope it helps 🙂 

[Nicktacula]

Usually generate audio form works for me when I don't see waveforms in an imported sequence, but your suggestion worked instantly. Went into the imported sequence, unlinked the original clip, rendered and replaced the audio, relinked, went back into the main sequence and audio was there again.