File: INSTALL.md

package info (click to toggle)
gmrender-resurrect 0.0.9-2
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, bullseye, sid
  • size: 588 kB
  • sloc: ansic: 4,734; sh: 192; makefile: 50; xml: 12
file content (194 lines) | stat: -rw-r--r-- 6,747 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
# Installing

On a typical Ubuntu or Debian system, you need tools to be able to bootstrap the
compilation configuration:

    sudo apt-get install build-essential autoconf automake libtool pkg-config

.. and the libraries needed for gmrender, most notably gstreamer.

```
sudo apt-get update
sudo aptitude install libupnp-dev libgstreamer1.0-dev \
             gstreamer1.0-plugins-base gstreamer1.0-plugins-good \
             gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly \
             gstreamer1.0-libav
```

(The code will also compile with the older 0.10 of gstreamer)

Then pulseaudio or alsa depending on what output you prefer (personally, I use
alsa)

    sudo aptitude install gstreamer1.0-alsa
    sudo aptitude install gstreamer1.0-pulseaudio


Get the source. If this is your first time using git, you first need to install
it:

    sudo apt-get install git

.. Then check out the source:

    git clone https://github.com/hzeller/gmrender-resurrect.git

Then configure and build

    cd gmrender-resurrect
    ./autogen.sh
    ./configure
    make

You then can run gmrender directly from here if you want. The `-f` option
provides the name under which the UPnP renderer advertises:

    ./src/gmediarender -f "My Renderer"

.. to install, run

    sudo make install

The final binary is in `/usr/local/bin/gmediarender` (unless you changed the
PREFIX in the configure step).

# Running

## Init Script

There is a sample init script in `scripts/init.d/gmediarenderer` that could be
a good start if you install things on your system.

A systemd unit file can be found in `dist-scripts/debian/gmrender-resurrect.service`.

(To Linux distribution packagers: please let me know if you have some
common changes that might be useful to have in upstream; other than that, just
do what makes most sense in your distribution)

## Commandline Options

If you write your own init script for your gmediarender, then the following
options are particularly useful.

### -f, --friendly-name
Friendly name to advertise. Usually, you want your renderer show up in your
controller under a nice name. This is the option to set that name.

### -u, --uuid
UUID to advertise. Usually, gmediarender comes with a built-in static id, that
is advertised and used by controllers to distinguish different renderers.
If you have multiple renderers running in your network, they will all share the
same static ID.
With this option, you can give each renderer its own id.
Best way is to create a UUID once by running the `uuidgen` tool:

    $ sudo apt-get install uuid-runtime
    $ uuidgen
    a07e8dfe-26a4-11e2-9dd1-5404a632c90e

You take different generated numbers and hard-code it in each script
starting an instance of gmediarender (In my init script, I just generate
some stable value based on the ethernet MAC address; see "Init Script" below).

Also, you can do this already at compile time, when running configure

    ./configure CPPFLAGS="-DGMRENDER_UUID='\"`uuidgen`\"'"

### --gstout-audiosink and --gstout-audiodevice
You can set the audio sink and audio device with these commandline
options.
Say, you want to use an ALSA device. You can see the available devices
with `aplay -L`. The main ALSA device is typically called `sysdefault`,
so this is how you select it on the command line:

    gmediarender --gstout-audiosink=alsasink --gstout-audiodevice=sysdefault

The options are described with

    gmediarender --help-gstout

There are other ways to configure the default gstreamer output devices via
some global system settings, but in particular if you are on some embedded
device, setting these directly via a commandline option is the very best.

### --gstout-initial-volume-db
This sets the initial volume on startup in decibel. The level 0.0 decibel
is 'full volume', -20db would show on the UPnP controller as '50%'. In the
following table you see the non-linear relationship:

     [decibel]  [level shown in player]
           0db    100     # this is the default if option not set
          -6db    85
         -10db    75
         -20db    50
         -40db    25
         -60db    0

So with --gstout-initial-volume-db=-10 the player would show up as being set
to #75.

Note, as always with the volume level in this renderer, this does not
influence the hardware level (e.g. Alsa), but only the internal attenuation.
So it is advised to always set the hardware output to 100% by system means.

### Running as daemon

If you want to run gmediarender as daemon, the follwing two options are for
you:

    -d, --daemon                      Run as daemon.
    -P, --pid-file                    File the process ID should be written to.


### Misc options

    --logfile <logfile>               Write a logfile.
        If you want this on the terminal use --logfile /dev/stdout
        This can be big over time, so only do it for debugging.

In particular when you file a bug, please always attach the output of such
a logfile; start gmrender-resurrect in foreground mode (without `-d`) on the
commandline and give it a file to log into. Attach that to your bug-report.

The following command makes sure to capture all logs from gmediarender and other
log entries that might come from gstreamer plugins not using the gmediarender
logging, all in one file:

    src/gmediarender -f "MyRender" --logfile=/tmp/gmrender.log >> /tmp/gmrender.log 2>&1

# Other installation resources
## Raspberry Pi
If you're installing gmrender-resurrect on the Raspberry Pi, there have
been reports of bad sound quality. For one, the 3.5mm output is very low
quality, so don't expect wonders (though it seems that driver changes improved
this quality a lot).

You can use gmrender-resurrect with Pulseaudio or ALSA (or whatever other output
ways gstreamer supports). Personally, I use ALSA as it is the most simple and
robust way (Pulseaudio would be a layer on top of ALSA anyway).
See flag --gstout-audiosink above how to tell gmediarender to use alsasink.

By default, ALSA seems to attempt some re-sampling apparently; A user
pointed out that this can be fixed by putting this in your `/etc/asound.conf`

    ctl.!default {
      type hw
      card 0
    }

Stephen Phillips wrote a comprehensive blog-post about installing
gmrender-resurrect on the Raspberry Pi (July 2013):

http://blog.scphillips.com/2013/07/playing-music-on-a-raspberry-pi-using-upnp-and-dlna-revisited/

## Arch Linux
There is an Arch package available here
 https://aur.archlinux.org/packages/gmrender-resurrect-git/

## Debian
Since Debian 8, the official `gmediarender` package uses the gmrender-resurrect code:
 https://packages.debian.org/stretch/gmediarender

## Nix
There is a Nix package available:
 https://nixos.org/nixos/packages.html?attr=gmrender-resurrect