MediaRecorder: dataavailable event

فهرست فصل‌ها دانلود آرشیوناشر

MDN Web Docs · نسخهٔ df622a2a1c1e · CC BY-SA 2.5 و مجوز جداگانهٔ ناشر برای نمونه‌کد

{{APIRef("MediaStream Recording")}}

The **dataavailable** event of the {{domxref("MediaRecorder")}} interface is fired when the MediaRecorder delivers media data to your application for its use. The data is provided in a {{domxref("Blob")}} object that contains the data. This occurs in four situations:

  • When the media stream ends, any media data not already delivered to your

ondataavailable handler is passed in a single {{domxref("Blob")}}.

  • When {{domxref("MediaRecorder.stop()")}} is called, all media data which has been

captured since recording began or the last time a dataavailable event occurred is delivered in a {{domxref("Blob")}}; after this, capturing ends.

  • When {{domxref("MediaRecorder.requestData()")}} is called, all media data which has

been captured since recording began or the last time a dataavailable event occurred is delivered; then a new Blob is created and media capture continues into that blob.

  • If a timeslice property was passed into the

{{domxref("MediaRecorder.start()")}} method that started media capture, a dataavailable event is fired every timeslice milliseconds. 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); — the dataavailable event 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 use timeslice alongside {{domxref("MediaRecorder.stop()")}} and {{domxref("MediaRecorder.requestData()")}} to produce multiple same-length blobs plus other shorter blobs as well.

توجه: Like other time values in web APIs, timeslice is 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 the dataavailable event), or other browser bugs. Such scenarios can also lead to significantly larger chunks. Therefore, don't rely on timeslice and the number of chunks received to calculate the time elapsed, because errors may accumulate. Instead, keep a separate timer using {{domxref("Event.timeStamp")}} or similar, that records the total time elapsed since starting.

The {{domxref("Blob")}} containing the media data is available in the dataavailable event's data property.

Syntax

Use the event name in {{domxref("EventTarget/addEventListener", "addEventListener()")}}:

js-nolint
addEventListener("dataavailable", (event) => { })

Alternatively, assign to the event handler property of the interface:

js-nolint
ondataavailable = (event) => { }

Event type

A {{domxref("BlobEvent")}}. Inherits from {{domxref("Event")}}.

{{InheritanceDiagram("BlobEvent")}}

Example

js
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

{{Specifications}}

Browser compatibility

{{Compat}}

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.
  • {{domxref("Navigator.getUserMedia()")}}
  • Dealing with huge MediaRecorder chunks on addpipe.com (2024)