I explained it already to you, this is normal.
You need to buffer more if the amount/throughput of data is higher (2x or even 4x).
You can check this yourself by watching the configurable minimum and maximum ASIO buffer sizes for single, double, quad speed:
- single speed 44.1 / 48 kHz, possible ASIO buffersizes from 32 to 2048
- double speed 88.2/96 kHz, possible ASIO buffersizes from 64 to 4096
- quad speed 176.4 / 192 kHz, possible ASIO buffersizes from 128 to 8192
The application has to properly handle samplerate and buffer size changes like every DAW does.
In the past there were also problems with the Music Player MusicBee when using an ASIO driver.
The author could at least fix the issue with sample rate changes, that didn't work properly. Now they do.
What remains as a problem (what DAWs do not have) that music playback stops if you change ONLY the ASIO buffersize during playback (sample rate stays the same). This still doesn't work.
The buffersize change that happens during sample rate change has been covered, which is sufficient for music playback, as there is no real reason to change buffersizes during music playback.
And I repeat, your application has a problem to interface properly with an ASIO driver and this needs to be fixed by the company behind Qobuz.
BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub13