Hi,
Nope, the issue is not related to the permissions of the files, it seems there was perhaps one bad sector on the server hard drive or a very small corruption of the file.
What would be interesting to add in the MC analyse audio is a "skip file" process if the file fails to get analysed in an amount of time and then when entire collection is analysed, then a report is created with the "errors".
What I have seen so far are two situations :
1) Some ripped files done with DBpoweramp are very small (a few KBite flac files) because there were errors on the CD's ripped, in this case, the analyse audio tool white "ERROR" instead of showing the percentage of completetion, if a few files have errors the entire analyse audio process stops stating "the previous files analysed showed erros", the process should continue instead of get stopped.
2) As just mentionned in the previous posts, if there is one bad sector in a file analysed or something that "blocks" the access to the analysed file then the audoi analyser freeze and stay in that state, it should also stop the analyse of this file and shows "error" also.
I am still 100% sure of what happened to my "bad sector" file as I deleted it (what a stupid action !!) hope I will get exactly the same issue soon, I am still analysing my files and I have less freeze issues as before as I stopped my antivirus, firewall and every other application working in the background also accessing the server.
