The fileoffset now works like a charm. Great!!
I know that you have instructed me a lot of times about the mighty pitch dsp processor usage. But I have to disappoint you. I have two pitch DSP’s in a chain and there’s almost no indicator of processor use 😛
I LOVE IT!!
- ddebono asked 12 years ago
Really good work on this version !
I’ve remarked that these errors : FMOD_ERR_REVERB_INSTANCE & FMOD_ERR_DSP_TOOMANYCONNECTIONS are defined in
FMOD_RESULT but there are no corresponding description in FMOD_ErrorString.
I don’t know if it is intentional or an oversight …
A little other thing, in chm documentation : FMOD_SOUND_NONBLOCKCALLBACK callback is missing.
FMOD_SOUND_OPENEDCALLBACK do not exist, no ?
I was waiting to see if the new release fixed our last remaining issue, but unfortunately it didn’t .
What we’re hearing is sometimes streams don’t play or only play a part of the stream. This only happens with 3D sounds using hardware. 2D hardware is fine, as is software for either 2D or 3D. There is usually only 1 other stream going when it does this so I’m not running out of channels or anything else obvious.
We can usually reproduce it by playing the same stream over and over (but not looping.. just retriggering it at regular interval) and occasionally playing a different stream. What we hear is dropout of the looping sample, and sometimes the new stream is skipped.
When running realtimestitching.exe I get:
The procediure entry point ?init@System@FMOD@@QAG?AW4FMOD_RESULT@@HHW4FMOD_INITFLAGS@@PBX@Z could not be located in the dynamic link library fmodex.dll.
The other examples seem to work just fine.
If i open the realtimestiching example and compile it, it works fine.
Looks as though the executable in the bin directory is linked to an older fmod ?
Please login first to submit.