Issue metadata
Sign in to add a comment
|
WebRTC MediaRecorder video only issue
Reported by
cmugu...@gmail.com,
Mar 14 2017
|
||||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36
Steps to reproduce the problem:
1. Initialize a simple peer to peer webrtc video only session using getUserMedia({video: true, audio: false}, ...)
2. Initialize a MediaRecorder to record the remote stream ( recorder = new MediaRecorder(pc.getRemoteStreams()[0], {mimeType: 'video/webm;codecs=vp8'}) ). The issue is still present when vp9 is used.
3. Start recording session.
4. After recording ends the resulted webm file cannot be played properly. Only 2 video frames are played. Below you can informations taken from chrome://media-internals for the played video stream:
render_id: 84
player_id: 0
pipeline_state: kPlaying
event: PAUSE
url: file:///Users/mugurel/mediarecorder/video%20(1).webm
total_bytes: 4586259
streaming: false
single_origin: true
passed_cors_access_check: false
range_header_supported: true
info: FFmpegDemuxer: created video stream, config codec: vp8 format: 2 profile: vp8 coded size: [640,480] visible rect: [0,0,640,480] natural size: [640,480] has extra data? false encrypted? false
duration: 0.033
bitrate: 0
found_audio_stream: false
found_video_stream: true
height: 480
max_duration: kInfiniteDuration
start_time: 0
time_base: 1/1000
video_codec_name: vp8
video_format: PIXEL_FORMAT_YV12
video_is_encrypted: false
width: 640
video_dds: false
video_decoder: FFmpegVideoDecoder
video_buffering_state: BUFFERING_HAVE_ENOUGH
pipeline_buffering_state: BUFFERING_HAVE_ENOUGH
What is the expected behavior?
A recorded video only webrtc remote stream should be played properly(all video frames rendered, no audio).
What went wrong?
There is an attached webm file that shows the issue.
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 57.0.2987.98 Channel: stable
OS Version: OS X 10.12.3
Flash Version:
This issue is reproducible also on Windows. In is not a MacOS specific issue. Video only recording for local webrtc streams is working fine.
,
Mar 15 2017
,
Mar 16 2017
,
Mar 18 2017
cmugurel@ would you have a codepen/jsbin or similar to repro the issue? Also, can you try with the latest Canary? Thanks
,
Mar 18 2017
Marking Win as well.
,
Mar 20 2017
cmugurel@: Could you please update the thread according to comment #4 & 5.
,
Mar 20 2017
The issue is still reproducible in Canary Version 59.0.3046.0 canary (64-bit) for both Mac OS and Windows. I have uploaded a changed serverless-webrtc(https://github.com/cjb/serverless-webrtc) that could be used to reproduce the issue.
,
Mar 20 2017
Thank you for providing more feedback. Adding requester "mcasas@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 27 2017
mcasas@: Could you please take a look into it and update the issue. Let us know if it can be triaged from TE end, if so please help with the steps as was unable to proceed with the given info.
,
Mar 27 2017
I cloned the project in #c7, launched the python server: python -m SimpleHTTPServer 8001 . navigated to it using a Chromium build, then cross copy-pasted the SDPs offered, and I can see the local and remote feeds (which are actually the same) and send messages across peers, but I cannot see the described issue. Searching for 'mediarecorder' on that repo doesn't return any results [1]. Can you help reproduce, cmugurel@ ? [1] https://github.com/cjb/serverless-webrtc/search?utf8=%E2%9C%93&q=MediaRecorder&type=
,
Mar 28 2017
You need to use the serverless-webrtc-master.zip I have uploaded in comment 7 that contains changes to reproduce the recording issue.
,
Mar 28 2017
Thank you for providing more feedback. Adding requester "durga.behera@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 29 2017
Tried with the zip file in #7, which I decompressed in a folder, then ran python -m SimpleHTTPServer 8001 . from that folder, then I used a Chromium ToT build: ./out/gn/Chromium.app/Contents/MacOS/Chromium \ --enable-blink-features=ImageCapture --allow-file-access-from-files --use-fake-device-for-media-stream --use-fake-ui-for-media-stream \ http://localhost:8001/serverless-webrtc.html http://localhost:8001/serverless-webrtc.html and opened two windows, to the html file. On the first one I clicked "create" but no SDP offer line came up (see attached screen shot). Please instruct, or upload to some place where I could repro easily...?
,
Mar 30 2017
You should wait a bit for the local offer to be generated because the local SDP contains also the ICE candidate list. How long did you wait after you pressed "Create" button?
,
Mar 30 2017
Thank you for providing more feedback. Adding requester "mcasas@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 30 2017
The local SDP will not show also if you don't have a camera connected to your computer.
,
Mar 30 2017
Ok, waiting for ~30s gives a SDP, but still I haven't managed to make it record anything because the remote peer freezes. This happens with both the MBP camera and with --use-fake-device-for-media-stream (which is treated as a normal WebCam). Attached is the log. Could you please try to make a tiny reproduction case, e.g. iterating from https://codepen.io/miguelao/pen/RRXPEv ?
,
Mar 31 2017
Remote peer should not freeze unless there is another Chrome bug. Can you try to reproduce the bug first by using an official Chrome release or at least a Canary version? It seems that the Chrome browser you are using to reproduce the bug is not able to create the MediaRecorder object.
,
Jun 20 2017
,
Aug 31 2017
I can reproduce this issue very easy. I also submitted new issue - ( Issue 760760 )
,
Jan 22 2018
Mac triage: marking as duplicate of the newer & more detailed issue 760760 . |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Mar 15 2017