ArtNet through Parallels

[Freddy Komp]

Dear Figure53/cloudbrain,


I have recently wanting to start playing with the Lighting function with QLab, and wondered if there are any caveats or tricks in making the following scenario work:

- El Capitan 11.6
- QLab 4 on the main machine, connected to a LAN or WLAN
- Parallels 12
- ArtNetominator or Wygilizer->Wysiwig on Windows 10

The goal being to control an Artnet Monitor and/or Visualisation via QLab 4, something that I managed with i.e. Claude Heintz's LXConsole without issues.

In QLab, I seem to have comparetively limited configuration options in terms of ArtNet address output, see attached comparison image.

With the settings on the right, ArtNetominator sees LXConsole fine in Windows.

Would it be possible to add the option of setting the broadcast address i.e. to 127.0.0.1, on top of selecting the network adaptor?

Or are there any other tips how to make this work?


Thank you very much for any insight.


Cheers,

Freddy

[Freddy Komp]

A minor update,

While ArtNetominator seemed to see the LXConsole node pretty much no matter what, only setting the send address to either the local IP of the Virtual Windows machine (in my case 10.0.0.8, with Parallels set up to be Default Adaptor, Bridged, whereas the physical/MacOS side's WiFi IP is 10.0.0.66), or to 10.0.0.255 seems to work.

With QLab4, setting the chosen adaptor to WiFi by itself does not work, setting it to broadcast seems to work, but unfortunately not reliably - signal seems to come and go with in intervals reminding of an indicator of a car, while cycling through various port numbers. Is broadcasting in this instance QLab polling various ports and only continuing to send if they get an answer from a potential receiver, and otherwise shut that send off and check the next port?

Any idea what the solution might be?

Being able to set the send-to address to in my case 10.0.0.8 or 10.0.0.255 (although in my mind, that address would refer to "broadcast" but maybe with a different meaning?) - would that help?


Cheers,

Freddy

[Chad Sellers]

Hi Freddy,

I'm not sure what's going on. First, no, QLab is not cycling through port numbers. There is only one port number for Art-Net (UDP port 6454), and that is all we send to. When in broadcast mode, we just send to the broadcast address of the chosen network adapter (e.g. 192.168.1.255). If there is no chosen network adapter, we send to the broadcast addresses of all the network adapters. So, if you're network adapter's broadcast address is 10.0.0.255, then that is the address QLab should be sending to.

One note - the 10.x.y.z network is a private class A network, meaning it's broadcast address is 10.255.255.255. Often people just use a class C network within it (as you seem to be doing), but this is often misconfigured, leading to some pieces configured as a class A and others a class C. Problems like yours can be caused by such network misconfiguration (e.g. your Mac thinks its network is class A, while Parallels is treating it as class C).

Other than that, I'm not sure what might be the problem. I just created a Parallels VM in bridged mode, and all of QLab's broadcast Art-Net packets seemed to get to it just fine when monitoring network traffic in it.

I hope that helps.

Thanks,

Chad Sellers

--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: http://twitter.com/Figure53
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/a9c8ee3e-6744-4797-8cdf-333e41ddd3f6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.