New project / loading project unusable for a while

Macbook Pro M1 Max 64gb / v12.6
Resolve Studio 18.03 Build 5

Adding new footage to the timeline, especially DJI Action 2 footage, but to a degree with GoPro footage. With about 2 hours of footage dropped onto the timeline, it can take 20-30 minutes before I see the audio waveforms and editing is basically not doable because playback will jump all over the place. Once I see all of the waveforms, then everything runs normally.

Even after everything is working normally, audio playback will jump between the left and right speakers, but be fine after exporting.

Open to suggestions here

[Peter Chamberlain]

When u load clips the audio waveforms need to be generated. They are store by default in the cache drive which is the first drive listed in preferences, system, media storage.

Do u have a SSD drive permanently attached and selected as that drive?

I am using the internal SSD drive as the cache drive.

If I grab 20 GoPro files and drag them to a timeline, the waveform is instantly shown

If I grab DJI Action 2 files it will take minutes for the wave to show up typically.

[Peter Chamberlain]

Can you post a link to a sample DJI clip as that looks to be the issue.

Here is a folder with 3 Action 2 clips. If you import them on the media page, then go to the Edit page, when you drop them on the timeline, it will take quite a while for the waveform to get processed. Then, you will usually hear the playback jump between left and right speakers.

https://drive.google.com/drive/folders/ ... sp=sharing

The waveforms of the test clips showed up in about a second for me in Studio 18.0.3 on Windows 10, using a single internal SSD.

The waveforms of the test clips showed up in about a second for me in Studio 18.0.3 on Windows 10, using a single internal SSD.

Weird. I just need to know if it is an inherent Mac issue, but that certainly narrows it down unless nobody on a similar machine to mine can replicate it either.

DJI has confirmed that this is a bug in their codec and is working on a firmware update to fix it. They also tested the new Action 3 and found it did not have this same bug.