2

Rendezvous unable to receive video

Hi, I just upgraded to Wirecast 8 and tried to use Rendezvous with adding an external guest with an iPhone (6s and 7). The (updated version of) Wirecast Go will accept the link I created within the Rendezvous Dashboard, but on the iPhone screen it always says "Uanble to receive video" and the screen in Wirecast will stay black. Any ideas what's going wrong here? Tried the iPhone in wifi and LTE mode, Macbook is running on 10.12.1. 

Thanks for any answers that might help. 

Max

37replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Today i got this error using the latest google chrome:

    No video or audio captures devices are found - please connect a camera or microphone to continue.

    I have mic working perfectly.

    Google Chrome is set to ask when a website or plugin wants to record.. but don't ask anything.

    Console log is empty, no errors, no warnings.Nothing.(w8)

    Same issue from Firefox, using windows 8.

    Same issue from Linux, using google chrome,and  chromium.

    Any idea? 

    Like
  • Using This:

    https://online-voice-recorder.com/es/beta/

    I saw that is recording perfectly.Because ask before por permissions. But rendesvouz, is not asking.

    Like
  • Daniel Silver said:
    No video or audio captures devices are found - please connect a camera or microphone to continue.

     This sounds like a settings issue on your end. Make sure Chrome is current. Please list the version. Please also list the OS as you mention Windows 8.

    You may want to read this.

    Like
  • This problem is now for me an issue. Two of the guests can join two cannot. Why. They see and hear each other on the Wirecast go but nothing but a black screen comes to me, the host except the two whom I can see and hear. What to do?  Windoes 10, Wirecast 10 Pro, everything upto date.

    Like 1
  • Same issue here. Windows 10, Wirecast Pro 10 and Rendezvous black screen for some guests

    Like
  • Atanasio Noriega Dos Anne-Maarit Sepling 
    Are your guests using Chrome version 70?
    It's possible that a recent Chrome update broke compatibility.
    Please confirm the browser and version number guests are using as soon as possible. That will help us immensely in our investigation.
    Firefox version 63 (also current version) works.

    Like
  • Ok, I'll try to do it. But I suppose that all of them are using version 70 cause is the current and Chrome updates itself all the time. I'll suggest using Firefox instead and we will see how it works... 😒

    Like
  • Using Rendezvous with Chrome 70 should now be fixed.  Please let us know if you run into any other problems.

    Like
  • Simon Clarke - I'm curious to know what hanged Simon? Was it indeed a change in chrome that required a corresponding change in the rendezvous infrastructure on your servers?

    Like
  • Had this issue yesterday with a client.

    We both have wirecast Pro (newest release)

    They started a Rendezvous session and sent me a link.

    I accepted and in their rendezvous dash my videp /input signal was "black".

    On my end (using wirecast go) newest iOS version (all permissions granted) their video signal was "black" too.

     

    then I decided to try and host it on my end using MBP 2017

    I sent invite....

    everything went fine.....

    then I asked him to perform a prt check using canyouseeme.org and my port 80 and 443 was open and his port 80 and 443 was closed.

    would this cause the issue?

    because in the end, our enviroments were exactly the same except our routing settings

    Like
  • David Galligan Rendezvous is designed to find an open port. It's possible that a very restrictive firewall can prevent that from happening but otherwise Rendezvous may find another open port.

    Like
  • David Galligan said:
    I accepted and in their rendezvous dash my videp /input signal was "black".
    On my end (using wirecast go) newest iOS version (all permissions granted) their video signal was "black" too.

    I get this semi regularly too. I usually turn off and reconnect to the same rendezvous session, and it seems to rectify the problem.

    Like
Like2 Follow
  • 2 Likes
  • 2 mths agoLast active
  • 37Replies
  • 1453Views
  • 12 Following