Hey,
I have found that when opening a stream in HW3D, then Playing it but with the paused flag on, then changing the frequency over about 12% (Say SetFrequency 60000) and then playing (unpausing the stream) will result in no sound being played.
If you first start the sound and THEN change the frequency then there is no problem.
Is this a bug in FMod, DirectX or my code?

Just one tick less still gives the same problem, but two ticks (I think basic acceleration) will solve the problem.
I’m using Windows XP Pro with a SB Live! Value.
When the acceleration is lowered, it also seems fmod is getting more control over the sound, as fmod’s vu function seems to work on these streams (which it did not on highest acceleration)

When on highest acceleration, the problem seems to occur at +-9% (+-47628 Hz).
Can this bug be fixed? Since I don’t think I can tell everyone to lower the acceleration.

I haven’t tested this yet, but when on lower acceleration, the vu works again, so does this mean the dsp callback gets the sound also, and if yes, what will it do with 3d sound?

I guess recording the mixed output of Hardware channels still isn’t possible?

[quote="brett":avfn06q4]i think it is a driver bug not fmod, im getting a strange result with 3d streams also on the extigy. Simply changing it to use software buffers instead of hardware buffers (in dsound) makes it work, which is the same as lowering the acceleration level in the control panel. [/quote:avfn06q4]
Hi ! This method produces unexpected results on the Audigy ; my program now works fine, but the sound spatialization doesn’t work correctly anymore (neither does the audigy built-in speakers test). Is this a solveable problem or do I have to buy a bugless (at least with FMOD) multichannel soundcard ?
Thanks a lot

In v3.61 I was able to set the frequency down to 100Hz as documented in the chm file. Maybe this extra contraint for hardware channels should be documented.
I checked out my DirectX caps and
dwMinSecondarySampleRate = 5000
dwMaxSecondarySampleRate = 48000.
Setting the frequency above 48000Hz doesn’t cause an error.

[quote="brett":3bihsy7y]you never could.
look at your caps in directX caps, and you will see that your sound card cannot change the frequency above or below the min/max values.

the entries are
dwMinSecondarySampleRate
dwMaxSecondarySampleRate

fmod just clamps to these values now because it is nescessary to know instead of ignoring the error.[/quote:3bihsy7y]