- by AnonRunzes at 11:20 AM EST on January 3, 2018
- I'm pretty sure I posted my deinterleaver script at some thread. Well, now you see it:
Alpha23's "deinterleaver" script barely worked, as even in his "latest" version he simply decided that putting out bunch of warnings that prevented you from actually deinterleaving the file with his script at all was a good idea.
edited 11:30 AM EST January 3, 2018
- by jeangene91 at 10:51 AM EST on January 4, 2018
- Thank you. Your deinterleaver created the .str files. When creating the .genh files, should the values in VGMToolbox be what Mygoshi suggested? Because I tried it and got crackling noises.
- by AnonRunzes at 11:06 AM EST on January 4, 2018
- "When creating the .genh files, should the values in VGMToolbox be what Mygoshi suggested? Because I tried it and got crackling noises."
Actually... I'm not too sure about that. At best, due to the nature of the audio codec itself(which is a non-linear kind of ADPCM codec), you could be sticking with the wrong interleave value. Try 0x8000 as the interleave value.
In the meantime, I'll just be trying to mess with these files myself with the samples you just provided just to give you an "correct" answer.
Okay, for "2-channel" files you can try the 0x8000 interleave value. Anything beyond that needs the 0xd800 interleave, although the output file(when converted into GENH as that untouched file that is) might be a garbled mess at best. As I also found this similar "stereo-interleave" Xbox IMA variant in Shellshock Nam' 67, you might need to make a few extra steps for this.
So, the best way to tell if a .wav.str file has two or six channels, take a look at a .wav file that accompanies it through a hex editor. If you know what hexadecimal numbers are, let alone which terms are used when it comes to "hexadecimal" numbers, you're good to go.
Okay, so you opened a .wav file with your hex editor. Take a look at the 0x70 "offset" of a .wav file. The 0x01 value in there indicates the .wav.str file in itself is a stereo file in itself. When you see any number beyond that at that exact offset of that exact .wav file(although I've only seen these files store as far as the 0x03 number in there), that means how many "stereo" audio layers are there. Keep that in mind before splitting anything.
After you're done finding that out, here are the interleave for these .wav.str files:
"stereo" files(as seen through an accompanying .wav file) - 0x8000
"2-3 stereo" files(as seen through an accompanying .wav file) - 0xd800
Now let's move on to the actual part. So you splitted everything containing 2-3 stereo files(yes, these .wav.str files) using my script, with LAYERS set to 2-3(as, in the information you have in mind from that accompanying .wav file that forms the soul of a .wav.str file) and the INTERLEAVE value set to 0xd800. Now you can convert these splitted files into GENH files with that exact values mygoshi suggested, however keep in mind the interleave I just posted here. The 0x8000 interleave value applies especially for all stereo files, even splitted ones so use 0x8000 instead for the interleave value.
The result will be "playable" GENH files out of these splitted "stereo" files. That's as far as I can go.
edited 11:36 AM EST January 4, 2018
- So Close I Can Taste It by jeangene91 at 9:43 PM EST on January 4, 2018
- The .genh files are made but their length is 0:00 in Winamp. Unless I missed anything else in the hex editor or some missing component (like how VGMToolbox's XMA converter needs ToWav and SoX), I have to throw in the towel.
I appreciate all you've done to help with this.
- by AnonRunzes at 10:10 PM EST on January 4, 2018
- You're welcome.
- It Works! by jeangene91 at 4:11 PM EST on January 17, 2018
- I decided to try converting the files again with the specs and values, and the .genh files play. I don't know what I was doing wrong before, but the process works. Thanks again for all of your help.
HCS Forum Index
Go to Page 0 1
Search this thread
Show all threads
Reply to this thread:
Halley's Comet Software
Generated in 0.0028s;