Qlab - ETC Nomad on the same Mac

[Roderick]

A little stuck with a project just for me at the moment.

 

In the past I have run ETC desks controlled from Qlab, both MSC and OSC, never a problem.

But to compact things I'd like to run both of the same machine. Installed Qlab and ETC Eos on a Mac running Mojave.

Both running fine but I can't trigger Eos from Qlab. I have run a OSC sniffer that shows OSC commands at the port, yet nothing happening in Eos land.

 

Here are screen shots from the set-up.

What am I missing to make this work?

 

http://www.rvg-lighting.com.au/MacScreen/Qlab1.jpg

http://www.rvg-lighting.com.au/MacScreen/Qlab2.jpg

http://www.rvg-lighting.com.au/MacScreen/OSCMon.jpg

http://www.rvg-lighting.com.au/MacScreen/Eos1.jpg

http://www.rvg-lighting.com.au/MacScreen/Eos2.jpg

[alistermorton]

Bit of a stab in the dark, but I have a feeling this icould be one of two or three things I've seen reported often on Facebook:

1) If there is no physical connection to the network port from a switch, the networking isn't enabled, so you can't loop back to yourself, although EOS reports the port as online so it's probably not that.

2) Perhaps you haven't enabled osc on the network port in the shell (scroll down a bit further on the enabled protocols to check) This used to be an option, I'm sure.

3) instead of setting the destination in QLab to localhost, try setting it to 10.1.1.148

 

 

Edit: I see you asked the same question on Facebook - did you not have any luck?

Edited October 15, 2019 by alistermorton

[Roderick]

Thanks Al, I'll give that a try soon.

 

Tried everything suggested on FB, still no joy so widening the circle...

[alistermorton]

I've seen one or two reports in the EOS group that OSC stopped working after upgrading to 2.9 but this doesn't seem to be consistent, and might be settings being reset to default.

[MarkPAman]

There don't seem to be many problems that don't get fixed in the Google Groups

[Roderick]

There don't seem to be many problems that don't get fixed in the Google Groups

I think it is more a ETC Nomad problem than Qlab.

OSC Monitor shows the TX messages from Qlab but they don't show up in Nomad Diagnostics.

At the same time, OSC TX from Nomad shows up in Diagnostics but not anywhere in OSC Monitor.

[Roderick]

It is working!

And I know why; I had just been running it as 'offline' without the dongle because I wasn't actually outputting DMX.

Looking at the "diagnostic" screen and pressing 'Network' I noticed it reported 'offline'.

Plugged in the dongle, rebooted Nomad and bingo, all works smoothly! Nomad without a dongle will not respond to OSC, go figure.

Certainly one to remember.

Thank you all for your assistance!

[IRW]

It is working!

And I know why; I had just been running it as 'offline' without the dongle because I wasn't actually outputting DMX.

Looking at the "diagnostic" screen and pressing 'Network' I noticed it reported 'offline'.

Plugged in the dongle, rebooted Nomad and bingo, all works smoothly! Nomad without a dongle will not respond to OSC, go figure.

Certainly one to remember.

Thank you all for your assistance!

 

It definiitely does (respond to OSC without a dongle)...maybe it's a mac thing? So long as you've got an NIC connected, it'll still pick up an IP address, but offline mode simply won't output DMX-related data.

Edited October 16, 2019 by IRW

[alistermorton]

I've had nomad offline with no dongle respond to OSC here, but on a PC.

[IRW]

Actually, I must have had it working offline on my desktop Mac, as I do my FocalPoint development on my windows machine, so I run EOS on my desktop to test it. To be fair, I've been away for the last three months or so, so a recent update may have broken it,

[IRW]

Just to drop back in on this, I can confirm for definite that Nomad started up in 'offline' mode and no dongle on a Mac does send and receive OSC data. Running Mac OS 10.15, and EOS version 2.9.1 Edited November 1, 2019 by IRW