From: Leonid Mironov <lvm@royal.net>
To: "cygwincygwin.com" <cygwin@cygwin.com>
Subject: pulseaudio borked
Date: Fri, 1 Sep 2023 09:37:03 +0200 [thread overview]
Message-ID: <trinity-115920bb-acef-4b1b-8689-4b791bd7b121-1693553823872@3c-app-mailcom-lxa13> (raw)
After the latest upgrade of mpg123 and mpg123-pulse from 1.25.10 to
1.31.3 and pulseaudio from 11.1 to 16.1 pulseaudio output in mpg123
became unusable - stuttering and stopping all the time with no
significant CPU load. Downgrading mpg123 without downgrading pulseaudio
didn't resolve this issue, so it looks like pulse is to blame. It is an
HP 840 G6 notebook with realtek sound chip and windows 10.
I should add that I started using pulse because with default settings
mpg123 reacted to keyboard commands after a huge delay and Takashi Yano
suggested using pulseaudio, which worked fine. I tried the default
device (output_win32.dll) again, and it works fine now, so for me
resolving this issue has no practical merit, still, not nice.
next reply other threads:[~2023-09-01 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 7:37 Leonid Mironov [this message]
2023-09-01 12:28 ` Takashi Yano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-115920bb-acef-4b1b-8689-4b791bd7b121-1693553823872@3c-app-mailcom-lxa13 \
--to=lvm@royal.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).