I'd like to make a few requests:
1. On this thread, please add a description after each tool. So instead of
ValleyBell wrote:
Current tool list:
dro2vgm, optvgmrf, vgm_cmp ...
you can write:
ValleyBell wrote:
Current tool list:
dro2vgm - Drowns two vegan monks,
optvgmrf - Opens tomb of vortigaunt mistery friend
vgm_cmp - Very green monster comparison
...
2. Have the tools behave more 'normally', like unix commands. So instead of vgm_cmp waiting for user input of parameters and after it has finished, add some command-line options such as:
Code: Select all
-o --output Output file
-s --start Start sample
-e --end End sample
-l --loop Loop sample
-a --auto Detect and remove silence from start and end automatically
-h --help Display help
-v --version Display version
and remove the wait-for-key at the end. For that sort of thing, use a batch file that reads input and then runs vgm_cmp at the end. Have sane defaults for -e and -l (-2 -1).
3. vgm_cmp (or another tool) should detect and remove silence. I know there are some initialization commands separated by waits, but the silence can be removed intelligently, even if it ends up being chip-specific. Just error out or don't remove any silence if the chip is not supported for auto silence removal. I would suggest supporting YM2151 and MSM6258 for starters, since that is what I need.