I posted this question btw in[url=http://www.fmod.org/forum/viewtopic.php?t=1659:1c18ik6y]another topic[/url:1c18ik6y], but there it will be overlooked, I think.
I created a FSOUND_STREAMCALLBACK using FSOUND_Stream_Create.
The docs say, when it is created by FSOUND_Stream_Create, it’s return-value can stop the stream, when it is returning 0.
In fmod 3.61 this worked fine, (not REALLY fine, because the other playbackbuffer is always played one more time before stopping) but in fmod 3.62 it has no effect.
Is this a Mini-Bug ?
If yes, and when it will be fixed, could there be an option for it of e.g.:
returning 0 = play the other buffer and stop then.
returning -1 = stop immediately at this moment.
The new fmod.dll doesn’t work here – I think it is the cdecl-Version, isn’t it ? Could you please update the stdcall-DLL, too ? I tried the one from the download-section, but it seems to be the old one.
Thanks a lot for your fast response ! 😛
Did you test the cdecl-version, the ‘normal’ fmod.dll ?
I cannot implement it, because I use PureBasic, therefore I need the stdcall-DLL (which you can download seperately from the Download-section) with the callback-functions. I just tested this one again – and this one doesn’t work until now.
But I have time … it’s getting summer here … 8)
Brett, why not just use stdcall as the primary calling convention? Most DLLs use stdcall anyway, and I don’t see any real advantages to using cdecl as the primary convention (even ST series, which is a C/C++ only library, uses stdcall)…
Okay, okay, don’t jump down my back Brett. I hadn’t even thought of it that way, since I was going by the assumption that most people recompile their software after updating to a new version of a library (I always recompile after downloading an updated version of FMOD). I guess that’s what I get for assuming.
If you can’t redo FMOD to use stdcall by default though, you should include stdcall fmod.dll in the main API distribution (say in api\stdcall), then in the docs or the readme, put a note about Visual Basic; something saying if the user wants to use FMOD callbacks in VB, they have to use the fmod.dll in the api\stdcall folder.
Please login first to submit.