This can be localhost if you're anti-social and wish only to stream to yourself , a private IP for instance, In most cases, you can reach your own stream by using This has 2 functions. First is the port to connect to yp. 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. 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.
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. Comment this out if you don't plan on using your server as a relay. Setting this will create a broadcaster and administrator. The broadcaster can log in with Password, and view connections.
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. 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. 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. 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.
SHOUTcast Server will automatically create a streaming media compatible play list for the mp3, and stream it on demand. 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 intro 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.
This will NOT work with relay servers. 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. 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.
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. This is the filename for the list of clients that are banned from your server. 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.
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. 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.
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. 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. Probably don't need to worry about this setting to much unless you use custom XML parsers to create custom statistics for you server.
You should also enable the AdministratorPassword. We'll start with simple on demand streaming for a simple startup, then work on SHOUTcast Trans later as it is somewhat more involved. On demand streaming, as shown in the configuration chapter, automatically sets up on demand play lists for mp3 files in the content directory. 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. OK, so the file is copied over now. The little banner is there to make sure that nothing dies right away i. 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. We'll begin to setup the configuration for SHOUTcast Trans, so that we can have a real to goodness streaming radio station. This setting requires an existing file, so let's go ahead and create a play list. Now that the play list is setup, we point the configuration file to it, and SHOUTcast Trans will now know what files to stream.
This setting decides where to send the streaming content. This sets up the title of your stream i. Radio One , the URL i. Electronica Trance Tribal. 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. Bitrate sets up the bit rate for your stream. This can be from 8kbps to kbps. SampleRate sets the sampling rate of the stream. This can be anything from kHz to kHz. 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 where you deal with how compressed the stream is.
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. 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. This sets up whether or not streams should be publicly listed when relaying to a server.
This sets up the information on how to reach you the DJ. You can setup your own IRC channel as well, so that you can interact with multiple users at once. We'll now get started on streaming your mp3's. I use MPlayer in this example to play the stream. This was somewhat clipped. The -cache variable was put in to over-ride my somewhat larger buffering settings.
You're now listening to streaming media! Use live streaming media instead of boring old text! 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. One of the most unique things is to be able to take requests. 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:. 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. I hope you benefited from the information here and please email me any comments or suggestions for this page! Add a comment. Active Oldest Votes. Improve this answer. Brad Brad k 45 45 gold badges silver badges bronze badges. Thanks but if say every 5 minutes I write that mp3 to the config file in shoutcast dont I need to re-boot the stream — RussellHarrower.
RussellHarrower, No, that's not what I'm saying. Leave the config file alone, pointed at somefile. Your script will write your updated MP3 files, replacing the file contents of somefile.
Does that make sense? If your MP3 files are of any reasonable size, I suggest making the symlink, as switching the symlink is very fast. I suspect there is a lock, but I am not sure. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.
The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta.
0コメント