Nah. I care, but getting it in lockstep with their API is just not possible.
Most of the delay is outside of our control–there’s about 25-30 hours (worst case) between when someone enters something into TIDAL and when we are able to start processing at the data.
Our processing is much smaller than that–more like 12hrs, and is regularly worked on to make it faster. We’ve sped out stuff by 2.5x over the past two years, and have plans to cut out a few more hours of processing over the next 6 months or so.
These aren’t the kind of problems that you just throw more computing power at, for the most part. They bottleneck on sequential data dependencies. The ones that parallelize well are run in parallel, but most of the work is not that way.
We’ve also been working on negotiating a better data transmission schedule with TIDAL that seeks to improve the general-case behavior by scheduling the dumps optimally within the day to avoid waiting during periods where metadata edits/additions are less likely. This is not in response to recent feedback…just something ongoing that we have been discussing with them over the past few months.
But in the end, the “make it the same as the Tidal app” goalpost is not something we’re going to be able to reach while maintaining the value-add that Roon provides. Just isn’t possible.