I have just been reading through some of the replies here and was absolutely dumbfounded. Once again I would like to refer to my original reply -
AWESOME STUFF :thup2::thup2:
Thank you a thousand times over Sean and Matt.
smeighan wrote:This process will get you to an exported file for whatever sequencer you are using
Is there any intention for the xLights and Nutcracker workflows to converge in future? It seems like this combined code forms the basis for a stand-alone sequencer (ie, hardware setup, create a sequence, create models for the props, generate multiple effects for the props, then schedule them all so the combined result becomes a full sequence).
I'm confused on why you would still need to export the results to Vixen or other sequencing software if you can create the effects/sequences and then schedule or play them back directly in xLights/Nutcracker.
don
Did I miss what the difference is between 3.0.0 and 3.0.1?
djulien wrote:Is there any intention for the xLights and Nutcracker workflows to converge in future? It seems like this combined code forms the basis for a stand-alone sequencer (ie, hardware setup, create a sequence, create models for the props, generate multiple effects for the props, then schedule them all so the combined result becomes a full sequence).I'm confused on why you would still need to export the results to Vixen or other sequencing software if you can create the effects/sequences and then schedule or play them back directly in xLights/Nutcracker.
don
It is a valid question. Original xLights was a scheduler with all the hardware support you need to play your show.
Nutcracker creates massive rgb animations.
What is missing? There is so much to sequencers. LSP has groups, Vixen 3.0 will have it. You can tweak individual pixels, cut and paste to the timeline (aka the spreadsheet mode). There s a tremendous amount of work to allow all of these features.
I have offered the nutcracker core effects to LSP, HLS,Vixen 3 and LOR. We need to discuss how that could work out.
My focus is to make a tool that fills a gap. Nutcracker is now pretty close to what you get with Madrix. Move slider bars, get immediate feedback on your effects.
Last year my entire show was created with Nutcracker and played by xLights. I never used a sequencer. But my show was missing lots of things. I had no beat highlights, individual timing effects for some of the DMX stuff. The audience didnt know that i had just an average show. This year i will add capabilities to nutcracker to do more.
I have no current plans to make xLights/Nutcracker as a replacement for say LOR or LSP. We are a tool to help you.
there is so much to do in the space i have marked out, massive rgb animations, that this year is full.
thanks
sean
battle79 wrote:Sean,Out of curiousity, do you have plans to implement an export to Vixen 3.0.4 (or whatever it get too soon) in the near future? given how vixen 3 handles channels (elements) is it even viable?
See it as something that would be useful now, but may end up unused given the direction some of the new effects are headed in vixen. (Don't think they have any plans for video ATM though)
Cheers,
Rowan
Yes. As soon as someone shares what the Vixen 3 file format is. I sure hope that it is NOT xml for the RGB data. Vixen 2.1 had it the best. xml for all data except the sequence data. That was in base64. On my 12,100 show, Vixen 2.1 loaded my show the fastest. Faster than HLS, LOR or LSP. LSP is really unfair until i can create a msq. The UserPatterns.xml is just painful because the file is so large.
thanks

