cindyb

lastly here is a very helpful error in the console.log: ``` {elapsedTime: 25613, group: 'media', level: 'warning', name: 'error', timestamp: 1660755568010, …} elapsedTime: 25613 group: "media" level: "warning" name: "error"...

we had to avoid publishing the track on Windows 10 Chrome in this way: ``` const aCanvasTrack = getLocalVideoTrackFromCanvas( participant.sid, canvasOverlayBuff ).then((track: LocalVideoTrack) => { if (supportsCPublishing) { // windows...

videoTracks @manjeshbhargav

to reproduce: go to https://bongo-upgrade-testing.herokuapp.com begin the session as Participant A in windows 10/chrome browser, and send yourself an email (gmail works best) at the PreJoinScreen/RoomName screen. Click Continue. Click...

hi @manjeshbhargav- I just removed all processor code (sorry, I thought I had) and pushed. The canvas track (there's only one canvas video track per participant btw) publishes also

hi @manjeshbhargav the changes that you requested are indeed there: a) "where you do not add any video processor to the local video track" - all the code for processor...

we more rarely get the Client error on mac (although it does happen). You need to try it on Windows 10 - it happens every time. We are publishing the...

@DenissSazanovs did you publish the canvas track as well? that's what repeatedly caused the error for me and for #1857 apparently

I am seeing this problem using React 15.4.1 on mac os in Chrome. Trying to solve for #181 does not work in my case

we have overridden Viewer `renderPage`, to do our own highlighting b/c we need to highlight multiple lines. We access the text layer's children and iterate to find a match. The...