r925 32-float sound output startup hang

[Enjay]

If I change the sound output format to 32 bit float then quit and restart, Zdoom hangs in the little startup window just after fmod loads. When you click the X button on the title bar to quit, Zdoom does indeed exit but a Windows generated "this program has stopped responding" followed by a send/don't send crash dialogue also pops up.

I have a SB Audigy which may, or may not, support this output type, but it shouldn't hang - right?

This happened with both r910 and r925

[edit]
Oh, and if anyone is trying to replicate this, if you get the problem it will mean that you cannot restart Zdoom until you fix your ini. Look for the line "snd_output_format" and delete it then Zdoom will restart and restore the line with the default value.

or maybe -nosound will work to allow you to restart and then change your options????

[Lemonzest]

Audigy supports only 16bit/48khz and through p16 24bit/96khz but no 32bit formats.

[Enjay]

Audigy supports only 16bit/48khz and through p16 24bit/96khz but no 32bit formats.

Thanks for the info. I can set sound output to 32 bit and Zdoom will start and make sounds though (even if, perhaps, the card is downsampling or something) but 32 bit float causes the hang.

[Nash]

Just purely for everyone's interest, I tried setting the sound output to 32-bit float on my system which uses an onboard AC97 soundcard.

At the start of nuts.wad, I literally jumped when I alerted the monsters because no volume limiting is ever applied in this output mode. :P

[randi]

It works for me. Have you tried running with +logfile to see if it's writing anything to the console while it's stuck?

[edward850]

I get the same problem with my laptop, but not with my computer. The odd thing is, you can’t get a log file because of when it hangs. It hangs straight after fmod has initialized (just before V_init allocate screen).

Works: Computer: SoundBlaster 16 (Yes, that old) + SoundBlaster 128 (Built in)
Doesn’t work: Laptop: Ali Audio Wave (That’s what it calls it)

[Kate]

I get the hang too. Interestingly enough, when I attach to it with the debugger, it appears to be creating threads into infinity. However, it appears to be hanging in FMODSoundRenderer::Init in fmodsound.cpp on line 666 from what I'm able to gather.

(It's the line no. of the beast! =o )

[edward850]

...hanging in FMODSoundRenderer::Init in fmodsound.cpp on line 666...

Oh the Irony

Important edit: Anything past 16bit doesn’t cause zdoom to hang, but rather, causes my speakers to produce static (and only static). Odd, but I think that’s something outside of zdoom’s control. Does anybody know a way I can confirm this?

[Project Shadowcat]

...hanging in FMODSoundRenderer::Init in fmodsound.cpp on line 666...

Oh the Irony

Important edit: Anything past 16bit doesn’t cause zdoom to hang, but rather, causes my speakers to produce static (and only static). Odd, but I think that’s something outside of zdoom’s control. Does anybody know a way I can confirm this?

Probably because you are still using the 16-bit sound card.

[Kate]

True. Static should usually be expected if you're trying to use a samplerate or bitrate far above what's expected as the card simply wouldn't be able to read the data it's recieving correctly, but it certainly shouldn't cause the entire program to bomb out or loop infinitely trying to initialize the sound and fail constantly. Sounds like FMOD has a problem with initializing this particular mode on some cards, particularly SB Audigy it seems (I have an Audigy 4 on this PC). Oddly enough, 32-bit normal works fine (If I increase the buffer to 2048 I can run 32/128 without the slightest problem), but float specifically causes a hang.

[Nash]

Also of note is that most humans probably can't hear the difference between 16-bit and any bit depth above it anyway... it's not like you'll magically hear more pristine quality sound while playing Doom (which uses 8-bit sounds for the most part to begin with)...

Even most top-notch recording studio facilities still mix music at 24-bit resolution at most.

[edward850]

Probably because you are still using the 16-bit sound card.

I'm not using my SoundBlaster 16. If a SB 16 can run 32-bit float sounds, why can't a SB 128 do so?

[Project Shadowcat]

I really want to know why you have two sound cards...

[edward850]

Because I had a SoundBlaster 16 in my computer while my Main board soundcard wasn't working. Then I managed to get drivers for it and never bothered in removing my SB16. Kind of obvious don’t you think?

[Project Shadowcat]

Not really, no.