I'm in a situation where I have some MP3 files I'd like to stream on- demand, but for various reasons can't just make the MP3 files themselves available. Is there a way, using icecast, to set up a server that would just bind to a port, and stream one file as specified in the config file, then stop? So somewhere in the icecast.xml, I'd like to say "File: /tmp/ myfile.mp3", and then just have the server start playing that. --Wade
H. Wade Minter schrieb:> I'm in a situation where I have some MP3 files I'd like to stream on- > demand, but for various reasons can't just make the MP3 files > themselves available. > > Is there a way, using icecast, to set up a server that would just bind > to a port, and stream one file as specified in the config file, then > stop? So somewhere in the icecast.xml, I'd like to say "File: /tmp/ > myfile.mp3", and then just have the server start playing that. >Icecast is not very good at on-demand streaming. It will serve files and apply some throttling to the throughput but it will be still more or less a ordinary download. When streaming mp3 you can't prevent a user dumping the stream and thus gaining the original file. The only thing you can do is to make it take longer by delivering it as a stream with a bitrate needed for real-time playback. Thomas
On Jun 4, 2008, at 5:25 AM, Thomas B. Ruecker wrote:> H. Wade Minter schrieb: >> I'm in a situation where I have some MP3 files I'd like to stream on- >> demand, but for various reasons can't just make the MP3 files >> themselves available. >> >> Is there a way, using icecast, to set up a server that would just >> bind >> to a port, and stream one file as specified in the config file, then >> stop? So somewhere in the icecast.xml, I'd like to say "File: /tmp/ >> myfile.mp3", and then just have the server start playing that. >> > Icecast is not very good at on-demand streaming. It will serve files > and > apply some throttling to the throughput but it will be still more or > less a ordinary download. > When streaming mp3 you can't prevent a user dumping the stream and > thus > gaining the original file. The only thing you can do is to make it > take > longer by delivering it as a stream with a bitrate needed for real- > time > playback.Sure, the user can always dump the stream to save the audio. Apparently having the streaming (vs. just providing an m3u with an MP3 URL) is sufficient for the people who make the rules, though. That's why I'd like to be able to just have a remote icecast server stream one file and then stop. --Wade
On Tue, Jun 03, 2008 at 08:45:21PM -0500, H. Wade Minter wrote:> I'm in a situation where I have some MP3 files I'd like to stream on- > demand, but for various reasons can't just make the MP3 files > themselves available. > > Is there a way, using icecast, to set up a server that would just bind > to a port, and stream one file as specified in the config file, then > stop? So somewhere in the icecast.xml, I'd like to say "File: /tmp/ > myfile.mp3", and then just have the server start playing that.This might work well... <mount> <mount-name>/stream.mp3</mount-name> <intro>/myfile.mp3</intro> <fallback-mount>/this_stream_has_finished.mp3</fallback-mount> <fallback-override>0</fallback-override> </mount> -- Paul Martin <pm at nowster.org.uk>