0
0

Was just testing some different wave-sounds, and Fmod plays a 64-bit 192khz wave twice as fast. A 32bit 192khz plays fine though. Is this a bug in Fmod? Can Fmod handle 32-bit sound?

  • You must to post comments
0
0

I think you mean can it handle 64 bit sound?

What version are you using? I just tried loading a 64bit wav and it returned an error. Looking at the code there is a specific check in release i’m using that returns an error if the number of bits is not 32.

No it doesnt support it, all i can think if you really wanted this we could internally downscale it to 32bit ieee float?
Otherwise we’d have to introduce a 64bit pipeline which would increase the code size a lot with all of the new mixer/resampler combinations.

Well actually the whole dsp network stuff would have to double in size as well, so to keep things sane it would have to be downscaled to 32bit at some point.

  • You must to post comments
0
0

I thought a 64-bit wave referred to the fact that it could handle files over 2GB in size, which is useful for high definition files such as 192khz/24 bit files.

There’s absolutely no reason, whatsoever to go to 64 bit sample size in an audio file; 24 bits already supports a dynamic range greater than what the human ear can handle.

There is some good arguments for doing some internal processing at 64 bits, like increasing accuracy of IIR filters, but you definitely don’t need the entire signal path to be 64 bit floats.

-Matt

  • You must to post comments
0
0

Nope, 64 bit wav = 8 bytes per sample for a mono sound, they are huge and sound forge can write them out. It writes out a double float per sample. I don’t know why they exist.

  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.