getUserMedia和MediaRecorder-416请求的范围不满足 [英] getUserMedia and MediaRecorder - 416 Requested Range Not Satisfiable
问题描述
我有一个HTML5媒体记录器，允许用户在网络应用程序中实时记录自己，回放和上传记录.
它使用带有getUserMedia的标准代码来获取网络摄像头和麦克风的手柄，使用<video>回放网络摄像头，并使用MediaRecorder记录来自getUserMedia的流.
那么，问题来了...
在某些Macbook Air设备上，当尝试在<video>元素中播放记录的流时，Google Chrome抛出错误416(请求范围不满足).到目前为止，该问题似乎仅在带有Chrome的OSX上发生，但并非在所有具有这种组合的设备上都发生.
有一个Chromium错误已打开，它引用了此问题，但已标记为已修复". https://bugs.chromium.org/p/chromium/issues/detail?id = 615940 但是，我不相信会根据票证说明解决所有问题.我最近的评论者提到这也会影响Facebook Messenger！
您以前是否曾见过此问题，并且您知道不使用使用Windows 或使用Firefox的带有Chrome的OSX 用户的解决方法?
我对此进行了一点挖掘，发现Chromium的开发人员已经意识到了这个问题，并且他们确认这主要是在影响Mac OS用户.似乎目前尚无解决方法.
好消息是，他们将在2017年12月发布Chrome 63更新，该更新应该可以解决.
I have a HTML5 media recorder allowing users to record themselves live inside a web application, playback, and upload the recording.
It uses standard code with getUserMedia for getting a handle on the webcam and microphone, <video> to playback the webcam, and MediaRecorder to record the stream from getUserMedia.
So, to the problem...
On some Macbook Air devices, Google Chrome throws error 416 (Requested Range Not Satisfiable) when trying to playback the recorded stream in the <video> element. The issue seems so far to only occur on OSX with Chrome, but it's not occurring on all devices of that combination.
There's a Chromium bug open that references this issue but it is marked as 'Fixed'. https://bugs.chromium.org/p/chromium/issues/detail?id=615940 I'm not convinced however that the full problem is resolved based on the ticket commentary. I recent commenter mentioned this affects Facebook Messenger too!
Have you seen this issue before, and do you know of a workaround for OSX with Chrome users that doesn't involve use Windows or use Firefox?
I dug in this a little bit and found that the developers of Chromium are aware of the issue and they confirmed that it's mostly affecting Mac OS users. Seems like there is no workaround for it at the moment.
The good news is that they are shipping an update with Chrome 63, which is coming in December 2017, that should fix it.
MediaRecorder Gets into Bad State and Raises Empty Data Events
这篇关于getUserMedia和MediaRecorder-416请求的范围不满足的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
