|
|
Post by Kevin on Mar 11, 2017 14:24:17 GMT -5
Has anyone been able to make OSC console linking with LW work with a PC?
I can make it work with a MAC but no dice yet with a windows 10 PC....
Kevin
|
|
|
|
Post by johnmcsoft on Mar 12, 2017 21:05:24 GMT -5
Choose a network interface that is on the same subnet as the console, make sure the console's OSC TX address isn't set to a different address as your PC. Even better, clear the OSC TX address field.
|
|
|
|
Post by Kevin on Mar 14, 2017 9:47:39 GMT -5
John,
I generally consider myself pretty network savvy. But this is definitely giving me a challenge.
I have my PC at 10.101.95.102 / 255.255.0.0
My RPU is 10.101.95.101 / 255.255.0.0
I've tried the gateway IP as both numbers.
I disabled all my other Network INterfaces except for the wired interface and then selected it with the above IP in LW.
I have tried disabling firewall and Virus Protection.
It all works great with my MAC but not on 2 different PC's running Windows 10.
I can ping the console successfully.
I can also connect with the EOS client using the same network settings.
Not really sure what to try next.
Kev
|
|
|
|
Post by johnmcsoft on Mar 20, 2017 8:54:02 GMT -5
It sounds like you're using the correct IP addresses. However, in Eos Show Settings, did you try clearing the OSC TX IP Address field? That should let Eos send to more than one OSC client (i.e. Lightwright).
|
|
|
|
Post by Kevin on Mar 20, 2017 14:35:51 GMT -5
Yup, it has no IP setting there.
|
|
|
|
Post by johnmcsoft on Mar 23, 2017 15:06:51 GMT -5
Matt H. recently recommended using a broadcast IP address in the OSC TX IP field, which would then (theoretically) broadcast returns to everyone on that subnet. Did you try that?
|
|
|
|
Post by florianb on Mar 22, 2018 9:36:41 GMT -5
@kevin is your RPU your Master? In LW you have to specify the IP address of the Master, not the Backup or client.
|
|
|
|
Post by Kevin on Mar 26, 2018 15:12:40 GMT -5
Yup,
I have tried that.
Have you managed to make it work on a PC?
Kevin
|
|
|
|
Post by johnmcsoft on Mar 27, 2018 8:05:10 GMT -5
I'm sure you've tried these already, but if not - on PCs, you'll need to choose which network interface you want Lightwright to use - the popup menu at the bottom of the Console Link window will have a list of the ones available. Choose the one that is on the same subnet as the console.
Also, you'll have better luck if you leave the OSC TX IP field blank, that way everyone connected gets the OSC messages, which is a good thing.
And have you tried using the PC equivalent of Little Snitch or other network-monitoring software that could show you what messages are coming/going to/from each client?
|
|
|
|
Post by Kevin on Mar 27, 2018 14:56:13 GMT -5
I'll give the snitch a try...
But I know that i am connected properly because I can connect with the Nomad Client Software.
I have tried the OSC TX IP blank, but I will give it a go again.
I know that i am definitely choosing the correct LAN card for my wired network.
I'll keep at it.
K
|
|
preston
LW User
Designing and programming as fast as I can!
Posts: 8
|
Post by preston on Mar 29, 2023 15:07:00 GMT -5
I'll give the snitch a try... But I know that i am connected properly because I can connect with the Nomad Client Software. I have tried the OSC TX IP blank, but I will give it a go again. I know that i am definitely choosing the correct LAN card for my wired network. I'll keep at it. K Howdy Kevin & John >>> It's now March of 2023 and this question still seems a bit on the gray side of answers. I am having issues when I'm running ETC Nomad/EOS on the same machine as Lightwright. When I'm logged into a real desk as a "Client - User" I can extract the cue information... and most of the patch info into LW. I can control the Ion/Gio desk of the day from my PC/Nomad, so I know I'm talking. (yet I can't actually control levels... but that's not really important to me as I use my Nomad for that feature.)I have found that with Console Link AND VW Data Exchange, my " as show opened" files are all updated and the patch is updated for future reference with minimal manual interference... such as dealing with two-fer instruments... which is a great feature! (as well as a printed backup of the Cue List for archival purposes!)
Will/Can this eliminate the "export" to EOS Family Patch and "import" Lightwright Patch steps? Since I work on one PC Notebook 24/7 >>> from VW to LW to ETC: with LW's built-in connectivity can I do it all internally? So--my real question is: What are the suggested PC settings for LW & ETC to use Console Link in the same lil'ol notebook computer?Bueller? Anybody? 😊 |
|
