|RYGEL.CONF(5)||Rygel User Manual||RYGEL.CONF(5)|
rygel.conf - Rygel configuration file
rygel reads its configuration values from the file $XDG_CONFIG_DIR/rygel.conf or a file given on command line with the --config option. If that file does not exist it uses the file /etc/rygel.conf.
Most of the options may be overriden by commandline arguments or envronment variables. See rygel(1) for details on those.
Lists in the configuration files are separated by a semicolon (;). Boolean values may be either true or false.
Only use this parameter if you know what your're doing or are being told to do so; overriding the default value might cause incompatibilites. If you find that adding your device here enables its usage with Rygel, please file an IOP bug so we can include it into the default configuration.
The settings in the [Database]section are for the database support library.
GSTREAMER MEDIA ENGINE SETTINGS¶
The settings in the [GstMediaEngine] section are specific to the GStreamer media engine, which is the default media engine. See the media-engine setting. These following options are available for the GStreamer media engine.
Sections for plugins are denoted with [PluginName] and can contain options specific to a plugin (see below) as well these common options:
The settings in [EnergyManagement-IFACENAME] sections specify the settings that relate to EnergyManagement services on this interface. Example: [EnergyManagement-eth0].
The tracker plugin uses the centralized database of meta information from the tracker project. See the tracker project website for more information about tracker.
The MediaExport plugin is an alternative to the tracker-backed media export. It extracts meta-data by itself and stores it in a SQLite database in $XDG_CACHE_DIR/rygel/media-export.db on UNIX platforms.
If both plugins, Tracker as well as MediaExport are enabled, MediaExport will disable itself in favour of the Tracker plugin.
There are several options supported by this plugin:
If you enter a normal path that contains whitespace there is no need to escape them with either a backslash or putting the string in quotes.
It is strongly advised against using an exported folder as a target for downloads when extract-metadata is enabled. Rygel will most likely ignore the files then because they will fail to extract.
Example 1. Possible values for uris
The Playbin plugin implements a media renderer (Digtal Media Renderer, DMR in DLNA terms). This plugin was known as GstRenderer.
It is highly recommended to leave the sink choice to playbin. If, however, the default choices don't work for you they can be reconfigured as follows
The LightMediaScanner plugin exports the contents of the lightmediascanner daemon
This plugin does not have any special options.
The GstLaunch plugin allows to expose GStreamer pipelines using the same syntax as the gst-launch utilty. You can configure several items in this plugins.
An example configuration is available in the distributed configuration file /etc/rygel.conf.
The External plugin is an consumer of the MediaServer2 DBus interface specification. This allows external programs to share their data via UPnP by implementing this DBus specification. The plugin picks up any implementation of this interface on the session bus and exposes the presented media via UPnP. Known implementors of this spec are gnome-dvb-daemon, Rhythmbox and Grilo via the grilo-ms2 project.
You can disable the whole functionality by setting enabled=false in the [External] section of the configuration file.
Individual peers may be enabled or disabled by creating sections corresponding to the D-Bus names of the peer:
This plugin has no additional options.
The MPRIS plugin is a consumer of the MPRIS2 DBus interface specification. The implementation conforms to version 2.0 of the standard.
rygel exposes media players that implement the provider side of this DBus specification as DLNA Digital Media Renderers (DMR) similar to the Playbin plugin. This means that you can easily turn your media player into a DMR by implementing this DBus specification.
Players that implement this spec and are known to work with rygel are Banshee, Rhythmbox and GNOME Videos (previously known as Totem)
You can disable the whole functionality by setting enabled=false in the [MRPIS] section of the configuration file.
The configuration of this plugin is special. Plugin configuration is not done on the plugin but rather per peer that is found providing the MPRIS2 interface. See the following example to set the title for Banshee on MPRIS:
[org.mpris.MediaPlayer2.banshee] title=@REALNAME@'s Banshee on @HOSTNAME@
This plugin has no additional options.
Jens Georg <email@example.com>
- file an IOP bug
- tracker project website
- lightmediascanner daemon
- MediaServer2 DBus interface specification
- MPRIS2 DBus interface specification
- GNOME Videos (previously known as Totem)