Waveforms not showing up
Waveforms disappearing at different zoom levels or not showing up at all. This has been an issue for countless versions now. Please figure it out!
Fixed in 14.3.3.
Nathan Dyess commented
Still an issue in December 2020... Show waveforms, generate waveforms, computer restart, nothing I'm doing is working. I'm no pro at all, just trying to put together a video for a small business I'm a part of. I need to see the waveform to edit these videos.
Another question: Are you using some sort of project manager or project converter application at all?
Maybe there are some crossed wires. Deleting the Cache is a workaround, not a fix, I mention it though because represents a clean state. It is the only way currently to try and figure out if this is cruft from badly formed peak files for already fixed bugs, or that this is repeatedly happening on new peak files after the bug fixes were put into the executable. The cleanest way to delete the Media Cache is to close Premiere, delete, and restart. If you are not restarting then I think there might still be some things left over. I'm not 100% sure what steps you have taken. I can speculate but that is ultimately all it is, speculation.
If I reading the below correctly, you are reporting that the peak file is repeatedly being generated wrong, that is the thing I cannot reproduce on my end. That is what I am trying to solve. I need to eliminate variables, and have been trying to do that. There are lots and lots of variables to eliminate though since I'm not able to sit and watch your workflow.
I've watched your video quite a few times. And all I see in that video is the Premiere window. All I can do is speculate that there is some background process running on you computer, or some permissions issue, that I don't have running so cannot reproduce. I don't have enough information to reproduce. I also cannot open the project you provided below. It is corrupted for some reason, this hinders my investigation also.
I understand that you are angry, that is partially why I offered the email@example.com email below, so you can contact me directly via that email. I will even have a phone conversation or screen share session if you wish, since I want this solved.
Hey Mitch and Matt,
I'm not sure how you concluded that removing Media Cache files fixes the issue in any way, given I explicitly said that it's a workaround, not a solution.
Even after removing the cache (both from within Premiere and just deleting from filesystem), the issue persists. For example, I've just had to clear the cache twice when working on the same sequence.
As a software developer myself, I can sympathize with "we can't reproduce it on our end". But I'm also a paying customer and waste time due to this bug.
At this point, I'm not willing to spend any more of my personal time on this. Hope you'll find a way to take care of this problem because it's hard to believe that I'm the only one affected by it (I'm running very conservative Win 10 setup, without any special stuff).
Mitch Wood commented
As Matt has said, there were several potential bug fixes ranging from 14.1 to 14.3.1 that could have addressed this. Since we weren't can't repro the problem internally, there's no way for us to test this and give you a specific version number that fixed it. You should also notice that I said that it "appears" the issue is fixed. I didn't say that the issue was definitively fixed. I also asked that if users were still able to reproduce the problem after updating to the latest version and after deleting all of the existing cache files, that we wanted to know about it.
Even your own testing appears to support the idea that this issue was fixed in one of the recent updates. You had the issue. You updated to 14.3. You deleted the cache files and then you could no longer reproduce the problem. That doesn't seem irrelevant.
We've definitely left the door open to the possibility that the issue is not resolved. You've provided great information so far. If you think the problem still exists and can help us figure out a way to get a reproducible case to share with the engineering team, we'd love that! Let us know if you can still cause the problem to happen. If it doesn't happen today, no problem. Even if it's another month or two before you see an issue, no problem. If it happens again, let us know and we'll happily investigate. We want the product to be a reliable as possible.
"WTF? If you want to tell us that the issue was fixed, then name the exact version"
According to some research that Mitch helped me with, this could be one of 4 bugs, fixed over 14.1 and 14.2 releases. We cannot reproduce internally as I stated below, but we can speculate that it has been fixed but cannot accurately name the exact build number as we don't know which bug your are hitting. So we can only assume that this is fixed.
The Peak file system is retained between versions. So, if a bug is hit in version X.1, and a malformed peak is created, installing version X.2 might not fix the issue. Deleting the Media Cache will reset the peak system, and new peaks will be created minus any previous bugs.
We think that the best course of action is for you to delete the Media Cache files. We suspect that your issue will go away when not using stale peak files. If it still happens after a complete deletion of the Media Cache, then we will investigate further. Please delete the Media Cache, if you still have issue contact me via the email I gave below.
I spent several hours to provide you folks with the most accurate, detailed and easy to use info about this issue, including recordings of how I encounter these bugs. Your comment suggests that you haven't seen any of that, and also haven't read our discussion with Matt.
"This issue appears to have been fixed in one of the recent updates" - WTF? If you want to tell us that the issue was fixed, then name the exact version. If you'd go over material I provided (where I show that my version is 14.3.0, one before the last as of today), you'd realize how irrelvant your statement is.
All in all, as far as I'm concerned, your comment is plain disrespect towards the effort I invested to help YOU debug YOUR bug, and the affected Adobe clients in general.
Mitch Wood commented
This issue appears to have been fixed in one of the recent updates. If you are still having this issue, update to the latest version of Premiere Pro, launch Premiere Pro and close all projects (but leave Premiere Pro open). Choose Edit > Preferences > Media Cache. Click the Delete button next to "Remove Media Cache Files", then choose the second option, "Delete all media cache files from the system." and click OK. Once the cache files have been deleted, click OK to close user preferences and then open your project file demonstrating the waveform problem. If you can still repro the issue after completing the above steps, we want to know about it.
A couple things:
1. The project you sent is corrupted. Can you send it to firstname.lastname@example.org attention Matt. We can also take this offline if you'd prefer, just reach out to me via that email.
Are you using any sort of project converter or any other software that is manipulating the data inside the project?
2. Please restart the application after deleting the Media Cache, this guarantees that the peak files are not being cached in memory and will result is less problems. If you want to guarantee that the Media Cache has been cleaned, Close Premiere, and delete the content of the Media Cache folder.
I understand it is frustrating. This isn't a general problem and something is messing with Premiere's media cache system on your computer. If you can think of some utility or something else that might be changing timestamps or manipulating files that would be a huge help. Any deamons running on your computer that I would not have running on my computer.
I encountered the other bug I described, when the actual sound and the waveform get out of sync.
So, I created another video to demonstrate it and also test "clear media cache" workaround. The workaround seems to work, though only if I close Premiere entirely. You can download the video using the below link. In addition, that archive contains the project and the original mp4 as well.
I don't have any special permissions set up for either directory on my PC and the problem reproduces with stereo files as well.
Hope this will give you enough info for poper debug.
This is EXTREMELY helpful. This level of information, including the video, eliminates hundred, if not thousands of variables for my tracking this down, decreasing the time it take to investigate.
Bugs, with out a solid way to reproduce, will not be filed. We generally do not file speculative bugs as there is no actionable information. I ask for more info so I can have a better understanding of how to approach an issue.
Would you be able to send me the Project file (without media) so I can investigate? And, if possible, post the media file that was showing the bug from the video?
Right now, my hypothesis is that there is something with the OBS MP4 file that is causing this. Getting the file will help immensely.
At 4:15 in your video, you reimport the file, and state that the waveform doesn't show up. If you watch your video, you will notice that when you re-import, Premiere starts to generate the waveform again (you can see it in the lower right corner) and that is why initially, there is no waveform. The waveform generation competes at 4:35 and the waveform appears. This is expected.
Premiere must scan through the entire file to get the amplitude information for the peak file, which is what you see displayed in the timeline. This take a finite amount of time, and happens as a background process that we show progress for.
What is more worrying is that, when you drag that file in, a new peak file is generated. This should not happen. The peak file system in Premiere (Media Cache Database) should know that the file already has a peak file, and use the exiting one. Is the file set to read-only or have some other permissions issue?
I spent some time generating files from OBS, in mono as you seem to be doing in the video. I cannot get anything to happen that is similar to either the issue you reported of the waveform disappearing or sync breaking, or the issue of the waveform being calculated a second time.
I suggest that you close premiere, and delete the entire contents of the Common folder where your media Cache files are and let them rebuild.
I created a video explaining the problem and showing it in real time. I believe the problem and its severity should be evident from this video, so please open a bug and attach this video there.
Unfortunately, I couldn't attach the video as a file here (indefinite progress indication), so I uploaded it to WeTransfer. You can get it with this link during the next 6 days:
As for your questions:
2. Media cache folder
3. Local media on the same solid state disk
4. For me, it's just mp4
5. I will test it the next time I encounter the issue and report back. Please note that in the attached video I only show the waveforms disappearing, but I suspect that "out of sync" waveforms-audio problem has the same root cause.
I can also send you the original video files if you point me to the appropriate channel (these are two 5GB each mp4's).
Let me know if I can provide you with any additional info.
Hi All. We are unable to replicate this internally, and there isn't much for us to go on in the below comments. If we were able to recreate this internally we would file a bug and have it fixed.
This might be related to specific files, and how the peak files are related to those files after you upgrade from one version of Premiere to another.
Premiere should reuse the peak files from version to version, but that might be failing in unpredictable ways. So, some info that would help up enormously (again, since we cannot replicate in our testing):
1. Were the files originally imported in an earlier version of Premiere?
2. Do you have the peak files set up to be stored in the Media Cache folder, or next to the original media? You can find this setting in "Preferences>Media Cache>Media Cache Files>Save .cfa and .pek media cache files next to original media when possible..."
3. Is you media on a network or other type of NAS?
4. What formats are showing this issue?
5. Does deleting the Media Cache files ("Preferences>Media Cache>Media Cache Files>Remove Media cache files..." button) have any affect on this issue?
Came here to report this same bug in 14.3.0 only to find out that it has already been reported multiple times.
Not being able to see waveforms in a professional editing tool is a showstopper bug that must have been addressed right away. It's ridiculous to not see waveforms in professional editing tool. Yet, it wasn't fixed for a YEAR?
Adobe, are you serious?
Still a variation of this issue exists in 14.2. with certain files the waveform is incorrect and you have to zoom in to see the accurate waveform. It's so bad that it looks like the waveform from a completely different part or even a different video and if you try to cut based on the waveform, where you see a pause, is actually the middle of a word when you zoom in.
paul wedel commented
I’ve had some success using from the top menu Clip->Generate waveform
Hope that helps!
PLEASE fix this, it's crazy how you can't fix this...
Paul Isakson commented
Chiming in. I edit interviews. PLEASE prioritize this, Adobe Gods. PLEASE.
Sam Jae commented
This is still an issue in Premiere Pro CC 2020. Please can this be fixed. It is random, sometimes it works other times it doesn't even with the same settings, project and footage.
Hari Bonda commented
yes its not working properly in v14 premiere pro 2020 , its not showing correct information