The post talks about how the "AirPlay Receiver" feature uses these ports and that it should be turned off to avoid conflict.
WIRECAST NDI SOFTWARE
However I did find a blog post talking about how Monterey uses ports in the 50 range and that it can be problematic for software developers.
WIRECAST NDI HOW TO
I couldn't readily figure out how to look at the ports in use since Network Utility was discontinued in Monterey. The moderator also said that this range might not be necessary for OBS, which would explain the above situation. I came across Wirecast forum of someone having similar issues and the moderator suggested to check to make sure ports 54-59xx were open. So basically at this point I thought that there's something not right with the Mac version of Teams and/or Wirecast on the Mac. I would just use a high performance PC but currently our only high end machine is a Mac Cylinder Pro. On a PC (Windows 10): NDI works from Teams to Wirecast, OBS and NDI viewer. NDI Issues May 2022: (note the first example where the notification in Teams changes goes on/off repeatedly and the connection status in Wirecast goes Not Connected/Receiving repeatedly on the left)
NDI outputs from both OBS and NDI Test Patterns to Wirecast show up. On a Mac (Monterey): NDI doesn't work from Teams to Wirecast, or from Teams to NDI viewer but it does work from Teams to OBS.
WIRECAST NDI UPGRADE
Note that we did recently upgrade to from Catalina to Monterey 2 weeks ago. After the problem continued, I even tried a prior version of Wirecast 14.3.4 and got the same issue.
WIRECAST NDI FOR MAC
Installed the newest NDI tools for Mac version 5.1.2.9. Had the newest version of Wirecast 15.0.1. Today's troubleshooting, I first cleared Teams cache, uninstalled/reinstalled Teams, checked for updates. In the moment, we had to use our pre-pandemic method of screen grabbing a Teams meeting from a capture card to send to Youtube. I tried relaunching applications and even restarting the machine with no difference. But the day of the event yesterday, the first person to come into Teams didn't work with NDI. We had a tech check meeting on Tuesday and all the NDI sources came into Wirecast fine. , you mentioned using a Tricaster, which uses Windows, so I wonder if there is a common issue in both the Windows/Mac versions of Teams that I might be missing. Ultimately from my end, I think it could be an issue with the Mac version of the Teams app and how the Apple Monterey OS works. I can recreate the issue repeatedly (see first video link). I spent the day trying to figure out the issue. We didn't have these issues a month ago during our last event. We have had the same workflow for over the past year as well. The only difference is we bring our NDI Teams sources into Wirecast. I was very surprised to see you were having the same issues we were having. We had this issue yesterday afternoon during our monthly technology town hall to the enterprise. That's why I wrote in that Q&A to see if others also experienced similar problems. Is it possible that when no device is recognized by Teams using the NDI stream, that Teams turns the broadcast off? Kind of an auto setting in the background.? So maybe it's a comunication problem between the software and the device.? Just a guess.Īnd yes, I also searched around and have not seen a similar report. In the Setup we experienced the issue we are only using the Epiphan Pearl2 to receive the Teams NDI stream (active Speaker). Normaly we are using Tricaster and OBS with Teams and NDI.Īnd yes, as long as I don't reconnect the call, the Teams NDI stream is not coming back and Teams itself shows the mentioned message that the capabilities have been turned off. We used to work with NDI from Teams a lot in Broadcast Productions over the last 1-2 years and also never experienced that issue. As we are 3 persons managing the whole IT Infrastructure I can say for sure that nothing has changed within the network, QOS or Firewall within the last month.
0 kommentar(er)
