Intermittent burst of LOUD distorted audio while scrubbing

Hello,

Occasionally while scrubbing in the edit page, and very occasionally after pressing play, there is a short burst of extremely loud distorted audio which is practically deafening. I've noticed this since the beta.

Anybody else experiencing this?

Davinci 14.1.1 running on MAC OS Sierra. iMac 27inch, late 2013. 3.5ghz Core I7. 32GB Ram. GeForce GTX780.

chris

This was something that used to happen in Pro Tools on MACs. Avid cured it with an update. Never had it on a PC and no one has reported it here with Resolve.

Yeah, I've encountered this on Windows 10. I don't know how to reproduce it so I haven't filed a report yet.

Seen it on OSX but haven't bothered to try to isolate it to a bug report. It happens repeatably when it happens, but I see no pattern at all as to what makes it happen in one place and not another.

According to my tests it happens when jumping back an forth in the timeline on the Edit page when audio scrubbing is on and when fairlight EQ is used on any track or bus. Bypassing/resetting the EQ or the used band(s) stops the bursts.
I have to do further testing but perhaps any of you can confirm this findings so far ...

Johannes

It happens to me all the time. I just figured it was a Resolve quirk.

It happens to me all the time. I just figured it was a Resolve quirk.

How do you work with it? I have headphones on and it deafens me. With speakers it's just intolerable.

I guess there has never been a fix for this? It really is a terrible problem. I get it periodically right after hitting play (and perhaps sometimes when scrubbing audio, can't recall for sure). Windows 10 here.

I've assumed it had something to do with my system getting bogged down as I don't think I've noticed it when working with less CPU intensive video files. While working with multiple tracks of 4k MP4s it happens very often (and it usually drops a few frames for a second or two after hitting play).

The same here. It has become more common since the beta. Please fix it before my expensive studio monitors are damaged.

I was getting this in early 16 betas. Hasn't happened in a while, though. Currently using Studio 16b7 for Windows.