Hexen Timidity++ Issue

[Korell]

I noticed today that whenever I start GZDoom for Hexen (or a Hexen mod), the console gives an error with Timidity++ as follows:

Code: Select all

S_Init: Setting up sound.
I_InitSound: Initializing OpenAL
  Opened device OpenAL Soft on Speakers (2- USB Audio Device)
  EFX enabled
Unable to create Timidity++ MIDI device. Falling back to FluidSynth

It doesn't happen when using doom.wad, doom2.wad, freedoom1.wad, freedoom2.wad, heretic.wad, strife1.wad, chex3.wad, hacx.wad, hacx2.wad, square1.pk3.
I'm only getting it happen when loading hexen.wad.

I do have Timidity++ set up to use Patch93's Roland SC-55 soundfont, but have also tried another SC-55 soundfont and the provided gzdoom.sf2 soundfont, and the same error occurs.

I'm using GZDoom 4.14.1

Also, if I use the Restart Sound option from the Advanced sound menu, the I_InitSound, Opened device, and EFX enabled lines show up in the console, but the error doesn't happen.

[Korell]

Just tried it with GZdoom 4.14.2 and it's the same.

[Graf Zahl]

Please post your INI file.

[Korell]

Here's the ini file that I'm using for Hexen (I choose to have separate ones for Doom, Heretic, Hexen, Strife, etc. and call the relevant one via batch files to launch).

[Graf Zahl]

In that case you will have to investigate yourself what is different about your Hexen config.
It certainly has nothing to do with the game itself, for me it works in Hexen just like in all the other games.

[Korell]

Okay then, so to prove that this is not a config issue, I've deleted my Hexen ini file so that the game recreates a new, clean one. The only change I've made was to add the additional IWAD folder for where I keep my Hexen IWAD. I then boot it up, change the MIDI device to Timidity++, quit and reload and the error is back. The only variable that was changed by changing the MIDI device was the default value snd_mididevice=-5 (FluidSynth) to snd_mididevice=-2 (Timidity++). And it's only Hexen having this issue.

I've attached my new, clean Hexen INI file where the only changes are the additional IWAD folder and the snd_mididevice value to select Timidity++.

[Graf Zahl]

This doesn't help me. Something about your setup must be different that it cannot find the sound font. Are you sure you are starting from the correct directory?
I think the only way to find out what's happening is if you copied the entire folder (minus IWAD and PWAD content, of course) and uploaded it somewhere for others to analyze.

[Korell]

The soundfont is in the default location, and this was with a clean INI file, so pointing to the gzdoom.sf2 soundfont. It literally only happens with Hexen and Timidity++. Other games work fine with Timidity++.
I'll set up a completely new, clean instance of GZDoom and drop the Hexen IWAD alongside the executable, so that way there will be nothing changed from default other than snd_mididevice=-2.

Yep, just as I expected, a completely new, clean extract of GZDoom, with the IWADs put in the executable folder and snd_mididevice=-2 for Timidity++, and I get the error with Hexen but not with Doom, Doom 2, Heretic, Strife.

[Korell]

So, I've now been through a load of different GZDoom versions from 4.0.0 onwards, and I have found that the issue wasn't present for versions 4.0.0 up to and including 4.7.1. But from 4.8.0 and onwards, it is present. Does this help?
I noticed that libmpg123-0.dll was removed for 4.8.0 onwards, but I wouldn't expect that to be the cause, what with the issue only affecting Hexen.

[Graf Zahl]

I did some closer checking. The error message does indeed appear but I never suspected anything wrong because in-game music sounded correct.
From the looks of it the title music played over the loading screen is the only thing being affected by this. And this piece only plays for a few seconds so it's virtually impossible to notice.

My suspicion is that this music somehow gets started before the CVARs are set up.

[Enjay]

Would this be at all related?

viewtopic.php?t=80020

Although I reported it for a custom startup, it seems that the Hexen startup music always fails after a second or so - even when just using the default Hexen IWAD.

[Graf Zahl]

ZDoom's startup code is quite messy and it may well be that something went wrong when the startup code was refactored.
I also noticed that with recent versions the startup screen wipes several times, so something's definitely not right there.