Zoom RTMP as a Source?

I've read the official guide to bringing Zoom in to Wirecast Pro, but it seems a little nuts to use screen capture as a way to bring Zoom in as a source. Since Zoom supports RTMP streaming is there no simple, low-latency way to stream from Zoom into Wirecast? I don't mind using an intermediary service, although I'm guessing the best route would be to have Zoom locally on the box streaming into Wirecast.


Incidentally, the main reason we'd want to use this instead of Rendezvous is because manually switching between 4 people on a podcast / videocast is legitimately hard, whereas Zoom automatically switches to the current speaker.

18replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • If Zoom sends RTMP to a sever you can then take the RTMP or HTTP (HLS) output of that sever and input it using Wirecast Web Stream plugin. Keep in mind there will be significant latency if you are cutting between Zoom and something else in Wirecast.

    You can setup a local Wowza server or equivalent.

  • CraigS  thanks - that's exactly as I expected. I guess my real question is if there's an RTMP server I can run locally on the box (which is in a datacenter, so it has a public IP and opening a port on the firewall is trivial, but hopefully the Zoom client can also stream to something sitting on localhost) which then in turn can serve up an RTMP / HLS stream? Wowza looks awfully overbuilt and expensive for such a trivial task - is this something that Nimble could do? Alternatively is there something else you're aware of that is lightweight that would work?

  • I think I answered my own question, as this seems to be a scenario that Nimble caters to (unless I'm totally misunderstanding this documentation) - https://blog.wmspanel.com/2014/10/rtmp-republishing-nimble-streamer.html

  • Riccardo S Yes I was going to suggest NImble.

  • Riccardo S said:
    it seems a little nuts to use screen capture as a way to bring Zoom in as a source. Since Zoom supports RTMP streaming is there no simple, low-latency way to stream from Zoom into Wirecast?

    Hi Ricardo.

    I've wanted to get the same functionality happening before, for various inputs. This exists in the Telestream queue under WIRE-14424, but there was no enthusiastic response indicating this would be delivered any time soon.


  • Greg Kuhnert I figured I wasn’t alone in wanting this. We ended up using Nimble, which works, but it definitely seems like a good use-case. Alternatively (for our use-case) they need to get Rendezvous to a point where it can be “fire and forget” in the way Zoom is - if there’s a 4 way conversation going on it’s annoying to have to switch between speakers and still focus on whatever overlays are required.

  • Riccardo S Do you know of a WebRTC service (Zoom doesn't use WebRTC) that supports that kind of auto camera switching? The problem with that technology is that sometimes background noises causes the camera to switch inadvertently.

  • CraigS good question - we’ve been playing with Whereby recently, which uses WebRTC, as an alternative to Zoom. I’m not aware of their having an “active speaker only” view, but I’ll test in a “large room” on Whereby and see how it works. If they don’t have something like that yet they’re certainly open to suggestions:)

  • CraigS as I posted my reply I realised that Slack does WebRTC *and* does active speaker detection. There’s a section here on how they do it: https://webrtchacks.com/slack-video/

  • Riccardo S Fill out the form and send us that as an example as a feature request. 

  • CraigS thanks - just did that:)

  • Riccardo S You're welcome of course.

  • An alternative to nimble is nginx. very simple as well.

    A solution to video conferencing comes from pexip. If you use PTZs they can even focus, position and zoom based on the number of people in the image. The AI approach. They just have it on display at their booth at ISE.

    Sennheiser showcases their team connect ceiling 2 array mic that can send the audio position of a source to trigger a PTZ preset.

    Webex also focusses on the one who is talking.

    RTMP has a lot of latency involved. And the bad thing is it varies. With SRT you add a constant latency, error correction annd security to your transmission. You can even send a SRT stream from your android phone using larix broadcaster app and receive it at your mixer. Unfortunately wirecast doesn't support SRT actually. But other software does.

  • CraigS Hi guys, I have been struggling to get something like this going solid. For me, as long as I can get my zoom meeting into Wirecast, and out to my audience via Facebook or YouTube, I am good. I am wondering if this is possible using two computers - Host the zoom meeting on computer #1 and send it to Wirecast on the second machine via RMTP. Any overlays can be done on machine #2, and the meeting can happen amongst the guests on machine one - which would still accommodate active speaker. If latency is introduced between machines 1 & 2, it shouldn't matter really (for me) as long as my guests and I can chat in real time - our viewers should see a good show.

  • Just use NDI to send from one computer to the other.

  • We've found another work around for this (with a big caveat which I'll get to) which is to push the zoom call to Castr or restream.io. Castr than gives you a RTMP pull code that you can add to wirecast as a web source. I have a co-worker that manages the zoom call and switches the cameras by spotlighting the speakers. Now the warning: We upgraded our computer from an old mac pro to a new PC and now the castr rtmp source is out sync of when it hits our cdn, though it appears in sync to the wirecast operator. The workflow was solid on the mac. I'm trying to troubleshoot but if anyone can think of some settings that could cause this I'd be very grateful.

      • CraigSModerator
      • Telestream Desktop Forum Moderator
      • CraigS
      • 1 mth ago
      • Reported - view

      Jamie Crausman There shouldn't be any significant difference between Mac and Windows Wirecast as long as they are the same version number. Perhaps something else changed as well.

Like1 Follow
  • 1 mth agoLast active
  • 18Replies
  • 975Views
  • 6 Following