This article probably articulates things in simpler terms:
https://www.soundonsound.com/techniques ... licks-popsIt’s old but valuable.
Where the author talks about pci latency and resource allocation… it aligns with the note regarding enabling MSI for dedicated signalling.
There are also other factors such as buffer size, bit depth and sampling rate that all play into the equation as well.
As I mentioned earlier, each system configuration is unique and the problems that manifest are unique.
No two problems are the same and no two solutions will be the same.
Troubleshooting requires a methodical approach. Sweeping statements and generalizations when one has no understanding of the issue won’t help solve things.
Just to be clear, these are likely system problems, not Resolve specific problems. I too used to think it was Resolve specific, but that frustration was misplaced. There really isn’t much BMD can do here with all the different system configurations. The crackling and popping happens across multiple applications and environments… it’s not just Resolve. Comparisons against other applications are also pointless.
What people are asking for is a quick fix for their particular issue, which is simply not possible.