-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Volume changes crash rocksmith #63
Comments
Could you try and test this further/tell me more? (Haven't read about this behavior before.)
(Just for clarity, "can you change it" means "does the game crash when you do it") The obvious workaround would be to use something with a volume knob. But even if that's feasible for you, that's still annoying and I can tell it bothers you either way because you wrote this issue. |
Yes, I also have a soundcard with a knob which would obviously work because it doesn't change the deck volume. But my goal is before and foremost to be able to play and practice on the go with the steamdeck. It works really well with Jack and Pipewire, the latency is incredibly small and the sound isn't distorted like on my previous attempts on the steamdeck. Only issue on my side which make it playable but a bit boring to play is that crash when you need to change the volume, which can happen quite often if you're playing CDLC as the guitar volume is sometimes too high depending the sound effect of the song. To be honnest it doesn't bother me that much, and I am already able to enjoy it! But I know that if I'm facing that issue, maybe other can experiment it as well, so well it will maybe help other users on the community. I'm not on Big picture mode as it crashes every time on big picture mode. And I still have to select my RS tone cable as the default input on steam deck launch so, moving in desktop mode every time I want to play RS. I did some test with "amixer" command and I figured out that when RS doesn't have the focus, it doesn't crash at all. Basically it made me think about an exclusivity issue so I disabled exclusive mode and tested again. Of course I got the Message from RS-Asio letting me know that I didn't had exclusive mode on followed by the rocksmith popup (no output device available) but I was able to change the volume. Maybe the issue is as dumb as the steam deck shows a little volume notification window and make a small sound when you change the volume and rocksmith which is then in exclusive mode doesn't like the fact that something else is trying to make a sound and just crash. I'm gonna try to test some other things. Thanks for your reply! |
Just tried something. I went into the SteamOs settings from desktop mode, in the audio section there is a setting called: Maybe something else would be doable to allow Rocksmith to run without having to disable that setting but not sure what. I'll do some research on changing SteamOS settings from command line and maybe that could be added to the startup script to disable it on RS launch and re-enable it after Rocksmith has been shutdown. |
Okay. Out of interest, I need to try this on my system. Now that I think about it, I never played any audio simultaneously.
Definitely worth noting and I might put this inside the Steam Deck guide instead, just below the start script links. Would you be happy with that?
The sub-guides are the same for all guides. Changing that probably means more files. But there's another request to adjust them in #62 for a specific purpose. If that's what people want, I can do that (or think of something). |
#Definitely worth noting and I might put this inside the Steam Deck guide instead, just below the start script links I searched for an option to change values of plasma settings from terminal but didn't found one. Not having the volume change notification sound isn't really annoying from my POV |
Done 0456b69 |
Which distro do you use?
Which Proton or wine version do you use?
Do you use pipewire?
did you choose native JACK or pipewire-jack?
What appears to be the problem? (Describe it as best as you can)
Did you notice any other unexpected behavior?
What did you try already?
Did you do any of the steps differently or leave them out?
Thank you guys for the amazing work of documentation and guidance!
The text was updated successfully, but these errors were encountered: