QNAP HS-453DX, 4Gb, 1.8 Build 753
(typical load does not reach 10%, I never had any performance issues on 1.7 even with multiple zones playing with DSP while downloading files at 80+MB/s)
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Fixed Gbit network, CAT7 cabling, DHCP with reserved IPs on router.
Fiber Access Point / Router (by provider, Deutsche Telekom): Sagemcom Fast 5655v2
Ignition Labs Portal router in transparent mode (switch + wifi AP)
TPLINK TL-SG105E managed switch
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Plays directly on the Windows 10 computer using the Asus X570 Workstation Pro Ace motherboard’s onboard DAC. Tried through Windows mixer, WASAPI and ASIO too.
Description Of Issue
There are many. The ones that others haven’t mentioned are
sluggish video performance, load spikes up to a 10% (reported to be “3D”) on an RTX 3080 (which is borderline insane): selection / highlighting of items in the multiple 100ms range, scrolling happens with similar delays to be shown (but scrolling seem to happen in the background) it basically looks like a new screen with new data after almost a second of lag
player and queue does not show anything playing while the decoder area shows the data decoded, the zone shows something being played (and playback actually happens)
note: the ASIO channel gets deleted from available zone list even though it is still allowed in settings
However, I did tinker somewhat with the settings. Apparently removing the ASIO channel solved the issue, now both the player and queue works. If I try to enable it again, the same problem returns. I did check the playback signal path shows the playback device to be the WASAPI / OS mixer (either works, just it is a bit tricky to switch between them, considering that I cannot stop the playback as the system thinks it does not play anything), so the ASIO channel is not in use when the problem appears.
I think by “all remote devices” you meant the problem with the playback information not being shown. Well, in that case the problem is a bit different. It shows the album and the title, but does not show progress of play, nor can you stop the playback. It also possible to access the queue with the songs, but shows no progress, including if you clear the upcoming queue (this is executed, but the changes are not shown).
Also, I have installed Fidelizer and now the lagging is somewhat reduced (it did not go away, just reduced by around 30-50%) for both selection and scrolling. Which is actually interesting. I do not know how Roon handles resources / cores but the very fact that a 3rd party optimization software makes a difference means that there is something wrong with the way how Roon handles the same.
Cheers
Áron
PS: even if you fix all the kinks, can’t we have a Roon 1.7 based Roon Classic theme pls? Or even better make the UI themable/skinnable. The 1.8 changes in UI/UX for me (and apparently for many) is a dealbreaker.
@dylan : Note, from today on Roon finds two WASAPI devices for the Realtek MOBO audio chip. However, the old one (that worked until yesterday evening) does not show up in the available zones, the new one if I enable it does not play anything. Enabling ASIO still hangs playback for good (until reboot). No amount of reboot, reset etc. helps. The only thing that changed since then is that ZBrush was updated to the 2021.5 version, which reeeally should not effect audio hardware (not even video as it is CPU bound).
Also, now I noticed that playing via Windows mixer introduces artifacts (this is how I would imagine quantization noise but that should not audible, right?).
@dylan Fun fact: neither the Tidal, nor the Qobuz native Windows app has any of these issues. Tidal works with both WASAPI modes (has no ASIO mode), Qobuz with (both) WASAPI modes and ASIO too. Both apps play via Directsound with NO artifacts at all (although presentation feels more muddy than WASAPI or especially ASIO).
@dylan Just tested this on a Chord Mojo via optical SPDIF. Noise with Directsound AND WASAPI non-exclusive mode (!) is there, but only via Roon. Under WASAPI exclusive mode, the noise disappears. Problem is that in the Roon reports device (which is in reality the SPDIF digital output of the MOBO) cannot be initalized when trying to play anything MQA (device is set to no MQA capabilities) with the exclusive mode on.
@dylan : there is a verry interesting addition to the sluggish UI (it is still slow after the last update). The interface is only sluggish while it has focus (runs in foreground). If it is running in the background with another app having focus (does not seem to matter which) it becomes responsive. It is rather strange.
Scrolling is still non-existent (it just jumps between states pre-scroll and post-scroll screen-states with no scrolling animation whatsoever).
Note CPU/GPU utilization does not change during this time, nor does it seem to have any impact on the playback. I’ve also tried killing all background apps in case it has a problem with either of these. No effect.
@dylan : the saga continues. The recent driver update by Nvidia apparently fixed the sluggishness issue.
Although I still find some things strange:
the touch screen version has fine scrolling, BUT the Windows one skips a whole line of album pictures upon using the mouse scroolwheel - and these are now massive, if I use the arrow keys the “scrolling” is still blocky, just each jump seem to be by a single character line
however, if you open an album in a list of filtered (using my own tags) albums using the bookmark and scroll down and open an album, stepping back using the back arrow will FINE scroll back to the top of the list instead of staying wherever you opened the album in the list. First of all, WHY would it do that (and why only in this scenario: it works just fine if you set the same scenario up in Focus)? Second, WHY fine scroll here, automatically, and not do that otherwise?
Now there seem to be an occasional strange flickering that happen from time to time. It is like a screen distortion / noise effecting mostly the areas with existing text or graphics. It is hard to make out what happens, it is only visible for only a frame or two, mostly after starting playback / loading new albums and will not repeat.