Post by ryan on Aug 14, 2006 1:11:56 GMT -5
Okay, here's a call to round-up ideas for how to continue Rose Rock Radio, our group's foray into webcasting. This weekend, I've been investigating our options to continue broadcasting. I haven't reached any definite conclusions yet, but I figured I'd share my thoughts and observations.
First off, we've all discussed Jeff's method of broadcasting, and while it certainly works (and inspired this venture), we've already established that it's not ideal. Jeff's method, as you probably recall, involved using an application called ShoutCast to stream audio off his PC through WinAmp and out over the Internet.
In this situation, all the programs responsible for streaming the audio are actually running on the broadcaster's PC at his or her house. This could be seen as an advantage, as it gives you total control over your broadcast -- but in reality, it's more of a disadvantage, because it means that your broadcast-bandwith will be limited to the bandwith of your residential ISP connection -- and even under the most ideal conditions, this probably means that only 5 to 10 listeners could connect to your audio-stream at any given time. In addition, it requires the broadcaster's computer to be powered-on, connected to the internet, and running WinAmp and the ShoutCast Server application anytime the station is to be broadcasting. Not to mention the security risks involved, this setup is terribly inconvenient for the broadcaster and, ultimately, for listeners who would doubtlessly prefer to tune-in at their own convenience.
I suggested that we try running ShoutCast off a webhosting space, thinking that this might resolve all the above problems. Well, I was ignorant about how the process actually works. It seems that, no matter how or where it's configured, the ShoutCast Server application must obtain its source material from a running copy of WinAmp, which must itself be configured with a special plugin which connects it to the "input" side of the ShoutCast Server. In a nutshell, this means that, even if we did get ShoutCast Server installed on a webhosting space, one of us would still have to assume the broadcasting duties, and dedicate our PC to running a WinAmp playlist while the station is airing. While this might resolve our bandwith issue (allowing for more users to connect, since the Server application is on a "real" webhosting space), it would still be inconvenient for us, the broadcasters.
Here's what I would like: I would like the station to be run entirely off of a server. I don't think it makes sense for any of us to have to run anything on our home PC's in order to broadcast. The broadcast should happen automatically, 24 hours a day. Any of us who wish to edit the station's playlist should be able to do so easily, using an FTP client to connect to the webhost to upload or delete song-files -- or using a simple back-end interface similar to those used by WordPress and CPanel. We should furthermore be able to construct a simple website containing a link to the audio feed; users click on the link, it launches in their default audio-player (windows media player or quicktime; winamp or realplayer support is secondary to me), and they hear the station. The feed should supply the name of each artist and song, and the feed should continue until the user closes the window in which it is playing.
So, with the scope of our group-knowledge, is there any way you guys can conceive of doing this?
I'm still researching the matter, but here's what I've discovered so far:
* The proper term for what we want to do is "Webcasting." "Internet Radio" is a less proper term, also used to mean the same thing. A Google search involving either of these terms reveals a myriad of resources. Also try "How to Stream Audio."
* There's always the "Live365" option, which we discussed a few months back. I don't mind going that way, but I'd prefer to have our audio streaming off our own webhosting space; that way, we can design a website around it if we want. If we have our station hosted by Live365, we have to send people to the Live365 website to find us. Live365 does have their "pro" accounts, which allow you to put your branding on their player and which give your station a customizeable URL -- but these accounts are expensive; they start at $75/month, which is frankly ridiculous for us.
* I'd prefer to have our radio station hosted on my friend Wassim's webserver. He runs a small webhosting business. I've used his webhosting service for years. His service is cheap, he offers top-of-the-line features -- and because he's a friend of mine, he's willing to do things for me that other webhosts would not, such as install certain server-side scripts at my request. His website is www.kmethosting.com.
* Check out this website: mp3soundstream.com. Watch the tutorials available there, and you'll see how this software works. It basically automates the process of creating a flash-movie containing an MP3 file and "player" controls. This is really cool. It doesn't exactly provide the webcasting solution I'm hoping for, but it got me to thinking outside the box.
First off, we've all discussed Jeff's method of broadcasting, and while it certainly works (and inspired this venture), we've already established that it's not ideal. Jeff's method, as you probably recall, involved using an application called ShoutCast to stream audio off his PC through WinAmp and out over the Internet.
In this situation, all the programs responsible for streaming the audio are actually running on the broadcaster's PC at his or her house. This could be seen as an advantage, as it gives you total control over your broadcast -- but in reality, it's more of a disadvantage, because it means that your broadcast-bandwith will be limited to the bandwith of your residential ISP connection -- and even under the most ideal conditions, this probably means that only 5 to 10 listeners could connect to your audio-stream at any given time. In addition, it requires the broadcaster's computer to be powered-on, connected to the internet, and running WinAmp and the ShoutCast Server application anytime the station is to be broadcasting. Not to mention the security risks involved, this setup is terribly inconvenient for the broadcaster and, ultimately, for listeners who would doubtlessly prefer to tune-in at their own convenience.
I suggested that we try running ShoutCast off a webhosting space, thinking that this might resolve all the above problems. Well, I was ignorant about how the process actually works. It seems that, no matter how or where it's configured, the ShoutCast Server application must obtain its source material from a running copy of WinAmp, which must itself be configured with a special plugin which connects it to the "input" side of the ShoutCast Server. In a nutshell, this means that, even if we did get ShoutCast Server installed on a webhosting space, one of us would still have to assume the broadcasting duties, and dedicate our PC to running a WinAmp playlist while the station is airing. While this might resolve our bandwith issue (allowing for more users to connect, since the Server application is on a "real" webhosting space), it would still be inconvenient for us, the broadcasters.
Here's what I would like: I would like the station to be run entirely off of a server. I don't think it makes sense for any of us to have to run anything on our home PC's in order to broadcast. The broadcast should happen automatically, 24 hours a day. Any of us who wish to edit the station's playlist should be able to do so easily, using an FTP client to connect to the webhost to upload or delete song-files -- or using a simple back-end interface similar to those used by WordPress and CPanel. We should furthermore be able to construct a simple website containing a link to the audio feed; users click on the link, it launches in their default audio-player (windows media player or quicktime; winamp or realplayer support is secondary to me), and they hear the station. The feed should supply the name of each artist and song, and the feed should continue until the user closes the window in which it is playing.
So, with the scope of our group-knowledge, is there any way you guys can conceive of doing this?
I'm still researching the matter, but here's what I've discovered so far:
* The proper term for what we want to do is "Webcasting." "Internet Radio" is a less proper term, also used to mean the same thing. A Google search involving either of these terms reveals a myriad of resources. Also try "How to Stream Audio."
* There's always the "Live365" option, which we discussed a few months back. I don't mind going that way, but I'd prefer to have our audio streaming off our own webhosting space; that way, we can design a website around it if we want. If we have our station hosted by Live365, we have to send people to the Live365 website to find us. Live365 does have their "pro" accounts, which allow you to put your branding on their player and which give your station a customizeable URL -- but these accounts are expensive; they start at $75/month, which is frankly ridiculous for us.
* I'd prefer to have our radio station hosted on my friend Wassim's webserver. He runs a small webhosting business. I've used his webhosting service for years. His service is cheap, he offers top-of-the-line features -- and because he's a friend of mine, he's willing to do things for me that other webhosts would not, such as install certain server-side scripts at my request. His website is www.kmethosting.com.
* Check out this website: mp3soundstream.com. Watch the tutorials available there, and you'll see how this software works. It basically automates the process of creating a flash-movie containing an MP3 file and "player" controls. This is really cool. It doesn't exactly provide the webcasting solution I'm hoping for, but it got me to thinking outside the box.