However, I recommend you use the status page instead. 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. If you put more than 20, you should probably consider more coffee.
Recommended for those who wish to have the most secure logging possible. 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 can be another server relaying , localhost regular , or any other IP that your interface supports. Security wise, it is better to set this to something specific. 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, 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.
Posted March 30, Pictures from my leased ShoutCast service: D. Link to comment Share on other sites More sharing options Recommended Posts. Question: What information is asked for is under your Encoder tab? KarenMichelle Lane Posted March 31, Posted March 31, You are so very welcome. Create an account or sign in to comment You need to be a member in order to leave a comment Create an account Sign up for a new account in our community.
Register a new account. Sign in Already have an account? Sign In Now. Go to question listing. Find More Posts by MavMix. Password Thread Tools. Mark Forums Read. User Name. Remember Me? Thread Tools. Posts: 4,
0コメント