Running Zoom video conferencing client on the Pi

[Botspot]

I came across a very interesting quote from a RPI engineer today: (emphasis added)

Work with the major suppliers of video conferencing (Zoom, Google, MS and any others) commonly be used by schools to get such software working well on at least the Pi4B. Even if only with an RPT-produced camera as the only choice, and allowing for a USB to headphone/mic adapter. I say this in light of the school closures and "distance learning" of the last 3 months and the likelihood of more of the same later this year.

Already happening. I've been working with the Foundation over the last couple of months to test various webcams and headsets for the three conferencing solutions you mention above. Meet and Zoom work out of the box with our current Chromium version; Teams requires a custom user agent setting to work, but does so when you make the relevant setting.

Which, for reference, is '--user-agent="Mozilla/5.0 (X11; CrOS x86_64 12871.34.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.42 Safari/537.36"' - add that to the Chromium command line to get Teams to work.

So it looks like the Foundation has seen these threads and has gotten to work.

[Botspot]

Haven't tried it yet, but does everyone remember Chromebook OS that can run on RPi? (FydeOS)
I opened an issue there 3 months ago requesting that NaCl be added. (since the root problem preventing zoom from working on RPi was because the stock Chromium didn't ship with NaCl.)
And they did it!
For more info see viewtopic.php?f=56&t=281729

[zooropean]

So I tried the updated FydeOS.

Yes the Chrome web app now works-but I couldn't get audio. Video still somewhat laggy but it's had to really evaluate it without audio.

But I admit FydeOS is not something I want to run since it seems "buggy" on my RPI4.

Would rather see RasPIOS get a native Zoom app or at least NaCl for Chromium.

[Botspot]

So I tried the updated FydeOS.

So did I this morning. I'll compare my findings to yours.

Yes the Chrome web app now works-but I couldn't get audio. Video still somewhat laggy but it's had to really evaluate it without audio.

I got audio just fine. In the menu thing on the right side, there's a setting for different audio outputs.

But I admit FydeOS is not something I want to run since it seems "buggy" on my RPI4.

I noticed the same thing... Pages flickered, the screen often blacked out for no apparent reason, and all animations were "scrambled". I've been keeping up with FydeOS for a while, and this is a new phenomenon AFAIK. Hopefully the graphics will be improved like they used to be.

Would rather see RasPIOS get a native Zoom app or at least NaCl for Chromium.

Me too. But hey, the Zoom Chrome App works in FydeOS, and that's certainly better than nothing. Now Pi users have 2 options instead of one:

• Join the meeting on the website.
• Join the meeting in the Chrome App on FydeOS.

Neither option is optimal, but now at least users can get "gallery view" like they requested.

[fruitoftheloom]

So I tried the updated FydeOS.

Yes the Chrome web app now works-but I couldn't get audio. Video still somewhat laggy but it's had to really evaluate it without audio.

But I admit FydeOS is not something I want to run since it seems "buggy" on my RPI4.

Would rather see RasPIOS get a native Zoom app or at least NaCl for Chromium.

Native Client (NaCl) in Chromium Operating System will be obsoleted in time, so it is a short term workaround:

https://developer.chrome.com/native-client


FydeOS is not yet ready for Prime Time, LineageOS (Android) may be a better solution ???

[joser369]

greetings everyone, I have tried this way, install the client, but it does not run, someone saw it or can try?
http://eng-tawfik.blogspot.com/2019/08/ ... iewer.html

thanks

[Botspot]

greetings everyone, I have tried this way, install the client, but it does not run, someone saw it or can try?
http://eng-tawfik.blogspot.com/2019/08/ ... iewer.html

thanks

It appears that tutorial is emulating a x86 CPU on the ARM RPi. In general, performance is terrible doing this. Let me repeat that: emulating a non-native CPU architecture is extremely slow! I tried running Windows Notepad using chroot and qemu once - it was around 10 fps. And that was just a text editor.

But looking closer, the tutorial doesn't emulate a whole x86 Linux OS like I've seen before, but instead adds x86 architecture to apt and sources.list.
This is a different approach than I've seen before, and it looks promising.
Still, I am far from convinced that QEMU could translate commands fast enough to handle 2+ video streams at once.

[joser369]

I use zoom through the browser, but the audio on the other side is not heard, but if I put youtube if there is sound, thanks for the help

[joser369]

hello
my web cam is usb , i installed fswebcam
but not funcional , only frozen image

thaks

[StephenMorton]

I have had zoom working on a Pi for a few seconds before it went to 100% of CPU used. This was using a cheap generic USB Webcam with a microphone.

Pi Hut are selling a Zoom solution. I wonder, has anybody tried it:

https://thepihut.com/products/1080p-ful ... microphone

Best wishes, Stephen.

[ptitSeb]

It's now possible to run Zoom x86 linux client using Box86 https://github.com/ptitSeb/box86

You can find a video here: https://www.youtube.com/watch?v=9yx3XzYnHV4

[valentim]

Yet one more good reason for people to give Twister OS a try. You get Box86 and PiKiss by default and the ability to run a lot of stuff originally made both for Linux and Windows x86 architecture (not just games).

Enabling HD quality lags the stream a bit (expected considering the Pi hardware limits) but it is otherwise working fine.

Thanks a bunch.

[ProfessorM]

How to run zoom video conferencing client on th Pi?

The only way at the moment is to use the Chromium browser (https://zoom.us/):
1. Select "Join a Meeting"
2. Enter the Meeting ID, click "Join".
3. *Cancel* the pop-up, "Open xdg-open?", scroll down, and click "Join From Your Browser".
4. Enter you name, and click "Join".

Camera: USB webcam, like a logitech C500, or the standard Pi cam board.
Mic: On the webcam, or a separate USB mic.

My camera worked ok, but the mic was blocked. The Zoom audio said "your browser is blocking access" (but it wasn't). To fix the Mic, edit the default config in "/home/pi/.asoundrc", as per instructions https://iotbytes.wordpress.com/connect- ... pberry-pi/

BTW, the chrome app extension (zoom, or zoom scheduler) doesn't work. It will install, but you'll get an infinite spinning wheel when you try to join a call. And, there's no Zoom Linux client for RaspberryPi, due to Pi's ARM CPU, and all the Zoom Linux clients are compiled for x86 CPUs.

[Botspot]

Maybe you should do more research before making statements like this, ProfessorM.

The only way at the moment is to use the Chromium browser (https://zoom.us/):

Wrong. In fact, there are 4 ways: in-browser, the chrome app, android app, and x86 linux app. I have tried them all out, and they all work to various degrees, with the x86 Linux app by far the best.

BTW, the chrome app extension (zoom, or zoom scheduler) doesn't work. It will install, but you'll get an infinite spinning wheel when you try to join a call.

Wrong again. The Chrome Zoom app doesn't work on Raspbian's Chromium, but there is a way around it with Chromebook OS on the Pi.

And, there's no Zoom Linux client for RaspberryPi, due to Pi's ARM CPU, and all the Zoom Linux clients are compiled for x86 CPUs.

Actually there is a x86 Linux Zoom app, running on hundreds or Raspberry Pies right now, and that number is increasing by the minute. It's called emulation. Go see viewtopic.php?f=63&t=287680

[Xolarwind]

It's now possible to run Zoom x86 linux client using Box86 https://github.com/ptitSeb/box86

You can find a video here: https://www.youtube.com/watch?v=9yx3XzYnHV4

Hello ptitSeb, recently Botspot solved a problem with pulseaudio utils and usb headset sound card (originated by spanish locale setting of raspbian) on zoom client installation using box86 (installed via pi Apps). Now pi Apps was updated and works perfect. Zoom client using box86 installed fine, and audio works really well, but video is not working on zoom client, using original rpi camera module v2 conected to CSI port or rpi4 4b 4gb board. It could be a problem with box86 ?. Could you please help me? . I am teaching in argentina using zoom with rpi 4 and this could be really helpfull (most of my students use rpi4b 4gb with pi camera module v2) . In zoom web with chromium, rpi camera v2 module works fine, but with the laggy and freezing video problems reported by everyone due to zoom not designed for ARM v8 architecture (also seen with usb web cameras). Apparently zoom client over box86 does not have that problem and works ok for usb web cameras with box86 (finally easy to install thanks to Botspot development, pi Apps). But sadly, is not working with v2 original rpi camera module. We are using that camera module, because its the cheapest camera, an excelent solution in our country, good integration with rpi (not using another usb port and preventing low voltage problems in 1750 ghz overclocked rpi 4), because usb web cameras compatible with videoconferencing are really expensive here (more cost than a rpi 4b 4gb and monitor alltogether), and cheap ones are now difficult to find due to pandemia lockdown, so it is for now the only solution. We are forced to zoom because local schools are switching to zoom platform, but we previously use google meet without problems with raspbian buster and Rpi4 and v2 camera module. If you could find a solution to make camera v2 module working with zoom client and box86 it would be great and really apreciated. If we could help you in any form, trying solutions (we are not software engineers, only rpi4b enthusiasts!) count on us. I will bring you some hints that could help you (i hope), if you are interested in this solution, in the next post. Thank you very much in advance.

[Botspot]

Xolarwind, just wanted to let you know that replying to someone unfortunately does not tag them and so they are still not likely to see your post.
I suggest you get in contact with ptitseb via Github on the Zoom-box86 issue.

[Xolarwind]

Ok. I didnt know, thank you !!!

[ge_ko]

The rpi camera (the HQ model) worked for me with v4l2loopback. Installing the v4l2loopback gives me an additional camera device in the zoom client named "Dummy video device (0x0000)". Then I started ffmpeg to copy the video stream from /dev/video0 (the real camera device) to /dev/video1 (the v4l2loopback device) with

Code: Select all

ffmpeg -hide_banner -f v4l2 -i /dev/video0  -f v4l2 /dev/video1

Input #0, video4linux2,v4l2, from '/dev/video0':
  Duration: N/A, start: 3826.775702, bitrate: 283115 kb/s
    Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 1024x768, 283115 kb/s, 30 fps, 30 tbr, 1000k tbn, 1000k tbc
Stream mapping:
  Stream #0:0 -> #0:0 (rawvideo (native) -> rawvideo (native))
Press [q] to stop, [?] for help
Output #0, video4linux2,v4l2, to '/dev/video1':
  Metadata:
    encoder         : Lavf58.20.100
    Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 1024x768, q=2-31, 283115 kb/s, 30 fps, 30 tbn, 30 tbc
    Metadata:
      encoder         : Lavc58.35.100 rawvideo
frame=51572 fps= 30 q=-0.0 Lsize=N/A time=00:28:39.06 bitrate=N/A dup=46965 drop=0 speed=   1x 

unfortunately there is a big latency (about 500ms) and a very low framerate (about 3/s) in the video. But this seems not related to the zoom client, I see the same behaviour when I open the /dev/video1 device in VLC.

[ge_ko]

Update:

changing the v4l2 config with

Code: Select all

v4l2-ctl --set-fmt-video=width=1280,height=720,pixelformat=H264

results in a smooth video with low latency.

[Botspot]

Update:

changing the v4l2 config with

Code: Select all

v4l2-ctl --set-fmt-video=width=1280,height=720,pixelformat=H264

results in a smooth video with low latency.

Whoa nice!
BTW I'm monitoring your posts and posting them in the box86 zoom thread.

[itainelken]

Update:

changing the v4l2 config with

Code: Select all

v4l2-ctl --set-fmt-video=width=1280,height=720,pixelformat=H264

results in a smooth video with low latency.

this doesn't work for me, I know the camera works because I tested it with

Code: Select all

raspistill -o test.jpg

.

when I run the command, nothing happens, and zoom doesn't see anything.