From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] bluez-alsa: debug output to terminal
Date: Wed, 12 May 2021 14:50:29 +0200 [thread overview]
Message-ID: <20210512125029.-4wtu_36xiAxZ6EqsI1cLYD-IIx3aB-vGShmB9qmX-I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26122@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]
Closed issue by 0xJes on void-packages repository
https://github.com/void-linux/void-packages/issues/26122
Description:
Bluealsa is compiled with enabled debug messages, wich polutes terminal output
https://github.com/void-linux/void-packages/blob/798a661d89a4078fbbfda83f02089d2157c16f8e/srcpkgs/bluez-alsa/template#L6
From bluez-alsa wiki:
> --enable-debug
> enable debugging support (a lot of debug text will be written to the stderr of both the daemon and the alsa client).
Example using mpv:
```
~ → mpv 'snd/Army of Mushrooms/01 Never Mind.opus'
(+) Audio --aid=1 'Never Mind' (opus 2ch 48000Hz)
File tags:
Artist: Infected Mushroom
Album: Army of Mushrooms
Date: 2012
Genre: Psytrance
Title: Never Mind
Track: 1
D: bluealsa-pcm.c:895: Getting BlueALSA PCM: PLAYBACK 04:02:CA:00:56:3E a2dp
D: bluealsa-pcm.c:769: /org/bluealsa/hci0/dev_04_02_CA_00_56_3E/a2dpsrc/sink: Setting constraints
D: bluealsa-pcm.c:396: /org/bluealsa/hci0/dev_04_02_CA_00_56_3E/a2dpsrc/sink: Initializing HW
D: bluealsa-pcm.c:416: /org/bluealsa/hci0/dev_04_02_CA_00_56_3E/a2dpsrc/sink: FIFO buffer size: 4096
D: bluealsa-pcm.c:422: /org/bluealsa/hci0/dev_04_02_CA_00_56_3E/a2dpsrc/sink: Selected HW buffer: 4 periods x 4800 bytes == 19200 bytes
D: bluealsa-pcm.c:440: /org/bluealsa/hci0/dev_04_02_CA_00_56_3E/a2dpsrc/sink: Initializing SW
D: bluealsa-pcm.c:440: /org/bluealsa/hci0/dev_04_02_CA_00_56_3E/a2dpsrc/sink: Initializing SW
D: bluealsa-pcm.c:440: /org/bluealsa/hci0/dev_04_02_CA_00_56_3E/a2dpsrc/sink: Initializing SW
D: bluealsa-pcm.c:477: /org/bluealsa/hci0/dev_04_02_CA_00_56_3E/a2dpsrc/sink: Prepared
D: bluealsa-pcm.c:440: /org/bluealsa/hci0/dev_04_02_CA_00_56_3E/a2dpsrc/sink: Initializing SW
AO: [alsa] 48000Hz stereo 2ch float
D: bluealsa-pcm.c:316: /org/bluealsa/hci0/dev_04_02_CA_00_56_3E/a2dpsrc/sink: Starting
D: bluealsa-pcm.c:176: /org/bluealsa/hci0/dev_04_02_CA_00_56_3E/a2dpsrc/sink: Waiting for first period of frames
D: bluealsa-pcm.c:183: /org/bluealsa/hci0/dev_04_02_CA_00_56_3E/a2dpsrc/sink: Starting IO loop: 11
A: 00:01:35 / 00:06:05 (26%)
```
This would affect cmus too, filling the cmus window with garbage
prev parent reply other threads:[~2021-05-12 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 0:52 [ISSUE] " 0xJes
2020-11-08 3:20 ` amak79
2020-11-08 3:21 ` amak79
2020-11-08 12:03 ` 0xJes
2020-11-08 12:08 ` amak79
2020-11-08 14:00 ` 0xJes
2021-01-20 20:51 ` ericonr
2021-05-12 12:50 ` ericonr [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=20210512125029.-4wtu_36xiAxZ6EqsI1cLYD-IIx3aB-vGShmB9qmX-I@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).