Pop!_OS (Linux)

5062 readers

1 users here now

Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.

Unleash your potential

Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We're all here because we have a shared love for Linux and open source software.

Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the "Support Pop" button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we'll work to push the Linux desktop forward with COSMIC.

Links

Guides

Hardware

Recommended

Community Rules

Follow the Code of Conduct

All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct

Be helpful

Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like "RTM" or links to LMGTFY. Linking to direct sources that answer the asker's question is fine, but it's advised to provide some explanation as to how you got to that source.

Critique should be constructive

We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic "It's bad" or other simple negative comments don't help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.

This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.

Don't post malicious "advice"

It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.

Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn't serious, but a new user might not.

No personal attacks

Posts making a personal attack on any user will not be tolerated.

No hate speech

Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.

founded 1 year ago

MODERATORS

[email protected]

Sound cutoff issues (lemmy.world)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

Hello! I'm pretty new to pop_os and linux, but am trying to switch over from windows. I've been having some sound issues where it seems like sounds get cut off. It seems to most noticeable with something like doing duolingo from my browser (lots of short sound clips of words and such; if I click on words quickly, then spotify playing in the background will stop playing briefly). I've tried disabling sleep, as described by https://support.system76.com/articles/audio/, without luck. I've also noticed that I see errors listed in pw-top which sometimes correspond to sounds getting cut off. That is, sometimes I notice a cutoff without seeing an increase in the number of errors, but when I notice an increase in the number of errors it usually corresponds to something getting cut off.

Is there a way to see what the errors from pw-top are? Or suggestions for other things I should look into? I've looked at dmesg and systemctl status --user pipewire.service (and pipewire-pulse) but the only error I see is a nvidia-drm thing which seems to be innocuous. I've also uploaded my alsa-info results, if that's useful.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 2 months ago (1 children)

That does seem to at least help. It seems to be harder to trigger the problems with higher values. I could still get it to happen with the quant at 2048, but I had to really work at it.

I notice that the + Firefox line seems to show up with a quant of 900 even when the minimum value is higher than that? That seems weird.

[–] [email protected] 2 points 2 months ago* (last edited 2 months ago)

I seem to recall the configuration having options that set different minimums depending on the source of audio. I’m not an expert in the settings. I kind of just tweaked them until I wasn’t seeing skips.

I do believe there’s a global minimum setting however. That might be the one you’re already using.

I think the main problem is the default settings are just not great. They are far too tight.