Can't Restore Waveform View

Editing video, including editing some audio with an external editor (iZotope RX 8). Everything works fine editing and sound-wise, but the waveform view disappears at some point. So I:

- Search for the command to make Resolve rebuild waveforms but can't find it. (There must be one, right?)
- See that some people have had success deleting their CacheClip directories.
- I delete my cacheclip directories, relaunch Resolve, let it rebuild waveforms and...
- Audio for unmodified clips now have waveforms, but
- Waveforms for clips with modified audio (.wav file format) still not visible in Edit view, BUT
- Waveforms for all clips are visible in Fairlight view!

How can I get my waveforms back in the Edit window? If I can't see the sound, the editing I need to do is going to take about 100 times longer.

Windows 10, Resolve Studio 17.1.1 Build 9.

Welcome to Resolve, and the. Never ending “where are my audio waveforms?” debate.


Sent from my iPhone using Tapatalk

Welcome to Resolve, and the. Never ending “where are my audio waveforms?” debate.

I mean, I knew it was glitchy, but I figured at worst there had to be a PITA workaround.

But to have them visible in one view but not in the other? That's...not what I'd expect in software that is so solid in most other respects.

I'm going to take a break from deleting .pfl files and cache directories and take a nap (or hopefully wake up from the nightmare this project has suddenly become?).

[Peter Chamberlain]

Was your track height in the edit page too small? and were waveforms on?
Is so, and you can generate a simple project that repos this please provide as ive not seen it here although im aware of reports from some time, inc from Trevor.

Was your track height in the edit page too small? and were waveforms on?

No and yes. The waveforms were visible for a while. There was an audio track above it that continued to show waveforms. I moved a clip from the problem track to the track above (which again, was showing waveforms), but that clip still didn't display any waveforms.

Is so, and you can generate a simple project that repos this please provide as ive not seen it here although im aware of reports from some time, inc from Trevor.

Well unfortunately after wrestling with it for too long, I just created a new project and started over. When I was done I deleted the previous projects.

There's one thing about this that might be a clue. The video I was working on came from Nvidia's screen recording software. There were two audio streams, my PC's audio and mic audio from me. Both were stereo. Before I restarted the project I muxed the audio so it had two mono tracks.

That's the only slightly unusual thing I can think of.

Thanks for getting back to me, anyway!

That's not slightly unusual. DR has problems with VFR and most screen recordings are VFR. Did you use ShadowPlay? Don't!

The video I was working on came from Nvidia's screen recording software.

I always recommend hardware recorders for screen capture you intend to edit. They typically offer editing friendly options like DNx and ProRes, whereas software normally doesn't.

https://www.blackmagicdesign.com/produc ... ideoassist

That's not slightly unusual. DR has problems with VFR and most screen recordings are VFR. Did you use ShadowPlay? Don't!

Well that's interesting. I used Nvidia Experience's screen recorder which is either Shadowplay or Shadowplay's successor (don't know if they changed anything about it since they dropped the Shadoplay name). I recorded about 2.5 hours of video that I edited down to 90 minutes. The video had lots of moments where absolutely nothing was changing, which I imagine is where VFR would really kick in.

But Resolve had no issues with the video (or audio, at least initially). Maybe this was just a fluke - I'll keep it in mind if I ever do this again and have problems.

I always recommend hardware recorders for screen capture you intend to edit. They typically offer editing friendly options like DNx and ProRes, whereas software normally doesn't.

I don't do this often enough (in fact this might be my first and last time) to justify a hardware recorder, but thanks for the suggestion.