* [ISSUE] bluez-alsa: debug output to terminal
@ 2020-11-04 0:52 0xJes
2020-11-08 3:20 ` amak79
` (6 more replies)
0 siblings, 7 replies; 8+ messages in thread
From: 0xJes @ 2020-11-04 0:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
New 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:
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: bluez-alsa: debug output to terminal
2020-11-04 0:52 [ISSUE] bluez-alsa: debug output to terminal 0xJes
@ 2020-11-08 3:20 ` amak79
2020-11-08 3:21 ` amak79
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: amak79 @ 2020-11-08 3:20 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
New comment by amak79 on void-packages repository
https://github.com/void-linux/void-packages/issues/26122#issuecomment-723525025
Comment:
Try adding the following to `/etc/sv/bluez-alsa`
```
OPTS="--syslog"
```
Then restart the `bluez-alsa` service.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: bluez-alsa: debug output to terminal
2020-11-04 0:52 [ISSUE] bluez-alsa: debug output to terminal 0xJes
2020-11-08 3:20 ` amak79
@ 2020-11-08 3:21 ` amak79
2020-11-08 12:03 ` 0xJes
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: amak79 @ 2020-11-08 3:21 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 262 bytes --]
New comment by amak79 on void-packages repository
https://github.com/void-linux/void-packages/issues/26122#issuecomment-723525025
Comment:
Try adding the following to `/etc/sv/bluez-alsa/conf`
```
OPTS="--syslog"
```
Then restart the `bluez-alsa` service.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: bluez-alsa: debug output to terminal
2020-11-04 0:52 [ISSUE] bluez-alsa: debug output to terminal 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
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: 0xJes @ 2020-11-08 12:03 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 224 bytes --]
New comment by 0xJes on void-packages repository
https://github.com/void-linux/void-packages/issues/26122#issuecomment-723568272
Comment:
I've tried the` --syslog` option but the debug output in the terminal did not stop.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: bluez-alsa: debug output to terminal
2020-11-04 0:52 [ISSUE] bluez-alsa: debug output to terminal 0xJes
` (2 preceding siblings ...)
2020-11-08 12:03 ` 0xJes
@ 2020-11-08 12:08 ` amak79
2020-11-08 14:00 ` 0xJes
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: amak79 @ 2020-11-08 12:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 226 bytes --]
New comment by amak79 on void-packages repository
https://github.com/void-linux/void-packages/issues/26122#issuecomment-723568820
Comment:
Have you enabled [logging](https://docs.voidlinux.org/config/services/logging.html)?
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: bluez-alsa: debug output to terminal
2020-11-04 0:52 [ISSUE] bluez-alsa: debug output to terminal 0xJes
` (3 preceding siblings ...)
2020-11-08 12:08 ` amak79
@ 2020-11-08 14:00 ` 0xJes
2021-01-20 20:51 ` ericonr
2021-05-12 12:50 ` [ISSUE] [CLOSED] " ericonr
6 siblings, 0 replies; 8+ messages in thread
From: 0xJes @ 2020-11-08 14:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 228 bytes --]
New comment by 0xJes on void-packages repository
https://github.com/void-linux/void-packages/issues/26122#issuecomment-723581077
Comment:
I enabled it when I tested bluealsa with `--syslog` option. Usually I don't use logging
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: bluez-alsa: debug output to terminal
2020-11-04 0:52 [ISSUE] bluez-alsa: debug output to terminal 0xJes
` (4 preceding siblings ...)
2020-11-08 14:00 ` 0xJes
@ 2021-01-20 20:51 ` ericonr
2021-05-12 12:50 ` [ISSUE] [CLOSED] " ericonr
6 siblings, 0 replies; 8+ messages in thread
From: ericonr @ 2021-01-20 20:51 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 215 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/26122#issuecomment-763928318
Comment:
@0xJes should be fine to make a PR to remove debugging, can you do that?
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [ISSUE] [CLOSED] bluez-alsa: debug output to terminal
2020-11-04 0:52 [ISSUE] bluez-alsa: debug output to terminal 0xJes
` (5 preceding siblings ...)
2021-01-20 20:51 ` ericonr
@ 2021-05-12 12:50 ` ericonr
6 siblings, 0 replies; 8+ messages in thread
From: ericonr @ 2021-05-12 12:50 UTC (permalink / raw)
To: ml
[-- 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
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2021-05-12 12:50 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-04 0:52 [ISSUE] bluez-alsa: debug output to terminal 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 ` [ISSUE] [CLOSED] " ericonr
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).