QNAP TS-1277 with AMD Ryzen7 1700 Eight core processor up to 3000MHz (8 cores, 16 threads), 48GB
QTS QTS 5.2.3.3006 (latest as of 04/02/2025)
Roon Server version 2.0 build 1496 production
Remote on Win10, iOS
Storage: 3x10TB WD Gold in Raid5 in auto tiering with 2x Samsung 970 EVO SSD in Raid1
Networking Gear & Setup Details
No VPN is used. The core is on wired 1Gbps Ethernet.
Fiber 1Gbps connection to the internet.
PFSense firewall, 1Gbps managed switch.
Connected Audio Devices
Devices: HQPlayer, DIYINHK DAC
Number of Tracks in Library
21000 albums, 400,000 tracks, Tidal service is used.
Clicking the Add to library e.g. on Home > New releases for you has no effect. It will not add the album to the library. Under Home > Recent Activity > Added the added album will not appear.
Restarting Roon core does not help. I was not able to add any album for 21 days now.
Also Tidal > Explore > Add to library will not add the album.
Thanks for reaching out with your message. I’ve activated diagnostics for your account and according to the error I am seeing, you’ve hit a favorites limit and the size of your TIDAL library is preventing you from adding more.
Thanks for the clarification, @Mike_O_Neill. Given that the Tidal favorite limit directly affects Roon’s ability to add items to the library, would it be possible to handle this differently? For example:
Could Roon store metadata entries separately from Tidal’s favorites to avoid the restriction?
If the limit must apply, could an explicit error message be shown when a user attempts to add more items? Something like: ‘Tidal limit reached: Unable to add more albums/tracks. Tidal has a maximum of 10,000 favorites, including albums, tracks, and artists.’
Are similar constraints present for Qobuz or other integrated services? If so, could the same warning mechanism be implemented for them and for any future integrations?
A warning or log entry would make troubleshooting much easier and avoid confusion for users who are unaware of the limit."
Roon’s user interface is limited by the availability of information from Tidal and Qobuz’s servers. These streaming services impose their own limits on library size, but they’re not fully transparent and subject to change at the discretion of the streaming service. When Roon receives an error via the Tidal or Qobuz API, it will be generic - there’s no way for Roon to be aware why Tidal or Qobuz’s servers rejected the content.
If you’d like to provide recommendations, we have a dedicated section here: Feature Suggestions. In this particular case, however, Roon is simply a forum/messenger delivering the streaming service policy.