HDMP3G & CDCDG

[nreel]

FYI
This doesn't effect any Songs that were Imported via a CD.

Any Songs Imported via a CD Disc may be Edited as many times as is necessay and Re-Building the DB will not have any negative effect.

Aarrgee
As to your question, which, AGAIN, only applies to HARD DRIVE IMPORTS, concerning any Edited HARD DRIVE Imports, where the DB HAS NOT been Re-Built, working OK with a Future "Fixed" version of Hoster, I will re-install 3.110 tomorrow, EDIT some HD Imported Songs, NOT RE-BUILD the DB, Install a Hoster BETA version where this problem has been fixed, RE-BUILD the DB to see what happens, and give you an answer.

Norm

[nreel]

Aarrgee

Sorry, it is as I suspected meaning that, since Editing a Trk causes the HEADER to Change, and, therefore, if the DB is Re-Built, Hoster will read HEADER info, as it Builds the DB, and Write that info into the Songs.MDB.

Originally, the EDIT SONGS Menu was programmed to EDIT the ONLY TYPE of Trk Hoster Imported, which was a CD IMPORTED KMA TRK. Now there are 5 (Five) Types of Trks, which are CDCDG (formerly know as, and Original TYPE=KMA), HDCDG, HDBIN, HDMP3G, and HDZIP.

The vast Majority, of Hoster Customers, are CD Importing Customers that this problem WILL NOT affect.

It was only recently that a decision was made to allow HARD DRIVE Imports in order to accommodate those Potential Customers who have large libraries stored on their Hard Drives.

As HARD DRIVE Importing is fairly new technology to Hoster, obviously, a minor setback has occurred in ONE module of all the intricate programming involved.

One way to fix any HD Imported Trks that were Edited is to use your Backup Trks and copy them to the Drive/Folder you use to run your Show. Hopefully, you will not have copied your Edited Trks over your Backup Trks.

If you are at a Show and you find that a Trk won't Play, you can Open the Songs.MDB, perform a SEARCH for the Trk in Question, TAB over to the TYPE Field and CHANGE the PREFIX from CD to HD...then the Trk will PLAY. This is a temporary fix as Re-Building the DB will cause the Prefix to CHANGE back to CD. The only Permanent Fix is to Re-Import the Trk.

If there is anyone who has EXCLUSIVELY Imported from the Hard Drive, EDITED several songs, and subsequently Re-Built their DB, it will be very easy to determine which Trks need to be Re-Imported to fix the Problem Trks permanently. Just perform an ALPHA Sort on the TYPE Column in the Songs.MDB. This will cause all the CDCDG Trks to be listed together. Simply note the DiscID of any Trk that is Listed as a CDCDG and Re-import the whole Disc or only the altered Trk(s) from that disc.

Norm

[Aarrgee]

Sorry but I still don't get your answer to my question. My question is: All my KMA were converted from zips on my HD. over 20,000. Since converting them to KMA's I have edited hundreds but I have not rebuilt my database because of the known problem which I knew all along. (Saved Hoster entire program folder) So now, having not rebuilt my database, I wanna know if rebuilding it with the update would not cause the problem again. Sorry if I didn't understand your answer, thanks again for the response.

[Wallymeister]

Aarrgee,
I think that the update will fix the problem with a rebuild database command. Re-importing will not be needed I'm sure. You will probably have to delete song.mdb before a rebuild though.

That's my understanding
Wally

[nreel]

Post #11 by Aarrgee

Sorry but I still don't get your answer to my question. My question is: All my KMA were converted from zips on my HD. over 20,000. Since converting them to KMA's I have edited hundreds but I have not rebuilt my database...I wanna know if rebuilding it with the update would not cause the problem again. Abridged / Emphasis added

I thought I had answered with this POST:
Post #10 by nreel

Sorry, it is as I suspected meaning that, since Editing a Trk causes the HEADER to Change, and, therefore, if the DB is Re-Built, Hoster will read HEADER info, as it Builds the DB, and Write that info into the Songs.MDB.

I will explain further.

You have CHANGED the KMA HEADER of EVERY TRK YOU EDITED. The "Damage" was done when the Trks were EDITED. Re-Building the DB has nothing to do with Damaging a Trk. Re-Building the DB simply READS and REPORTS what is ALREADY in the HEADER.

Therefore, the Answer to your question is NO. No, a FIXED Version of Hoster will NOT do anything to correct Headers of Song Trks that have been EDITED via the EDIT SONGS Menu of released versions of v3.110 and possibly v3.108.

But, at least, it will be easier for you to identify which Trks to Re-Import by following what I stated earlier:

If there is anyone who has EXCLUSIVELY Imported from the Hard Drive, EDITED several songs, and subsequently Re-Built their DB, it will be very easy to determine which Trks need to be Re-Imported to fix the Problem Trks permanently. Just perform an ALPHA Sort on the TYPE Column in the Songs.MDB. This will cause all the CDCDG Trks to be listed together. Simply note the DiscID of any Trk that is Listed as a CDCDG and Re-import the whole Disc or only the altered Trk(s) from that disc.

[Aarrgee]

Okay maybe you're not understanding my question. Here goes again. All the tracks that I have edited play perfect because I have not rebuilt my database. All I really want to know is that if with the new update, can I go ahead and rebuild my database and if the KMA's would play well just as they are doing now? I know that when I edit a KMA file, the header changes and becomes ireversable. That is why I haven't rebuilt my database because the bug would change it from HD to CD and thus would cause an error.

[nreel]

That is why I haven't rebuilt my database because the bug would change it from HD to CD and thus would cause an error.

It seems to me that you already answered your own question in the QUOTE above.

If you Re-Build your DB with any Version, NEW or OLD, any EDITED songs that were Imported from the Hard Drive WILL NOT Play! <---Is that clear enough?


Post #12 by Wallymeister

Aarrgee,
I think that the update will fix the problem with a rebuild database command.

This is wrong. There is NO Problem with the REBUILD DB COMMAND.
The problem is with the EDIT SONGS Menu.