--- a/media-stream-capture/MediaRecorder.html Tue Jul 23 18:40:39 2013 +1000
+++ b/media-stream-capture/MediaRecorder.html Thu Aug 08 14:41:34 2013 -0400
@@ -16,7 +16,7 @@
company: "Microsoft Corp.",
url: "mailto:travis.leithead@microsoft.com?subject=MediaStream Capture Scenarios Feedback",
companyURL: "http://www.microsoft.com"}],
- publishDate: "2013-06-12",
+ publishDate: "2013-08-09",
edDraftURI: "http://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-capture/RecordingProposal.html",
previousPublishDate: null,
prevED: "",
@@ -204,7 +204,7 @@
<li>When the <code>stream</code> is ended set <code>recording</code>
to 'false' and stop gathering data.</li>
<li>Then raise a <code>dataavailable</code> event containing the Blob of data.</li>
- <li>Finally, raise a <code>stoprecording</code> event.</li>
+ <li>Finally, raise a <code>stop</code> event.</li>
</ol>
<p>Note that <code>stop()</code>,
@@ -212,12 +212,15 @@
<p>The UA <em title="must" class="rfc2119">must</em> record the MediaStream
- in such a way that the original Tracks can be retrieved at playback time. If any Track within the
+ in such a way that the original Tracks can be retrieved at playback time. When multiple Blobs
+ are returned (because of <code>timeSlice</code> or <code>requestData</code>), the individual
+ Blobs need not be playable, but the combination of all the Blobs from a completed recording <em title="must" class="rfc2119">must</em>
+ be playable. If any Track within the
MediaStream is muted at any time (i.e., if its <code>readyState</code> is set to <code>muted</code>), the UA
<em title="must" class="rfc2119">must</em> insert black frames or silence until the Track is unmuted. If the UA is
unable to start recording or at any point is unable to contine recording, it <em title="must" class="rfc2119">must</em> raise
a <code>DOMError</code> event, followed by a <code>dataavailable</code> event containing
- the Blob it has gathered, follwed by the <code>stoprecording</code> event.
+ the Blob it has gathered, follwed by the <code>stop</code> event.
</p>
<dl class='parameters'>
<dt>optional long timeslice</dt>
@@ -237,7 +240,7 @@
Otherwise:</li>
<li>Set <code>state</code> to 'inactive' and stop gathering data. </li>
<li>Raise a <code>dataavailable</code> event containing the Blob of data that has been gathered.</li>
- <li>Raise a <code>done</code> event</li>
+ <li>Raise a <code>stop</code> event</li>
</ol>
</dd>
<dt>void pause()</dt>
@@ -277,7 +280,8 @@
raise a DOM
<code>InvalidState</code> error and terminate these steps.
Otherwise:</li>
- <li>Raise a <code>dataavailable</code> event containing the current Blob of saved data.</li>
+ <li>Raise a <code>dataavailable</code> event containing the current Blob of saved data. (Note that this Blob
+ will be empty if no data has been gathered yet.)</li>
<li>Create a new Blob and gather subsequent data into it.</li>
</ol>
</dd>
@@ -407,7 +411,7 @@
the <code>RecordingErrorName</code>
enums. If recording has been started and not yet stopped when the error occurs, then after raising the error, the UA <em title="must" class="rfc2119">must</em>
raise a dataavailable event, containing any data that it has gathered,
- and then a recordingdone event. The UA <em title="may" class="rfc2119">may</em> set platform-specific
+ and then a stop event. The UA <em title="may" class="rfc2119">may</em> set platform-specific
limits, such those for the minimum and maximum Blob size that it will support, or the number of
Tracks it will record at once. It <em title="must" class="rfc2119">must</em> signal a fatal
error if these limits are exceeded. If a non-fatal error occurs during recording, the UA
@@ -500,7 +504,7 @@
<tr>
<td><dfn id="event-mediarecorder-resume"><code>resume</code></dfn></td>
- <td><code>MediaSteamEvent</code></td>
+ <td><code>Event</code></td>
<td>The UA has resumed recording data on the MediaStream.</td>
</tr>