Waveform show veeery slow

I noticed that 20 beta1 takes a lot more time to display the audio waveform in edit page when you load a new clip than 19 version. Worst part it is barely using a 7% of the CPU and only 80mb/s of the SSD. Basically I have to wait while the pc is basically in idle until the waveform appears.

It is specially painfully when you have to edit 6-8 hours video from a twitch stream, you just wait minutes and minutes until the waveform is displayed and you don't even know if davinci is working on it, since there isn't even a % or something giving you feedback about the progress or if it is stuck or whatever.

So, I would like the waveform process have higher priority or performance, or at least a tick in the config to enable higher process priority or a progressive display as it is being processed, so I can start to do stuff even if it isn't completed at 100%.

Example of usage while processing waveform:

I made the same request 3 years ago: viewtopic.php?f=33&t=161578

You do know davinci is doing something, the IO light is on solid. I'm getting 5k IO on one file, and 15k IO on 4 files.

Numbers for comparison: viewtopic.php?f=21&t=208065&p=1080383
viewtopic.php?f=21&t=210474&p=1091942#p1091942

My system (as seen below):
Davinci 19:
23 hours: 160 seconds
20 hours: 420 seconds
40 hours: 720 seconds
70 hours: 1080 seconds
90 hours: 1440 seconds

Davinci 20 beta:
49 hours: 500 seconds.
61 hours: 600 seconds.

So yes, Davinci is getting slower

I made the same request 3 years ago: viewtopic.php?f=33&t=161578

You do know davinci is doing something, the IO light is on solid. I'm getting 5k IO on one file, and 15k IO on 4 files.

Numbers for comparison: viewtopic.php?f=21&t=208065&p=1080383
viewtopic.php?f=21&t=210474&p=1091942#p1091942

My system (as seen below):
Davinci 19:
23 hours: 160 seconds
20 hours: 420 seconds
40 hours: 720 seconds
70 hours: 1080 seconds
90 hours: 1440 seconds

Davinci 20 beta:
49 hours: 500 seconds.
61 hours: 600 seconds.

So yes, Davinci is getting slower

They would need all your system specs. In Windows, go to the Resolve Help menu and select "Create Diagnostics Log on Desktop." Also, create a MSinfo32 info file by selecting Start > All Programs > Accessories > System Tools > System Information, then choosing Save.

On Mac, go to the Help Menu and select "Create Diagnostics Log on Desktop." Also, provide a Mac System info file by going into Mac System Prefs -> About, and clicking "System Report." Save this file (as an SPX file).

Either way, post the files to a download site like Dropbox and the support people here will check it out. I have yet to try an actual project yet, but so far, Resolve 20 seems very fast -- the program opens more than twice as fast as Resolve 19 on my system.

I made the same request 3 years ago: viewtopic.php?f=33&t=161578

You do know davinci is doing something, the IO light is on solid. I'm getting 5k IO on one file, and 15k IO on 4 files.

Numbers for comparison: viewtopic.php?f=21&t=208065&p=1080383
viewtopic.php?f=21&t=210474&p=1091942#p1091942

My system (as seen below):
Davinci 19:
23 hours: 160 seconds
20 hours: 420 seconds
40 hours: 720 seconds
70 hours: 1080 seconds
90 hours: 1440 seconds

Davinci 20 beta:
49 hours: 500 seconds.
61 hours: 600 seconds.

So yes, Davinci is getting slower

They would need all your system specs. In Windows, go to the Resolve Help menu and select "Create Diagnostics Log on Desktop." Also, create a MSinfo32 info file by selecting Start > All Programs > Accessories > System Tools > System Information, then choosing Save.

On Mac, go to the Help Menu and select "Create Diagnostics Log on Desktop." Also, provide a Mac System info file by going into Mac System Prefs -> About, and clicking "System Report." Save this file (as an SPX file).

Either way, post the files to a download site like Dropbox and the support people here will check it out. I have yet to try an actual project yet, but so far, Resolve 20 seems very fast -- the program opens more than twice as fast as Resolve 19 on my system.

I don't think specs are relevant, since resolve varely uses a minimun ammount of the specs.

I have a Ryzen 9 9950x3d, a RTX 5080, 64GB DDR5-6000 and a Samsung EVO 2tb pci-e 5 (7250MB/s). But it doesn't matters, since as you can see in the screenshot of the task manager, davinci only uses a 5,2% of the CPU, 8GB of RAM, 35,6 MB/s and a 2,7% of the GPU while creating the waveform.

It is specially painfull, since it creates a bottleneck for me, since I can't start to edit without the waveform in the timeline, it feels like editing blindfolded.

Francisco, are you saying that it takes longer than 3 minutes to generate the waveform?
In any case, how long time does it take?

Francisco, are you saying that it takes longer than 3 minutes to generate the waveform?
In any case, how long time does it take?

Made a test with a 3 hours and 25 minutes video:

Davinci 19: 64 seconds.
Davinci 20: 71 seconds.

It doesn't sound like a lot, but I usually work with 10-12 hours VODs, so it is about 4-5 minutes each.

Made a test with the same video in Capcut (since it is free for this purpose).

Capcut 5.9.1: 26 seconds. (and the soundwave was being drawn in real time as it was being processed, so I could start to edit after a couple of seconds).

Having the same issue but in my case the waveform are not been generated at all.
For new projects with new imported footage, or for older projects upgraded to V20.

The few waveforms it generates are looking weird as well. You can see them when zooming out, but zooming in makes them disappear in the edit page. Fairlight similar behaviour.

I noticed it generates for some files but not for others (mp3 seems to be ok sometimes, m4a mostly are not generated).