0
0

Calling stop() for a Channel causes an annoying "click" with some sounds.
I’ve now tried to solve the problem by setting volume to zero first and delaying the channel stopping until the next system update. However, that adds unnecessary complexity to the code. I supposed FMOD would take care of preventing clicks when stopping a channel?

  • You must to post comments
0
0

If the channel stops while the sound is at an extremely high or low output volume it’s going to click simply because the output sound is jumping from one value to another. ‘Preventing clicks’ would probably be undesirable in many cases since it implies either a forced fade-out or a delayed stop.

Setting volume to 0 should do the trick since the volume ramping will turn that into a quick fade out.

  • You must to post comments
0
0

Is this a hardware or software voice?

The problem at the moment is that it creates some issues to do with re-using a voice, if you wanted that same voice, you would have to wait a frame before using it again.
I guess we can mark that voice as still playing for another millisecond or 2, while the mixer finishes up on it.

  • You must to post comments
0
0

Both hardware and software voices click.

Yes, Janus, I know what you said is the reason for the clicks. But, I was told by a more experienced colleague that the sound system (FMOD in this case) should handle that 😕

  • You must to post comments
0
0

Pushing this up one more time 😳

Is this clicking going to be fixed (isn’t it an issue FMOD should handle) ?
Clicking can be easily produced with for instance swish.wav sound used in FMOD examples.

  • You must to post comments
Showing 4 results
Your Answer

Please first to submit.