Messages

1

Bugs in xLights/Nutcracker / Re: xLights crash on render & DMX light beams not showing

« on: July 01, 2020, 06:56:14 PM »

I am having a hard time understanding what needs to happen in order for the model to function. I have added both a "Moving Head 3D" and a "Moving Head" under the DMX drop down in both 2D & 3D modes. And when I add a "Moving Head" in 3D mode and switch it's type to "Moving Head 3D" it doesn't even draw a fixture. In layout mode it shows a brown box and in sequencer mode, nothing is there. Also, in 2D the fixtures appear as a red box with an X in it.

2

Bugs in xLights/Nutcracker / Re: xLights crash on render & DMX light beams not showing

« on: June 15, 2020, 08:27:09 AM »

Here is a 2 minute screen capture explaining exactly what is going on. Also attached are the log files for this sequence. One thing I didn't mention in the video is that the crash on render is fixed. So my bug is now 50% fixed.

3

Bugs in xLights/Nutcracker / Re: xLights crash on render & DMX light beams not showing

« on: June 13, 2020, 09:23:30 AM »

I have downloaded .24 & rendered 4 different sequences now. The crash on render problem seems to be fixed. However, you are right. the DMX fixtures still do not respond. My models are shown as the "Moving Head 3D". IDK if that has anything to do with it. Even with that still broken, at least I can get back to doing some sequencing again! 

4

Bugs in xLights/Nutcracker / xLights crash on render & DMX light beams not showing

« on: June 12, 2020, 11:37:23 AM »

Hello!

xLights wants to crash on render. This has been happening since v2020.2. My only display changes from 2019 to 2020 have been going from a P10 matrix to a P5 matrix. Layout & Universe counts have been updated to follow suit.

Replication:
I open xLights (Currently 2020.23 x64), open my sequence, hit render, and wait. It almost gets to the end of rendering (like 90%) and then dies. No crash popup either.

I have also noticed from v2020.2 that while in the layout tab the DMX Moving Head 3D beams do properly show up, but neither the beams appear nor do the heads show they are locked into their positions during playback. It has me think this is due to the rendering fail. Even when clicking on any effect on any model, causes a crash with no popup.

These issues can be replicated on my sequencing computer and on my work computer.

Something tells me that my RGB_Effects is corrupt. The fear of starting from scratch is real y'all.

Thanks!

5

Do You Need Help? Post it here / Re: Phantom data appearing after render.

« on: September 24, 2019, 06:58:15 PM »

Ok. So I changed the GWTS model from a matrix to single line with 17 strings and 1 light per string. I shifted the relevant effects up into nodes 2-17 and dropped the effects on strand 1 onto node 1 and it worked!

6

Do You Need Help? Post it here / Re: Phantom data appearing after render.

« on: September 24, 2019, 06:28:34 PM »

Doh! 56 color palettes for a 90 second song? The conversion process from Vixen 2.1 was not kind. Didn't even think about the intensities being translated into colors instead.

As for the matrix of single color nodes, how would you have done it? I picked a matrix so the data would be more visible in the whole home preview. Single Line model?

7

Do You Need Help? Post it here / Re: Phantom data appearing after render.

« on: September 24, 2019, 01:18:15 PM »

Here are the XML & RGB Effects files.

8

Do You Need Help? Post it here / Phantom data appearing after render.

« on: September 24, 2019, 09:49:57 AM »

Hi all!
All my sequences began in Vixen 2.1 and were migrated to xLights last year. I had to use both the "import as data layer" and the "import as effects" functions in order for my display to behave correctly. This year the .vix data layer is long gone and I am editing my sequences for 2019. The biggest issue is my Glow With The Show controls. I have 17 channels that require exact intensities, and after rendering a whole ton of information & wrong values appear.

In the first picture is a fresh startup of xLights & load of the sequence. Everything looks good and all intensity values look correct at the Strand level. In the second picture I had just hit the render all button and all this new information appears at the Node level. Some of this new stuff even has incorrect intensities between the Strand and Node levels further corrupting the GWTS data.

Following a suggestion I found somewhere, I deleted the .fseq file and made sure the render mode is not in canvas. No change occurred. I don't understand where this "phantom" data is being read from.

On top of that, every single one of the On effects in all my sequences say a starting intensity & ending intensity of 100% when it is very obvious that the actual data being outputted to lights is not 100%.

Ideas?.

(And yes I still use Winamp, and I'm proud of it!  )

9

Vixen 2.x, Vixen+ / 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.