Quote:
Originally Posted by sbequette
Now, for those of you that are actually on here to help people, I will continue. I tried rebuilding the database but it did not help as I expected it wouldn't, because the files are actualy in fact corrupt. They are corrupt for reasons that had nothing to do with Hoster, they were simply corrupt before importing, and Hoster seemed to have made it through the import without verifying them. Probably because they we MP3+G that I backed up previously, and to the speed of that sort of import probably no verifacation happens which is fine. My question is not why these file are corrupt. I know this, but what I don't know is how many corrupt files I actually have. Hoster has the ability to determine this obviously because when I try to play the file, Hoster marks it as corrupt. So what I was wondering was if there was a tool, script or anything, that could go through the files, try to open them, and tell me which ones do not load correctly. One way to do this would be to add all songs in the database and let them continuously play, but this option is not a good one since the majority of songs are not corrupt and will actually play. With 3-4 minutes per valid song, this will take a very long time. I need something that will open one, if it opens ok, move on to the next one without playing the whole song. If this tool doesn't exist, it would be usefull to have in the future.
|
sbequette, I understand your point above, and agree it is a pain. However, it is my understanding that rebuilding the database will error check your files, which is why I suggested that. I went back and read the manual, and there is a log file created of all duplicate BookIDs when the Build Songs Database command is run. My bad!
I'm not on the primary support team... and normally off in the next or second next releases to come.
I'll have our lead programmer check the Build Songs Database command. If it doesn't verify the MP3 portion of HDMP3G or HDZIP files, then I'll see if we can add that to provide an "error check" after importing, and log the bad files in the .log file.
As to MP3G/ZIP files, we have 8 error traps in the Import Hard Drive Files screen that process when converting MP3G and ZIP files to KMAs. I'm shocked that any error got through.
If you would email one of the files that displays error when played to
support@mtu.com, we'll find what's wrong and add a 9th error trap in the next release. If you email it, please reference this Thread URL (get it from the Address line above when viewing the posts here).
Thanks for reporting it.