Blackmagic Forum

I use the mixer view compressor.
I can reproduce everytime. If I click to open the mixer compressor on fairlight page and also the EQ I get an immediate crash. Resolve shuts down. I cannot find any reason for this to happen except being 19 beta?

I do also see there is still lag on applying simple effects like eq on the timeline page from the inspector. Sometimes an eq adjustment works sometimes not. Subtract an eq adjustment; (pull 100k down) and you get a little bit of the sound producing the cut in frequency but rest of audio is not affected as should be.

Help or just Beta.

We can only help if you provide the logs and NFO, as per the FAQ

I was able to create this file log but it is too big to upload here. 669mb.
Here is what the crash report says.

#TIME Sat Apr 27 11:55:21 2024 - Uptime 00:00:45 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.0.0b.0020 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID e8470537-5963-4283-975e-e8bec006b44e
#BMD_GIT_COMMIT fddf98e7de0487f62967586e58d5e30dac3f3e64
#BMD_UTIL_VERSION 19.0.0b.0020
#OS Windows

00007FF728803A4C

The FAQ at the top of the forum includes instructions how to generate logs:
viewtopic.php?f=21&t=90190#16

Use a file sharing service (e.g. WeTransfer) and include a link in this thread.

Here we go:

https://we.tl/t-cOhKGivmCF

To add to this I have narrowed down what I think is the issue.
The audio file comes in having audio on the right output and nothing on the left. I go to clip attributes and choose bothl/r to be right. Then I get audio on both channels. From here I would choose mono as the track and get a mono track.
Seems when I do the clip attribute conversion and then go to mixer dynamics (compressor) and click on it I get the crash. If I don't do the clip conversion? No crash. But It will still crash after the conversion is removed. You have to delete project and start new to get no crash.

Hope this makes sense. ; )

Was hoping this would help support on this problem or should I be directing this somewhere else?
Open ears here.
: )

No logs for the Devs to look at them and no info on the PC.

For example for now there seems to be an issue related to some Intel CPUs being ran out of spec because of wrong MB defaults, that could lead to crashes in applications.

Please provide a small sample Project Archive .dra (zipped) that contains an audio file that will cause the crash as described.

Also provide a Windows System Information .NFO file.

Hello Dwaine.
After doing some support myself on this issue. I found it to be a sample rate problem. If I started a new project and changed it to 44khz. Then dropped in dji footage that was 48khz? Then tried the mixer EQ or Compressor? It would crash.I figured resolve would accomadate the incoming sample rate but I understand now that the sample rate cannot be changed once commited on starting new project.
But I also read that it is common to use mixed sample rates on a timeline in fairlight??? Confused here.


Most audio samples and loops are 44khz.So I figured I would set all my daws/ programs to 44 khz rather than 48.

Help?

I am using studio one to create music while recording in OBS for youtube videos. Then I switch to Resolve for the video portion editing and also voice over in fairlight while using OBS if this makes any sense.

I'm not seeing this. But you mentioned in the earlier message that you only got the crash with a single channel file and use Clip Attributes to make it 2 channel. Is that still the case?

If so, can you provide a link to that file?

Hello Dwaine.
If I have a time line that is setup as 48khz and my imported audio is 48khz. I am able to turn stereo audio into mono no problem and no issues with dynamics or eq.

I did have an issue just now where I had to reset my audio interface sample rate in windows. It was sitting at 48khz. I switched to 44 khz 24bit and now the problem with resolve and dynamics and eq are gone. :/

Going to keep checking.
I just closed out resolve and tried again and the problem of crashing with the dynamics or eq is back.
Frustrating. This was a timeline of 44 khz and an audio file that was 48 khz that worked fine just a bit ago.

: (

For anything video, rather stick to 48. So, keep your timeline at that sample rate and convert your other sources. And avoid MP3 while doing that, always use PCM (WAV or AIFF). I’m pretty sure your problems will go away.
This not meant to deny possible issues with the beta.

Dwaine.

And thank you for the reply Uli.

The way I understand Resolve is it will down/up sample to what I put on the timeline such as the timeline being set to default 48 khz and adding footage with audio at 44 khz. Thus it would upscale the 44 to 48.
I have never had an issue with mixed audio on timelines before coming from Premiere either.

An example here is I just started a new project in Resolve and changed the sample rate to 44 khz since some footage is 44 khz heavy and a smaller amount of 48 khz on this same timeline.

When I go into Fairlight to work on the 48 khz voiceover and try to arm the dynamics or eq on the mixer? It will crash fairlight/resolve every time. Can reproduce with old or new projects. This is with Beta 19.
Here is the NFO file.

https://we.tl/t-AVoPSqZRQ1

Error report does show the crash for Resolve and windows.

According to the NFO, it's the fusionsystem.dll that is crashing.

What would be extremely helpful would be a link to the smallest project archive .dra that you can generate that will allow us to reproduce the issue, along with details of what to do in that project once we restore it, to cause the crash.

A project archive .dra includes all the media files in the Media Pool. So again, as few and as small of files in the Media Pool as takes to repro the crash.

Ok Dwaine thank you.

Here is the project file and the video. I only used one video file to keep small.

It's just a bad B roll shot. ; )

https://we.tl/t-brjUk1pc9C

Open project with the video I sent. Timeline should read 44 for sample rate.
Video file is 48 sample rate.

Go to fairlight page and try to double click on the dynamics in the mixer. Or eq.
Dynamics window should open and freeze.
I can reproduce with any other video file that is opposite of timeline.

Timeline that is say 48 sample rate and video that is 48 works fine.

The issue of trying to change a stereo track to a mono one does not seem to be acting up now.

If you don't want to generate a project archive .dra, we would ideally want a project export .drp of the project, which you generate by opening the Resolve Project Manager page, and right clicking the project, and selecting Export Project.

I'll endeavor to make what you sent work.

Thanks. Repro'd and acknowledged by the dev team.

Awesome!! That is that I'm not alone on this LOL. Thought I was in a twilight zone episode LOL!
I will look forward to the update.
Thank you for the time and help Dwaine!!
DR

Same problem here on the beta in a 44.1 khz project with 44.1 clips. Resolve crashes everytime i try to open the dynamics interface where I want to enable the compressor and limiter.

Hope this will be fixed on official release

Hi, I have project crashing (stuck loading at 100%) everytime i open the problematic timeline, except if i open through stacking timeline. at first i found out that its only happen to pro res footage, but then i came across this page and upon checking I believe it might be the same case, the pro res footage does have 44khz audio and the timeline is 48khz, but i did not use the fairlight page. it happened after closing davinci. This is happening on DR studio 19 beta 1 and beta 2.

I, too, am experiencing crashes which seem to be related to sample rate.
I have submitted several of them using the built-in crash reporter, but not yet received any support or contact for them.

I have found that the fist thing to do when you start getting crashing out of nowhere is to delete the render cache. Do it through the Manage render cache menu under playback. I have had this fix everything from clips going black to crashes when opening fusion clips. I really wish they would overhaul this whole system because it is nothing but problems.