2 ms·

You had audio latency issues and instead of googling "Linux audio latency", you spent several hours installing distributions, kernels, graphics drivers (?), and

by mahkoh 3y ago

You had audio latency issues and instead of googling "Linux audio latency", you spent several hours installing distributions, kernels, graphics drivers (?), and UIs (??). You could have avoided this by doing what any windows user would have done in your situation. >This article describes how to configure your system for recording, mixing and playing back audio as well as using it to synthesize and generate sounds. Those activities are subsumed under the term professional audio (pro audio) and typically require low latency performance. First link.

bongodongobob 3y ago
Of course I started with that. I then I noticed screen tearing in my browser (fresh install of Ubuntu 22.04). Oh ok, well maybe I've got the wrong drivers and it's eating CPU. Run all the tests to ensure I have the right Nvidia drivers. All checks out. Then I find something about hybrid graphics mode. Sure enough, I needed to set my graphics to discreet mode in the BIOS. Screen tearing is now gone. Well now that I'm on it, why don't I move to LXDE from Gnome? Can't hurt right? No dice. I look up my laptop. Find that only 20.04 is "officially" supported by Lenovo. Ok, well I need to install that now to rule that out. While I'm waiting for that to install, I stumble upon real time kernels, apparently popular for audio stuff. Try that, marginally better but latency is now unstable. Switch kernels again. Now I dig into Reaper settings. There are tons of things that can improve latency (that I'm also familiar with). Bitrates, buffers, sample rates, etc. This is all to say I didn't think I'd have to change whatever the hell pulseaudio is to ALSA. Why should I have to do anything? I don't in Windows. This whole thing was a project to get myself off of Windows and my point is it shouldn't be this hard. I've used various DAWs in Windows over the last 20 years and it was never difficult.
- PH95VuimJjqBqy 3y ago
  that description is a far cry from your original claim that it took you that much effort to get _audio_ working under linux with low latency.
  - bongodongobob 3y ago
    It's the summarized off the top of my head version. It literally took all day Saturday and all day Sunday.

by mahkoh 3y ago

bongodongobob 3y ago

Of course I started with that. I then I noticed screen tearing in my browser (fresh install of Ubuntu 22.04). Oh ok, well maybe I've got the wrong drivers and it's eating CPU. Run all the tests to ensure I have the right Nvidia drivers. All checks out. Then I find something about hybrid graphics mode. Sure enough, I needed to set my graphics to discreet mode in the BIOS. Screen tearing is now gone. Well now that I'm on it, why don't I move to LXDE from Gnome? Can't hurt right? No dice. I look up my laptop. Find that only 20.04 is "officially" supported by Lenovo. Ok, well I need to install that now to rule that out. While I'm waiting for that to install, I stumble upon real time kernels, apparently popular for audio stuff. Try that, marginally better but latency is now unstable. Switch kernels again. Now I dig into Reaper settings. There are tons of things that can improve latency (that I'm also familiar with). Bitrates, buffers, sample rates, etc. This is all to say I didn't think I'd have to change whatever the hell pulseaudio is to ALSA. Why should I have to do anything? I don't in Windows. This whole thing was a project to get myself off of Windows and my point is it shouldn't be this hard. I've used various DAWs in Windows over the last 20 years and it was never difficult.

PH95VuimJjqBqy 3y ago
that description is a far cry from your original claim that it took you that much effort to get _audio_ working under linux with low latency.
- bongodongobob 3y ago
  It's the summarized off the top of my head version. It literally took all day Saturday and all day Sunday.