Jeremiah Stanley <miah@miah.org> writes:> It is my understanding that you have the highest bitrate stored and you > just want to re-encode the files on the fly over a stream. You do this > rather than just store all the different enc rates.Basically yes. The material I have available is currently over 30gb and growing. If I stored all the various combinations of bit rates the storage needed would go up significantly.> Correct my assumption, but can't ices create playlists from perl scripts?I'm not exactly sure what ices can and cannot do. I compiled it once and have updated cvs a couple of times and have not managed to compile it since. Now, I haven't spent a lot of time on it exactly either.> Couldn't you just set the playlist/connections to icecast up by using > custom mountpoints that are dynamically assigned to the user. I would do > this by having them login to the website and then 'their' stream is just a > md5 hash of their username. When the pick a file to stream their bitrate > is then sent to ices to stream to their 'mountpoint'. Looking similar to > this:I do something similar although easier. I use /mnt- and attach the pid of the running script to create the mount points. http://www.my.domain:8000/mnt-21453. I pass that into my streamer from the script and then make the return url have it as well.> I guess this is just a question of what limits what you can do with the > ices perl playlist generation. Is there any documentation on the subject?I will have to check. Probably there is in ices/doc. The icecast group tend to be very good at documentation. That raises another question though, what would ices do in the event of a listener disconnecting before the source finished streaming, Which is my main difficulty. Kirk -- Kirk Reiser The Computer Braille Facility e-mail: kirk@braille.uwo.ca University of Western Ontario phone: (519) 661-3061 --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> happily use it. My system works pretty well except for a number of > small issues I am still working on.It is my understanding that you have the highest bitrate stored and you just want to re-encode the files on the fly over a stream. You do this rather than just store all the different enc rates. Correct my assumption, but can't ices create playlists from perl scripts? Couldn't you just set the playlist/connections to icecast up by using custom mountpoints that are dynamically assigned to the user. I would do this by having them login to the website and then 'their' stream is just a md5 hash of their username. When the pick a file to stream their bitrate is then sent to ices to stream to their 'mountpoint'. Looking similar to this: http://mp3.yourdomain.com:8000/aWNlY2FzdHJvY2tz I guess this is just a question of what limits what you can do with the ices perl playlist generation. Is there any documentation on the subject? JStanley --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> > It is my understanding that you have the highest bitrate stored and you > > just want to re-encode the files on the fly over a stream. You do this > > rather than just store all the different enc rates. > > Basically yes. The material I have available is currently over 30gb > and growing. If I stored all the various combinations of bit rates > the storage needed would go up significantly.Not really. Maybe about 50% for all the extra bitrates. Depends on what your master bitrate is. Icecast is still not the right tool for the job here. You would just be building a lot of glue to make it do something it was just not meant to do. What you want is a perl script. http://www.server.com/music?file=blah.mp3&bitrate=24 which would set up a pipe with lame and send the reencoding file back to the client. You'll still need the m3u files, or at least an m3u generator: http://www.server.com/music?file=blah.mp3&bitrate=24&mode=m3u etc. You could even use apache rewrite rules to turn those into: http://www.server.com/music/24/blah.m3u etc. jack. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.