| | 27 | A complete setup contains 5 parts: |
| | 28 | * A user |
| | 29 | * A user interface |
| | 30 | * rpld |
| | 31 | * A RoarAudio Server |
| | 32 | * An Operating System |
| | 33 | |
| | 34 | While some of those are not exactly need from technical point there can be any number of other components as well. The next section will list some other examples of software which can be included in a setup. |
| | 35 | |
| | 36 | === The user === |
| | 37 | This is you. While not needed normally you (or some other person) controls rpld using the an user interface. |
| | 38 | In some cases there is no user but rpld is configured in a way to start playback of a given list automatically at startup. |
| | 39 | |
| | 40 | === The user interface === |
| | 41 | This is a software allowing you to control rpld. This could be a GUI, random commandlion tools, a web interface, an IR remote (with a IR daemon), an App for your smartphone or anything else that allows you to interact with rpld. |
| | 42 | |
| | 43 | === rpld itself === |
| | 44 | This is rpld. It does all the playlist work. |
| | 45 | |
| | 46 | === The RoarAudio Server === |
| | 47 | This server does all the audio work. It decodes the files, sends them to the audio sink. Normally the audio sink is your soundcard so you can listen with your speakers or headphones. Yet the server is free to send the data to any other kind of sink. This could for example be a streaming server such as Icecast or a VHF/FM Radio Transmitter. |
| | 48 | |
| | 49 | === The Operating System === |
| | 50 | This is the system all or some of the components run on. Examples include GNU/Linux. See the list in the next section for details. |
| | 51 | |
