It'sa me, Mario Leo!
Nooooo! If that happens, I will withdraw my support of the project... Hehe.
I'm out of town at the moment, but I'll be back home this weekend. I can trace the pin of the 5205 ADPCM chip to see what clock signal is driving it. I don't remember off hand and Charles MacDonald's doc doesn't give any specifics about it. I also don't have the source code to mednafen with me to look at (I'm sure the emulator has the exact rate other wise audio would slowly get out of sync in HuVideo stuffs).
Excellent! Thanks! It'd be good to clear this up, and not just for this, for other dubbing projects as well (
although it's a very minor difference in value, you do want precision). Shadoff's judgement is excellent, but a 2nd opinion won't hurt and maybe you'll likely just wind up verifying what he used. Oh, I'll see if Charles is hanging around on IRC and raise the issue. I met him a few weeks ago, pretty cool guy.
EDIT: I got a response from Charles and it looks like we will need to change that sample rate! He pointed me to a document that he wrote long ago that's only available through a wayback internet archive so I uploaded it to my site, and linked it below. I highlighted the table row in question:
http://www.ysutopia.net/special/MSM5205.htm#MSM5205_timingThe value would have to be somewhere around 16,043.75 Hz! We are gonna need some changes made to the batch files after all! It appears the info I ran into back in '05 (Khz = 32 / (16 - _DH)) about a divider and only 16 possible sample rates was on to something. Problem is Shadoff's ADPCM tools don't handle decimal points and a possible audio tool that developers used at the time (SOX) doesn't either! Which brings us to that:
http://sox.sourceforge.netCharles says the ADPCM format of the Oki MSM5205, which is what NEC gaming systems were using, is identical to the Intel/Dialogic VOX format which this 'Sound eXchange' utility ('sox') supports! Meaning, the ADPCM tools that Shadoff made may not have been necessary! I downloaded SOX and am currently reading the documentation on its use. Example:
; Convert WAV file to 32 KHz ADPCM data
sox music.wav -r 32000 music.vox
Thinking about it some more, if developers couldn't use a decimal point when encoding to ADPCM format, then this raw 16,043.75 Hz can't be the value that was used! I would have to assume that at the commandline, they ran, "sox music.wav -r 16000 music.vox" or "sox music.wav -r 16044 music.vox" perhaps
Well, we still need your help, Bonknuts!! I'm glad I never forget about this issue, I thought that there still might be a minor problem here.