k_one
Ok, so I just got my own Virtual Vinyl(yey).
Everything went fine in installation, and it seems to work just as good as my copy of CUE(which should be no surprise) and also it seems to suffer from the same issues as well(crashing on search, and not playing wav files) No surprise there either.
But, I've now tried to analyze my entire library of music several times, and I'm running into a bit of a problem. When it comes a little over halfway through the library it crashes and the program closes. My educated guess would be that this is because of a corrupted file. That's all fine, but the problem is that everything analyzed before the crash is not being saved. Which means I have to start the analzying all over again, and what do you know? It crashes again!
Wouldn't it be better if VJD/VV/CUE saved the analyzing after each file finished? At least then it would be easier to recover from something like this.
Also, since I haven't got all week set aside to stare at the filenames being analyzed, I've got no clue of which file is causing the crash. Is there any software that can do a search and help me find the file that potentially is causing the crash?
Also, why can't you select several folders at once (like you can in the PC version) to be analyzed? This means I need to analyze the entire iTUNES folder, or do it artist by artist and spend freakin' forever getting it done. Doing it "bulk" wise would make it easier to find the corrupted file.
And yeah...ID3 tag support MUST be put higher on the "to-do-list" for the dev-team.
Not having ID3 tag support is just plain stupid. (And causes a lot of irritation, especailly when "search" crashes the software...)
Everything went fine in installation, and it seems to work just as good as my copy of CUE(which should be no surprise) and also it seems to suffer from the same issues as well(crashing on search, and not playing wav files) No surprise there either.
But, I've now tried to analyze my entire library of music several times, and I'm running into a bit of a problem. When it comes a little over halfway through the library it crashes and the program closes. My educated guess would be that this is because of a corrupted file. That's all fine, but the problem is that everything analyzed before the crash is not being saved. Which means I have to start the analzying all over again, and what do you know? It crashes again!
Wouldn't it be better if VJD/VV/CUE saved the analyzing after each file finished? At least then it would be easier to recover from something like this.
Also, since I haven't got all week set aside to stare at the filenames being analyzed, I've got no clue of which file is causing the crash. Is there any software that can do a search and help me find the file that potentially is causing the crash?
Also, why can't you select several folders at once (like you can in the PC version) to be analyzed? This means I need to analyze the entire iTUNES folder, or do it artist by artist and spend freakin' forever getting it done. Doing it "bulk" wise would make it easier to find the corrupted file.
And yeah...ID3 tag support MUST be put higher on the "to-do-list" for the dev-team.
Not having ID3 tag support is just plain stupid. (And causes a lot of irritation, especailly when "search" crashes the software...)
geposted Mon 07 May 07 @ 3:17 pm
bottomend
I am having the same analyzing problem. (One not Full 200 gb Hard drive ran fine, The full 200 Gb drive fails at some point). I gave up on it because I don't know where to start to find the offending file.
geposted Mon 07 May 07 @ 10:55 pm