example.php just shows how the inclusionary process works. So taking existing php scripts and adding the include lines and the neccessary output of the vars should be no problem even with many different php scripts because they are using includes.php to get their vars.

should look like it would in a media player

http://localhost:8000/mount.mp3

As I said Steamcast doesn't work it's stats that way. You have to specify the mount point. Also you should notice that steamcast and icecast's yp directories are also using the mount point? Why should you change anything but Radio Toolbox? Just add the mount point and all will work fine. Steamcast ...

are you sure you are putting the right address in Radio Toolbox? You need to include the mount.

Steamcast is not a shoutcast server in that it has the capability of handling more then one source. You simply are running in shoutcast compatibility mode which means that people can connect to one of your sources via the index like a shoutcast server. The stats generated by steamcast are still ...

You need to specify the mount, for example:

http://ip.address:port/live.mp3

start it by going to the directory you untarred it to and typing

./steamcast

that url doesn't work for me, could you place it somewhere public or try your best to describe the problem?

You must have Steamcast 0.9.61

You are current running Steamcast 0.9.6

Get the latest Steamcast version from www.steamcast.com

I quickly whipped up an PHP script which will parse your Steamcast stats. Feel free to use it for whatever needs you might have. You can also modify it easy by using the Tag name in the $sources array.


Example:
$sources['/mount.mp3']['NAME'] holds the name of the stream
$sources['/mount.mp3 ...

An update has been made to Radio Toolbox to include Icecast 2.2.x branch support and Steamcast support.

Change Log for Radio Toolbox

Legend
======
* Modified/Fixed
+ Added
- Removed

1.1.1
=====
* Updated Icecast2 compatibility to the 2.2.x branch
+ Added support for Steamcast servers

Go get it ...

the directory tester only makes 2 connections when your server requests to be added to the directory. The first one is a connection to the audio portion of your server, the second is to the web interface. Please check to see if you see any yp-adds near the connection attempts. If you do then these ...

well any listeners that you would get from shoutcast.com would be lost so you lose an outlet to advertise your stream. Your current listeners will notice no effect and those who have bookmarked your stream or gain access to it through your website will still be able to get to it.

I would talk to your host provider in this case. the directory tester should not cause you buffering. Alternatively, you can just make your stream private and shoutcast won't need to test your stream as you will no longer request to be listed at www.shoutcast.com

that is the shoutcast directory tester, it does this to ensure that your stream is shoutcast complient. It certainly shouldn't kick your source, if it kicks your listeners then it is in the RIP list, which is crucial for being added to the directory, if your server is full when it tries to connect ...