# MS ADPCM encoded .wav results in FMOD\_ERR\_FILE\_BAD using FMOD\_System\_CreateSound **URL:** \ **Category:** FMOD Engine\ **Tags:** cpp\ **Created:** [December 26, 2025, 9:05pm UTC](https://qa.fmod.com/t/ms-adpcm-encoded-wav-results-in-fmod-err-file-bad-using-fmod-system-createsound/23848 "2025-12-26T21:05:17Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![MatVeiQaaa](https://avatars.discourse-cdn.com/v4/letter/m/76d3ee/32.png) [@MatVeiQaaa](https://qa.fmod.com/u/MatVeiQaaa)\ **Post date:** [December 26, 2025, 9:05pm UTC](https://qa.fmod.com/t/ms-adpcm-encoded-wav-results-in-fmod-err-file-bad-using-fmod-system-createsound/23848/1 "2025-12-26T21:05:17Z")
MS ADPCM encoded .wav files with 16 bits per sample fail to load with `FMOD_CREATESAMPLE` and `FMOD_CREATECOMPRESSEDSAMPLE` flags, while `FMOD_CREATESTREAM` works as expected, but 4 bits per sample files always fail. Outputting the log, `[ERR] CodecWav::readInternal : acmStreamPrepareHeader returned 512.` can be seen. Tools such as VLC can play those files and display their codec information, so the header seems to be valid. From what could be understood in the documentation, this format is supported, and the log suggests that there is an attempt to load it. Is this a bug that’s meant to be fixed, or an expected behavior? This problem can be reproduced in FMOD 2.03.11, as well as 1.10.20. ---
**Author:** ![jeff\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/jeff_fmod/32/1766_2.png) [@jeff\_fmod](https://qa.fmod.com/u/jeff_fmod)\ **Post date:** [January 4, 2026, 10:14pm UTC](https://qa.fmod.com/t/ms-adpcm-encoded-wav-results-in-fmod-err-file-bad-using-fmod-system-createsound/23848/2 "2026-01-04T22:14:52Z")
4bit MS ADPCM is working fine for me as stream/sample/compressed in the latest version of FMOD. I don’t seem to have a 16bit MS ADPCM option in any of the DAWs I have installed- what DAW did you use to export these audio files? Can you please upload some of the files that are failing to play to your [FMOD Profile](https://fmod.com/profile#uploads)? ---
**Author:** ![MatVeiQaaa](https://avatars.discourse-cdn.com/v4/letter/m/76d3ee/32.png) [@MatVeiQaaa](https://qa.fmod.com/u/MatVeiQaaa)\ **Post date:** [January 5, 2026, 1:22pm UTC](https://qa.fmod.com/t/ms-adpcm-encoded-wav-results-in-fmod-err-file-bad-using-fmod-system-createsound/23848/3 "2026-01-05T13:22:31Z")
It’s not possible to upload a file to my profile without registering a product, and it’s not possible to register a product as a non-commercial profile. I could upload those files to my OneDrive and share the link there if that’s permitted. The files come from user-provided content, so it’s impossible to tell which DAW was used to produce them. Likely, they were produced with some early 2000s software. FMODex used to not have problems with them. ---
**Author:** ![jeff\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/jeff_fmod/32/1766_2.png) [@jeff\_fmod](https://qa.fmod.com/u/jeff_fmod)\ **Post date:** [January 11, 2026, 10:18pm UTC](https://qa.fmod.com/t/ms-adpcm-encoded-wav-results-in-fmod-err-file-bad-using-fmod-system-createsound/23848/4 "2026-01-11T22:18:34Z")
Sure you can send me a OneDrive link instead. ---
**Author:** ![MatVeiQaaa](https://avatars.discourse-cdn.com/v4/letter/m/76d3ee/32.png) [@MatVeiQaaa](https://qa.fmod.com/u/MatVeiQaaa)\ **Post date:** [January 11, 2026, 10:53pm UTC](https://qa.fmod.com/t/ms-adpcm-encoded-wav-results-in-fmod-err-file-bad-using-fmod-system-createsound/23848/5 "2026-01-11T22:53:53Z")
[FMOD MS ADPCM samples](https://1drv.ms/f/c/4cf08022feb1d9ab/IgAhteR61CTdSJNuyWnInfCvAWUw4lLpESLm7Mirt2ohcAY?e=A4QTJJ) ---
**Author:** ![jeff\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/jeff_fmod/32/1766_2.png) [@jeff\_fmod](https://qa.fmod.com/u/jeff_fmod)\ **Post date:** [January 14, 2026, 3:49am UTC](https://qa.fmod.com/t/ms-adpcm-encoded-wav-results-in-fmod-err-file-bad-using-fmod-system-createsound/23848/6 "2026-01-14T03:49:41Z")
Thanks, I can repro with these files. Looks like they have some sort of abnormal length which is affecting our decoder- I have passed this onto the Dev team to investigate further. I’m finding these files open fine in Reaper, so in the meantime you could potentially re-export these files in a DAW as a workaround.