Strange... vgmstream detects correct codec (XMA2) irrespective of extension. Just trimming first 4 bytes was the definitive solution, without needind the .txth.
Strange... vgmstream detects correct codec (XMA2) irrespective of extension. Just trimming first 4 bytes was the definitive solution, without needing the .txth.
Well... I though that, in the past. So, now I'm mistaken. But I preferred the ".txth"-governed approach of playing sound files instead of modern (internal) vgmstream-mandated extension-based. But some media players interferre with that, I reckon.
What player are you using? winamp (as I), foobar2000, xmplay, audacious Did you install latest vgmstream libraries/plugins? Besides, the renaming to .xma2 should apply to the trimmed .wav files I put in this link NOT the originals.
Ask the moderators of vgmstream to support these files. They are supported, your setup/configuration must have something specific going on.
IMG Open foobar2000 application. Go to File -> Preferences. At "Components" section, drag&drop the "foo_input_vgmstream.fb2k-component" file that was just downloaded. Accept the warning, press Apply then OK buttons & restart the application.
IMG When you want to play those .wav files, vgmstream (or fb2k maybe) will protest.
IMG So, the course of action is to rename those .wav to a format recognizable by vgmstream, in this case, .xma2 ...
IMG ... and thus the (internal) format is recognized allowing the files to play.
So, try to update your program (& component) version to latest (for both).
I tried following your instructions and it still doesn't work!! *bawls* How is it possible that your's work and mine don't? You're not alone sir, I'm baffled at your case too. Only vgmstream authors might answer your inquiry.
If I am to hypothetize on your case, it might be that there's another plugin, system-wide maybe, in your side that interferes with vgmstream.