Can System::createSound pay attention to the CREATESOUNDEXINFO structure’s "format" field in all situations, and if it’s specified when not absolutely necessary it’s treated as the user specifying the sound format provided.
If the sound is not in the specified format, an error is returned (even if it’s a valid sound in some other format)
As it is now I pay the cost associated with "figuring out" the sound format every single time, when I often know what the format is ahead of time.
- Dogbert asked 11 years ago
[quote="Adiss":3r12wnv1]Dogbert, there already is a suggestedsoundtype member in the FMOD_CREATESOUNDEXINFO structure. I don’t think it returns an error if it’s not in that format, but it does skip directly to the format that you specify.[/quote:3r12wnv1]
Hmm, this looks like exactly what I want, I guess I got so hung up on "format" that I missed it altogether.
I’m suggesting it be changed so that it throws errors in all situations (OPENUSER/OPENRAW and otherwise) when it is specified and the supplied data is not in the specified format. A "suggestedsoundtype" would be similarly useful.
I’m just looking to eliminate the 15+ different format checks whenever I create a sound when I already know what format the sound should be in.
‘format’ is for FMOD_OPENUSER or FMOD_OPENRAW as specified in the documentation.
Are you talking about suggestedsoundtype or something? I’m not sure what you’re talking about. The format specifier is used for user or raw sounds and doesnt cause errors with normal sound file use.
Please login first to submit.