Hello everyone, longtime Freestyler user new ArtNet user.
I'm having a hard time getting Freestyler to send ArtNet.
Settings:
Freestyler interface local LAN adapter 192.168.1.12
Freestyler interface broadcast addy 192.168.1.255
Tried 1:0:1 and 0:0:0 for the net/something/universe settings.
The Pi is running OLA at 192.168.1.31, and has an artnet input with 1:0:1 (tried 0:0:0 also with both sides configured the same.)
Output on OLA is FTDI DMX driving a OpenDMX and a Philips KiNet. The web console works with both interfaces, the web OLA monitor shows all 0's when waiting for input from my FreeStyler computers.
Back in FreeStyler on my one laptop (now updated to latest version) the DMX monitor always shows all 0's on all channels even when I manipulate my test fixtures.
On my desktop system which runs an earlier version of FreeStyler, the DMX monitor does show changes to the fixtures when I manipulate faders.
When I TCPDump looking for udp traffic on the 6454 (I think that was the port) I'm not seeing anything coming from either FreeStyler equipped system arriving at the Pi. The Pi has no firewall. Windows Firewall is turned off on both systems.
Any thoughts as to what I'm missing?
Can't get ArtNet working? (Targeting OLA on Pi)
Forum rules
Please do NOT post bugs here! If you spot a potential Bug please report it HERE first then you can chat about it with other users in the appropriate section.
Please do NOT post bugs here! If you spot a potential Bug please report it HERE first then you can chat about it with other users in the appropriate section.
-
- Knows how to turn Lights ON
- Posts: 4
- Joined: September 6th, 2013, 6:43 am
- I Use FreeStyler for: Just for the Fun of it.
-
- Knows how to turn Lights ON
- Posts: 4
- Joined: September 6th, 2013, 6:43 am
- I Use FreeStyler for: Just for the Fun of it.
Re: Can't get ArtNet working? (Targeting OLA on Pi)
Got it working, I turned on the always broadcast option in OLA in the ola-artnet.conf and that fixed it. I had tried that the night before, but I think my laptop has issues (desktop is working.)
When sniffing using wireshark I noticed that the broadcast was wrong when I used 192.168.1.255 as broadcast but works right when using x.x.x.255
When sniffing using wireshark I noticed that the broadcast was wrong when I used 192.168.1.255 as broadcast but works right when using x.x.x.255