Quote:
Some MP3+G and ZIP files already don't have Brand-DiscID-Track# identification. Currently, it is impossible to import these into Hoster 3.108. Hoster 3.109+ MUST allow batch importing INDIVIDUAL Files as KMA files indexed in the Songs Database.
.................
Here is a problem. The Import screen Status field shows IMPORTED when a file has already been imported. This CURRENTLY requires the DiscID, which is uniquely tied to the BookID ROOT. I doubt if we can continue to do this check and verify. There is a LOT of code and error checking behind this function. I'd hate to see it disappear.
|
For MP3+G and ZIP files without a diskID, What about using an entry such as cst????-??. (I used cst = to custom for the example, the first 7 characters being the DiskID, the second two after the - being the Track)
Here's the logic in this:
- Say I have 12 songs by elvis that are in MP3+G format I want to import. Using the second method I could assign a DiskID of cst1001-01 for the first then increment the number after the - for each one, putting all the songs by Elvis under one DiskID (the number after the - being used as a TrackID)
- In a batch import of non-related songs contrary to the above, You could either have the user enter a starting DiskID (CST1001 for example) and a Max Track ID (say 1 through 20), or have an Auto-Increment DiskID check box that would automatically find the first open CST???? Disk ID available and start from there. The import could then start with CST0001-01 for the first imported song, then increment the track ID until it reaches the Max value. Then move on to the next available DiskID (CST1002). I'd recommend a check box for this along the lines of "Automatically increment DiskID". This way, those who want to assign their own DiskID's for each "set" can, and those who just want to import them can tell it to Auto increment and let it go.
This would assign all imported songs with a unique DiskID-TrackID combination. And unless I missed something (highly possible) would keep the existing BookID system intact. Granted there is nothing to prevent the user from importing the same song multiple times under multiple DiskID-TrackID combinations except being cautious in the even the song does not have the combination in the file name.
Also, say down the line I get 3 more elvis songs I would like to import, I could go back to the original DiskID (CST1001 in the example) and add them to the end using the next free TrackID entries. In the example that would be CST1001-13, etc.
This would give users some flexibility in maintaining their lists when it comes to MP3+G's that have no associated DiskID-TrackID, while maintaining the current structure.