Meeting bad audio and bad video

Hi there,

The audio quality issue with the web sdk is also (after many tests with different hardware profiles) related to user’s CPU capacities.

To make it simple for people here that did not perform any performance tests, the web SDK is doing everything by CPU : tasks like audio processing & so on but also video encoding.
Video encoding will use at least 1 complete CPU, and from what i have monitored during tests with multiple hardware it can use much more depending on the situation and the hardware.

But i’m pretty sure that over the net, most of “basic” users (understand non IT people with monster machines) use to buy entry level computer with let say dual core cheap CPU.

With such low specs machines, just running an integrated application with zoom web SDK (with nothing else running on same machine) would use more or less 80% of the available CPU. This is just enough to have both audio & video working with sometime some impacts if something else is running on the same machine.

If you start to activate screen sharing (or just application/tab sharing as screen would be even worse), then it will start to consume more CPU for the video processing and since there is not much this would have a direct impact on audio processing on this host machine, thus drop audio quality delivered to all meeting participants.

So don’t forget about that too when you face such issue. There is not a single source for this kind of issue. Fixing web sdk library is one thing, running on too low specifications (unfortunately that’s a requirements for web sdk) is another one.

1 Like

Hey @aya,

The Web SDK release has been delayed:

Apologies for the inconvenience,
Tommy

Hey @nvivot,

Thanks for sharing this info with the community.

We are working to fix the CPU issue on Chrome, but it depends on a Chrome release. Stay tuned.

-Tommy

1 Like

@tommy looks like 1.7.9 is out for SDK. We are having an issue with the recaptcha feature. First we would just like to disable it. Barring that, we have allowed pop ups in our iframe so that this feature can work, but it is failing because it says our browser is in icognito mode when it is not.

EDIT: I posted in the 1.7.9 release thread. Can ignore this.

Hey @pat.ransdell,

I have added the link to your post so others can reference.

-Tommy

Audio Quality is still low, and CPU usage is still high, It could be argued that is a Browser limitation or because using low spec machines. but other web based conferences apps don’t have this issue.
Have been waiting more that 2 months for this fix. already lost clients because of this, and not getting an answer or a fix, none of the releases have notes on this.

I’m having the same problem and am getting a lot of complaints. I do regular webinars and online classes. When I meet with one or two people, the video and sound are mostly fine. When I do a webinar with 70+ people and we disable all video but my screensharing, audio is mostly fine. But when I have 100+ people all on video, the sound quality drops dramatically–lots of stuttering sounds and sometimes audio stops completely for 5 - 7 seconds. Sometimes video freezes.

This is a significant issue, so I’d also be grateful for a solution!

Hey @JuanLopez, @kathryngz,

We are in the process of fixing this issue. I will keep you updated.

What version of the Web SDK are you using?

Thanks,
Tommy

1 Like

Hi, just experienced the same issue in a test meeting. We’re using embedded Zoom Web SDK for an online conference, embedded the Zoom link and when the two of us testing joined, our audio was terrible and broken up and the video was completely out of sync. We disconnected from that and joined via the desktop Zoom app, and audio and video were both normal (also for the Zoom stream embedded in the browser), so it was to do with the AV input coming via Zoom Web SDK. The whole point of embedding Zoom in this fashion was to minimise the barrier for entry (e.g. no need for app) but this performance issue is a big problem. Are there any planned fixes for this?

Hey @rhobslein,

Yes, we are working on fixing this in a future release. I will keep you posted. (CS-2018)

Thanks,
Tommy

Hi, just confirming this issue from May is still happening.

Hey @sjp49659,

Thanks for letting us know you are seeing this issue. We are in the process of fixing it. :slight_smile:

-Tommy

1 Like

Any resolution here? Any ETA?

Hey @webdev,

We are prioritizing fixing this issue. I will let you know when we have an ETA.

Thanks,
Tommy

Ok. Do you have any visibility to when it occurs, what browsers, and any workarounds? Or half-measures? Thx.

I’m trying the Web SDK feature for the first time. I’m attending a conference being run on Whova using Zoom SDK. My laptop is not a basic/intro level one so should have plenty of CPU availability. I have absolutely no sound when viewing the SDK feed inside Whova on Chrome.

My workaround is to have the direct zoom meeting link running (with sound) in the background and the Whova open to view the video stream and have access to the whova Q&A and Chat features.

Hey @webdev,

We suggest using Chrome and having a strong internet connection.

Thanks,
Tommy

Hey @Enfys,

Thanks for sharing your work around. However the audio should work on chrome. Can you please provide more details like what version of the Web SDK you are using, and which version of Chrome?

Thanks,
Tommy

Hi Tommy,
I’m using “Version 85.0.4183.121 (Official Build) (64-bit)” of Google Chrome.

I was using the Whova Web App as an attendee at a conference. I’m afraid I don’t know what version of the Web SDK Whova are using.

The sound is now working when I play-back sessions that were recorded during the conference but during the live-stream of the lectures I had zero sound via the zoom Web SDK in the Whova Web App in Chrome. I adjusted / checked all the audio settings I could find, tried the laptop speakers, Bluetooth headphones and wired headphones as well as the good old turn it off and back on again trick.

Hey @Enfys,

Thanks for letting us know. We will continue to debug the issue. :slight_smile:

If you experience this issue again, I suggest to reach out to Whova so they are aware and can work with us to debug the issue.

-Tommy