Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[lyapounov]

Hello everybody

thx to welcome me here. First time I use JRiver, discovering this great tool !

My environment: Synology DS920+, with 4G of memory. I downloaded MC29 using, of course Docker.

So far, my first use of JRiver is to compute the R128 and DR of my music library, using the Analyze Audio tool. It works perfectly... Except that it is slow, very slow. Basically, it takes between between 10 seconds and one minute per track.

(Un)fortunatly, I have 142297 tracks in over 9000 albums, in Flac with all variations (from 16/44 to 24/192) and also DSD64 DSD128 DSD256. So I forecast the whole process will be around 25-30 days to complete.

- Question 1: is there a way to speed up this process ?


Now, in 2 weeks time, I'll have another Synology DS220+, this one with 2 8T Samsung QVO. I will copy all my music files to this new one (over 7TB).

I bet the audio analysis process then will be much much faster, because writing is faster.

- Question 2: if I export the jriver library on Synology 1, import the library on Synology 2: will JRiver know which files have been analyzed, and continue the process on synology 2 where it stopped, or will JRiver reanalyze all audio files from scratch ?

- Question 3: is there somewhere where the progress of audio analysis is displayed ?

- Question 4: surprinsingly, my flac files which have been analyzed are smaller in size than the original ones, even though more tags were written. Why so ? Is this an issue ?

Thx for any answer !

Best

[Awesome Donkey]

To be honest, I'd be surprised if it could go any faster with your NAS, even if you add another one. A NAS typically isn't even close to being as powerful as most PCs or Macs (at least mid-range to high-end), and on top of that you're running it in a virtual machine (Docker container) which has overhead and lowers overall performance as well. The DS920+ runs an Intel Celeron J4125 quad-core CPU, which is a pretty low-end CPU (the DS220+ has a Intel Celeron J4025 which is weaker/less powerful than the J4125, only being a dual-core CPU). With that in mind, I'd say what you're experiencing (depending on type of audio file) from between 10 seconds to a minute is accurate. It also won't matter if you switch to SSDs, the limiting factor is the NAS' CPU and switching to SSDs won't change anything in regards to the speed of audio analysis.

You can try disabling audio analysis during auto-import, then selecting all your files and right clicking > Library Tools > Analyze Audio and set it to process 2 or 3 files at a time (I honestly wouldn't go to 4 files at a time or beyond that, which would be what I'd consider the maximum for a quad-core CPU like that with only 4 cores and 4 threads) but do know if you go this route that it's going to peg the NAS' system resources like the CPU to nearly to or at 100% the entire time audio analysis is running, which is going to use more power and generate more heat thus it could be hard on the NAS and/or the hard drive(s) installed. And even then it'll likely take a week or two or more.

The only other way to speed it up would be to use a fast PC or Mac and import all your files and run audio analysis on that, making sure you save the generated audio analysis metadata to the files themselves (which you can setup in the configure auto-import section of MC's Options > Library & Folders, it's the last checkbox there). That way if run MC on another device and import your files, they'll have already had audio analysis done to them, so it won't re-analyze the files again.

P.S. As a comparison, if I were to decide to re-run audio analysis on my music library, even with my Intel Core i7 8700K and my 131,000+ FLAC and 500+ DSF files it'd likely take over a week to complete.

[JimH]

And a NAS is a computer.  Why not just put the files on a big drive on the same computer where you installed MC? 

[lyapounov]

Thank you to both of you for your very accurate answers.

I really thought the bottleneck was the writing of tags, but I understand it is the CPU.

My solution would then be to buy a 10T external drive, copy the files, plug-it to my Mac M1, install JRiver on my Mac, and run the analysis on the files.

If I understand correctly, the fact that I am currently writing the tags to the files means that when I do the analysis on another machine, it won't analyze the files already analyzed ? Or do I also need to export / import my JRiver library ?

Thank you !!

Best

[EnglishTiger]

Thank you to both of you for your very accurate answers.

I really thought the bottleneck was the writing of tags, but I understand it is the CPU.

My solution would then be to buy a 10T external drive, copy the files, plug-it to my Mac M1, install JRiver on my Mac, and run the analysis on the files.

If I understand correctly, the fact that I am currently writing the tags to the files means that when I do the analysis on another machine, it won't analyze the files already analyzed ? Or do I also need to export / import my JRiver library ?

Thank you !!

Best

If the literature for the M1 Mini is telling the truth it looks like 8TB is the largest disc size it can handle/recognize.

To stop Audio Analysis from re-analysing Tracks that have already been analysed you will need to install/copy your existing library to the Mac Mini.

[lyapounov]

Hello

some updates: I have run my entire library in JRiver, on my Mac M1 (I know, I should move this thread).

However, there are roughly 10% of the files which have not been analyzed. Now, to make a test, I took an album which has not been analyzed, and ran audio analysis on it.

Well, on the 15 tracks, 13 were analyzed, and two not analyzed (or rather, the tags were not written).

Is there a log file which states why those tracks have not been analyzed  ?

Many thx !

Best