From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Leonid Mironov <lvm@royal.net>
Subject: Re: pulseaudio borked
Date: Fri, 1 Sep 2023 21:28:26 +0900 [thread overview]
Message-ID: <20230901212826.72717c260f22640ef71f01b8@nifty.ne.jp> (raw)
In-Reply-To: <trinity-115920bb-acef-4b1b-8689-4b791bd7b121-1693553823872@3c-app-mailcom-lxa13>
On Fri, 1 Sep 2023 09:37:03 +0200
Leonid Mironov wrote:
> 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.
Thanks for the report. In my PC for developement, the issue
is not reproducible. However, I found one of my note pc can
preroduce that.
I will fix that and release pulseaudio 16.1-2 shortly.
Please test.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2023-09-01 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 7:37 Leonid Mironov
2023-09-01 12:28 ` Takashi Yano [this message]
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=20230901212826.72717c260f22640ef71f01b8@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
--cc=lvm@royal.net \
/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).