With the new RecordRTC system, Chrome is not allowing participants to play back their own video recordings.
Affected frames
video-config-qualityvideo-consent
Background and implementation info
This seems to be a Media Recording bug in Chrome where, after a recording is made with mime typevideo/webm, Chrome reports the file's mime type as "video/x-matroska;codecs=avc1,opus" (despite actually being webm) and therefore will not play it in the HTML5 video element (see this stackoverflow post).
The easiest solution is to playback the recording using the recorder's blob instead of data URI, since the former does not specify the mime type. (This issue might be resolved anyway when we change the RecordRTC mime type specification in order to fix problems with video recording playback across browsers, e.g. for researchers watching consent videos in different browsers. But I think it makes sense to stick with replaying the videos via blobs instead of data URIs, unless there are any unforeseen problems.)
Bug description
With the new RecordRTC system, Chrome is not allowing participants to play back their own video recordings.
Affected frames
video-config-qualityvideo-consentBackground and implementation info
This seems to be a Media Recording bug in Chrome where, after a recording is made with mime type
video/webm, Chrome reports the file's mime type as "video/x-matroska;codecs=avc1,opus" (despite actually being webm) and therefore will not play it in the HTML5videoelement (see this stackoverflow post).The easiest solution is to playback the recording using the recorder's blob instead of data URI, since the former does not specify the mime type. (This issue might be resolved anyway when we change the RecordRTC mime type specification in order to fix problems with video recording playback across browsers, e.g. for researchers watching consent videos in different browsers. But I think it makes sense to stick with replaying the videos via blobs instead of data URIs, unless there are any unforeseen problems.)