Artnet out troubles

mysecretstache · Post by **mysecretstache** » Thu Jul 11, 2013 3:50 pm

I'm using the latest build of LX Console, but I'm having trouble sending Artnet. My network settings are correct, as the hardware works with other Artnet capable software installed, but I'm getting no response with LX Console.

I've tried with the 10.x.x.x and 2.x.x.x network ranges with appropriate IPs and a variety of Subnets. I can always see the node to try and unicast to it, but I never get output from LX console. MagicQ and JVlightning both output through the node with the same network settings.

I also have an alternate node that listens to sACN that is working fine with with LX Console, but I would rather not leave it with the show.

My Artnet node is a DMX king eDMX 1 connected directly to the mac.

Post by **admin** » Thu Jul 11, 2013 6:40 pm

Have you checked the starting universe setting in the preferences? If you used LXConsole with ACN, it would have to be 1 for the first universe. But for Artnet it needs to be 0.

mysecretstache · Post by **mysecretstache** » Thu Jul 11, 2013 7:23 pm

Yes, I've double checked output universe settings, and even outputting on an alternate universe.

Post by **admin** » Thu Jul 11, 2013 7:36 pm

In the DMX info tab, not the DMX out tab, have you selected the exact ethernet connection? This would be the 10.n.n.n connection defined in the system network preferences.

Also, a big necessity is that you close all other Art-Net applications first. If they are holding the port open, then LXConsole will not be able to open a connection. You may need to restart if the port has not been closed properly and the kernel thinks it is still open. You'll see error messages in the Messages window if you enable ethernet and LXConsole can't establish a socket.

mysecretstache · Post by **mysecretstache** » Thu Jul 11, 2013 7:41 pm

LX console is the only software open, and the ip is selected.

I can see the ip of the node in the output window as an option for unicast, so it is responding to the poll from LX console.

Node is 10.105.35.147
Computer is 10.105.35.142

Same subnets, tried 255.0.0.0 and 255.255.0.0 and 255.255.255.0

No connection errors in the messages window, but no output tried sending channels as well, but still no output.

I'm stumped

I also tried two laptops side by side one listening, one transmitting artnet, and still couldn't see output from LX console

Post by **admin** » Thu Jul 11, 2013 9:06 pm

When you select File->External->Ethernet, what does it say in the messages window? It should say something like this after you've adjusted a channel in live mode (which starts the sending):

DMX ethernet out connected to 10.20.30.40

If not, there should be some other message.

HarryTwoFingers · Post by **HarryTwoFingers** » Sat Oct 12, 2013 1:03 pm

Hi Claude and list.
I also have problem with getting DMX out of my ODE from LXConsole.
Using the ODE I get output to dimmers if I use Enttec's NMU tool. A testtool for finding ODE on a network and testing it. The activity led on the ODE blinks wildly when LXconsole sends dmx to it.
Message window in LXConsole says "ethernet dmx out is connected to 10.49.187.108."
Live window is open and ethernet is activated.
Last time I used the ODE was sometime in march 2013. Has something been changed in the LXConsole versions since then?

My best

Post by **admin** » Sat Oct 12, 2013 3:09 pm

I would verify the subnet and universe settings match between LXConsole and the ODE. And, also confirm that your channels are patched. With the LED blinking, that would indicate that the connection is good. So, there's probably one of those other things that is wrong.

HarryTwoFingers · Post by **HarryTwoFingers** » Sat Oct 12, 2013 4:01 pm

Hi, Claude!
Universe and subnet are the same in lxconsole and the ode, ie 0,0.
This is version 3.2.4. Latest version and no i can't get dmx out of the ODE with this version of lxconsole.....but....
i downloaded version 2.7 (6420) and that works.
It's the same lxcues file.
Best

Post by **admin** » Sat Oct 12, 2013 4:38 pm

Interesting that 2.7 works and 3.2.4 does not. Is everything else exactly the same? Do you see any error messages either in LXConsole's messages window or in the OS X Console? You can always e-mail the file so that I can take a look.

Does your dimmer patch use universe notation? 3.2.4 does not allow numeric characters to be used as the universe separator. At the moment this means the minus sign is not allowed. Although this should be corrected soon.

HarryTwoFingers · Post by **HarryTwoFingers** » Sat Oct 12, 2013 5:31 pm

I use a macbook pro 15", Mountain Lion, bootcamped with windows7.
This evening between updates or downdates of lxconsole i haven't fiddled with the computer. It is the same show file I use. No change to that either.

One oddity has happend. The first time i changed from 3.2 to 2.7 and loaded the showfile into 2.7, the showfile had no patching. I can't remember what i did next. The main window was like greyed out but i think i saw the numbers in the background. After patching 1 to 1 main window was normal.

I will also test the show file on a new imac.

There are no messages in lxconsoles message window.

The following is from osx system message:

2013-10-12 19:09:10,101 LXConsole[1256]: *** Assertion failure in -[NSTextFieldCell _objectValue:forString:errorDescription:], /SourceCache/AppKit/AppKit-1187.40/AppKit.subproj/NSCell.m:1532
2013-10-12 19:09:10,102 LXConsole[1256]: Invalid parameter not satisfying: aString != nil
2013-10-12 19:09:10,104 LXConsole[1256]: (
0 CoreFoundation 0x00007fff8ded3b06 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff972833f0 objc_exception_throw + 43
2 CoreFoundation 0x00007fff8ded3948 +[NSException raise:format:arguments:] + 104
3 Foundation 0x00007fff8f6bf4c2 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 189
4 AppKit 0x00007fff98153125 -[NSCell _objectValue:forString:errorDescription:] + 159
5 AppKit 0x00007fff9815307f -[NSCell _objectValue:forString:] + 20
6 AppKit 0x00007fff98152ffb -[NSCell setStringValue:] + 39
7 AppKit 0x00007fff981e732c -[NSControl setStringValue:] + 138
8 LXConsole 0x0000000100049649 LXConsole + 300617
9 Foundation 0x00007fff8f7455ca __NSThreadPerformPerform + 225
10 CoreFoundation 0x00007fff8de52b31 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
11 CoreFoundation 0x00007fff8de52455 __CFRunLoopDoSources0 + 245
12 CoreFoundation 0x00007fff8de757f5 __CFRunLoopRun + 789
13 CoreFoundation 0x00007fff8de750e2 CFRunLoopRunSpecific + 290
14 HIToolbox 0x00007fff8d546eb4 RunCurrentEventLoopInMode + 209
15 HIToolbox 0x00007fff8d546c52 ReceiveNextEventCommon + 356
16 HIToolbox 0x00007fff8d546ae3 BlockUntilNextEventMatchingListInMode + 62
17 AppKit 0x00007fff98175533 _DPSNextEvent + 685
18 AppKit 0x00007fff98174df2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
19 AppKit 0x00007fff9816c1a3 -[NSApplication run] + 517
20 AppKit 0x00007fff98110bd6 NSApplicationMain + 869
21 LXConsole 0x0000000100001d74 LXConsole + 7540
22 ??? 0x0000000000000002 0x0 + 2
)

HarryTwoFingers · Post by **HarryTwoFingers** » Sat Oct 12, 2013 6:39 pm

Version 3.1.2 also works on my macbook pro.

Post by **admin** » Sun Oct 13, 2013 6:16 pm

The latest build, Version 3.2.4 (6914A) should fix the error message you posted. Its not likely to have altered your ArtNet issue.

I'm still guessing it is a patch issue. The ODE ethernet light will blink even if the patch is cleared--which, of course, does not produce output. The fact that you have a good network connection, evidenced by the blinking light, probably means that is is another setting, either the universe, subnet or patch that is causing the received packets not to produce output. It sounds like the universe and subnet match and you've checked that, so it leaves the patch.

The patch is not necessary if the "Send Channels" preference is enabled. A change in that setting could cause a formerly working document to quit working. You can always go into the setup window channels tab and patch 1 to 1 which is basically the same as having the send channels preference enabled.

The new version (6914A) has the ability to reset the preferences. You might try that to see if it makes a difference if nothing else seems to work. (You will need to set the dmx output to Art-Net again and re-enable ethernet to test it out).

Post by **admin** » Mon Oct 14, 2013 3:55 pm

Before you reset your preferences, you can also try the dimmer check function in the latest build 3.2.5 (6914B) That will allow you to turn on any single dimmer, bypassing the patch entirely.

Johan SÃ¶derberg · Post by **Johan SÃ¶derberg** » Mon Oct 14, 2013 11:07 pm

I dont know if it has anything to do with this but I had some similar connectionproblems recently on an old laptop that used to work before.
Nothing had changed at all in the network settings and it was still running its same old version of LXConsole, but it couldnt connect anymore.

The solution in that case was to change the laptops subnetmask.
It was 255.255.255.255 originally but I changed it to 255.0.0.0
That solved it.

Original LXSeries Forum

Artnet out troubles

Artnet out troubles

hmm