![]() |
|
Hoster Help Post Hoster questions, tips and suggestions here. |
|
Thread Tools | Display Modes |
#7
|
|||
|
|||
Re: Hoster 3.2 - Song Book and BookID (or SongID) renumbering
Quote:
![]() Digital Party... THANK YOU for your suggestion. That is what I am looking for; working together with us. If we simply start numbering the "new BookID" from the last one in your Songs Database, that looks like it IS the answer! I have just spent 5 hours coming to that conclusion. ![]() ![]() ![]() However, we don't have a buy-off from MTU Programmers yet. It does look very promising though. 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. While you have been posting, I have been thinking... because I was ALREADY AWARE reprinting Song Books is expensive. When we cut over to "Song based BookID", we would do the following:
If song filenames only have Title and possibly Artist, duplicates will happen. When MP3G and ZIP filenames contain the DiscID and Track# fields within the filenames, Hoster 3.108 searches the Import and Song Databases. If the DiscID is found, it automatically fills in the Title and Artist fields before importing. We will add a new means into Hoster 3.109 (not in 3.108) to batch import MP3G and ZIP files. You can have FAST IMPORT, or CAREFUL IMPORT. The latter takes time and attention. We will try to create the new means to be unattended if desired. There is no other way to get 20,000 MP3G songs into KMA files and indexed in the Songs Database. At 1 second/song (which is the right ballpark for converting MP3 based files), 20,000 will take 5.55 hours. That's with the FAST IMPORT with unattended operation. If you are involved, it will take MUCH longer, but the songs will then be CAREFULLY IMPORTED. Our goal will be to provide the "tool" to allow both. Now it's your turn... please evaluate and post your comments on these proposed changes. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|