Just to be clear. Does that include Playlists where “show playlists” has been set to “no” in General Settings?
I am noticing other odd and inconsistent behaviours in Windows 11. When enlarging a window to full screen mode (and roon is not in full screen mode, and scaling is set to 125%), Playlists will briefly highlight “blue” and is clickable but once the scroll bar is clicked, Playlists greys out.
I am only aware of these other behaviour variations because roon support have asked when Playists is accessible/not accessible on a Windows 11 device. There must be at least 3! combinations? Probably others as well.
Yes, exactly. There is only the main „Playlists“ item but no individual lists are displayed.
When Roon is not fullscreen but in a non-maximized window, the vertical window size is not large enough to fit the whole length of sidebar, but I can scroll up and down in the sidebar and then can successfully click the Playlists item.
The scrolling is with a two-finger drag on the trackpad, I don’t have a mouse to test with.
I am using a trackpad as well on a Windows 11 laptop.
What version of iOS are you using? So far similar inconsistent scrolling behaviour is being reported on Windows 11 (at least myself and @Daren_Peacock) and also Samsung Galaxy S24 (Android 15 latest).
I have been living with this for quite some time but stopped paying attention when my daily mixes feed died. I wasn’t wanting access to the Playlists as frequently as usual and made do with the workarounds I describe. The daily mix feed is now fixed so now I do want access to Playlists in a more convenient way.
Thanks for the additional information! Our team was able to reproduce this in a similar manner and we have a ticket in with our development team for further investigation towards a solution.
We’re uncertain of any timelines for now, but we’ll keep you updated with any progress along the way. Thanks again for sharing the report!
The associated fix is unfortunately not yet included in the most recent #earlyaccess build (the next pending Roon update), but it is making progress through the pipeline. We anticipate an upcoming build will resolve this issue. We’ll share updates from development as available. Thanks!