I ended up switching to JACK for the sound server, and directing ALSA to point to JACK, and while not perfect, the result is actually better. mplayer fails for whatever reason, but YouTube works well, and the game running under WINE isn't perfect, but the occasional audio glitches are not nearly as bad as the prior situation.
You do know you can have multiple audio backends at once right? (such as pa for normal usage as well as jack2 (btw did you switch to JACK or JACK2
?) for proaudio/other software)
Also, it helps that JACK has a GUI utility (qjackctl) that allows me to tweak things like the buffer size (which affects latency).
Both alsa and pa have utilities for configuration. They usually don't come with GUI per se but I don't see what's the problem. It's not like they do not display visual feedback. It's only a matter of personal bias and unjustified disgust of console based tools at this point.
You will also inevitably have to change some config file by hand at some point, especially in jack.
Also, should you have had chosen answering the questions you would be at the very least directed towards materials that would ensure proper assistance with your pa problem. But instead you refused out of your own... I don't know... ego?
You will inevitably run into issues again sooner or later. After all both jack and jack2 are far more complex than pa.
At that point ask yourself a question once again and at the very least be honest with yourself
Do you feel confident enough to ask for help of others (based on the fact that you don't possess enough knowledge and experience to fix the problem by yourself) and then refuse to answer your helpers' very valid questions (neccessary for troubleshooting without being physically at your place, and it doesn't
matter if you
understand the point
of asking them for them to still be valid, in fact it's the very fact that people are more experienced than you causing them to ask very specific questions that you may not understand reasoning behind asking for) based on your own personal pretense?
JACK was actually already installed, because I was thinking of playing around with programs that require it like supercollider and sonic-pi (and I believe Ardour as well); now that I have actually been able to get it working, I might actually try those programs.
I wish you the best of luck with your problematic endevours.
But I will not waste my own personal time trying to help you if you will keep to pretentiously refuse to answer my valid troubleshooting-related questions.
Hola, tengo un juego de la compañia Deep silver. ¿como pueod reclamar el deadight?
1.Use english next time. Machine translation isn't exactly of best quality.
2.This thread isn't for these kinds of questions. It's for troubleshooting issues with games played on Linux. NOT with GOG account issues (such as issues with or lack of knowledge how to redeem a key).
Downgraded my kernel from 5.10 (debian bullseye kernel) to 4.19 (debian buster kernel), and it looks like that may have fixed my audio issue.
(This means that there must have been a regression at some point.)
I want you to know and understand that what I'm about to say here isn't
a personal attack.
I just want to bring you to your senses early on, otherwise either someone else will do that sometime down the line, or you will one day feel the consequences of your mistakes on your own self.
You must seriously not understand how Linux software development works.
According to public info there is 738 days between 4.19.0 and 5.10.0.
I'm assuming you meant LTS (which you failed to speak about).
In case of LTS only security fixes and major bugfixes are backported. New
functionality improvements usually don't find their way into LTS builds. At which point the afformentioned 738 days come into play.
If you fail to understand that this much time is far beyond just regressions, it's literal code rebase
then you will run into worse issues other time based on your fundamental lack of understanding of kernel release cycles and what it means to backport stuff, also what LTS is for, and how you can expect software to behave on it.
And no, it most certainly wasn't a regression.
Don't associate problem-on-Linux == regression because things don't work like that by default
It was 99% certainly a misconfiguration on your end.
Linux isn't Windows.
There is literally the fact that each and every single Linux deployment is it's individual ecosystem where unique issues may arise.
Choosing Linux needs to be done consciously with that in mind.
If you want to use it you must also face the reality - you will not be able to run from problems indefinitely - at some point you will have to spark internal courage to learn to fix them.
It's beyond foolish to jump major
kernel versions and expect just minor
things to change.
You better buckle up as you are up for the journey of discovering what stopped working and started misbehaving.
Remember. YOU chose this by first asking for help and then refusing to answer debugging questions.
Now you jumped one year of funcionality
At this point helping you becomes a chore and if you keep ignoring people's questions, not just mine
but also others', then you will not get anywhere.
Please grow some common sense and be responsible when you ask for help. Troubleshooting and such isn't about someone magically fixing your problems.
You have to cooperate too or you will not get very far.
I hope for your understanding (tho I feel you won't have enough of it for some time).
And have a good day.
edit: fixed broken quotes (rearranged them)