4.11 to 4.22- import zips

[Deeter]

First off, I apologize if this has been covered before, but I cannot find it in the recent threads.
I upgraded yesterday from 4.11 to 4.22. Since I went 2 weeks over my year, that cost me the $69.99. That's ok, I wasn't paying attention.
Last night I went to add a few zip file songs to the database. Found them, imported them and they function fine. No out of sync problems as previously experienced.
But in the previous versions of Hoster, the zip was converted to a kma file which was then deposited in my KMA files directory.
Now the original zip is left in it's current location and a kmh file is created in the same folder, doubling the number of files.
I learned that there is no "moving" these files, Hoster will not find them. So you must move them back, delete them within Hoster, then re-import them from another location where apparently they should reside forever.
So when loading new zips, is the suggested way to create a new folder each time in the KMA files directory?
And I am just asking- what was the reason for the change in file handling procedures between the older versions of Hoster and the latest?
Thanks

[ddouglass]

Originally Posted by Deeter

First off, I apologize if this has been covered before, but I cannot find it in the recent threads.
I upgraded yesterday from 4.11 to 4.22. Since I went 2 weeks over my year, that cost me the $69.99. That's ok, I wasn't paying attention.
Last night I went to add a few zip file songs to the database. Found them, imported them and they function fine. No out of sync problems as previously experienced.
But in the previous versions of Hoster, the zip was converted to a kma file which was then deposited in my KMA files directory.
Now the original zip is left in it's current location and a kmh file is created in the same folder, doubling the number of files.
I learned that there is no "moving" these files, Hoster will not find them. So you must move them back, delete them within Hoster, then re-import them from another location where apparently they should reside forever.
So when loading new zips, is the suggested way to create a new folder each time in the KMA files directory?
And I am just asking- what was the reason for the change in file handling procedures between the older versions of Hoster and the latest?
Thanks

Several reasons why this was done.
1. Hoster does not recompress any file that is already compressed by another format, such as ZIP, MP3, WMA, etc. So rather than creating a second full copy of the zip adding the Hoster header to it and rendering it useless for any other program.
MTU decided to create just the Header file (KMH) and added to where ever the muzic file is located. If you haven't noticed the KMH file is very small where a KMA would have been slightly larger than the original file. So actually you are saving space on your drives by not having two large files (KMA and original ZIP) and only have one KMH (256 Bytes) and one large file (ZIP). Also if you noticed Import was extremely fast.
2. This leaves the original file as it is allowing it to be used in other programs which was a request by users.

The KMH was needed basically for Video files because Hoster had no way to import these and this proved the easiest way to set that up to allow us to import Video Karaoke files and add them to our Song Database.

I do not currently use any ZIP, MP3+G, or Videos, but I do use some MP3 audio music files. I found the easiest way to do this was to create a separate folder in the same area where my KMAs or stored to put all my Music files in. This keeps the number of folders down for the Rebuild to search to build the Songs database.
If I had MP3+G or ZIP or Videos I would do the same thing for each of them.

[Deeter]

OK, thanks. I guess what I will do is build a sub-folder within my KMA files directory each time I load new songs. I keep a back-up of the entire KMA folder in case of catastrophe. As long as it doesn't bother Hoster to have the sub-folders in there, that seems like the best solution......

[ddouglass]

Just remember that if you have to reload from your back-up then you will have to be sure and list all of the folders separately in the Rebuild screen. Listing just the top folder will not get to the sub-folders in this case.

[RandyMcCharles]

I haven't tried to import any zips with 4.22 but I will in the future. Currently I import all new tracks on my desktop, then copy tracks to my notebook and add them to the notebook database. It sounds like I will not be able to do this going forward.
I understand the 'not modifying existing file compression' part, but why can you not move the files after they are imported?

[Deeter]

I assume that when the "wrapper" (kmh) is written and placed with the zip file, then there is a pointer in the songs database that points to that location. Move the zip, the pointer is no longer valid.
I understand the adding a tag (kmh) and appreciate the fact that it doesn't modify the zip, but it will still take some getting used to.

[RandyMcCharles]

If the zip and kmh are in the same folder the pointer is to 'here' (relative pointer) and you should be able to move the files. I assume that a 'fixed point' was used. eg 'C:\kma\zipfiles' but this is unnecessary if the file pairs are always kept together.

[ddouglass]

Originally Posted by RandyMcCharles

If the zip and kmh are in the same folder the pointer is to 'here' (relative pointer) and you should be able to move the files. I assume that a 'fixed point' was used. eg 'C:\kma\zipfiles' but this is unnecessary if the file pairs are always kept together.

The location is in the Songs Database and not in the KMH file. So if you move just the ZIP files it will not work. If you move both files then you will need to rebuild the database changing the Folder list to reflect the new location.
Any location where the ZIP files and KMH files are co-located has to be included in the Folder List in the Rebuild Database screen or they will not be included.

[RandyMcCharles]

Douglass. Excellent. I didn't understand that from the earlier discussion. That is exactly what I currently do so I'm happy.

[Joe Nieves]

Why can't a "Move" File or Folder feature within Hoster be added for this task, instead of Rebuilding the Database?

Joe...

[ddouglass]

Joe you need to put that idea in New Features.

[Joe Nieves]

Well Ok, the thread conversation was threading toward the "Move" File/Folder subject and remembered I thought of this idea years ago, but never posted, so I figured why not throw it in the mix..., wasn't trying to hijack the thread it just came to me then....

Joe....