[Bug] Audio popping when using Fluidsynth on the latest development build

[Heckalope]

Seems to consistently occur on the title menu music of Bitter Dream (bitter.wad). Doesn't occur on Nugget Doom or Woof in testing.

Below I've linked the tested Action and WAD:

https://github.com/xemonix0/Cherry-Doom/actions/runs/13214675547

https://www.doomworld.com/idgames/levels/doom2/Ports/a-c/bitter

[xemonix0]

Cannot reproduce, sounds perfectly fine for me. Are you sure your audio settings are identical across all three ports? Same MIDI player and all? I don't think I modified any of the sound-related code at all, it shouldn't differ from Nugget's (or probably even Woof's) in the slightest.

[Heckalope]

To better illustrate what I'm experiencing, I went ahead and got a few audio samples from this engine and the others.

The conditions are that all 3 are using default settings, with the only thing being changed being the MIDI player, which has been set to FluidSynth: TimGM6mb.sf2:

sample.mp4

Hopefully you notice the difference on the third one, which has a rhythmic popping / clipping sound.

I've also attached my config files for this below so you can see if there's anything off about them.

woof.txt

nugget-doom.txt

cherry-doom.txt

[MrAlaux]

This could be an issue with the version of FluidSynth that the builds were compiled with. I would suggest that @xemonix0 triggers a re-run of the latest action to generate new builds.

[xemonix0]

Apologies, apparently I was testing the wrong build. Yes, the issue is definitely there. But it's there for the latest builds of Nugget and Woof for me as well, and the new builds after re-running the workflows still have it too.

I also think it's an issue with FluidSynth itself

[Heckalope]

I can confirm it appears to be happening on the other projects for me as well. Is there anything that could be done to revert any unwanted updates on this dependency until it gets looked at? If not I can stick to the most recent stable build of Nugget Doom.

[Heckalope]

Something interesting I've noticed is that when using the stable release of Nugget Doom 4.3.0, the audio problem isn't there. That is a more current build which in theory wouldn't contain differences. Is there a difference between how FluidSynth is built between the GitHub actions and the release versions?

[MrAlaux]

I'll assume that Xemonix provides actions builds for releases, like I do.

FluidSynth is a project with its own development, independent of us. As such, it releases new versions occasionally, which are then used by our projects' actions when they generate the autobuilds.

It's very much possible that functionally identical builds of Nugget/Cherry are packaged with different versions of FS which behave differently. In fact, the official Nugget 4.3.0 release is packaged with a version of FS that suffers from crashes under certain conditions, so I might generate new 4.3.0 builds to replace the existing ones for the sole purpose of having an updated FS version without the issue, but the port part itself would be unchanged.

[Heckalope]

That makes a lot of sense when you explain it that way, thanks for the clarification.