-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2 networks on Mac computer #170
Comments
Satellite is simply following the routing table in your OS for knowing what network interface to make the connection over. |
The PC sees the Mac and the satellite connection, but doesn't see the surface. Any ideas on what we may need to fix? |
oh, so its that the mac isn't offering the streamdeck over satellite? could some other software on the mac be using the streamdeck? if another application has opened the streamdeck then satellite wont be able to. |
I closed the Companion software so that I could launch Satellite. I don't think anything else is trying to see it. Although, we use qLab and that looks for it, could that be possibly doing it? |
Good Morning, I tried something this morning where I made sure it didn't load the orginal Companion that we were running on the Mac and put Satellite in the startup so that only that launched and not launching Companion, and now the PC doesn't even see the Satellite connection. Not sure what else to try! |
We are trying to merge all our companions to one computer, a PC and 2 of our Macs are running 2 networks, as is our PC. One Mac is running just the one network and is talking to the lead computer fine with satellite. The lead computer is the PC. The Macs with 2 networks have a Dante network and regular network. The lead computer see the connection, but doesn't see the SD. In the discover list, the Dante network is listed first as it is a 169 base IP where as the host is on a 198 base IP. I can't see a way for Satellite to pick the correct IP. Any suggestions would be great! Thanks - Jon King with Northridge Church, Webster, NY.
The text was updated successfully, but these errors were encountered: