Created attachment 724143 [details] Example User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.160 Safari/537.22 Steps to reproduce: I succesfully create a peer to peer video connection (one-way) between pc1 and pc2. And added the pc2 remoteStream to a video#vid2 element in the onaddstream callback. Then I use the pc2 remoteStream as argument for the addStream method on a third peer pc3 that is conencted to pc4. On the pc4 onaddstream callback I added the stream to video#vid3 element. All was done in one page, with the signaling made directly with the objects. Actual results: I have two different behaviours: 1) The video taken from the pc4 was extremely slow. Something like 1 frame/minute. 2) No video at all in the in the video#vid3 element Expected results: I hoped that the video was forward from pc1->pc2 and the from pc3->pc4 passing the stream received in pc2 to pc3.
Summary: Forward a remote stream works very slow → Forward a remote stream works very slow when it works
Taking until we know more, making blocking likewise. Reporter (if you didn't get this from tim already): logs with NSPR_LOG_MODULES=mediastreamgraph:5,mediapipeline:5,signaling:5 would help. Doesn't have to be long (logs from this can be large, you may need to compress before uploading)
Assignee: nobody → rjesup
Priority: -- → P2
Attachment #724143 - Attachment mime type: text/plain → text/html
Created attachment 724380 [details] NSPR Logs NSPR_LOG_MODULES=mediastreamgraph:5,mediapipeline:5,signaling:5
Comment on attachment 724143 [details] Example I will upload a new example, with some fixes
Attachment #724143 - Attachment is obsolete: true
Attachment #724382 - Attachment mime type: text/plain → text/html
Whiteboard: [WebRTC],[blocking-webrtc+] → [WebRTC],[blocking-webrtc-]
Status: NEW → RESOLVED
Last Resolved: 3 years ago
QA Contact: jsmith
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.