Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support pulseaudio in raspberrypi #141

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

support pulseaudio in raspberrypi #141

wants to merge 3 commits into from

Conversation

nivw
Copy link

@nivw nivw commented Sep 22, 2017

i also want to add the logrotate as I write a log in the service now.

@nivw
Copy link
Author

nivw commented Sep 23, 2017

I fixed the systemd service file to support pulseaudio, this is the way to run gmrender-resurrect
on my rpi. works fine. just have to create the environment var file

Copy link
Owner

@hzeller hzeller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution!
I have essentially only one comment, making the choice of audio output system less dependent on what the output system happens to be, but make it a deliberate choice of the user.

@@ -25,17 +25,29 @@ INITIAL_VOLUME_DB=-10
# 'aplay -L'), then gmediarenderer will use that ALSA device to play
# audio. Otherwise, whatever default is configured for gstreamer for the
# '$DAEMON_USER' is used.
ALSA_DEVICE="sysdefault"
RET=`dpkg -l pulseaudio`
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here, you are making the choice of pulseaudio vs. Alsa dependent on the existence of a particular packet, which sounds like it will result in non-repeatable results: if accidentally a pulseaudio package is installed, suddenly the way gmrender works is changing, which can make things surprising.

So I suggest to rather have this as a variable at the top (USE_PULSEAUDIO=1 or something).

@hzeller
Copy link
Owner

hzeller commented Oct 22, 2019

Did you get a chance to address the requested change ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants