|
cdgmerge
Bandl,
When using CDGMERGE, all of your file names must conform to the old DOS standards, as far as max number of characters, number of spaces, etc. Otherwise it won't work and won't tell you why.
I completely agree that cdgmerge is tricky to use. However, I have never had any problem with its reliability or how well it does its job. I wonder if your problems are based on file format. Often, what one software manufacturer calls a .CDG file may actually be a .BIN and vice versa. Example, what KHPRO saves as a .CDG is the same as goldenhawk's .BIN. Just change the file extension to .BIN and you can burn KHPRO files with CDRWIN. Likewise, you may have to change the file extensions in order to get CDGMERGE to function correctly, as well as set CDGMERGE's switches (-b, -c etc.)
I think the file-format confusion stems from some CDG software vendors save the graphics in a separate file from the audio, and refer to the graphics file as a .CDG. This is CDGMERGE's definition of a .CDG file.
MTU and CDGCreator on the other hand, save the audio & graphics together in the equivalent of a .BIN file and call it .CDG
|