Nah. We keep cutting the processing time down on our end. It’s shorter than it has ever been right now, and the compute work on our end is about to get about 40% faster once we get current in-development work out to production.
Six months ago, the processing time on our end was 15-16 hours. When we first launched Roon, it was >24hrs. We’re having no trouble achieving significant speedups in this process, even as we continue to add more data.
The great majority of the delay is the up-to-24hours that happens on the TIDAL or Qobuz side between a change made on their end, and the data dump becoming available to us + the upload/download time for the data, which is not negligible.
When the system was designed, there was an intended solution to this–it’s possible for both partners to deliver metadata to us before an album is released with an embargo date embedded in the metadata. Roon fully supports this, and will hide the album until the appropriate time. Unfortunately, they do not consistently use this mechanism. It’s unfortunate, because if they did, it would make this topic nearly invisible to our users. We cannot force them to use it–it is their data, and ultimately, their confidentiality to be concerned about when handling embargoed content.
We take a lot of punches on this topic. We are also doing everything we can about this, including continually working on process improvements/optimizations on our end. Unfortunately, we are probably at a point where the biggest gains possible are on the streaming services’ side.
Same symptom here on Qobuz, select all genres, no update, deselect any random genre and all the new albums appear. @brian
This sounds like an item for @support to investigate.