This is Woof! 14.3.0 (Mar 15, 2024)

I listened with relatively high-quality headphones and still can't hear. I think in my youth there was too much very loud music. Anyway, we decided to rework the Woof sound system to sound exactly like Crispy Doom in the next major release. But this will take time.

Yeah, it's exactly the same hiss I have. It was present in Woof 5 too. You don't need a thousand enemies to hear it, only 1 or 2 loud enemies. Thanks for recording.

To me Woof, Chocolate, Crispy and PrBoom-plus all sound very close to one another. Also, I don't detect anything out of the norm in the video. I am also in the excessive exposure to loud music category though. Just curious, if you have Crispy or Chocolate, can you go into your crispy_doom.cfg or chocolate_doom.cfg and change the use_libsamplerate variable to 2? Then play Crispy/Chocolate and see how its sound effects compare to what you're hearing in Woof. I suspect that you may have really good hearing and are picking up high frequency resampling artifacts. Setting use_libsamplerate to 2 creates maximum artifacts, i.e. it will use the poorest quality resampling technique.

It's definitely there. There may be some discrepancies here related to age since at a certain point you stop being able to hear higher frequencies.

8 hours ago, mikeday said:

To me Woof, Chocolate, Crispy and PrBoom-plus all sound very close to one another. Also, I don't detect anything out of the norm in the video. I am also in the excessive exposure to loud music category though. Just curious, if you have Crispy or Chocolate, can you go into your crispy_doom.cfg or chocolate_doom.cfg and change the use_libsamplerate variable to 2? Then play Crispy/Chocolate and see how its sound effects compare to what you're hearing in Woof. I suspect that you may have really good hearing and are picking up high frequency resampling artifacts. Setting use_libsamplerate to 2 creates maximum artifacts, i.e. it will use the poorest quality resampling technique.

From what I can hear, it just makes the entire game sound more "crispy" and old- as if I had really bad headphones or speakers.
 

10 hours ago, rfomin said:

I listened with relatively high-quality headphones and still can't hear. I think in my youth there was too much very loud music. Anyway, we decided to rework the Woof sound system to sound exactly like Crispy Doom in the next major release. But this will take time.

Great to hear! I'll definitely be looking forward to the next major release.

I still don't understand how the fact that random sound pitch apparently fixes the issue fits into the picture.

6 hours ago, mikeday said:

Just curious, if you have Crispy or Chocolate, can you go into your crispy_doom.cfg or chocolate_doom.cfg and change the use_libsamplerate variable to 2? Then play Crispy/Chocolate and see how its sound effects compare to what you're hearing in Woof. I suspect that you may have really good hearing and are picking up high frequency resampling artifacts. Setting use_libsamplerate to 2 creates maximum artifacts, i.e. it will use the poorest quality resampling technique.

You may be right, this results in some hiss as well.

But it's not like those nice crunchy old sounds in Chocolate Doom - those don't come with such unpleasant effects.

By the way, I use speakers and I suffer from tinnitus, but those factors are irrelevant. The noise (in Fireseth's video) appears to have similar high frequency to those used in hearing tests so some people may not hear it.

12 hours ago, Fireseth said:

I can actually record the strange high pitched hiss I've been experiencing... Take a listen for yourself:
(If you listen very closely, when I press a button in the main menu the hiss is still present for any audio being played from Woof!)

I just watched through the whole video with headphones and couldn't hear a single hiss sound, sorry! Well, I am 40 years old and used to play in a metal band in my youth, so maybe this is the result of it. Anyway, we have an optional low-pass filter in PrBoom+ (and Choco, if I am not mistaken) that we could apply here.

I took a listen to the video, the hissing sounds (to me) like the noise you'd hear from low bit-depth audio. I also hear what sounds to me like a >10kHz whine when there are a lot of enemies on screen. I wanna say Odamex had an issue where SDL's resampling was poo-poo, does that sound like something that might be happening, or am I totally off-base?

@AlexMax, I think we talked about this on the discord at one point?

SDL changed the resampler in a somewhat recent 2.0.x patch and it sounds like Thelonious Dump when used on Doom's sounds.  Chocolate Doom only dodges the problem by using libsamplerate, if you turn support for it off you can hear how SDL muffles it by default.

Odamex bypassed the issue by using the naive resampler which doesn't sound fantastic, but at least it's not muffled.

I have added the low-pass filter from Chocolate Doom (optional and disabled by default) but forgot to do a test build that I could upload. 

I'm on 5.1.0 atm playing Alien Vendetta and feel the need to still report that MAP07's exit is busted even when setting compatibility to vanilla after killing all arachnotrons.

Works fine for me on 6.1.0 -complevel vanilla.

Colored blood? Auto map rotation? Save game backwards compatibility?! I need to upgrade my copy tonight!

Using the latest (6.1.0), it seems that some (if not all?) of the MBF21 flags are still not supported. I have a melee weapon with the +SILENT flag, but still wakes up all monsters in a regular fashion, and a projectile that has the +RIP flag but does not pierce through enemies.

I'm also still getting a "bad sfx #:0" error. If I'm troubleshooting it correctly, it seems to happen when I set Args3 to 0 for A_MonsterMeleeAttack (the arg that determines what sound is played on hit).

The automap looks like this for some reason while playing Full Moon on 6.1.0 (Haven't check other wads):
 

11 hours ago, Aurelius said:

Using the latest (6.1.0), it seems that some (if not all?) of the MBF21 flags are still not supported.

Are you sure you have the complevel properly set to "mbf21"?

1 hour ago, Catpho said:

The automap looks like this for some reason while playing Full Moon on 6.1.0 (Haven't check other wads):

There is a line break in the map title? How does this look in PrBoom+?

5 minutes ago, fabian said:

Are you sure you have the complevel properly set to "mbf21"?

I was blissfully unaware there was a complevel option, sorry about that! However, when I went to check it's set at MBF21 by default. I even switched it over to MBF, restarted, then back to MBF21, restarted, but still no luck. Both errors are still present.

@fabian Checked it in dsda doom 0.19.7. In dsda doom it looks the same as my first screenshot, but leaves no artifacts on the stat bar unlike in woof.

4 hours ago, Catpho said:

@fabian Checked it in dsda doom 0.19.7. In dsda doom it looks the same as my first screenshot, but leaves no artifacts on the stat bar unlike in woof.

What renderer do you use? If you use gl for instance, the stat bar gets rendered on every frame, which could explain why the artifact disappears there.

6 hours ago, Aurelius said:

 

I was blissfully unaware there was a complevel option, sorry about that! However, when I went to check it's set at MBF21 by default. I even switched it over to MBF, restarted, then back to MBF21, restarted, but still no luck. Both errors are still present.

Could you please open a bug at the issue tracker at github and post the contents of your dehacked lump there? 

6 hours ago, Catpho said:

@fabian Checked it in dsda doom 0.19.7. In dsda doom it looks the same as my first screenshot, but leaves no artifacts on the stat bar unlike in woof.

I think it would be best if we just trimmed the levelname at the first line break. 

On 6/30/2021 at 10:00 AM, roadworx said:

so, uh.....when loading a save for any map using crushers, this happens

 

 

here's the save file

woofsav0.rar

 

I just had the same thing on Alien Bastards MAP04 after loading

20 minutes ago, game said:

 

I just had the same thing on Alien Bastards MAP04 after loading

Have you upgraded to 6.1.0?

5 minutes ago, fabian said:

Have you upgraded to 6.1.0?

Oh forgive me, I forgot. Maybe it's no longer relevant then.

Does this port support soundfonts, if so how would I go about getting Woof! to read and load them? Loving the updates fabian!

6 hours ago, Lila Feuer said:

Does this port support soundfonts, if so how would I go about getting Woof! to read and load them? Loving the updates fabian!

I'm not sure about Windows, but on Linux - you have to set the default soundfont by editing two config files just so you can have music play in the first place.

On 6/27/2021 at 7:43 PM, Ar_e_en said:

1. Install Fluidsynth and download a sf2 soundfont. 
2. Go to your "bashrc" file (it's a hidden file in your user directory) and add the following to the end of the file:

# SDL soundfont setting
export SDL_SOUNDFONTS=/usr/share/soundfonts/FluidR3_GM.sf2

(The pathway there is the location of your downloaded sf2 soundfont)

 

3. Find your Fluidsynth config file (it should be in "/etc/conf.d") and change it so it looks like this:

# Mandatory parameters (uncomment and edit)
SOUND_FONT=/usr/share/soundfonts/FluidR3_GM.sf2

# Additional optional parameters (may be useful, see 'man fluidsynth' for further info)
OTHER_OPTS='-a alsa -m alsa_seq -r 48000'

(You may or maynot need the line with "OTHER_OPTS", it depends on if it works or not)

 

4.Restart your PC and launch Woof through your terminal (preferably with the "-iwad" parameter pointing to the location of your preferred iwad).

I haven't tried this myself, but on Windows, I'm guessing you can set the environment variable SDL_SOUNDFONTS to point to your soundfont of choice. If you'd rather set the variable in a batch file, you can do that with "set," e.g. set "SDL_SOUNDFONTS=C:\Users\..."

@Lila Feuer Unless you mean some internal support for soundfonts, use VirtualMIDISynth, add the configurator shortcut on desktop and switch between sound banks on the fly. I recommend Chorium soundfont.

Woof! 6.2.0

• The low-pass filter for sound effects has been ported over from Chocolate Doom, optional and disabled by default.
• The map title widget string is now capped at the first line break.
• The fix for A_SpawnObject() not transferring pointers as intended if called in a missile's death state has been ported over from DSDA-Doom.
• Calling S_StartSound() for sfx_None does not quit with an error message anymore.
• Deleting savegames from the "Save" menu has been fixed (@rfomin).
• Numerical values already set for MBF21 Bits fields are not overridden anymore by checking for mnemonics.
• The WI_updateStats() timing has been adjusted for demo compatibility with PrBoom+ (@rfomin).
• Unsigned integers are now read in deh_GetData() (@rfomin).

https://github.com/fabiangreffrath/woof/releases/download/woof_6.2.0/Woof-6.2.0-win32.zip

The low pass filtre that has to be applied in cfg file reduces the hiss during noisy moments a bit but it's still not something that I will be enduring. Doesn't seem like the right solution. As I said before, Sunlust MAP18 is good for testing this because you wake up big groups of enemies in it. I mean, maybe I personally can get used to the variable pitch effects mode that fixes it but most others may experience this flaw, which is sad because otherwise Woof is the best source port.