I have a capture card bringing live and recorded video in from a dslr.  I can select it for both audio and video, and the video comes in just fine.  But no audio comes through.  
1st, am I missing anything beyond selecting that capture card as the audio input? And 2nd, the compatible campfire cards that zoom recommends for Mac were all quite expensive ($400-some). Has anyone had luck with a less expensive kind. For both audio and video?

Has anyone encountered this problem?

Recently, as a Meeting Host,  I have been unable to share and 'play' a video (like a YouTube or Vimeo video) during a Zoom meeting. I can cue it up before I start the meeting and start the video with no problem. But as soon as I start my meeting, when I share and try to play - it won't play.

Here are add'l datapoints:

• When sharing - I check both "Share sound" and " Optimize for video clip"
• I'm using a Windows PC (Windows 10 Enterprise)
• Running on Version 5.11.1
• Meetings have had less than 20 attendees
• Network Speedtest shows: 
  • download speed: 283 mbps
  • upload speed: 18 mbps
  • latency: 12 ms

I need help setting up a 24/7 Zoom meeting that's accessible by anyone with the link even if I'm not there hosting. Right now I have it set to a recurring meeting, but I don't really understand what that means. I can see that I'm able to log on and so are other users, but do I have to specify how long the meeting is recurring for? I'm also using the free account and underneath the meeting it says that my account can only support 40 minutes per meeting.

Does that mean the meeting will cut out at 40 minutes? It doesn't seem like any of the account options offer an indefinite meeting. I'm very lost and don't want to pay for a higher tier account I might not need just to get access to tech support.

Hi,

I have two different 2K mp4 videos made with my iPad. One doesn't work and I can't figure out why. Both files are about the same size at 25GB and a run time of 20min.  The one that doesn't work, I've shortened to a 5 min, 500MB video and it still doesn't work. I then shortened it to a 1 sec video and it *worked*.  A two min version doesn't work. 

What's happening here? I'd like the video loops to run 10-20 minutes.  I'd settle for 2-5 minutes. But this one video only works as a 1s video.  Has anyone seen this before?

Hello,
I'm trying to install the latest Zoom 5.14.7 (2928) from your Download Center webpage on my Ubuntu 20.04 but this build appears to be using a different public key than the one linked in that page:

https://us06web.zoom.us/client/latest/zoom_amd64.deb
https://us06web.zoom.us/linux/download/pubkey

$ gpg --import package-signing-key.pub  
gpg: keybox '/home/czarate3/.gnupg/pubring.kbx' created
gpg: /home/czarate3/.gnupg/trustdb.gpg: trustdb created
gpg: key B903BF1861A7C71D: public key "Zoom Video Communcations, Inc. Linux Package Signing Key ***********" imported
gpg: Total number processed: 1
gpg:               imported: 1

$ gpg --show-keys package-signing-key.pub
pub   rsa2048 2015-06-07 [SC]
     396060CADD8A75220BFCB369B903BF1861A7C71D
uid                      Zoom Video Communcations, Inc. Linux Package Signing Key ***********
sub   rsa2048 2015-06-07 [E]

$ gpg --verify zoom_amd64.deb
gpg: Signature made Fri 05 May 2023 12:41:04 AM CDT
gpg: using RSA key 59C86188E22ABB19BD5540477B04A1B8DD79B481
gpg: Can't check signature: No public key

$ dpkg-sig -verify zoom_amd64.deb
Processing zoom_amd64.deb...
UNKNOWNSIG _gpgbuilder DD79B481

 Please let me know whether this is just someone missing a new public key or whether that file has been tampered with. Thanks,

This is super frustrating.  After logging into the desktop app with Google, I click switch account.  It takes me to the login screen.  I want to switch to another google account so I click the Google icon, but it just takes me right back in with the currently authenticated Google account. There is no way to actually switch because I'm not seeing the typical intermediate screen that lists my google accounts to choose from to switch to!

I honestly don't know how in the hell this issue hasn't been an urgent usability issue that has been already resolved