It is a great question and yes you could just use xLights/Nutcracker. In simple terms you would build your element (Matrix) and then use effects to do as needed with the element. You can then save it and use it in xLights scheduler.
That is really pretty much the ease of using xLights/Nutcracker. If I am wrong, I am sure someone will help both of us.
The reason you may see other people using xLights/Nutcracker and another sequencing program is history.
Example: I have been using Vixen for over 5 years. I have a significant DMX network of lights built over those 5 years (386channels). With sequencing times in my past being 3-5 hours for every minute of music, I have chosen to just add elements every year. When I first started with RGB the sequencing time was closer to 50 plus hours for very simple movements. Then Nutcracker came along and over the last couple of years it has been growing into a leading software. Even more true now that xLights has combined with Nutcracker. I now use xLights/Nutcracker to add RGB elements to my original vixen sequences. I then convert them back to xLights/Nutcracker to use in the scheduler. xLights scheduler is flawless for me and I have used it from its inception. Good luck and ask lots of questions. I hope this is not to confusing or off subject.
Not confusing at all, that pretty much summed it up for me. I don't do a show, all my stuff is generally homemade, but not synced (mechanically animated displays, animated wireframes, etc.). When I wanted to replace my incandescent countdown clock, I thought I would dabble int the pixel world as it opened up so many additional possibilities, and would be more expandable in the future. I have NO IDEA what I was in for! I don't want to not be expandable in the future, so I am trying to lay a good groundwork of knowledge and hardware now, but I also want to K.I.S.S. so as to not have too much overkill or complexity. A 50x13 matrix is not a small amount of channels, but it also is MUCH below the number use in a whole house display.
I sort of wondered if the holdover to the other tools was the people who did all the work in the past on Vixen (etc.), so that was good to clear up so I don't feel like I
have to use those other tools.
there are some people
aaron, dave,zach myself and i am sure others who just used xlights.nutcracker as the sequencer. this really works best if most of your show is rgb. all of us are in the 20-40K channel range. when the shows get large, the other sequencers bog down. I think HLS is another sequencer that can do large channel counts but i have not used it.
we owe matt brown a big thanks for designing the architecture for xlights/nutcracker in a way that it scales to such large channel counts. i had nothing to do with this. You can model and run 60K channel displays.
either xlights as a player or the pi player as a player both can play large channel count shows.
there are plans to make a master/slave pi player. give each pi responsible for something like 30-60K channels and then get another if you need higher channel count. we are targeting 100-120K channels as a use case. If we get it to work with that then all the smaller shows should not have issues.
we barely had anyone with more than 10K channels in 2012. 2013 saw dozens approaching the 20-30K channels. so to stay ahead of the curve we will work on the > 100K channels for 2014.
As far as the PC is concerned, the matrix will be the only thing in my show, so I will be ONLY RGB at this point (and I assume any additions in the future will be RBG as well).
One final question (for now, there will always be more!), you mention xlights and the pi player separately. I assume you are talking about the falconpiplayer. Wouldn't xlights be running on that? Or did I misunderstand that, and if you use the pi player, you use their sequencer?
Thanks everyone, you all have been very helpful for helping to get me up to speed!