Importing zip files from HD?

[admin]

Originally Posted by bryant

Unless, I might have songverted those last three folders from zip to zip first, and if sonverter converts (processes) them in alphabetical order does that set them up for "proper" transmission to Hoster afterwards?

Songverter will process files in some order, and I'd have to get our programmer to search the code to define that order. How they are stored back to the hard drive when converted would make sense it establishes an order in the Windows FAT table for that drive. Then, if you copy that block of files to your Flash Drive, the FAT order determines the order they copy in. That could explain your "right" ordering.

Hoster cannot guess what you want to do. It is given files with filenames. We have done everything... EVERYTHING... possible to make it as flexible as we can.

If your filenames have no DiscID, you are telling Hoster "I don't care" which are grouped together, up to 99 in the order that Hoster and Windows' FAT find them in.

If your filenames have no Track#, you are telling Hoster "I don't care" what track Hoster will then assign, up to 99... soon to be 9,999 in Hoster 4.00x.

These are 2 facts you must deal with. If you want to group by DiscID, you must provide one. If you want to order by Track#, you must provide one. We can't program in ESP to read your mind. We have programmed total flexibility to allow you to define what fields are in what order in the filenames. Beyond that, it's impossible.

FYI: We are beta testing Hoster 3.318 with a number of bug fixes for 3.310 and higher users. We expect to release 3.318 this week. One of the "bugs" we fixed is assigning the Track# from Hoster's Import Hard Drive Files screen, Track List at the bottom. Each "slot" in this list has a track number. If your filenames include a defined Track#, then they are used to place each track into the correct numbered "slot". If there are no Track#'s defined, then we put them in first to last slot positions. In 3.318, we again are assigning the slot number to be the Track# in the KMA file. This will allow you to import again when your filenames don't contain a Track#.

That's the best I can do to define the problem you are struggling with.

The real answer is... add DiscID-Track# entries to your filenames.

That's all I gotta say about that!