[admin]

As kjzone has pointed out, there could well be differences in the files read in from one disc as a .bin or as .cdg. However, we have never said we are compatitble with CDRWIN, and have never made any legal claims on our website to that effect. I personally have not done binary or hex compares of .bin -vs- .cdg imported files, nor will we ever take the time. We have 5 products that we produce that covers all phases of what is needed for Karaoke CDG production.

We have designed our products for the Karaoke Market, Goldenhawk has not. Their product is far too technical for (IMHO) 98-99% of this market. Thus, anyone using CDRWIN is more technically astute than the VAST marjority of the Karaoke market. Enjoy, that you have the technical chops to use CDRWIN, but please, keep the false advice that MTU MUST support .bin files out of MTU's Forums.

The bin/cdg controversy is OF NO IMPORTANCE TO THE VAST MAJORITY OF MTU'S CUSTOMERS. It is not something that will benefit MTU or our client base, and we will not modify our products to resolve any differences between .bin and .cdg files. Our format as stated before, is fully self-sufficient to have everything in one file that is needed to import, play, assembly, and write a CDG song to a CDG Karaoke disc. That, my friends is the controlling factor. There is no other reason other than engineering esoterics that is even at play here.

Some users have posted that they can interchange .bin and .cdg files bi-directional. I believe that to be the case, knowing what I do about CDRWIN and Microstudio. If there are some conditions where this is not the case, Frankly... I do not care one bit about it.

Thus, in closing, I am not trying to be arogant, but clearly state the fact that MTU has designed the .cdg format specifically to meet the needs of the CDG Karaoke communicty, not the disc-duplication community. We did this way before the "johnny come lately's" redefined the .cdg for their purposes, ignoring there already existed a "standard definiton" for the .cdg extension. In the 32 years I have been developing products with crack-engineering teams, we often have defined the "bleeding edge" of technology evolution.

The point man usually is "shot at" because he is out there and is cutting the path for others to follow. We are visionary. We will not modify our products to work with CDRWIN, as that is NOT a product our market demands. This thread is closed.

QED!