Happy to have Sallah find a technical solution for networking his PCs, but time to get this post back on track.
One thing I have noticed in combining Tags: it really slows the performance of the Roon search system quite a bit. I suspect there is some coding inefficiency in combining Tags.
My Roon Core is an AMD quad-core 3.6 GHz, 16 GB RAM, and plenty fast for almost anything. Just using it for upsampling without any DSD or similar format conversion. Library is on a fast Samsung SSD. Thoroughly modern.
So, I can have all albums or all tracks displayed (6800 albums, maybe 90k tracks). Filter by a single Tag works quite quickly to display only objects associated with that Tag. So far, so good. BUT, add a second Tag and then click it to minus for the “AND NOT” logical function, and it will show that little processing Roon symbol (looks like my son with his cheeks full of apples he is chewing) for 15-30 seconds or more depending on how many objects are involved in the AND NOT filter process.
Given the modernity of the hardware and the availability of system resources at the time, there must be some issue with the efficiency of the coding in this area. That’s not meant to be an attack - I am not qualified to speak to the overall coding quality – but this seems so much slower than almost anything else I see Roon do (other than wait for Tidal track streams to kick in, which can be really slow at times as well) that I have a sense that the coders have not yet optimized this process.
This slowness is also reflected when initiating a shuffle of the resulting tracks or albums…there will be a 5-15 second delay before the new Shuffle starts to play once the shuffle button is pressed.
So, in addition to the Roon features discussed above that the masses MUST have I think Roon also needs to look at the performance of multiple tags or filters being applied in layers.