[ISSUE] bluez-alsa: debug output to terminal

[ISSUE] bluez-alsa: debug output to terminal

[0xJes]

[-- 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: 

Re: bluez-alsa: debug output to terminal

[amak79]

[-- 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.

Re: bluez-alsa: debug output to terminal

[amak79]

[-- 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.

Re: bluez-alsa: debug output to terminal

[0xJes]

[-- 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.

Re: bluez-alsa: debug output to terminal

[amak79]

[-- 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)?

Re: bluez-alsa: debug output to terminal

[0xJes]

[-- 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

Re: bluez-alsa: debug output to terminal

[ericonr]

[-- 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?

Re: [ISSUE] [CLOSED] bluez-alsa: debug output to terminal

[ericonr]

[-- 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