xlights * Vixen+

[Dvc2013]

I have all of my sequences completed in VixenPlus.  Since Vixen+ does not and will not have a scheduler this year I am trying to convert my sequences to xlights for scheduling.  However xlights is behaving quite strange.  I used it last year to run the show and it worked flawlessly.

I am currently trying to create a simple sequence for controller testing.  I created my main profile in Vixen+ and created a test sequence attached to my 2014 profile.  At least half of the time xlights crashes while attempting to convert the sequence file.  If I do get a successful conversion and play the sequence in xlights everything is off by one channel.  It drops channel 1 and outputs that data on channel 2, channel 256 is output on 257, etc.  All is fine if run the sequence directly from Vixen+.  The problem only exists when playing the sequence in xlights.

My setup is on a dedicated show network direct from an Ethernet card to a 6 port E1.31 bridge with 2 universes both outputting DMX data.

However if I create a sequence in Vixen+ that is not attached to a sequence everything appears to be fine.  The sequence converts fine and the data is output on the correct channels.  However if I convert a file and try and play it without closing xlights first, xlights crashes and has to be restarted.

This situation is the same on 3 different computer systems.  It's been tried on Windows 8, Windows 7 & XP with the exact same result.

Since the problem only occurs with a sequence attached to a Vixen+ profile, is this an xlights issue, or is this a problem in John's newest release of Vixen+ with the new Profile Editor

Any suggestions from anybody

[dkulp]

What version of xLights?   The latest version has a completely re-written Vixen import (new XML parser to allow importing gigantic sequences).  I may have screwed something up. 

In either case, it definitely should not crash at all.   If Vixen+ is generating a bad file, xLights should warn, but not crash.   If the file is good, xLights definitely shouldn't crash.   Can you send me the sequences and the xlights_network.xml file?   (and the xlights_rgbeffects.xml if you have some models setup to preview it)  If it's relatively small, dan at kulp dot com is fine or send a dropbox link to me.

[Dvc2013]

I'm using v3.4.4

My biggest problem is that it is dropping the first channel on anything attached to a profile.  Another member at DIYC.org tried it with my file and his with the same result.

I'll email you me vixen+ sequence and profile.  The setup/test files are small so I'll send them in a few minutes.

Thanks

[mms]

In to follow this thread.

I haven't quite made the transition to V+ but I like what I've seen.  I'm surprised more people aren't using V+ to be honest.

[dkulp]

I pushed a "fix" for this today, but we'll likely have to wait till Sean gets back from the academy to get a new Windows release.

Basically, the code is expecting the Vixen channels to start at output channel "0".  However, the Vixen+ profile starts them at output 1.   Thus, everything gets pushed over one.   The fix I made was to compute min/max and use that range with min->0.  Thus, the lowest output Vixen channel, no matter what the output number is, will be the first channel in xLights.

[Dvc2013]

So far it looks like the new version 3.4.5 fixed my problems with Vixen+.  My sequences are no longer off by 1 channel and I have not had any crashes of xlights while doing conversions.

Thanks to Sean, Dan and the xlights team for the quick fix for the Vixen Plus users.