Note that there are some explanatory texts on larger screens.

plurals
  1. POHTML5 live "real-time" streaming audio (not from a file)
    primarykey
    data
    text
    <p>I've written a network "audio server" that streams audio data in real-time from a software-defined radio receiver. Currently, the server acts as an RTSP server (as per <a href="http://www.ietf.org/rfc/rfc2326.txt" rel="nofollow">RFC2326</a>) and the data is streamed over RTP (as per <a href="http://www.ietf.org/rfc/rfc3550.txt" rel="nofollow">RFC3550</a>) when a client requests it via RTSP.</p> <p>Currently, this requires a native application to act as the RTP receiver (e.g. VLC, gstreamer, etc.). I'd like to be able to stream audio data to clients <em>without</em> requiring them to install a separate piece of software -- i.e. just load a webpage and the audio plays (maybe with a basic control UI displayed as well).</p> <p>I've been out of the web development game for a while, but recently I've seen a lot of chatter about the new "streaming" <code>&lt;audio&gt;</code> tag in HTML5. However, although it's called "streaming," it still seems to be file-oriented -- i.e. you have to have all the data on-hand a-priori. So my question is:</p> <p><strong>Is there a way to play "live" audio data (which is being generated in real-time) on a webpage using standard technologies/javascript libraries? Ideally, it would work on both desktop and "mobile" platforms.</strong></p> <p>It doesn't have to use the RTP transport under the hood -- I can rewrite or add new transports to the server if needed. The goal is to avoid having any "special" native software on the client -- just load the webpage and the audio plays.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload