0
0

I have a custom DSP generator and wondered why it wouldn’t pan either in 2D nor 3D modes. It seems in the current version this occurs in the ‘generatetone’ example too using built-in DSPs. So I’m guessing it’s a bug.

I’m only testing on the Mac at the moment but the problem (tested with ‘generatetone’) exists in API versions:
[list:wzxqg9r6][:wzxqg9r6]4.30.06[/:m:wzxqg9r6]
[:wzxqg9r6]4.31.05[/:m:wzxqg9r6]
[:wzxqg9r6]4.32.00[/:m:wzxqg9r6]
[:wzxqg9r6]4.33.00[/:m:wzxqg9r6][/list:u:wzxqg9r6]

It was fine in 4.28.08 but I don’t have any version in between 4.28.08 and 4.30.06 so not sure when it was introduced.

  • You must to post comments
0
0

BTW I got around this for now by implementing this as a custom sound rather than custom dsp and 2D+3D panning works as expected.

  • You must to post comments
0
0

Well this bug is in FMOD for years.
You can not do Pan or SpeakerMixes with PlayDSP created sounds. You will need to do those functions by your own when using the very narrow DSP to play back samples.

  • You must to post comments
0
0

Thanks for the tip.

But, the panning in the generatetone example worked in 4.28.08 (from Feb 2010) but not now.

On a related note then does FMOD_INIT_SOFTWARE_OCCLUSION and FMOD_INIT_SOFTWARE_HRTF only affect playSound()/playStream() and not playDSP() created channels?

  • You must to post comments
0
0

Hi, looks like this problem was introduced 17th of May, i’ve found the problem and fixed int on all branches for our next release.
If you want to pan the sound, use Channel::getDSPHead and then call DSP::setLevels in the meantime.

  • You must to post comments
Showing 4 results
Your Answer

Please first to submit.