Vous avez été tellement nombreux à demander le téléchargement d’Audirvāna Studio 1.7 que cela a saturé temporairement le serveur de téléchargement.
Afin d’éviter à l’avenir un tel embouteillage, j’ai activé la mise en cache du fichier d’installation sur le CDN Cloudflare.
You have been so many to request the new Audirvāna Studio 1.7 download that the file server has been overloaded, and was sending those HTTP 429 (retry later) errors to many of you.
To avoid such bottleneck issue in the future, and serve the installer faster, I’ve activated caching on Cloudflare CDN for those installer files.
You can now request again the update.
Thank you for your patience, and enjoy your music!
Hi Jacob, just making sure you see this from Damien few minutes ago
Good day
Thanks. I will try to play with the options but at this stage I’m trying to sync the DB with the updated version 3.5.50 and so far no success.
It appears that I observe the very same behaviour as I got with Studio: Audirvana running, around 20% of CPU usage, not a big activity on network side or NAS (Small disk activity).
I’m just wondering what the app is doing? Nothing in the log…
Studio will currently analyse all your audio files to obtain a ‘fingerprint’ - early versions of AS wrote a MusicBrainz metadata tag to files, I assume this is now off by default as many of us didnpt like Audirvana writing metadata to our files without our knowledge.
The fingerprinting process can take absolutely ages, days or longer over a LAN I found for NAS based files - I’d rather it didn’t and maybe only fingerprinted when actually playing local files for example as for a large library if it read 100s of GBs of data or more over a network I think that could cause issues and I really dont want my NAS being accessed excessively without actual need.
I saw the thread. However, I’m asking, because during the trial period, when there were very frequent updates, there were important changes in sound quality that were never acknowledged in the release notes. There were ups and downs…
Ok, I see. I did not find the time to make such comparison. And anyway, it could be hard to tell unless it’s pretty obvious.
Now that I managed to have AS ingesting my library, I tried to get the same results with the 3.5.50 version. I checked everything (SMB3 is used on the connection) but still have Audirvana using 20% of the CPU and doing something, but what?
I found in the list of open files that it tries to browse through the albums but it’s pretty slow (4 seconds at least per album) and it seems that some of the albums are scanned multiple times. But it’s hard to tell why…
Spending more time to debug than to listen to music…
After 6 hours of “something”, the real processing starts and I can see some messages in the log.
But, during this 6 hours of time, Audirvana actually run during around 1 hour (processing time). What did it do during the 5 hours of difference? Waiting for network/NAS? No clear signal this is the case…
I don’t think it’s due to one particular file as finally, after a very long period, it completes the process.
I cannot compare the total number of albums I got on A3.5 with the one on AS 1.7 as the info is gone on the updated version (Tried to play with font size but to no avail).
So, for me, two major problems with the new version:
No more data on the total number of albums.
Need to reenter the credentials AT EACH restart of AS…
The sync story is another thing but I cannot understand it without knowing what the app is trying to do when saying “Synchronisation” and then when it says “Synchronisation of /xxx/XXX”.
Not enough info on the app design to understand this I guess.
The reason might be, because AS tried to connect to MuscBrainz servers for some reason. Sometimes, the server of MusicBrainz is offline during many hours.
Network speed: direct transfert from my Mac to the NAS are reasonably fast.
I restarted MAC, NAS and switches.
In total I have around 6000 albums on the main network volume (the one that needs more than 6 hours to complete sync). That’s a big number, not a huge one.
Still investigating but I would be helped with AS giving the possibility to have a higher level of trace (explaining what it does, producing a log file on Mac, …)
Version 1.7 no longer displays the number of albums and tracks. The number of artists is OK.
No problem with version 3.5.50 on the same computer and music files.
I already tried to rebuild the indexes and to go back to the small font display.
