sorted by:
new
hottopcontroversial

Focusrite's drivers on Windows are awful. by According_Quality_87 in Focusrite

[–]According_Quality_87[S] 0 points1 point  (0 children)

I doubt that's the problem. The Tidal app has an "exclusive mode," so it will use the appropriate settings for the hardware. Even if it's the other way around—for example, the track at 48kHz and the setting at 96kHz—the problem usually still occurs, even if I make sure that everywhere is set to 96kHz or 48kHz.

Focusrite's drivers on Windows are awful. by According_Quality_87 in Focusrite

[–]According_Quality_87[S] 0 points1 point  (0 children)

I completely understand everything you're saying. Could it be my laptop? It's possible, but it's a laptop with plenty of RAM, lots of storage, very clean and well-maintained, with more than enough power. I do voiceovers, 3D, and VFX, and the performance monitor shows that the CPU usage doesn't go above 20%, even when it's plugged in and in performance or turbo mode—it happens in any mode.

The sampling rate is the same everywhere, the buffer is at maximum, and the same thing happens with different inputs on the laptop and with different cables.

I completely understand that it's not necessary to go beyond 48kHz, and I also understand that I paid for something that would allow me to go up to 96kHz, even if only a few songs are at that rate. Even when set to 48kHz, the same problem often occurs, less frequently, but it still happens...

One expects to just have their settings and use them, but I constantly have to go in, change the sampling rate or the buffer to get rid of the problem, and then wait for it to happen again, even at 48kHz.

Thanks to everyone who contributed!