Currupt File Verifacation

[Harryoke]

Might it be something to do with the MP3G imported files? I run Hoster, and use only the KMA files from ripping the discs. A friend came over who uses another program, and we hooked his external hard drive to my PC to see how Hoster would handle playing MP3G files in its newer incarnation.

It seemed to work fine, until we started getting our sing on and looking deeper in the catalog, finding files that would not play, saying they were corrupt.

This bugged me as well, but all my KMA ripped files have always played well. I would be reluctant, based on that experience, to use a catalog of MP3G files until I was certain that was not the problem. It could involve how the tracks may have been ripped to that format perhaps??

Just another thought to explore.

[gd123]

Hoster has always had problems Importing Mp3+Gs, whether in ZIP form or expanded form.

It's always the same song about the mp3 not being ripped at the correct compression, even though every Mp3 and Mp3+G Player in the known universe plays them perfectly.

I was helping a friend last Monday with Importing ZIPs and we were getting quite a few ERRORs during Import.

I used MP3GToolz 3.0 to expand and Compress back to ZIP, used Winrar 3.42 to Convert the ZIP, and the Trk Imported correctly.

I suggested to my friend that, since the process of Expanding, Compressing, and Converting...leave alone having to make a note of which trks had errors in order to find them for repair later...BECAUSE HOSTER DOESN'T MAKE A LIST FOR YOU<---look...I'm yelling...I'm sorry...I just break up laughing every time I see some comment about Yelling...I wasn't aware that the ears could hear what the Eyes were seeing...man...that Yelling is just Offensive...ewweee...see...my Yelling got me side-tracked...sorry.

So, I suggested to him to do what I do, and, that is, to convert the ZIPs to BINs and Import as BINs. Actually, I take it one step further and rename the BINs to CDGs and Import as a HDCDG. I seem to recall a version that caused a catastrophe with EDITED/IMPORTED BINS upon rebuilding the DB. I had to re-import hundreds of Trks starting from a certain DATE.

BINs are so nice in that...hey...they're not Mp3+Gs so...no errors. Also, a little tidbit for those who have all kinds of comments in there Mp3 Headers. Converting to BINs and back to Mp3+Gs cleans all the HEADER info up.

But, the bottom line is, you don't need to listen to any KMAs generated from Mp3+G to check for Errors.

Now, I know this will be a lot of work. But, join the Hoster Club. You won't be the first to re-import to fix something.

[bryant]

Ouch, sorry about the flame, if that is the way you took it. We on the East coast consider several as usually meaning 2 or 3 or 4. However, three to four weeks might be construed as "many" long nights.

Once again, my mistake, just thought it was odd that
you could've typed that fast.

[ddouglass]

Originally Posted by GD123

I seem to recall a version that caused a catastrophe with EDITED/IMPORTED BINS upon rebuilding the DB. Actually, I take it one step further and rename the BINs to CDGs and Import as a HDCDG.

This was corrected as soon as it was found and no longer is an issue. In actuality the BIN and CDG are the same, so renaming isn't necessary.

MP3 is really the worst compression format ever devised. The loss of sound quality is not offset by the amount of storage space saved.

Steve, if those files came from original CDG discs and were not originally MP3+G zip format I would highly recommend you go back and import directly from the disc to get the best sound quality. If originally MP3+G then do as GD123 says and uncompress to BIN and import that way. Once you have them in KMA format then you can use that as your backup.

[gd123]

This was corrected as soon as it was found and no longer is an issue. In actuality the BIN and CDG are the same, so renaming isn't necessary.

As usuall, you missed the point.

And, the point is:

BIN was the problem...not CDG. Renaming an extension takes all of 1 sec.

Fool me once, shame on you...Fool me twice, shame on me.

With each version that comes out, I would have to TEST to make sure that what was being imported, as BIN, wasn't going to be hosed later by editing and rebuilding, etc. So, why should I go through all that testing for peace of mind?

I use a, known good, version to import with and will NEVER use any other version.

I ONLY use newer versions at shows. And, even that has stopped since v3.312, which is the last update that works 100%...screen redraw problems and all, since v3.313 to current.

My suggestion stands...Convert to BIN, rename to CDG, and Import under the CDG tab.

[ddouglass]

Originally Posted by gd123

As usuall, you missed the point.

And, the point is:

BIN was the problem...not CDG. Renaming an extension takes all of 1 sec.

Fool me once, shame on you...Fool me twice, shame on me.

With each version that comes out, I would have to TEST to make sure that what was being imported, as BIN, wasn't going to be hosed later by editing and rebuilding, etc. So, why should I go through all that testing for peace of mind?

I use a, known good, version to import with and will NEVER use any other version.

I ONLY use newer versions at shows. And, even that has stopped since v3.312, which is the last update that works 100%...screen redraw problems and all, since v3.313 to current.

My suggestion stands...Convert to BIN, rename to CDG, and Import under the CDG tab.

And mine still stands that the problem was corrected as quickly as it was discovered. And no one has reported the problem since that correction. MTU has done nothing but try to improve their software and to give us what we ask for in a karaoke hosting program.