Closed theNizo closed 2 years ago
Heres one: https://pastebin.com/5VMx0NEC
Pasting a few links for later, haven't read them completely yet:
wineasio issues:
pipewire issues:
something else: https://forum.vb-audio.com/viewtopic.php?t=1204
Taken from the posted links.
Some people said that you can use pipewire with traditional jack. So, install the normal jack, but now the alsa driver is provided by pipewire-alsa
.
It's a workaround for now, but it would obviously be better if it worked with pipewire-jack
. Also, I didn't test what I've written here yet.
EDIT: Nope, didn't work. I might have overlooked something from the instructions of others.
It seems to work now with Pipewire 0.3.50 See here: Gitlab - wineasio crashes
It seems to work now with Pipewire 0.3.50 See here: Gitlab - wineasio crashes
Had a short look at it, my first vague guess is that it will be kinda experimental, but definitely better than nothing. Got a machine to try out on now, hopefully I find some time this weekend.
Or if someone else wants to try, I'll take pull requests, other forms of instructions, or any kind of pointers. I'd list you in the credits of course.
Tried with the patched wineasio version. Patchbay does the correct thing out of the box, Rocksmith seems to crash when initializing ASIO.
I will try and test a bit more...
Different output with freshly compiled wineasio (tobi version)
I GOT IT THROUGH!!!
EDIT: I got sound, but microphone makes an unwanted sound and if it starts is pretty much based on luck.
2nd EDIT: Now it won't start again...
Seems to work when you move the focus away from the window as fast as possible and let it run until you hear sound. I opened the QJackCTL graph view, so that I can see what's going on. Can't confirm if the window focussed matters, but it most likely doesn't.
needed and recommended packages: pipewire, pipewire-alsa, pipewire-pulse, pipewire-jack
Instructions for people who don't need pretty ones:
git clone https://github.com/TobiasKozel/wineasio --recursive
cd wineasio
make 64
make 32
do these steps according to the other asio guides:
open pavucontrol, make only one output and one input available (it will automatically connect everything, but rocksmith detects only one input device. also, rocksmith crashes when modifying the patchbay.)
cd into the root of the game, then run the game with PIPEWIRE_LATENCY=256/48000 WINEPREFIX=$STEAMLIBRARY/compatdata/221680/pfx $PROTON/bin/wine Rocksmith2014.exe
As soon as the window appears, focus out until it starts loading the game (logo screens start)
modifications that I did to my pipewire config (have yet to figure out the importance of them):
(this isn't pretty because I wanted to get the info out as fast as possible)
Oh, come on, is it really that simple?
The only difference is setting the available input and output devices and unfocussing the window until the logo screens appear (not even always needed, but it's the most reliable way.)
Will TobiasKozel's fix be implemented upstream? There's no pull request.
You should ask him. Makes no sense to ask here.
Will TobiasKozel's fix be implemented upstream? There's no pull request.
I figured out when writing the actual pipewire guide that wineasio/wineasio works perfectly fine for this usecase. To be fair, I didn't document this piece of information in this issue.
Considering that, this issue is most likely the wrong place to ask.
IIRC the game crashes at start when using pipewire.
(I don't have a log to share right now)