Disk ID# restrictions?

[fairway01]

Hi,

I imported a custom assembly of track 15's that were muli protected. I gave the disk id# a value of 'Track15sV1' and subsequent discs had V2, V3, ect. After successful import I forgot about it without testing. At a later date I tried playing one of these songs in Hoster and got the red error label. After further investigation I determined all the songs that had the disk id# (listed above) were bad. I re-imported them with a different disk id# and they all worked. Just curious, but are there any naming covention restrictions with the disk id# and what would be wrong with the label above? Nothing about this in the Hoster manual that I could find.

Thanks,
T

[jdavia]

If you can't find the Disk in the Database you will have to make a custom disk.
Using the "Customs" tab to import your songs, you should be able to use any reasonable short name you want in the BRAND field. I was lost for a name once so I used my initials. I think there are some characters you can't use, but using all letters and numbers should be OK. But the Book ID must be in numbers.
I haven't tried it yet, but in Windows Explorer I believe you can rename the files, but you will have to update the Database. That is quicker than recording all over again. You can do a Find/Replace/All in Word.

[admin]

Originally Posted by fairway01

Hi,

I imported a custom assembly of track 15's that were muli protected. I gave the disk id# a value of 'Track15sV1' and subsequent discs had V2, V3, ect. After successful import I forgot about it without testing. At a later date I tried playing one of these songs in Hoster and got the red error label. After further investigation I determined all the songs that had the disk id# (listed above) were bad. I re-imported them with a different disk id# and they all worked. Just curious, but are there any naming covention restrictions with the disk id# and what would be wrong with the label above? Nothing about this in the Hoster manual that I could find.

To our research on this, this problem can only happen if you move the files after importing them, and have not run the Build Songs Database command. Then, whey you add them to the Playlist, the ERROR appears because the song is not where it belongs.

Turns out, the DiscID field allowed any alpha-numeric-symbol string with infinite length. That was a potential hazzard waiting to be discovered.

In Hoster 2.214 we have limited the DiscID entry to 12 alpha-numeric characters. You can uses symbols at your own risk as to where they end up in the database... I'm not documenting all the possible conditions. Use alpha-numeric characters only for safety sake.