RoarAudio PlayList Daemon (rpld)
What is the RoarAudio PlayList Daemon (rpld)?
The RoarAudio PlayList Daemon (short rpld) is a player backend based on RoarAudio. It manages playlists and the actual playback of tracks. It does not provide any user interface but a remote control so user interfaces can connect and control everything rpld does. rpld can handle multiple user interfaces (remote controls) at a time.
If rpld is combined with a GUI which connects to it and a RoarAudio sound server the result is a full media player as most today's users are used to expect that rpld has multiple playlists. There are playlists created by the user. Those can for example hold a single album or a complet music collection.
In additions there are so called queues and so called historys. The queues are the lists of currently queued music. If you want to play some music you queue the tracks. This means the track is appended to a queue. The queue is processes from top to bottom. As soon as all songs above the added one are done the song is played. Of cause it's perfectly possible to jump to a song directly (commonly called "Play now!") or queue it as next song independed on how full the queue is.
The historys are the playlists where played songs go to. You can view it manually or just use the next and previous feature (buttons as you expect them in most GUIs) to navigate thru the history.
By default there is a Main Queue as well as a Main History representing the default output. Each queue is independed and represent a independed stream of music. You can add and remove any number of queues and historys e.g. one per room or user.
What if a queue runs out of songs?
There is something called playlist pointers which are a powerful tool to auto insert songs into the queue. Simples usecase is to set a pointer to a entry in a playlist and rpld starts to play back from this possition to end of playlist. GUIs should add some nice buttons to the user for easy pointer management like a Play from here-button or something the like.
On what OperatingSystem does the RoarAudio PlayList Daemon run?
The RoarAudio PlayList Daemon is designed to run on all POSIX systems but may also run on other systems, too. As it only depeneds on libroar it is very portable.
What Containers/Codecs/Plugins/Specal Effects/... are supported?
As the RoarAudio PlayList Daemon does not handle any of those stuffs itself it does not support any of them. Those stuff is handled on diffrent layers. All of the Audio processing is done within the connected RoarAudio sound server. So the support for containers, codecs and audio processing stuff depends on the server. But also read the paragraph about the codec-helper bellow.
Other stuff like connecting a IR remote control is handled externaly. Those stuff connect like a system service to rpld and interacts with it using it's normal remote protocol.
What is the codec-helper?
The codec-helper is a normaly a little script which implements codecs not supported by
the server. This was added to rpld because a free and open RoarAudio server can not
implment MP3 support legaly because of patents and licenses of MP3.
To enable the user to play his/her/its/hir MP3s as well rpld will just call this script
to transcode the music before sending it to the server.
|Powered by Fellig.org, Vim and Freedom.|