MediaRecorder: dataavailable event
MediaStream Recording
MediaStream Recording
The dataavailable event of the MediaRecorder interface is fired when the MediaRecorder delivers media
data to your application for its use. The data is provided in a Blob
object that contains the data. This occurs in four situations:
- When the media stream ends, any media data not already delivered to your
ondataavailablehandler is passed in a single Blob. - When MediaRecorder.stop() is called, all media data which has been
captured since recording began or the last time a
dataavailableevent occurred is delivered in a Blob; after this, capturing ends. - When MediaRecorder.requestData() is called, all media data which has
been captured since recording began or the last time a
dataavailableevent occurred is delivered; then a newBlobis created and media capture continues into that blob. - If a
timesliceproperty was passed into the MediaRecorder.start() method that started media capture, adataavailableevent is fired everytimeslicemilliseconds. That means that normally, each blob will have a specific time duration (except the last blob, which might be shorter, since it would be whatever is left over since the last event). So if the method call looked like this —recorder.start(1000);— thedataavailableevent would fire after each second of media capture, and our event handler would be called every second with a blob of media data that's one second long. You can usetimeslicealongside MediaRecorder.stop() and MediaRecorder.requestData() to produce multiple same-length blobs plus other shorter blobs as well.
[!NOTE] Like other time values in web APIs,
timesliceis not exact and the real intervals may be delayed due to other pending tasks, browser features (pausing the camera and microphone in Safari), browser-specific behaviors (locking the screen while recording on Chrome on Android pauses thedataavailableevent), or other browser bugs. Such scenarios can also lead to significantly larger chunks.Therefore, don't rely on
timesliceand the number of chunks received to calculate the time elapsed, because errors may accumulate. Instead, keep a separate timer using Event.timeStamp or similar, that records the total time elapsed since starting.
The Blob containing the media data is available in the dataavailable event's data property.
Syntax
Use the event name in addEventListener():
addEventListener("dataavailable", (event) => { })
Alternatively, assign to the event handler property of the interface:
ondataavailable = (event) => { }
Event type
A BlobEvent. Inherits from Event.
BlobEvent
Example
const chunks = [];
mediaRecorder.onstop = (e) => {
console.log("data available after MediaRecorder.stop() called.");
const audio = document.createElement("audio");
audio.controls = true;
const blob = new Blob(chunks, { type: mediaRecorder.mimeType });
const audioURL = window.URL.createObjectURL(blob);
audio.src = audioURL;
console.log("recorder stopped");
};
mediaRecorder.ondataavailable = (e) => {
chunks.push(e.data);
};
Specifications
Browser compatibility
See also
- Using the MediaStream Recording API
- Web Dictaphone: MediaRecorder + getUserMedia + Web Audio API visualization demo, by Chris Mills (source on GitHub.)
- simpl.info MediaStream Recording demo, by Sam Dutton.
- Navigator.getUserMedia()
- Dealing with huge MediaRecorder chunks on addpipe.com (2024)