| 1 |
swift 08/05/19 20:43:16 |
| 2 |
|
| 3 |
Modified: shoutcast-config.xml |
| 4 |
Log: |
| 5 |
Coding style |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.16 xml/htdocs/doc/en/shoutcast-config.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/shoutcast-config.xml?rev=1.16&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/shoutcast-config.xml?rev=1.16&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/shoutcast-config.xml?r1=1.15&r2=1.16 |
| 13 |
|
| 14 |
Index: shoutcast-config.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/shoutcast-config.xml,v |
| 17 |
retrieving revision 1.15 |
| 18 |
retrieving revision 1.16 |
| 19 |
diff -u -r1.15 -r1.16 |
| 20 |
--- shoutcast-config.xml 2 Nov 2006 18:52:48 -0000 1.15 |
| 21 |
+++ shoutcast-config.xml 19 May 2008 20:43:16 -0000 1.16 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version='1.0' encoding='UTF-8'?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/shoutcast-config.xml,v 1.15 2006/11/02 18:52:48 nightmorph Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/shoutcast-config.xml,v 1.16 2008/05/19 20:43:16 swift Exp $ --> |
| 27 |
<guide link="/doc/en/shoutcast-config.xml"> |
| 28 |
<title>Streaming Radio With SHOUTcast</title> |
| 29 |
|
| 30 |
@@ -30,7 +30,7 @@ |
| 31 |
<body> |
| 32 |
|
| 33 |
<p> |
| 34 |
-The SHOUTcast Server can be found in media-sound/SHOUTcast-server-bin. You can |
| 35 |
+The SHOUTcast Server can be found in media-sound/SHOUTcast-server-bin. You can |
| 36 |
install it with the following command: |
| 37 |
</p> |
| 38 |
|
| 39 |
@@ -39,7 +39,7 @@ |
| 40 |
</pre> |
| 41 |
|
| 42 |
<p> |
| 43 |
-The SHOUTcast Server will now be installed. The next step is configuring your |
| 44 |
+The SHOUTcast Server will now be installed. The next step is configuring your |
| 45 |
new SHOUTcast Server. |
| 46 |
</p> |
| 47 |
|
| 48 |
@@ -50,10 +50,10 @@ |
| 49 |
<body> |
| 50 |
|
| 51 |
<p> |
| 52 |
-Now that SHOUTcast Server is installed, it must be configured. The |
| 53 |
-configuration file can be found in <path>/etc/shoutcast/sc_serv.conf</path>. |
| 54 |
-Let's begin with the configuration. Make sure you are root, and open the |
| 55 |
-configuration file with your favorite editor. I choose vi for this example. |
| 56 |
+Now that SHOUTcast Server is installed, it must be configured. The |
| 57 |
+configuration file can be found in <path>/etc/shoutcast/sc_serv.conf</path>. |
| 58 |
+Let's begin with the configuration. Make sure you are root, and open the |
| 59 |
+configuration file with your favorite editor. I choose vi for this example. |
| 60 |
Now I'll bring up the file with vi: |
| 61 |
</p> |
| 62 |
|
| 63 |
@@ -62,8 +62,8 @@ |
| 64 |
</pre> |
| 65 |
|
| 66 |
<p> |
| 67 |
-This will bring up the SHOUTcast Server configuration file for viewing. |
| 68 |
-From there you will see the configuration file and the different options |
| 69 |
+This will bring up the SHOUTcast Server configuration file for viewing. |
| 70 |
+From there you will see the configuration file and the different options |
| 71 |
that you can set. Let's take a look on how to setup these particular options. |
| 72 |
</p> |
| 73 |
|
| 74 |
@@ -84,10 +84,10 @@ |
| 75 |
</pre> |
| 76 |
|
| 77 |
<p> |
| 78 |
-This is where the maximum number of users is set. As the caption states, |
| 79 |
+This is where the maximum number of users is set. As the caption states, |
| 80 |
it is foolish to setup 100 users on a 256kbps upload (This is what I have set, |
| 81 |
-as my upload is about that). If you're running SHOUTcast Server to serve a |
| 82 |
-LAN, you can probably set this MUCH higher (to the 100 mentioned easily). |
| 83 |
+as my upload is about that). If you're running SHOUTcast Server to serve a |
| 84 |
+LAN, you can probably set this MUCH higher (to the 100 mentioned easily). |
| 85 |
Please remember to not abuse whatever bandwidth you are using though. Bandwidth |
| 86 |
comes at quite a high price to ISPs and some will cut your account, fine you |
| 87 |
high costs to makeup, or both. |
| 88 |
@@ -104,11 +104,11 @@ |
| 89 |
</pre> |
| 90 |
|
| 91 |
<p> |
| 92 |
-Here is where you setup the password. The password itself is clear text. For |
| 93 |
+Here is where you setup the password. The password itself is clear text. For |
| 94 |
security purposes, I STRONGLY recommend that you don't use passwords that are |
| 95 |
-used to access critical system components or other sensitive information. |
| 96 |
+used to access critical system components or other sensitive information. |
| 97 |
Make this as random as possible, with a combination of letters and numbers. |
| 98 |
-This password will be what SHOUTcast Trans (or any other content provider) |
| 99 |
+This password will be what SHOUTcast Trans (or any other content provider) |
| 100 |
will use to connect and provide streaming content. |
| 101 |
</p> |
| 102 |
|
| 103 |
@@ -141,7 +141,7 @@ |
| 104 |
</pre> |
| 105 |
|
| 106 |
<p> |
| 107 |
-This sets the location of the SHOUTcast server log file. The ebuild |
| 108 |
+This sets the location of the SHOUTcast server log file. The ebuild |
| 109 |
has it set to /dev/null, so you will need to change it in order to get a real |
| 110 |
log. I have it setup in the basic /var/log location. You can have it log to |
| 111 |
wherever you need. |
| 112 |
@@ -155,9 +155,9 @@ |
| 113 |
</pre> |
| 114 |
|
| 115 |
<p> |
| 116 |
-This displays information on the current song to stdout every second. This |
| 117 |
+This displays information on the current song to stdout every second. This |
| 118 |
is disabled by the ebuild so that the SHOUTcast daemon can run as silently |
| 119 |
-as possible. Set this to 1 if you want these updates each second. However, I |
| 120 |
+as possible. Set this to 1 if you want these updates each second. However, I |
| 121 |
recommend you use the status page instead. |
| 122 |
</p> |
| 123 |
|
| 124 |
@@ -171,7 +171,7 @@ |
| 125 |
<p> |
| 126 |
This is disabled by default in the ebuild to make the daemon run as |
| 127 |
silently as possible. This will log any events (connects, disconnects, etc) |
| 128 |
-to stdout as they happen in real time. However, because the log file |
| 129 |
+to stdout as they happen in real time. However, because the log file |
| 130 |
does the same thing, I recommend using it instead. |
| 131 |
</p> |
| 132 |
|
| 133 |
@@ -183,7 +183,7 @@ |
| 134 |
|
| 135 |
<p> |
| 136 |
Just as it states, this value will set how many of the most recently played |
| 137 |
-/played.html will display. If you put more than 20, you should probably |
| 138 |
+/played.html will display. If you put more than 20, you should probably |
| 139 |
consider more coffee. |
| 140 |
</p> |
| 141 |
|
| 142 |
@@ -196,9 +196,9 @@ |
| 143 |
</pre> |
| 144 |
|
| 145 |
<p> |
| 146 |
-This setting enables or disables logging for directory modifications |
| 147 |
-by the DNAS (Distributed Network Audio Server), or SHOUTcast for short. |
| 148 |
-Recommended for those who wish to have the most secure logging possible. |
| 149 |
+This setting enables or disables logging for directory modifications |
| 150 |
+by the DNAS (Distributed Network Audio Server), or SHOUTcast for short. |
| 151 |
+Recommended for those who wish to have the most secure logging possible. |
| 152 |
Basic home/casual users probably don't need this. |
| 153 |
</p> |
| 154 |
|
| 155 |
@@ -216,7 +216,7 @@ |
| 156 |
|
| 157 |
<p> |
| 158 |
This specifies whether or not you want to log hits to the HTTP server that |
| 159 |
-SHOUTcast provides. Once again, recommended for those who wish the most |
| 160 |
+SHOUTcast provides. Once again, recommended for those who wish the most |
| 161 |
secure logging possible, but not recommended for home/casual users. |
| 162 |
</p> |
| 163 |
|
| 164 |
@@ -234,8 +234,8 @@ |
| 165 |
</pre> |
| 166 |
|
| 167 |
<p> |
| 168 |
-The first option enables W3C logging. This type of logging can be easily parsed |
| 169 |
-by the programs listed. This is highly recommended for those who wish to |
| 170 |
+The first option enables W3C logging. This type of logging can be easily parsed |
| 171 |
+by the programs listed. This is highly recommended for those who wish to |
| 172 |
have the most in depth statistics possible. The second option specifies where |
| 173 |
to store the W3C log. This is set to /dev/null by the ebuild. |
| 174 |
</p> |
| 175 |
@@ -255,10 +255,10 @@ |
| 176 |
</pre> |
| 177 |
|
| 178 |
<p> |
| 179 |
-The SrcIP variable sets what IP streaming content is coming from. This can |
| 180 |
-be another server (relaying), localhost (regular), or any other IP that your |
| 181 |
-interface supports. Setting to localhost prevents any other server from |
| 182 |
-using your SHOUTcast Server as a broadcast source. The default is ANY |
| 183 |
+The SrcIP variable sets what IP streaming content is coming from. This can |
| 184 |
+be another server (relaying), localhost (regular), or any other IP that your |
| 185 |
+interface supports. Setting to localhost prevents any other server from |
| 186 |
+using your SHOUTcast Server as a broadcast source. The default is ANY |
| 187 |
and will cause your SHOUTcast Server to source from any IP. Security wise, it |
| 188 |
is better to set this to something specific. |
| 189 |
</p> |
| 190 |
@@ -271,12 +271,12 @@ |
| 191 |
</pre> |
| 192 |
|
| 193 |
<p> |
| 194 |
-This determines which IP on your interface you will allow users to connect to. |
| 195 |
-This can be localhost (if you're anti-social and wish only to |
| 196 |
-stream to yourself), a private IP (for instance, 192.168.0.101, for hosting to |
| 197 |
-a local network), or your external IP (for instance, 209.204.249.201, for |
| 198 |
-streaming to a WAN, but not a LAN). In most cases, you can reach your own |
| 199 |
-stream by using 127.0.0.1 instead of what is listed here. ANY lets your |
| 200 |
+This determines which IP on your interface you will allow users to connect to. |
| 201 |
+This can be localhost (if you're anti-social and wish only to |
| 202 |
+stream to yourself), a private IP (for instance, 192.168.0.101, for hosting to |
| 203 |
+a local network), or your external IP (for instance, 209.204.249.201, for |
| 204 |
+streaming to a WAN, but not a LAN). In most cases, you can reach your own |
| 205 |
+stream by using 127.0.0.1 instead of what is listed here. ANY lets your |
| 206 |
SHOUTcast Server bind to all IP addresses on all available interfaces. |
| 207 |
</p> |
| 208 |
|
| 209 |
@@ -290,9 +290,9 @@ |
| 210 |
</pre> |
| 211 |
|
| 212 |
<p> |
| 213 |
-This has 2 functions. First is the port to connect to yp.SHOUTcast.com with. |
| 214 |
+This has 2 functions. First is the port to connect to yp.SHOUTcast.com with. |
| 215 |
yp.SHOUTcast.com is nullsoft's page for public servers so users know where to |
| 216 |
-listen in on. Users can search for your station from this page. The |
| 217 |
+listen in on. Users can search for your station from this page. The |
| 218 |
secondary use is for web proxies. Set this to the port you use for proxy |
| 219 |
connects, and set DestIP to your proxy for streaming. |
| 220 |
</p> |
| 221 |
@@ -305,7 +305,7 @@ |
| 222 |
</pre> |
| 223 |
|
| 224 |
<p> |
| 225 |
-This option specifies whether or not you want to perform reverse DNS lookups |
| 226 |
+This option specifies whether or not you want to perform reverse DNS lookups |
| 227 |
on clients. This would take an IP address and try to find out the corresponding |
| 228 |
host name. Use this for logging purposes to create a more detailed report. |
| 229 |
</p> |
| 230 |
@@ -320,10 +320,10 @@ |
| 231 |
</pre> |
| 232 |
|
| 233 |
<p> |
| 234 |
-This specifies that you are acting as a relay server. Relay servers are |
| 235 |
+This specifies that you are acting as a relay server. Relay servers are |
| 236 |
often used to take a low bandwidth connection that can only stream to one |
| 237 |
-client, and use its own higher bandwidth to serve to more clients. RelayPort |
| 238 |
-specifies the port and IP address of the SHOUTcast Server you wish to |
| 239 |
+client, and use its own higher bandwidth to serve to more clients. RelayPort |
| 240 |
+specifies the port and IP address of the SHOUTcast Server you wish to |
| 241 |
relay for. Comment this out if you don't plan on using your server as a relay. |
| 242 |
</p> |
| 243 |
|
| 244 |
@@ -346,11 +346,11 @@ |
| 245 |
</pre> |
| 246 |
|
| 247 |
<p> |
| 248 |
-Setting this will create a broadcaster and administrator. The broadcaster can |
| 249 |
-log in with Password, and view connections. However, should the person want |
| 250 |
+Setting this will create a broadcaster and administrator. The broadcaster can |
| 251 |
+log in with Password, and view connections. However, should the person want |
| 252 |
to kick/ban/administer the server, they must have the Admin password. This |
| 253 |
-option creates more specific roles for your server. This is recommended for |
| 254 |
-instances where the system administrator is not the same person as the |
| 255 |
+option creates more specific roles for your server. This is recommended for |
| 256 |
+instances where the system administrator is not the same person as the |
| 257 |
broadcaster. |
| 258 |
</p> |
| 259 |
|
| 260 |
@@ -362,8 +362,8 @@ |
| 261 |
|
| 262 |
<p> |
| 263 |
This specifies whether or not users are kicked out if the stream disconnects |
| 264 |
-for any reason. This is set to 0, so that clients will either timeout |
| 265 |
-themselves, or keep trying to buffer a stream. Use this if you expect |
| 266 |
+for any reason. This is set to 0, so that clients will either timeout |
| 267 |
+themselves, or keep trying to buffer a stream. Use this if you expect |
| 268 |
short interruptions at any time. |
| 269 |
</p> |
| 270 |
|
| 271 |
@@ -375,7 +375,7 @@ |
| 272 |
</pre> |
| 273 |
|
| 274 |
<p> |
| 275 |
-This specifies when the SHOUTcast Server should give up waiting for a source |
| 276 |
+This specifies when the SHOUTcast Server should give up waiting for a source |
| 277 |
(mainly a relay server) to stream content from. Anywhere from 30 to 60 should be |
| 278 |
a reasonable value for this. |
| 279 |
</p> |
| 280 |
@@ -389,14 +389,14 @@ |
| 281 |
</pre> |
| 282 |
|
| 283 |
<p> |
| 284 |
-The ContentDir specifies where to put on demand content. For example, if you |
| 285 |
-wish to stream an announcement to employees, you could use this for that |
| 286 |
-purpose. The SHOUTcast Server ebuild sets this to |
| 287 |
+The ContentDir specifies where to put on demand content. For example, if you |
| 288 |
+wish to stream an announcement to employees, you could use this for that |
| 289 |
+purpose. The SHOUTcast Server ebuild sets this to |
| 290 |
<path>/opt/SHOUTcast/content</path> for you. To use this, put an mp3 in the |
| 291 |
-content directory, then point your browser to |
| 292 |
-<c>http://example.com:[port]/content/mp3name.pls</c>. SHOUTcast Server will |
| 293 |
-automatically create a streaming media compatible play list for the mp3, and |
| 294 |
-stream it on demand. Use this as an alternative to SHOUTcast Trans for |
| 295 |
+content directory, then point your browser to |
| 296 |
+<c>http://example.com:[port]/content/mp3name.pls</c>. SHOUTcast Server will |
| 297 |
+automatically create a streaming media compatible play list for the mp3, and |
| 298 |
+stream it on demand. Use this as an alternative to SHOUTcast Trans for |
| 299 |
streaming media source. |
| 300 |
</p> |
| 301 |
|
| 302 |
@@ -412,11 +412,12 @@ |
| 303 |
</pre> |
| 304 |
|
| 305 |
<p> |
| 306 |
-This allows you to configure an intro file. Every time users connect, they'll |
| 307 |
-hear this file played. As it states, the stream bit rate and the intro song |
| 308 |
-bit rate must match, or else things will break. You can, however, put |
| 309 |
-something such as intro128.mp3 and intro64.mp3, and it will play intro128.mp3 |
| 310 |
-to users connecting to a 128kbps stream, and intro64 for users connecting at 64kbps. |
| 311 |
+This allows you to configure an intro file. Every time users connect, they'll |
| 312 |
+hear this file played. As it states, the stream bit rate and the intro song |
| 313 |
+bit rate must match, or else things will break. You can, however, put |
| 314 |
+something such as intro128.mp3 and intro64.mp3, and it will play intro128.mp3 |
| 315 |
+to users connecting to a 128kbps stream, and intro64 for users connecting at |
| 316 |
+64kbps. |
| 317 |
</p> |
| 318 |
|
| 319 |
<pre caption="Setting up a back file"> |
| 320 |
@@ -433,8 +434,8 @@ |
| 321 |
</pre> |
| 322 |
|
| 323 |
<p> |
| 324 |
-This is the same as above, but will be played when the stream source ends, |
| 325 |
-instead of when users disconnect. This will only work if AutoDumpUsers is set |
| 326 |
+This is the same as above, but will be played when the stream source ends, |
| 327 |
+instead of when users disconnect. This will only work if AutoDumpUsers is set |
| 328 |
to 0. |
| 329 |
</p> |
| 330 |
|
| 331 |
@@ -451,8 +452,8 @@ |
| 332 |
</pre> |
| 333 |
|
| 334 |
<p> |
| 335 |
-This sets up a non-variable title for your Shoutcast server. Use this if your |
| 336 |
-source stream differs from your SHOUTcast Server's name. This will NOT work |
| 337 |
+This sets up a non-variable title for your Shoutcast server. Use this if your |
| 338 |
+source stream differs from your SHOUTcast Server's name. This will NOT work |
| 339 |
with relay servers. |
| 340 |
</p> |
| 341 |
|
| 342 |
@@ -464,7 +465,7 @@ |
| 343 |
</pre> |
| 344 |
|
| 345 |
<p> |
| 346 |
-This is the same as TitleFormat except that the URL listed above is used |
| 347 |
+This is the same as TitleFormat except that the URL listed above is used |
| 348 |
instead of the source stream's URL. |
| 349 |
</p> |
| 350 |
|
| 351 |
@@ -476,7 +477,7 @@ |
| 352 |
</pre> |
| 353 |
|
| 354 |
<p> |
| 355 |
-This specifies whether or not you want to be listed as a public server even if |
| 356 |
+This specifies whether or not you want to be listed as a public server even if |
| 357 |
your relay server/source plug-in is listed as such. |
| 358 |
</p> |
| 359 |
|
| 360 |
@@ -525,15 +526,15 @@ |
| 361 |
<pre caption="Setting the max listner time"> |
| 362 |
<comment>; ListenerTimer is a value in minutes of maximum permitted time for |
| 363 |
; a connected listener. If someone is connected for longer than this |
| 364 |
-; amount of time, in minutes, they are disconnected. When undefined, |
| 365 |
+; amount of time, in minutes, they are disconnected. When undefined, |
| 366 |
; there is no limit defined. Default is undefined. |
| 367 |
; ListenerTimer=600</comment> |
| 368 |
</pre> |
| 369 |
|
| 370 |
<p> |
| 371 |
-I'm not to sure why you'd need this one. Basically, if a user is on for too |
| 372 |
-many minutes, disconnect them. Only thing I can think of is to kick idlers |
| 373 |
-off, or people you think should be doing other things than listening to your |
| 374 |
+I'm not to sure why you'd need this one. Basically, if a user is on for too |
| 375 |
+many minutes, disconnect them. Only thing I can think of is to kick idlers |
| 376 |
+off, or people you think should be doing other things than listening to your |
| 377 |
stream. Value is measured in minutes. |
| 378 |
</p> |
| 379 |
|
| 380 |
@@ -546,8 +547,8 @@ |
| 381 |
</pre> |
| 382 |
|
| 383 |
<p> |
| 384 |
-This is the filename for the list of clients that are banned from your server. |
| 385 |
-The default is sc_serv.ban, but you can use whatever name you so desire with |
| 386 |
+This is the filename for the list of clients that are banned from your server. |
| 387 |
+The default is sc_serv.ban, but you can use whatever name you so desire with |
| 388 |
this setting. |
| 389 |
</p> |
| 390 |
|
| 391 |
@@ -564,10 +565,10 @@ |
| 392 |
</pre> |
| 393 |
|
| 394 |
<p> |
| 395 |
-As grim as it sounds, Rip actually stands for "Reserved IP". Use this for |
| 396 |
+As grim as it sounds, Rip actually stands for "Reserved IP". Use this for |
| 397 |
your friends or other people you consider more important than random users. |
| 398 |
-If you are currently streaming to the max number of users possible, and one |
| 399 |
-of your rip members tries to get on, it will kick the longest listening person |
| 400 |
+If you are currently streaming to the max number of users possible, and one |
| 401 |
+of your rip members tries to get on, it will kick the longest listening person |
| 402 |
from the server to get them on. |
| 403 |
</p> |
| 404 |
|
| 405 |
@@ -609,14 +610,14 @@ |
| 406 |
</pre> |
| 407 |
|
| 408 |
<p> |
| 409 |
-Basically, if you're running lots of SHOUTcast Servers, it would be a dire |
| 410 |
-pain to change all the log/ban/etc. files to something unique for every |
| 411 |
-configuration. Instead, you can set Unique to something, and $ will be |
| 412 |
-replaced with whatever Unique is set to. For example, if one file had |
| 413 |
-Unique=Jazz and another had Unique=Rock, then Log=/var/log/$.log would |
| 414 |
-produce /var/log/Jazz.log on one configuration file and /var/log/Rock.log on another |
| 415 |
-configuration file. Much easier when dealing with multiple SHOUTcast Servers on |
| 416 |
-similar configurations. |
| 417 |
+Basically, if you're running lots of SHOUTcast Servers, it would be a dire |
| 418 |
+pain to change all the log/ban/etc. files to something unique for every |
| 419 |
+configuration. Instead, you can set Unique to something, and $ will be |
| 420 |
+replaced with whatever Unique is set to. For example, if one file had |
| 421 |
+Unique=Jazz and another had Unique=Rock, then Log=/var/log/$.log would |
| 422 |
+produce /var/log/Jazz.log on one configuration file and /var/log/Rock.log |
| 423 |
+on another configuration file. Much easier when dealing with multiple |
| 424 |
+SHOUTcast Servers on similar configurations. |
| 425 |
</p> |
| 426 |
|
| 427 |
<pre caption="Setting up common configure variables"> |
| 428 |
@@ -633,9 +634,9 @@ |
| 429 |
</pre> |
| 430 |
|
| 431 |
<p> |
| 432 |
-If you're running multiple SHOUTcast Servers and wish to utilize similar |
| 433 |
-configuration variables without setting them all for each configuration |
| 434 |
-file, you can set this to point to a file that contains settings that are |
| 435 |
+If you're running multiple SHOUTcast Servers and wish to utilize similar |
| 436 |
+configuration variables without setting them all for each configuration |
| 437 |
+file, you can set this to point to a file that contains settings that are |
| 438 |
similar between multiple configurations. |
| 439 |
</p> |
| 440 |
|
| 441 |
@@ -659,8 +660,8 @@ |
| 442 |
</pre> |
| 443 |
|
| 444 |
<p> |
| 445 |
-On multiple CPU systems, use this setting to force the SHOUTcast Server to |
| 446 |
-utilize CpuCount # of processors. The default to assign one thread to each |
| 447 |
+On multiple CPU systems, use this setting to force the SHOUTcast Server to |
| 448 |
+utilize CpuCount # of processors. The default to assign one thread to each |
| 449 |
processor, and have listeners across all the threads. If you set this lower |
| 450 |
than your total processor count, this will leave processors free to do other |
| 451 |
things. |
| 452 |
@@ -683,11 +684,11 @@ |
| 453 |
</pre> |
| 454 |
|
| 455 |
<p> |
| 456 |
-The SHOUTcast Server will use the sleep value in determining the gap between |
| 457 |
+The SHOUTcast Server will use the sleep value in determining the gap between |
| 458 |
sending data. The higher the value, the longer the gap, the lower the value, |
| 459 |
the shorter the gap and the more CPU usage SHOUTcast Server will take up. On |
| 460 |
-slower systems, as it states, you might want to lower this so that the |
| 461 |
-SHOUTcast Servers sends data more and more frequently to users. Best to leave |
| 462 |
+slower systems, as it states, you might want to lower this so that the |
| 463 |
+SHOUTcast Servers sends data more and more frequently to users. Best to leave |
| 464 |
as is. |
| 465 |
</p> |
| 466 |
|
| 467 |
@@ -699,9 +700,9 @@ |
| 468 |
</pre> |
| 469 |
|
| 470 |
<p> |
| 471 |
-Probably don't need to worry about this setting to much unless you use custom |
| 472 |
-XML parsers to create custom statistics for you server. If the XML parser |
| 473 |
-cannot handle whitespace and line feeds in XML, set this to Yes, and all should |
| 474 |
+Probably don't need to worry about this setting to much unless you use custom |
| 475 |
+XML parsers to create custom statistics for you server. If the XML parser |
| 476 |
+cannot handle whitespace and line feeds in XML, set this to Yes, and all should |
| 477 |
work. |
| 478 |
</p> |
| 479 |
|
| 480 |
@@ -712,16 +713,16 @@ |
| 481 |
<body> |
| 482 |
|
| 483 |
<p> |
| 484 |
-Your SHOUTcast Server should now be configured. For businesses that are using |
| 485 |
-SHOUTcast, I recommend turning on WC3 logging, as it can be easily parsed, and |
| 486 |
-used for creating custom statistics. You should also enable the |
| 487 |
-AdministratorPassword. You might also wish to enable some of the mass |
| 488 |
+Your SHOUTcast Server should now be configured. For businesses that are using |
| 489 |
+SHOUTcast, I recommend turning on WC3 logging, as it can be easily parsed, and |
| 490 |
+used for creating custom statistics. You should also enable the |
| 491 |
+AdministratorPassword. You might also wish to enable some of the mass |
| 492 |
configuration options if you're creating multiple SHOUTcast Servers. |
| 493 |
</p> |
| 494 |
|
| 495 |
<p> |
| 496 |
-With the configuration setup, we'll now work on getting SHOUTcast up and |
| 497 |
-running. We'll start with simple on demand streaming for a simple startup, |
| 498 |
+With the configuration setup, we'll now work on getting SHOUTcast up and |
| 499 |
+running. We'll start with simple on demand streaming for a simple startup, |
| 500 |
then work on SHOUTcast Trans later (as it is somewhat more involved). |
| 501 |
</p> |
| 502 |
|
| 503 |
@@ -736,15 +737,15 @@ |
| 504 |
<body> |
| 505 |
|
| 506 |
<p> |
| 507 |
-On demand streaming, as shown in the configuration chapter, automatically sets |
| 508 |
-up on demand play lists for mp3 files in the content directory. The Shoutcast |
| 509 |
+On demand streaming, as shown in the configuration chapter, automatically sets |
| 510 |
+up on demand play lists for mp3 files in the content directory. The Shoutcast |
| 511 |
server ebuild has a directory setup in /opt/SHOUTcast/content for all your on |
| 512 |
demand mp3's. Let's get started by creating a simple on demand streaming mp3. |
| 513 |
</p> |
| 514 |
|
| 515 |
<p> |
| 516 |
-First we'll need to get an mp3 from somewhere and put it in the content |
| 517 |
-directory. We'll take this sample.mp3 file from an /Mp3 directory I have |
| 518 |
+First we'll need to get an mp3 from somewhere and put it in the content |
| 519 |
+directory. We'll take this sample.mp3 file from an /Mp3 directory I have |
| 520 |
created. |
| 521 |
</p> |
| 522 |
|
| 523 |
@@ -756,7 +757,7 @@ |
| 524 |
</pre> |
| 525 |
|
| 526 |
<p> |
| 527 |
-OK, so the file is copied over now. Now we'll need to startup our SHOUTcast |
| 528 |
+OK, so the file is copied over now. Now we'll need to startup our SHOUTcast |
| 529 |
Server so the file can be accessed. |
| 530 |
</p> |
| 531 |
|
| 532 |
@@ -767,7 +768,7 @@ |
| 533 |
** SHOUTcast Distributed Network Audio Server |
| 534 |
** Copyright (C) 1998-2004 Nullsoft, Inc. All Rights Reserved. |
| 535 |
** Use "sc_serv filename.ini" to specify an ini file. |
| 536 |
-******************************************************************************* |
| 537 |
+******************************************************************************* |
| 538 |
[ ok ] |
| 539 |
</pre> |
| 540 |
|
| 541 |
@@ -780,7 +781,8 @@ |
| 542 |
see the result on the next image. |
| 543 |
</p> |
| 544 |
|
| 545 |
-<figure caption="On Demand Content" short="OnDemandContent" link="/images/docs/shoutcast-OnDemandContent.jpg" /> |
| 546 |
+<figure caption="On Demand Content" short="OnDemandContent" |
| 547 |
+link="/images/docs/shoutcast-OnDemandContent.jpg" /> |
| 548 |
|
| 549 |
<p> |
| 550 |
Some people have Audacious setup to handle their audio mime types, so your |
| 551 |
@@ -800,12 +802,12 @@ |
| 552 |
<body> |
| 553 |
|
| 554 |
<p> |
| 555 |
-SHOUTcast Trans stands for SHOUTcast Trans(coder), as it is able to transcode |
| 556 |
-mp3's to lower or higher bit rates. SHOUTcast Trans works by streaming mp3's |
| 557 |
+SHOUTcast Trans stands for SHOUTcast Trans(coder), as it is able to transcode |
| 558 |
+mp3's to lower or higher bit rates. SHOUTcast Trans works by streaming mp3's |
| 559 |
from a play list specified in the configuration file. We'll begin to setup the |
| 560 |
-configuration for SHOUTcast Trans, so that we can have a real to goodness |
| 561 |
+configuration for SHOUTcast Trans, so that we can have a real to goodness |
| 562 |
streaming radio station. We'll begin by opening the configuration file for |
| 563 |
-SHOUTcast Trans, which just so happens to be located in |
| 564 |
+SHOUTcast Trans, which just so happens to be located in |
| 565 |
/etc/shoutcast/sc_trans.conf. |
| 566 |
</p> |
| 567 |
|
| 568 |
@@ -817,7 +819,7 @@ |
| 569 |
</pre> |
| 570 |
|
| 571 |
<p> |
| 572 |
-Now that we have the SHOUTcast Trans configuration file open, we'll begin to |
| 573 |
+Now that we have the SHOUTcast Trans configuration file open, we'll begin to |
| 574 |
setup the streaming source. |
| 575 |
</p> |
| 576 |
|
| 577 |
@@ -834,9 +836,9 @@ |
| 578 |
</pre> |
| 579 |
|
| 580 |
<p> |
| 581 |
-This setting tells SHOUTcast where to find its streaming media content from. |
| 582 |
-This setting requires an existing file, so let's go ahead and create a |
| 583 |
-play list. I'll create one real quick from my /Mp3 directory referred to |
| 584 |
+This setting tells SHOUTcast where to find its streaming media content from. |
| 585 |
+This setting requires an existing file, so let's go ahead and create a |
| 586 |
+play list. I'll create one real quick from my /Mp3 directory referred to |
| 587 |
earlier. |
| 588 |
</p> |
| 589 |
|
| 590 |
@@ -845,7 +847,7 @@ |
| 591 |
</pre> |
| 592 |
|
| 593 |
<p> |
| 594 |
-Now that the play list is setup, we point the configuration file to it, and |
| 595 |
+Now that the play list is setup, we point the configuration file to it, and |
| 596 |
SHOUTcast Trans will now know what files to stream. |
| 597 |
</p> |
| 598 |
|
| 599 |
@@ -856,8 +858,8 @@ |
| 600 |
</pre> |
| 601 |
|
| 602 |
<p> |
| 603 |
-This setting decides where to send the streaming content. In this guide, |
| 604 |
-it will be the SHOUTcast Server's IP and port that you setup previously |
| 605 |
+This setting decides where to send the streaming content. In this guide, |
| 606 |
+it will be the SHOUTcast Server's IP and port that you setup previously |
| 607 |
(DestIP and PortBase). |
| 608 |
</p> |
| 609 |
|
| 610 |
@@ -879,7 +881,7 @@ |
| 611 |
</pre> |
| 612 |
|
| 613 |
<p> |
| 614 |
-This sets up the title of your stream (i.e. Radio One), the URL (i.e. |
| 615 |
+This sets up the title of your stream (i.e. Radio One), the URL (i.e. |
| 616 |
http://www.radio-one.com), and the Genre (i.e. Electronica Trance Tribal). |
| 617 |
</p> |
| 618 |
|
| 619 |
@@ -901,8 +903,8 @@ |
| 620 |
</pre> |
| 621 |
|
| 622 |
<p> |
| 623 |
-Decide on whether or not you want your play list to play random songs from your |
| 624 |
-list each time. Most will set this to 1. If you're going to be accepting |
| 625 |
+Decide on whether or not you want your play list to play random songs from your |
| 626 |
+list each time. Most will set this to 1. If you're going to be accepting |
| 627 |
song requests, set this to 0 and I'll explain how to do that later on. |
| 628 |
</p> |
| 629 |
|
| 630 |
@@ -924,12 +926,12 @@ |
| 631 |
</pre> |
| 632 |
|
| 633 |
<p> |
| 634 |
-Bitrate sets up the bit rate for your stream. This can be from 8000 (8kbps) to |
| 635 |
+Bitrate sets up the bit rate for your stream. This can be from 8000 (8kbps) to |
| 636 |
128000 (128kbps). SampleRate sets the sampling rate of the stream. This can |
| 637 |
-be anything from 11025 (11025kHz) to 44100 (44100kHz). Channels sets how |
| 638 |
+be anything from 11025 (11025kHz) to 44100 (44100kHz). Channels sets how |
| 639 |
many channels your stream will broadcast. This can be anything from 1 (mono) |
| 640 |
-to 2 (stereo). Quality sets the stream quality. This is somewhat still |
| 641 |
-controlled by the Bitrate/SampleRate/Channels. This is where you deal with |
| 642 |
+to 2 (stereo). Quality sets the stream quality. This is somewhat still |
| 643 |
+controlled by the Bitrate/SampleRate/Channels. This is where you deal with |
| 644 |
how compressed the stream is. 1 gives you best quality, 10 gives you the best |
| 645 |
speed. Keep your connection in mind when you set these values! Use the guide |
| 646 |
given in order to figure out what your mp3's should be streamed at. |
| 647 |
@@ -943,9 +945,9 @@ |
| 648 |
</pre> |
| 649 |
|
| 650 |
<p> |
| 651 |
-This sets up song cross fading. Setting this to 0 will disable cross fading. |
| 652 |
+This sets up song cross fading. Setting this to 0 will disable cross fading. |
| 653 |
If you set it to 1, Song 1 will fade out and Song 2 will fade in. If you set |
| 654 |
-it to 2, Song 1 will fade in and Song 2 will fade out. The length is how long |
| 655 |
+it to 2, Song 1 will fade in and Song 2 will fade out. The length is how long |
| 656 |
in ms the cross fade occurs. |
| 657 |
</p> |
| 658 |
|
| 659 |
@@ -954,7 +956,7 @@ |
| 660 |
</pre> |
| 661 |
|
| 662 |
<p> |
| 663 |
-This decides whether or not you wish to use the ID3 tag for information about |
| 664 |
+This decides whether or not you wish to use the ID3 tag for information about |
| 665 |
the mp3. |
| 666 |
</p> |
| 667 |
|
| 668 |
@@ -976,7 +978,7 @@ |
| 669 |
</pre> |
| 670 |
|
| 671 |
<p> |
| 672 |
-This sets up the information on how to reach you (the DJ). You can setup AIM |
| 673 |
+This sets up the information on how to reach you (the DJ). You can setup AIM |
| 674 |
or ICQ channels for song requests/anything. You can setup your own IRC channel |
| 675 |
as well, so that you can interact with multiple users at once. |
| 676 |
</p> |
| 677 |
@@ -988,7 +990,7 @@ |
| 678 |
<body> |
| 679 |
|
| 680 |
<p> |
| 681 |
-Your SHOUTcast Trans is now ready to stream to your SHOUTcast Server! We'll |
| 682 |
+Your SHOUTcast Trans is now ready to stream to your SHOUTcast Server! We'll |
| 683 |
now get started on streaming your mp3's. |
| 684 |
</p> |
| 685 |
|
| 686 |
@@ -1003,7 +1005,7 @@ |
| 687 |
<body> |
| 688 |
|
| 689 |
<p> |
| 690 |
-As I most often use SHOUTcast Trans with SHOUTcast Server, I tend to startup |
| 691 |
+As I most often use SHOUTcast Trans with SHOUTcast Server, I tend to startup |
| 692 |
SHOUTcast Trans, which in turns starts up SHOUTcast for you (much easier). So |
| 693 |
we'll go ahead and get SHOUTcast Trans started. |
| 694 |
</p> |
| 695 |
@@ -1015,7 +1017,7 @@ |
| 696 |
** SHOUTcast Distributed Network Audio Server |
| 697 |
** Copyright (C) 1998-2004 Nullsoft, Inc. All Rights Reserved. |
| 698 |
** Use "sc_serv filename.ini" to specify an ini file. |
| 699 |
-******************************************************************************* |
| 700 |
+******************************************************************************* |
| 701 |
[ ok ] |
| 702 |
* Starting Shoutcast Trans... [ ok ] |
| 703 |
</pre> |
| 704 |
@@ -1027,7 +1029,7 @@ |
| 705 |
<body> |
| 706 |
|
| 707 |
<p> |
| 708 |
-Now that SHOUTcast Trans is started, we'll start listening to the stream. I |
| 709 |
+Now that SHOUTcast Trans is started, we'll start listening to the stream. I |
| 710 |
use MPlayer in this example to play the stream. |
| 711 |
</p> |
| 712 |
|
| 713 |
@@ -1061,9 +1063,9 @@ |
| 714 |
</pre> |
| 715 |
|
| 716 |
<p> |
| 717 |
-This was somewhat clipped. The -cache variable was put in to over-ride my |
| 718 |
-somewhat larger buffering settings. And viola! You're now listening to |
| 719 |
-streaming media! In the next chapter, we'll show you how to do a little |
| 720 |
+This was somewhat clipped. The -cache variable was put in to over-ride my |
| 721 |
+somewhat larger buffering settings. And viola! You're now listening to |
| 722 |
+streaming media! In the next chapter, we'll show you how to do a little |
| 723 |
bit more with your SHOUTcast Server. |
| 724 |
</p> |
| 725 |
|
| 726 |
@@ -1082,23 +1084,23 @@ |
| 727 |
</p> |
| 728 |
|
| 729 |
<ol> |
| 730 |
- <li> |
| 731 |
+ <li> |
| 732 |
Use on demand content streaming to make more interesting daily |
| 733 |
- announcements. |
| 734 |
+ announcements. |
| 735 |
</li> |
| 736 |
- <li> |
| 737 |
- Have streaming public announcements available as they happen, let your |
| 738 |
- clients know what's going on, on the spot! Then archive them as on |
| 739 |
+ <li> |
| 740 |
+ Have streaming public announcements available as they happen, let your |
| 741 |
+ clients know what's going on, on the spot! Then archive them as on |
| 742 |
demand content streaming for future reference. |
| 743 |
</li> |
| 744 |
- <li> |
| 745 |
- Do interviews as streaming media and archive them as on demand content |
| 746 |
+ <li> |
| 747 |
+ Do interviews as streaming media and archive them as on demand content |
| 748 |
streaming. |
| 749 |
</li> |
| 750 |
</ol> |
| 751 |
|
| 752 |
<p> |
| 753 |
-There are more possibilities on how to utilize SHOUTcast Server for businesses. |
| 754 |
+There are more possibilities on how to utilize SHOUTcast Server for businesses. |
| 755 |
Use live streaming media instead of boring old text! |
| 756 |
</p> |
| 757 |
|
| 758 |
@@ -1109,38 +1111,38 @@ |
| 759 |
<body> |
| 760 |
|
| 761 |
<p> |
| 762 |
-SHOUTcast Server is one of the most popular servers for both new and veteran |
| 763 |
-DJs alike. For those just starting, there are a few ways to increase the |
| 764 |
-user experience of your SHOUTcast Server. Having an intro song is very key. |
| 765 |
-It gives the users an idea of what your station is all about. Be sure to |
| 766 |
-include this! Post your server on yp.SHOUTcast.com (described in the |
| 767 |
-SHOUTcast Server configuration section) so that everyone knows where you |
| 768 |
-are. One of the most unique things is to be able to take requests. To set |
| 769 |
-up requesting, first turn Shuffle off in sc_Trans.conf. Have about, I'd say, |
| 770 |
+SHOUTcast Server is one of the most popular servers for both new and veteran |
| 771 |
+DJs alike. For those just starting, there are a few ways to increase the |
| 772 |
+user experience of your SHOUTcast Server. Having an intro song is very key. |
| 773 |
+It gives the users an idea of what your station is all about. Be sure to |
| 774 |
+include this! Post your server on yp.SHOUTcast.com (described in the |
| 775 |
+SHOUTcast Server configuration section) so that everyone knows where you |
| 776 |
+are. One of the most unique things is to be able to take requests. To set |
| 777 |
+up requesting, first turn Shuffle off in sc_Trans.conf. Have about, I'd say, |
| 778 |
10 or so songs ready to get you started. Then start requesting song requests |
| 779 |
in the middle. When someone requests a song, simple add it to the end of your |
| 780 |
-play list, and then you can use this script here to control what SHOUTcast |
| 781 |
+play list, and then you can use this script here to control what SHOUTcast |
| 782 |
Trans does with your play list: |
| 783 |
</p> |
| 784 |
|
| 785 |
<pre caption="djcontrol"> |
| 786 |
<comment>#!/bin/bash</comment> |
| 787 |
|
| 788 |
-case "$1" in |
| 789 |
- "reload") |
| 790 |
- kill -s USR1 `cat /var/run/SHOUTcast_Trans.pid` |
| 791 |
- ;; |
| 792 |
- "next") |
| 793 |
- kill -s WINCH `cat /var/run/SHOUTcast_Trans.pid` |
| 794 |
- ;; |
| 795 |
- *) |
| 796 |
- echo "Invalid command" |
| 797 |
- ;; |
| 798 |
+case "$1" in |
| 799 |
+ "reload") |
| 800 |
+ kill -s USR1 `cat /var/run/SHOUTcast_Trans.pid` |
| 801 |
+ ;; |
| 802 |
+ "next") |
| 803 |
+ kill -s WINCH `cat /var/run/SHOUTcast_Trans.pid` |
| 804 |
+ ;; |
| 805 |
+ *) |
| 806 |
+ echo "Invalid command" |
| 807 |
+ ;; |
| 808 |
esac |
| 809 |
</pre> |
| 810 |
|
| 811 |
<p> |
| 812 |
-When you've added the song to the play list, you need to tell SHOUTcast Trans |
| 813 |
+When you've added the song to the play list, you need to tell SHOUTcast Trans |
| 814 |
that your play list has changed with the new request entry. |
| 815 |
</p> |
| 816 |
|
| 817 |
@@ -1149,7 +1151,7 @@ |
| 818 |
</pre> |
| 819 |
|
| 820 |
<p> |
| 821 |
-You should now let the users know after what song the requests will start. Or |
| 822 |
+You should now let the users know after what song the requests will start. Or |
| 823 |
if you want, you can keep skipping with: |
| 824 |
</p> |
| 825 |
|
| 826 |
@@ -1158,11 +1160,11 @@ |
| 827 |
</pre> |
| 828 |
|
| 829 |
<p> |
| 830 |
-Be careful not to skip too much, as there is no previous control. Once you |
| 831 |
+Be careful not to skip too much, as there is no previous control. Once you |
| 832 |
hit their song, the requesting begins. I'd get about 5 or so requests before |
| 833 |
-you start requesting. This way you don't run all the way back to the |
| 834 |
-beginning. If you start to lack in requests and expect that your request |
| 835 |
-hour is over with, then simply copy your next session's play list over the |
| 836 |
+you start requesting. This way you don't run all the way back to the |
| 837 |
+beginning. If you start to lack in requests and expect that your request |
| 838 |
+hour is over with, then simply copy your next session's play list over the |
| 839 |
requests play list and reload the play list. Once the current song is over, |
| 840 |
it will go back to the new play list. |
| 841 |
</p> |
| 842 |
@@ -1174,8 +1176,8 @@ |
| 843 |
<body> |
| 844 |
|
| 845 |
<p> |
| 846 |
-That ends it for the SHOUTcast Server and SHOUTcast Trans tutorial. I hope |
| 847 |
-you benefited from the information here and please email me any comments or |
| 848 |
+That ends it for the SHOUTcast Server and SHOUTcast Trans tutorial. I hope |
| 849 |
+you benefited from the information here and please email me any comments or |
| 850 |
suggestions for this page! Enjoy your new streaming SHOUTcast Server! |
| 851 |
</p> |
| 852 |
|
| 853 |
|
| 854 |
|
| 855 |
|
| 856 |
-- |
| 857 |
gentoo-doc-cvs@l.g.o mailing list |
Archives