Is someone here very good with #pipewire? I seem to have an issue where some applications don't seem to be able to emit any sound, especially games. I also have pipewire-pulseaudio installed, but that doesn't really help. It also just doesn't show up in easyeffects. What could be the cause of this?
@nyovaya I had that with some games through Proton; enabling Alsa Compat with protontricks made them work, as cursed as it is.
@yuri It is a native (mono) one tho.
@nyovaya @yuri Is it using MonoGame? If so, you might be able to get something working by specifying the SDL audio driver.
@celdaemon @yuri Hmm how do I know? The binary doesnt seem to be linked against SDL tho, but that doesnt mean anything.

@nyovaya @yuri Hm, what did you mean with:

(mono)exactly?

I assumed you meant it's a dotnet application, in which case native libraries are loaded at runtime, outside of the usual dynamic linker.

@celdaemon @yuri Yes its a dotnet application, but theres also native binary which is probably just the dotnet runtime. But I could also run the dotnet executable using mono by hand.
@nyovaya @yuri That's an fxr host stub executable, it's responsible for starting the dotnet program using a system-installed or self-contained dotnet installation. Odd that it runs with mono though, mono is for .NET Framework apps, not .NET Core.

Which game is it though, maybe I can figure out what it uses?
@celdaemon @yuri Mono doesnt support .NET Core? Its Kistune Tails
@nyovaya @yuri I think it does support it, but there's not really a reason to use it over just normal .NET Core. Also, that game uses FNA on Linux, which does in fact use SDL under the hood.

You could try setting the
SDL_AUDIODRIVER to pipewire, I'm hoping the bundled version of SDL supports it.
@celdaemon @yuri I was just used to use mono over the years and sometimes I get these stupid libhostpolicy errors with dotnet core. I could try the next time, atm it just shows up in easyeffects as expected :)
@nyovaya @yuri ooo that actually worked?

Well damn, colour me surprised. Odd that it wasn't able to figure out what driver to use by itself though?
@nyovaya Ah nvm I just realised you probably meant it was already working again, oops.
@celdaemon @yuri It worked after I configured the output in qpwgraph, but didnt show up in easyeffects before. Maybe when I reboot Ill have that issue again and can use that envvar.