thanks geoff - Yes, I had disabled the <alias source="/" dest="/status.xsl"/> in the config. To answer your question: If the mountpoint is set to "radio.mp3" and the host tag is set for a local broadcast. ie.: <hostname>localhost</hostname> (for testing purposes), this is what happens when I enter "http://localhost:7000/" into a browser: The audio is streamed to disk under what looks like a random filename (eg wjgol87m). If the mountpoint is set to "radio", an error page is loaded into the browser: "The source you requested could not be found." In this state, entering http://localhost:7000/radio.m3u lets me listen to the audio in xmms. But i notice the mountpoint must be named radio.mp3 for "*.pls" file to be used. cheers, iain On Sat, 2005-06-04 at 11:43 +1000, Geoff Shang wrote:> Note that I think in the supplied config file, "/" is aliased to one > of the > stats pages, so you'd need to delete/comment out this definition. > > What happens when you try to connect to "/" manually? >
Iain Mott wrote:> To answer your question: If the mountpoint is set to "radio.mp3" and the > host tag is set for a local broadcast. ie.: > <hostname>localhost</hostname> (for testing purposes), this is what > happens when I enter "http://localhost:7000/" into a browser: The audio > is streamed to disk under what looks like a random filename (eg > wjgol87m).You shouldn't enter a stream URL into your browser, because this is the kind of thing that will happen. The way this works is that your browser downloads a file or page, then passes it off to the appropriate application if it can't deal with it itself. Since a stream never ends, it will never finish downloading, and even if it did eventually, you want to listen to it as it comes in, not afterwoods. So that's why you use a playlist file like an .M3U or .PLS file. This file gets downloaded and passed to your player, which opens it and sees where the stream is. And the player then opens the stream and plays it.> If the mountpoint is set to "radio", an error page is loaded into the > browser: "The source you requested could not be found."This means that there's no stream on that mount point. If this is where you actually want it, you'll need to check your configurations to find out why it's not working.> In this state, entering http://localhost:7000/radio.m3u lets me listen > to the audio in xmms. But i notice the mountpoint must be named > radio.mp3 for "*.pls" file to be used.It shouldn't need to be. Anyway, all this is a bit academic. You want Shoutcast to be able to relay your stream. Simply aliasing "/" to whatever your active mount point is should do the trick. Geoff.
figured it out! I have a dynamically allocated IP address - and i was entering a dynamic DNS name in the shoutcast server config expecting it to be resolved. It wasn't. I entered the IP address just then and it relays perfectly! Will follow up with the shoutcast service support to see why my dynamic name isn't being resolved (perhaps it can't be with shoutcast?). re. 44.1 and stereo/mono: As well as doing streaming, my system will be providing local playback at full bandwidth (ie. it's going to be play 44.1 material for listeners at an actual installation). My software can support downsampling, enabling support for a number of sampling rates - but it's a nasty sounding algorithm so i'll leave it at 44.1. The shoutcast service (audiorealm.com) is fixed in stereo unfortunately. Thanks for your help. iain On Sun, 2005-06-05 at 10:40 +1000, Geoff Shang wrote:> Hi, > > Works fine for me, both using /radio and just / > > So to get the shoutcast server to relay it, just set it to relay > http://beijing.zhongshuo.org:7000 and that should work fine. > > BTW: There's no way you're going to get 44.1kHz stereo sound out of a > 32kbps MP3 stream. So unless you're using MP3Pro or something, you may as > well drop the sample rate and since it's being roled off anyway, you might > get better quality for your buck. > > Geoff. > >
On Sun, 5 Jun 2005, Iain Mott wrote:> figured it out! I have a dynamically allocated IP address - and i was > entering a dynamic DNS name in the shoutcast server config expecting it > to be resolved. It wasn't. I entered the IP address just then and it > relays perfectly! Will follow up with the shoutcast service support to > see why my dynamic name isn't being resolved (perhaps it can't be with > shoutcast?).DNS means "Domain Name Service". In order to serve ANYTHING on the Internet, you have to have a reliable -- i.e., STATIC -- IP address, mapped forward and reverse, name to IP address and vice versa. What you are describing for your connection is DHCP -- where you are the client of your upstream -- and you cannot serve anything for more than the time of your current connection, meaning your "service", whatever it is, is at best transient. Robert Muchnick Xenterra.net 720-276-7917