Sean Meighan
Software => Bugs in xLights/Nutcracker => Topic started by: VBryan on March 03, 2019, 10:56:07 AM
-
Not sure if this is a bug or just a lesson learned. I have a short sequence (50 sec long) to introduce each song in my program. I was doing a butterfly effect on the whole house and thought I would try to put the kaleidoscope effect over the butterfly to see what it would look like and the render time went from 9 sec to 1.5 hours. The .fseq file is 11 Megs ( up from 547 K with just the butterfly) and the .xml file is 20 K.
-
If you are using compressed fseq files than butterfly will expand them. As for the render time blowout I would like to see your files.
Sent from my iPhone using Tapatalk
-
Here is my .xml file
-
There's definitely room for some algorithmic improvements to Kaleidoscope. I did some traces through and on my whole house group, it loops through every pixel of an 600x400 buffer 400 times for each frame. Takes a long time. For a simple improvement, I've updated it to use a parallel_for so it will at least use all the cores you have in your machine. That's a big help. However, I do want to look at this a bit closer.
Another issue with Kaleidoscope is that it requires Canvas mode. That's another area that is expensive. I also updated that to use a parallel_for so the next build should improve a bit (assuming you have a bunch of cores in your machine).