The program now supports generating multiple floppies disk images and sorts the files to try to fit as many as possible. I think the program is almost ready to be released, but I've read on about the amiga's file system and some Amiga programming in general and I can see how a program of this type might be made much, much better.
For starters, the OFS (Old File System, used on the Amigas with kickstart 1.X) use only 488 bytes out of 512 on the floppy block. The other 24 bytes are used for some metadata (to make floppies more reliable), also, each file takes one extra block just for it's name and other data and you can't have 2 files on the same block. Let's take 1kb file for example.
1 Block (512 bytes) just for it mere existence
3 Blocks of data (488 bytes each), the last one only takes 148 bytes, but the second file can't write to that empty space, it has to use another free block.
Also unpacking the files for the playback with real filesystem is a big problem. If you're not aware, The Amiga has 2 types of memory. Chip mem and Slow/fast mem. Chip mem is what is built in, so for the A500 it's 512 kb, Slow/Fast is what comes on expansions. Most people have the 512kb chip + 512kb slow Amiga 500. If you want to play any music or display any graphics it has to be in chip mem, custom chips can only read from there (hence the name), the other memory is only for the CPU. What's the problem then. Well, HIP player will load the file from floppy to whatever memory is available, parse it and when it finally decides that it is a music file and what routine to use it only then loads it to the chip mem so it can work with it. When you have packed file that's even worse, because first you load the packed file, then you unpack it and only then HIP can take look at the file. That's why even though I have 1MB amiga I can't play modules that are larger than about 300kb.
If I was to write my own player and depacked I'd allocate let's say 400kb of chip mem for the module and hardcode that address into the depacker so it always depacks there and the player could just go from there. I could also use all the 512 bytes of the block on the floppy disk to store more data. All of this is planned for v2 of my program, unless someone beats me to it.