Author Topic: Vixen 2.4.1 Import into xLights Phantom Data  (Read 4204 times)

Offline ericw

  • Newbie
  • *
  • Posts: 9
    • View Profile
Vixen 2.4.1 Import into xLights Phantom Data
« on: November 12, 2018, 09:56:14 PM »
Hello!

I am running Vixen 2.4.1 and xLights 2018.42 64bit. I do 99% of my programming in Vixen and only use xLights to add my P10 Tune To sign. This requires importing the Vixen data. This year I also have added Glow With The Show Mickey Ear control. These channels require short bursts of exact intensities, in which mostly work just fine. To complicate matters further, I use 9 DMX moving head fixtures that require all the pan/tilt/master yadda yadda information for them to properly function. My show controller is the FPP V2.4 on the RPi B+v3. I am constantly throwing it between Master and Bridge modes to test from local Pi, Vixen and xLights.

I know there is more than one way to import a .vix file. Either editable (preferred) or through a data layer. Problem #1 is that if I only do an import, my moving fixtures do not respond. It's like the required P/T/master data is being ignored by xLights. It is only when I import AND add the vix as a data layer, do they work. Which leads to problem #2. All of the sudden on my GWTS channels, there is this phantom data that appears to mimic a dimmer channel, duplicated across all 17 GWTS channels! I know the phantom data shouldn't be there because there is a nice long ramp if the data layer, where GWTS absolutely can not have a ramp on any channel. And the data layer and the imported effects do not line up at all.

Is someone able to help me sort this out? I can provide files if needed to test with. I feel like this is a unique situation due to the DMX fixtures rather than the generic Vixen tutorials out there.

Offline keithsw1111

  • Administrator
  • Hero Member
  • *****
  • Posts: 2733
    • View Profile
    • Kellyville Christmas Lights
Re: Vixen 2.4.1 Import into xLights Phantom Data
« Reply #1 on: November 13, 2018, 12:03:15 PM »
If you post me your files and make me a video that shows me how I can reproduce the issue then I will look at it.


Sent from my iPhone using Tapatalk