SHOUTcast/Installation/fr

Ce guide vous guide à travers les différentes étapes nécessaires à l'installation et la configuration d'un serveur de diffusion en flux pour la radio avec SHOUTcast serveur et SHOUTcast Trans.

Installer les fichiers
Le serveur SHOUTcast se trouve dans media-sound/SHOUTcast-serveur-bin. Vous pouvez l'installer avec la commande suivante :

Le serveur SHOUTcast est maintenant installé. La prochaine étape sera de le configurer.

Configurer le serveur SHOUTcast
Le fichier de configuration est. Assurez-vous d'être reconnu en tant qu'utilisateur root, et ouvrez le fichier de configuration avec votre éditeur favori. J'ai choisi vi dans ce cas.

Ceci affichera le fichier de configuration du serveur SHOUTcast. Vous pouvez y observer les différentes options à définir. Jetons-y un coup d'œil.

Options obligatoires
Définir la limite utilisateur

C'est ici que le nombre maximum d'utilisateurs est défini. Comme le titre le suggère, il n'est pas raisonnable de définir 100 utilisateurs avec une bande passante montante de 256 kbps (c'est ce que j'ai défini, car ma bande montante est environ celle-là). Si vous faites tourner un serveur SHOUTcast pour servir un LAN, vous pouvez probablement définir une valeur TRÈS supérieure (facilement jusqu'à 100). Rappelez-vous de ne pas abuse de ne pas exagérer, quelque soit votre bande passante. La bande passante coûte à vote FAI et certains couperont votre compte, vous factureront des prix élevés, ou les deux.

Définir le mot de passe

C'est ici que vous définissez votre mot de passe. Le mot de passe lui-même est du texte en clair. Pour des raisons de sécurité, il est FORTEMENT recommandé que vous n'utilisiez pas des mots de passe qui sont utilisés pour accéder à des composants critiques du système ou à d'autres informations sensibles. Rendez-le aussi aléatoire que possible, avec une combinaison de chiffres et de lettres. Ce mot de passe sera celui que SHOUTcast Trans (ou tout autre fournisseur de contenu) utilisera pour se connecter et fournir le contenu du flux diffusé.

Définir votre port d'écoute

Cette valeur définit le port par lequel les utilisateurs se connecteront à votre serveur SHOUTcast. La valeur par défaut est 8000., car c'est ce que la plupart des programmes comprenant un serveurs mp3 utilisent par défaut (Audacious, winamp, etc.). Comme dit précédemment, si vous voulez utiliser un numéro de port inférieur à 1024, vous devez être root. Néanmoins, je vous recommande fortement de ne pas utiliser un numéro de port inférieur à 1024 pour votre serveur SHOUTcast.

Définir la journalisation

Ceci définit l'emplacement de fichier de journalisation du serveur SHOUTcast. L'ebuild le définit à /dev/null, c'est pourquoi vous devez le changer pour avoir une journalisation réelle. Je le défini dans l'emplacement de base /var/log. Vous pouvez choisir ce que vous voulez.

Activer les satistiques de temps réel

Ceci affiche des informations sur la chanson courante vers la sortie standard toutes les secondes. Ceci est désactivé par l'ebuild de manière à ce que le démon SHOUTcast puisse tourner aussi silencieusement que possible. Mettez ceci à 1 si vous voulez cette mise à jour toutes les secondes. Néanmoins, nous recommandons d'utiliser plutôt la page d'état.

Enabling real time logging

This is disabled by default in the ebuild to make the daemon run as silently as possible. This will log any events (connects, disconnects, etc) to stdout as they happen in real time. However, because the log file does the same thing, I recommend using it instead.

Setting the last number of songs displayed

Just as it states, this value will set how many of the most recently played /played.html will display. If you put more than 20, you should probably consider more coffee.

Setting up filesystem modification logging

This setting enables or disables logging for directory modifications by the DNAS (Distributed Network Audio Server), or SHOUTcast for short. Recommended for those who wish to have the most secure logging possible. Basic home/casual users probably don't need this.

Enabling http request logging

This specifies whether or not you want to log hits to the HTTP server that SHOUTcast provides. Once again, recommended for those who wish the most secure logging possible, but not recommended for home/casual users.

Enabling W3C Logging

The first option enables W3C logging. This type of logging can be easily parsed by the programs listed. This is highly recommended for those who wish to have the most in depth statistics possible. The second option specifies where to store the W3C log. This is set to /dev/null by the ebuild.

Network Configuration
Setting the source IP

The SrcIP variable sets what IP streaming content is coming from. This can be another server (relaying), localhost (regular), or any other IP that your interface supports. Setting to localhost prevents any other server from using your SHOUTcast Server as a broadcast source. The default is ANY and will cause your SHOUTcast Server to source from any IP. Security wise, it is better to set this to something specific.

Setting the destination IP

This determines which IP on your interface you will allow users to connect to. This can be localhost (if you're anti-social and wish only to stream to yourself), a private IP (for instance, 192.168.0.101, for hosting to a local network), or your external IP (for instance, 209.204.249.201, for streaming to a WAN, but not a LAN). In most cases, you can reach your own stream by using 127.0.0.1 instead of what is listed here. ANY lets your SHOUTcast Server bind to all IP addresses on all available interfaces.

Setting proxy/yp.SHOUTcast.com port

This has 2 functions. First is the port to connect to yp.SHOUTcast.com with. yp.SHOUTcast.com is nullsoft's page for public servers so users know where to listen in on. Users can search for your station from this page. The secondary use is for web proxies. Set this to the port you use for proxy connects, and set DestIP to your proxy for streaming.

Setting up reverse DNS

This option specifies whether or not you want to perform reverse DNS lookups on clients. This would take an IP address and try to find out the corresponding host name. Use this for logging purposes to create a more detailed report.

Setting up relaying

This specifies that you are acting as a relay server. Relay servers are often used to take a low bandwidth connection that can only stream to one client, and use its own higher bandwidth to serve to more clients. RelayPort specifies the port and IP address of the SHOUTcast Server you wish to relay for. Comment this out if you don't plan on using your server as a relay.

Server Configuration
Setting the admin password

Setting this will create a broadcaster and administrator. The broadcaster can log in with Password, and view connections. However, should the person want to kick/ban/administer the server, they must have the Admin password. This option creates more specific roles for your server. This is recommended for instances where the system administrator is not the same person as the broadcaster.

Setting up auto user disconnect

This specifies whether or not users are kicked out if the stream disconnects for any reason. This is set to 0, so that clients will either timeout themselves, or keep trying to buffer a stream. Use this if you expect short interruptions at any time.

Setting up the source timeout

This specifies when the SHOUTcast Server should give up waiting for a source (mainly a relay server) to stream content from. Anywhere from 30 to 60 should be a reasonable value for this.

Setting up the content directory

The ContentDir specifies where to put on demand content. For example, if you wish to stream an announcement to employees, you could use this for that purpose. The SHOUTcast Server ebuild sets this to for you. To use this, put an mp3 in the content directory, then point your browser to. SHOUTcast Server will automatically create a streaming media compatible play list for the mp3, and stream it on demand. Use this as an alternative to SHOUTcast Trans for streaming media source.

Setting up an intro file

This allows you to configure an intro file. Every time users connect, they'll hear this file played. As it states, the stream bit rate and the intro song bit rate must match, or else things will break. You can, however, put something such as intro128.mp3 and intro64.mp3, and it will play intro128.mp3 to users connecting to a 128kbps stream, and intro64.mp3 for users connecting at 64kbps.

Setting up a back file

This is the same as above, but will be played when the stream source ends, instead of when users disconnect. This will only work if AutoDumpUsers is set to 0.

Setting up a title format

This sets up a non-variable title for your SHOUTcast server. Use this if your source stream differs from your SHOUTcast Server's name. This will NOT work with relay servers.

Setting up a URL format

This is the same as TitleFormat except that the URL listed above is used instead of the source stream's URL.

Setting up the public status of a source stream

This specifies whether or not you want to be listed as a public server even if your relay server/source plug-in is listed as such.

Allowing relaying

AllowRelay determines if other servers are allowed to relay your content. If you don't think you'll ever relay at all, set this to No.

Allowing relays to publically display the source

AllowPublicRelay specifies whether or not you wish to be listed in the SHOUTcastpublic directory if the server you're relaying to is already listed. Note that PublicServer can override this setting.

Setting MetaInterval

Just leave this as is.

Access Configuration
Setting the max listener time

I'm not to sure why you'd need this one. Basically, if a user is on for too many minutes, disconnect them. Only thing I can think of is to kick idlers off, or people you think should be doing other things than listening to your stream. Value is measured in minutes.

Setting up the ban file

This is the filename for the list of clients that are banned from your server. The default is sc_serv.ban, but you can use whatever name you so desire with this setting.

Setting the Rip list

As grim as it sounds, Rip actually stands for "Reserved IP". Use this for your friends or other people you consider more important than random users. If you are currently streaming to the max number of users possible, and one of your rip members tries to get on, it will kick the longest listening person from the server to get them on.

Setup if Rip only users can access your server

This allows for only Rip members to connect to your SHOUTcast Server. You can either use this for private radio streams, or to make it so that only certain relays will be able to access your stream.

Mass Configuration
Setting Unique variables

Basically, if you're running lots of SHOUTcast Servers, it would be a dire pain to change all the log/ban/etc. files to something unique for every configuration. Instead, you can set Unique to something, and $ will be replaced with whatever Unique is set to. For example, if one file had Unique=Jazz and another had Unique=Rock, then Log=/var/log/$.log would produce /var/log/Jazz.log on one configuration file and /var/log/Rock.log on another configuration file. Much easier when dealing with multiple SHOUTcast Servers on similar configurations.

Setting up common configure variables

If you're running multiple SHOUTcast Servers and wish to utilize similar configuration variables without setting them all for each configuration file, you can set this to point to a file that contains settings that are similar between multiple configurations.

Optimization Configuration
Setup number of CPU's utilized

On multiple CPU systems, use this setting to force the SHOUTcast Server to utilize CpuCount # of processors. The default to assign one thread to each processor, and have listeners across all the threads. If you set this lower than your total processor count, this will leave processors free to do other things.

Setup data submission gap

The SHOUTcast Server will use the sleep value in determining the gap between sending data. The higher the value, the longer the gap, the lower the value, the shorter the gap and the more CPU usage SHOUTcast Server will take up. On slower systems, as it states, you might want to lower this so that the SHOUTcast Servers sends data more and more frequently to users. Best to leave as is.

Setup XML output

Probably don't need to worry about this setting to much unless you use custom XML parsers to create custom statistics for you server. If the XML parser cannot handle whitespace and line feeds in XML, set this to Yes, and all should work.

Configuration Conclusion
Your SHOUTcast Server should now be configured. For businesses that are using SHOUTcast, I recommend turning on WC3 logging, as it can be easily parsed, and used for creating custom statistics. You should also enable the AdministratorPassword. You might also wish to enable some of the mass configuration options if you're creating multiple SHOUTcast Servers.

With the configuration setup, we'll now work on getting SHOUTcast up and running. We'll start with simple on demand streaming for a simple startup, then work on SHOUTcast Trans later (as it is somewhat more involved).

Setting up on demand streaming
On demand streaming, as shown in the configuration chapter, automatically sets up on demand play lists for mp3 files in the content directory. The SHOUTcast server ebuild has a directory setup in /opt/SHOUTcast/content for all your on demand mp3's. Let's get started by creating a simple on demand streaming mp3.

First we'll need to get an mp3 from somewhere and put it in the content directory. We'll take this sample.mp3 file from an /Mp3 directory I have created.

OK, so the file is copied over now. Now we'll need to startup our SHOUTcast Server so the file can be accessed.

The little banner is there to make sure that nothing dies right away (i.e. so you know your server actually started). Your SHOUTcast Server is now started! Because of the nature of on demand content, you will ONLY be able to access it from a browser. MPlayer or anything else won't be able to stream it as is. I use kmplayer in order to access the stream directly from my browser. You can see the result on the next image.

Some people have Audacious setup to handle their audio mime types, so your browser may spawn Audacious up in order to play the resulting streaming content. Now that you are able to work with on demand content, we'll now work on using SHOUTcast Trans to create a true streaming radio server.

SHOUTcast Trans introduction
SHOUTcast Trans stands for SHOUTcast Trans(coder), as it is able to transcode mp3's to lower or higher bit rates. SHOUTcast Trans works by streaming mp3's from a play list specified in the configuration file. We'll begin to setup the configuration for SHOUTcast Trans, so that we can have a real to goodness streaming radio station. We'll begin by opening the configuration file for SHOUTcast Trans, which just so happens to be located in /etc/shoutcast/sc_trans.conf.

Now that we have the SHOUTcast Trans configuration file open, we'll begin to setup the streaming source.

Configuring SHOUTcast Trans
Setting up the playlist

This setting tells SHOUTcast where to find its streaming media content from. This setting requires an existing file, so let's go ahead and create a play list. I'll create one real quick from my /Mp3 directory referred to earlier.

Now that the play list is setup, we point the configuration file to it, and SHOUTcast Trans will now know what files to stream.

Setting the server IP and port

This setting decides where to send the streaming content. In this guide, it will be the SHOUTcast Server's IP and port that you setup previously (DestIP and PortBase).

Setting the SHOUTcast Server password

The is the same password that you setup in the SHOUTcast Server configuration.

Setting up your stream information

This sets up the title of your stream (i.e. Radio One), the URL (i.e. http://www.radio-one.com), and the Genre (i.e. Electronica Trance Tribal).

Setting up your logfile

This will point to the log file for SHOUTcast Trans. All your logging goes here.

Setting up shuffling

Decide on whether or not you want your play list to play random songs from your list each time. Most will set this to 1. If you're going to be accepting song requests, set this to 0 and I'll explain how to do that later on.

Setting up the stream

Bitrate sets up the bit rate for your stream. This can be from 8000 (8kbps) to 128000 (128kbps). SampleRate sets the sampling rate of the stream. This can be anything from 11025 (11025kHz) to 44100 (44100kHz). Channels sets how many channels your stream will broadcast. This can be anything from 1 (mono) to 2 (stereo). Quality sets the stream quality. This is somewhat still controlled by the Bitrate/SampleRate/Channels. This is where you deal with how compressed the stream is. 1 gives you best quality, 10 gives you the best speed. Keep your connection in mind when you set these values! Use the guide given in order to figure out what your mp3's should be streamed at.

Setting up crossfading

This sets up song cross fading. Setting this to 0 will disable cross fading. If you set it to 1, Song 1 will fade out and Song 2 will fade in. If you set it to 2, Song 1 will fade in and Song 2 will fade out. The length is how long in ms the cross fade occurs.

Enabling ID3 usage

This decides whether or not you wish to use the ID3 tag for information about the mp3.

Setting up public status

This sets up whether or not streams should be publicly listed when relaying to a server. Remember PublicServer in sc_serv.conf can over-ride this!

Setting up user interaction

This sets up the information on how to reach you (the DJ). You can setup AIM or ICQ channels for song requests/anything. You can setup your own IRC channel as well, so that you can interact with multiple users at once.

SHOUTcast Trans Setup Conclusion
Your SHOUTcast Trans is now ready to stream to your SHOUTcast Server! We'll now get started on streaming your mp3's.

Starting up SHOUTcast Trans
As I most often use SHOUTcast Trans with SHOUTcast Server, I tend to startup SHOUTcast Trans, which in turns starts up SHOUTcast for you (much easier). So we'll go ahead and get SHOUTcast Trans started.

Listening to the SHOUTcast Trans stream
Now that SHOUTcast Trans is started, we'll start listening to the stream. I use MPlayer in this example to play the stream.

{{Cmd|mplayer -cache 1024 http://127.0.0.1:8000/|output= ... Playing http://127.0.0.1:8000/. Connecting to server 127.0.0.1[127.0.0.1]:8000 ... Name  : Chris Gentoo Beats Genre : JPOP Electronica And More! Website: http://www.gentoo.org Public : no Bitrate: 128kbit/s Cache size set to 1024 KBytes Connected to server: 127.0.0.1 Cache fill: 9.38% (98304 bytes)    Audio file detected.

=
============================================================= Opening audio decoder: [mp3lib] MPEG layer-2, layer-3 MP3lib: init layer2 and 3 finished, tables done mpg123: Can't rewind stream by 156 bits! AUDIO: 44100 Hz, 2 ch, 16 bit (0x10), ratio: 16000->176400 (128.0 kbit) Selected audio codec: [mp3] afm:mp3lib (mp3lib MPEG layer-2, layer-3)

=
============================================================= Checking audio filter chain for 44100Hz/2ch/16bit -> 44100Hz/2ch/16bit... AF_pre: af format: 2 bps, 2 ch, 44100 hz, little endian signed int AF_pre: 44100Hz 2ch Signed 16-bit (Little-Endian) AO: [oss] 44100Hz 2ch Signed 16-bit (Little-Endian) (2 bps) Building audio filter chain for 44100Hz/2ch/16bit -> 44100Hz/2ch/16bit... Video: no video Starting playback... }}

This was somewhat clipped. The -cache variable was put in to over-ride my somewhat larger buffering settings. And voilÃ ! You're now listening to streaming media! In the next chapter, we'll show you how to do a little bit more with your SHOUTcast Server.

Business Usage
Businesses can use SHOUTcast in a number of ways:


 * 1) Use on demand content streaming to make more interesting daily announcements.
 * 2) Have streaming public announcements available as they happen, let your clients know what's going on, on the spot! Then archive them as on demand content streaming for future reference.
 * 3) Do interviews as streaming media and archive them as on demand content streaming.

There are more possibilities on how to utilize SHOUTcast Server for businesses. Use live streaming media instead of boring old text!

DJ-ing with SHOUTcast
SHOUTcast Server is one of the most popular servers for both new and veteran DJs alike. For those just starting, there are a few ways to increase the user experience of your SHOUTcast Server. Having an intro song is very key. It gives the users an idea of what your station is all about. Be sure to include this! Post your server on yp.SHOUTcast.com (described in the SHOUTcast Server configuration section) so that everyone knows where you are. One of the most unique things is to be able to take requests. To set up requesting, first turn Shuffle off in sc_Trans.conf. Have about, I'd say, 10 or so songs ready to get you started. Then start requesting song requests in the middle. When someone requests a song, simple add it to the end of your play list, and then you can use this script here to control what SHOUTcast Trans does with your play list:

djcontrol

When you've added the song to the play list, you need to tell SHOUTcast Trans that your play list has changed with the new request entry.

You should now let the users know after what song the requests will start. Or if you want, you can keep skipping with:

Be careful not to skip too much, as there is no previous control. Once you hit their song, the requesting begins. I'd get about 5 or so requests before you start requesting. This way you don't run all the way back to the beginning. If you start to lack in requests and expect that your request hour is over with, then simply copy your next session's play list over the requests play list and reload the play list. Once the current song is over, it will go back to the new play list.

Conclusion
That ends it for the SHOUTcast Server and SHOUTcast Trans tutorial. I hope you benefited from the information here and please email me any comments or suggestions for this page! Enjoy your new streaming SHOUTcast Server!

Acknowledgements
We would like to thank the following authors and editors for their contributions to this guide:


 * Chris White
 * Shyam Mani