I've written up a nice streaming jukebox so I can listen to my mp3's and ogg's from anywhere with a net connection. I even got it set up so you can re-encode mp3's on the fly by calling lame and using stdout as the output. I've found a program ( http://www.inf.ufpr.br/~rja00/ogg.html ) called ogg2ogg which basically is oggenc combined with oggdec, allowing you to re-encode an ogg to a lower bitrate and send the output to stdout. However, it doesn't seem to work as well as its lame counterpart. (Winamp will connect and get an HTTP 200/OK response, then stop.) Given this vague description, does anyone see a problem with this scheme? Is it even possible to stream incomplete ogg files that are still in the process of being encoded? --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-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.
Chris Nuccitelli wrote:> mp3's on the fly by calling lame and using stdout as the output. I've found a > program ( http://www.inf.ufpr.br/~rja00/ogg.html ) called ogg2ogg which[snip]> Given this vague description, does anyone see a problem with this scheme? IsThere's nothing bad about that IMO, although it will become redundant with Ogg eventually, when bitrate peeling makes its way from the paper/code experiments to mainline CVS. Peeling will result in better quality than reencoding can ever achieve - at least theoretically. Btw, can't ices2 reencode already, too? <p>Moritz --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-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.