Quote:
Originally Posted by aaronplant
1. I recently purchased Hoster, and I am trying to get my existing mp3+g library imported.
Previously they were being used in the Sax n Dottys Hoster, and this program did not have any problems with these files.
2. During the importing process Hoster is skipping files giving a status of 'error' but these files check out fine when accessed manually to check their contents. The filenaming is correct etc.
3. I have seen some comments about 'special' characters in filenames, such as ',' and '&' etc but it doesn't seem to be just these files causing a problem, as some of them are straight forward word filenames.
|
1. Do you know the source of your 84,000 CDG songs? Did you import them from CDG discs using one of the MP3+G rippers? We're not aware of any MP3+G formats that S&D's "Show Presenter" product supports that Hoster doesn't.
I am assuming your files are NOT ZIPPED. If they are, then Dale's point about "max compression" would apply. Hoster won't unzip files with max compression.
2. We often hear that Hoster has no problem importing MP3+Gs and ZIPs that were used on S&D's player. Thus, some unique error condition exists in the files reporting "error" during importing. There are three error conditions on MP3+G files that could cause "error" during importing:
A. Both a .mp3 and a .cdg file with the same name must be in the same folder. Hoster's filename checking is case insensitive.
B. Neither file can be open (locked) by another program while trying to import. This would deny Hoster access to one or the other of the file pair.
C. Hoster opens the .mp3 header to obtain the compression and duration. If the header is non-stadard, Hoster may not be able to open it.
You can easily determine if A or B above are met. If so, then the files that are showing "error" may have mp3 headers that Hostre doesn't recognize.
Please email "support at mtu dot com" a zip file containing the .mp3 and .cdg for two songs that show "error" while importing. We will analize them and make our import accept them... unless they have been created with some really screwy header that is non-standard, then we may have to decide to support it or not.
3. All reported problems of "special" characters in the filenames have been fixed in 3.316 or prior. We tried a number of them just now in both Hoster 3.316 and Microstudio 4.000 and both played and/or imported the "dummied up" bad files without errors.
