Why wont LXConsole save the device info?

Johan SÃ¶derberg · Post by **Johan SÃ¶derberg** » Fri Sep 28, 2012 5:00 pm

Ive got this one night to reprogram three different shows.
The group has invested in some new LED fixtures so Ive set up all devices and got them all to work.
But when I just returned after a coffebreak to open the saved files everything was there including the channels for intensity but no other device info was saved..

So nothings is shown - there is nothing saved in the channels for rgb, macro, strobes etc.

Is there a checkbox somewhere to be checked?
Or should I start all over and run it all straight channel by channel.

Grateful for a quick reply. Its getting late fast over here on this old continent.

Johan SÃ¶derberg · Post by **Johan SÃ¶derberg** » Fri Sep 28, 2012 5:40 pm

Just realized most of you are west of me... When its early evening here youre all out late fridaynight partying I guess.

So I resign...
Ill program the shows patched 1:1.

Im controlling 11 lamps but will have a window showing 200 channels and wont be able to use the channel controls.

It will be and look silly, but it will work.

Long night ahead:(

Post by **admin** » Fri Sep 28, 2012 8:46 pm

Email the file you had setup with the device channels along with the version of LXConsole and the version of OSX and I'll take a look. I have a dress rehearsal and a show today. But, I'll do my best to get you an answer.

BTW, the show I'm doing is using LXConsole, latest build on 10.8 and it has just under 300 total channels with ETC Selador LEDs, color changers and an ETC Revolution moving light. All the devices are working, including some multi-part color chases with the Seladors.

Johan SÃ¶derberg · Post by **Johan SÃ¶derberg** » Sat Sep 29, 2012 9:00 pm

Thanks Claude that´s very kind of you, but too late.
I created 1:1 versions with no subchannels. Had only one night available in the venue so it just had to be done at once.

But I´ve sent you another small sample show, Key and plot.
its in the inbox at sales@macl...

Hope your dress rehearsal went well!

Greetings JS

Post by **admin** » Sun Sep 30, 2012 8:09 pm

This problem was cause by the fact that the universe separator character was being used to interpret a channel/subchannel string. With the universe separator set to a comma, reading the file was using the universe separator and expecting "channel,subchannel". But, the file is written "channel.subchannel". So, the sub channels were being interpreted as zero and then read as intensity values.

LXConsole extends standard USITT ASCII which defines a comma as a field separator. So, LXConsole (and the rest of the LXSeries) will only allow the "channel.subchannel" format in the future.

This critical issue is fixed in LXConsole build 5630.

Johan SÃ¶derberg · Post by **Johan SÃ¶derberg** » Mon Oct 01, 2012 12:20 am

Thats great!

Betatesting has its rewards and drawbacks.
Glad this minute but critical little issue could be pinned down

JS.

Post by **admin** » Wed Oct 03, 2012 10:12 pm

Using a comma as the universe separator has an additional consequence. Multiple dimmers patched to a channel are separated by a comma in the channels table! Consider trying to patch the first two addresses "2,1, 2,2" would not work. So, if you use a comma notation for the universe, you must use a semicolon to separate the addresses: "2,1; 2,2" will now patch address 513 and 514 to the channel. (assuming you've set the universe separator to ",".

This also was not much of an issue because LXConsole would only output the first 512 addresses anyway. So...

The latest LXConsole (5703) also adds a second universe of DMX output. This also includes beta support for outputting the second universe through ENTTEC's upcoming DMX USB Pro 2 which will have 2 DMX ports. In the latest build the second universe is sent over Art-Net or ACN when an address above 512 is patched.