Author Topic: Need help converting to xLights from vixen3. Issues with import  (Read 6920 times)

Offline stampedeboss

  • Full Member
  • ***
  • Posts: 108
    • View Profile
I am trying to migrate from vixen3 to xLights for my 2016 show.  I am trying to migrate my existing sequences via vix, fseq without success.  I end up with nothing showing in my preview.

I have setup my network to match my vixen configuration including creating all the models with the same names and ports.  I have tried both windows and linux versions of xLights with the same results.  (FYI, reason for converting is I want to get away from having to use windows, the only use is sequencing lights.)

I have:
  • Open New Sequence and selected the appropriate mp3
  • Selected 50ms timing which matches both my fseq and vix (which I exported from vixen)
  • Selected the appropriate sequence file (I have tried both)
  • Click Done
  • Switch to sequence tab and select view (Have several setup, tried them all with same results)
  • Toggle Strings and Nodes on Models, click green render button
  • Nothing appears on the "nodes" just looks like solid black bars

I have also tried import with the same results.

Any suggestions,  I've watched every youtube video I can find, they are seem to be for LOR users.

Offline jnealand

  • Hero Member
  • *****
  • Posts: 1421
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #1 on: March 13, 2016, 03:32:01 PM »
I have never heard of anyone converting vixen 3 files.  AFAIK all vixen 3 users have done is to generate a fseq file directly from vixen 3.
Jim Nealand
Kennesaw, GA

Offline stampedeboss

  • Full Member
  • ***
  • Posts: 108
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #2 on: March 13, 2016, 03:40:36 PM »
I have never heard of anyone converting vixen 3 files.  AFAIK all vixen 3 users have done is to generate a fseq file directly from vixen 3.
You are correct, I created vix and fseq files for input to xLights.

Sent from my SM-N900V using Tapatalk


Offline Phrog30

  • Hero Member
  • *****
  • Posts: 1234
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #3 on: March 13, 2016, 07:19:33 PM »
I am trying to migrate from vixen3 to xLights for my 2016 show.  I am trying to migrate my existing sequences via vix, fseq without success.  I end up with nothing showing in my preview.

I have setup my network to match my vixen configuration including creating all the models with the same names and ports.  I have tried both windows and linux versions of xLights with the same results.  (FYI, reason for converting is I want to get away from having to use windows, the only use is sequencing lights.)

I have:
  • Open New Sequence and selected the appropriate mp3
  • Selected 50ms timing which matches both my fseq and vix (which I exported from vixen)
  • Selected the appropriate sequence file (I have tried both)
  • Click Done
  • Switch to sequence tab and select view (Have several setup, tried them all with same results)
  • Toggle Strings and Nodes on Models, click green render button
  • Nothing appears on the "nodes" just looks like solid black bars

I have also tried import with the same results.

Any suggestions,  I've watched every youtube video I can find, they are seem to be for LOR users.
Are you wanting to be able to edit the sequence after you import into xlights, or just import so it will play?

I used to use Vixen 3. When I was using I would export from Vixen 3 as Vixen 2.1. Then in xlights add this as a data layer.

I know this works. Let us know what your end goal is. We can go from there. If necessary, I can do a teamviewer session to assist.

James

Sent from my SM-G900V using Tapatalk


Offline stampedeboss

  • Full Member
  • ***
  • Posts: 108
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #4 on: March 13, 2016, 08:09:48 PM »
Yes I would like to be ale to enhance and rework in xLights.  My goal is to move away from Vixen and use xLights exclusively.   

I'm not sure what the issue is, I would be grateful for any assistance.

Sent from my SM-N900V using Tapatalk


Offline Phrog30

  • Hero Member
  • *****
  • Posts: 1234
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #5 on: March 13, 2016, 08:36:43 PM »
Yes I would like to be ale to enhance and rework in xLights.  My goal is to move away from Vixen and use xLights exclusively.   

I'm not sure what the issue is, I would be grateful for any assistance.

Sent from my SM-N900V using Tapatalk

Then using a data layer is out. You can't edit this.

You can import effects using a Vixen 2.1 file, but it requires you to map Vixen to xlights and I'm not sure how long that would take.  Also, I'm not sure how the effects are created. My guess is you will get a bunch of on effects at the node level, not at the model level.

I suggest you import as a data layer first, just to make sure you have things mapped 1 to 1. Then go from there.

I have one Vixen 3 file that I'm redoing in xlights, last year I imported as a data layer. It might be best for you to do the same.

Can you try the data layer and see what you get?

James

Sent from my SM-G900V using Tapatalk

Offline stampedeboss

  • Full Member
  • ***
  • Posts: 108
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #6 on: March 14, 2016, 04:33:46 PM »
My data layer ends up showing zero channels.  I have posted all the various files to my dropbox at the following url: https://www.dropbox.com/sh/anypp35pk6e8uml/AADNiW0Xs-Ff2QAdgpaBgd_xa?dl=0

They were too large to attach.  When I load the "saved" xml from the data import, it shows zero channels.

Offline Phrog30

  • Hero Member
  • *****
  • Posts: 1234
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #7 on: March 14, 2016, 04:54:15 PM »
My data layer ends up showing zero channels.  I have posted all the various files to my dropbox at the following url: https://www.dropbox.com/sh/anypp35pk6e8uml/AADNiW0Xs-Ff2QAdgpaBgd_xa?dl=0

They were too large to attach.  When I load the "saved" xml from the data import, it shows zero channels.
Can you take a screenshot of your Vixen setup?

James

Sent from my SM-G900V using Tapatalk


Offline stampedeboss

  • Full Member
  • ***
  • Posts: 108
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #8 on: March 14, 2016, 05:09:13 PM »
Certainly, I also included the export html file in the list of files.

Offline Phrog30

  • Hero Member
  • *****
  • Posts: 1234
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #9 on: March 14, 2016, 07:40:18 PM »
I took your files and created a data layer.  I'm seeing data.

James

Offline stampedeboss

  • Full Member
  • ***
  • Posts: 108
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #10 on: March 15, 2016, 04:23:31 AM »
Ok, I went back to zero and re-exported the files, it appears my originals were affected by a known problem in Vixen.

I'm now able to get a "data" layer imported.  Now on to the next problem, since my display is all pixels, each node has three channels.  On the import dialog, its a node, how do I import all three channels per node?

Offline Phrog30

  • Hero Member
  • *****
  • Posts: 1234
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #11 on: March 15, 2016, 05:09:01 AM »
Ok, I went back to zero and re-exported the files, it appears my originals were affected by a known problem in Vixen.

I'm now able to get a "data" layer imported.  Now on to the next problem, since my display is all pixels, each node has three channels.  On the import dialog, its a node, how do I import all three channels per node?
That one is over my head. It might be an issue with Vixen. If you looked at the video Dan did when he imported his hls stuff his dialog showed each channel and each node. For whatever reason Vixen only gives you the option for each channel.

Hopefully someone else may chime in on a solution.

James

Sent from my SM-G900V using Tapatalk


Offline stampedeboss

  • Full Member
  • ***
  • Posts: 108
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #12 on: March 16, 2016, 10:07:42 AM »
Can anyone provide guidance on importing RGB Pixels from vix sequences?

Model appears to only support a single channel in the import for a Node which has 3 channels.  I have confirmed that it will import one of the RED, BLUE, or GREEN channels but no idea how to import all 3.

I have tried just the Node name portion without Red, Green or Blue and nothing imports.  If I give it the full Node, eg: Megatree S1 Px 1 Green, the green items do import. An apparent concern is it appears to replace the color from the effect with a single color specified in the map.  While this makes sense for ac strings, it doesn't for pixels since color value may be anywhere from 00 - ff at different points in time,  I can tell the code is there since the data import properly displays the colors.  But not the import of which I can only figure out a single channel.

Offline Phrog30

  • Hero Member
  • *****
  • Posts: 1234
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #13 on: March 16, 2016, 10:14:27 AM »
Here's a pic of what is happening.  Instead of being able to map a node (which includes all 3 colors), it only allows each individual color/channel to be mapped.

I will create a Github ticket for this. (Ticket #499)

James
« Last Edit: March 16, 2016, 10:17:02 AM by Phrog30 »

Offline stampedeboss

  • Full Member
  • ***
  • Posts: 108
    • View Profile
Re: Need help converting to xLights from vixen3. Issues with import
« Reply #14 on: March 16, 2016, 10:46:30 AM »
Here's a pic of what is happening.  Instead of being able to map a node (which includes all 3 colors), it only allows each individual color/channel to be mapped.

I will create a Github ticket for this. (Ticket #499)

James

Thank you.