No subject

involved. This is easy enough to verify, dump to a file as described on
that page and feed the resulting file to 'ogginfo'.

If it is indeed properly muxed into an Ogg container, then just
forwarding it via HTTP PUT instead of writing it to a file should do the
job.

I'd suggest someone just tries it. If you need a Icecast server to test
against I can also provide that. Ping me on IRC or send me a private email.

> In the other, I assume, like Jamie, that there is a way to send it
> over a PUT request. Isnt it ?

other? huh?


Cheers

Thomas

>     Hi Jamie,
>
>     The webRTC API does not sound suitable for source->server streaming
>     for many reason. For instance, the peer-to-peer connection requires
>     input from both end and seems quite unfeasible to implement in a
>     server. Likewise, codecs are completely abstracted and much more.
>
>     In reality, webRTC is an API to acheive full-duplex conversations a-la
>     skype and not for streaming.
>
>     For these reasons, we at liquidsoap have been working on implementing
>     a simple websocket protocol for sending source streams from a browser
>     to a server. The protocol is documented and implemented there:
>       https://github.com/savonet/webcast
>
>     We also have a pull request on liquidsoap that implements the protocol
>     and should be merged fairly soon:
>       https://github.com/savonet/liquidsoap/pull/90
>
>     The bottlenecks right now are the availability of the Web Audio API,
>     which is only partially implemented in firefox and the encoding speed.
>
>     Because there is no native encoding API for browser-side javascript,
>     we have (temporarily?) resorted to using javascript-compiled libraries
>     for mp3 encoding. However, only firefox seems to show suitable
>     performances for mp3 encoding, using the libshine build and thanks to
>     its asm.js support.
>       https://github.com/savonet/shine/tree/master/js
>
>     On the other hand, only chrome implements the adequate Web Audio API,
>     but is too slow to encode :-o
>
>     All in all, if we keep forging, it is very likely that once mozilla
>     finishes implementing the web audio API, we should have a function
>     browser source client using firefox. And Chrome when their asm.js
>     perfs improve as well.
>
>     Romain
>     2013/7/23 Jamie McClelland <jm at mayfirst.org <http://lists.xiph.org/mailman/listinfo/icecast-dev>>:
>     >/ I'm following up on a thread started by Stephen a couple months ago about
>     />/ building a JavaScript source client using webrtc.
>     />/
>     />/ The first step suggested was to figure out how to mux the audio and video.
>     />/ After I posted a feature request on the webrtc experiment js library, we
>     />/ seem to have a solution:
>     />/ https://github.com/muaz-khan/WebRTC-Experiment/issues/28#issuecomment-20791759
>     />/
>     />/ Based on the last comment on the icecast Dec list, we now only need to do do
>     />/ an HTTP put request to the icecast server (
>     />/ http://lists.xiph.org/pipermail/icecast-dev/2013-May/002171.html).
>     />/
>     />/ Great! I've got my jquery ready, but am having trouble finding docs on how
>     />/ to build the put request. I tried looking at the libshout source, but my c
>     />/ skills aren't quite good enough to figure it out.
>     />/
>     />/ Any help would be appreciated, particularly with an example.
>     />/
>     />/ Thanks for all your work on icecast - we use it a lot here at May
>     />/ First/People Link.
>     />/
>     />/ Jamie
>     />/
>     />/ _______________________________________________
>     />/ Icecast-dev mailing list
>     />/ Icecast-dev at xiph.org <http://lists.xiph.org/mailman/listinfo/icecast-dev>
>     />/ http://lists.xiph.org/mailman/listinfo/icecast-dev
>     />
>
>