Sean Meighan
Software => Bugs in xLights/Nutcracker => Topic started by: dwetzel on June 26, 2015, 03:46:58 AM
-
Is there a reason why you can't set the start channel above 99,999? I have a matrix 128 x 256 and the channel numbers grows real fast. If I start my models with this I can't finish setting all the start channels due to the limitation. My work around was to do the matrix last so the start channel is below this limit.
-
no one has ever asked this. ill look into the code, but why not put all other display elements first?
If you have 50000 channels of other stuff and start your 128x256 at 50001 it works. in fact you can have nearly 100,000 stuff and still get it to have a starting of channel of 99,999.
do you have two 128x256 matrixes? This would not work with current code.
when i started xlights/nutcracker a few years ago i never thought i would hear someone say we ran out of address space with our current 199,998 channel range.
the new p10 panels are probably going to drive channel count higher and higher.
again thanks to dave pitts and capt murdoch for making hardware that can drive these high channels (Not! lol)
http://falconchristmas.com/forum/index.php/board,51.0.html
Also ronp has made a controller that can drive the p10 panels.
i look forward to some videos this year from those of you using p10 panels.
-
Yeah I've never seen that part of the code that might be imposing that limit. But even if things work with all this in one sequence you may find it more pleasing to sequence by putting that matrix into a sequence by itself.
-
It is also crashing when I save. I am using 4.1.8. Here is my Excel channel listing. I did put the big matrix last for start channels, I also have two matrices a smaller one 64 x 128 for my Tune to sign. I am using BeagleBone Black and Octoscroller with Falcon Player to drive each of the matrices. Each one can drive up to 64 16 x 32 panels in the matrix. I have the 54 x 128 working and I will have to get a video of it and show off. I hope the save issue is easy to fix, I did the channel setup with 251 universes, set the save folder, built the models, went to create new sequence, added text effect to smaller matrix and saved. It just sat there no saving but curser moves and you can select shutdown. You get a warning about losing unsaved data and that is it, you have to use Task manager to close it down.
-
Oops version 4.1.18
-
it will be interesting when we start supporting P5 and P3 panels. will they be able to support a 512x256 matrix or higher. It does get to the point that dmx addressing on these panels is not the way to go and we need to use other technology such as DVI for the panels.
-
If use FPP running on a beagle bone. No data goes out e1.31 or dmx. Get a frequent file then the data is pumped to the octoscroller. No data on Ethernet. With huge channel count you prob don't want to pump it out serial lines.
Same when I use the falcon fpd connected to raspberry pi via a ribbon cable.. No network traffic when running my 24k channel show
-
Well it doesn't sound like you got a crash because you were still able to operate the program. I think there are a few things we haven't gotten locked out while its saving and if you start clicking on things it can screw up the save. So for saves that take an ungodly amount of time like having 251 universes I imagine it increases the chance that the user gets impatient and starts clicking around.
-
I'm sure it is pushing some limits. I just noticed after I clicked on save about 3 hours ago, as the mouse hovers over the exit "X" there is a brief message that says "Export only channels associated with one model" Does that mean anything? I removed the big matrix model and then saved, but still no change.
-
I would guess that the FSEQ file size would be increasing as the render/save happens. If it is the same size for more than 10 minutes I would think that the process has stalled.
Sean, Gil ?
-
I opened the same sequence. reduced the universes to 60, then saved. it was ok. Went to layout tab checked models the changes were all saved. Went to sequencer tab there is only effect on the smaller matrix (scrolling text). then clicked on the save icon at the top of the page. You are right it doesn't crash it just hangs.
-
Sean, you are right about no traffic when Beagle is running FPP, But don't you still have to build models and universes and sequence to get the fseq file? Am I doing something I don't need to?
-
There is a xLights_dbgrpt in the show folder, it is zipped .
-
Sean, you are right about no traffic when Beagle is running FPP, But don't you still have to build models and universes and sequence to get the fseq file? Am I doing something I don't need to?
Let's say you have a Master FPP and 3 slaves. When the Master is scheduled to play "Merry Christmas.fseq" it will send out the necessary data to the slaves to also start playing "Merry Christmas.fseq"
There is nothing requiring the versions on the Slaves to duplicate all the models from the Master or other slaves. The file name and sequence length just needs to match so the start and stop together.
-
does this mean that you would create a separate sequence for your matrix panels running on the slaves, with its own models?
I can see that having a large matrix panel I may well want to split it up into areas and the models for these areas would do this.
-
does this mean that you would create a separate sequence for your matrix panels running on the slaves, with its own models?
I can see that having a large matrix panel I may well want to split it up into areas and the models for these areas would do this.
It means you COULD create separate sequences. But, again, to be started and stopped by the Master, the file names and lengths (time, not file size) should match.
I seem to remember there is some "file naming logic" built in for Master/Slave control, but I don't remember off the top of my head. An exact match would be pretty easy, though. Confusing, maybe. :P
-
As we start to add those large P10 matrix's with 256*128 (98304 channels) or greater with P5/P3 panels it makes sense to me to run it from a BBB with octoscroller cape by itself and not clutter up your main sequence for your other models. I tend to sequence each model anyway. I guess the only drawback would be in your preview window in that you will not see your matrix and other models together in the same sequence.
-
There is a xLights_dbgrpt in the show folder, it is zipped .
I've seen that type of crash a couple times now. It's strange because it looks like it's crashing trying to re-enable one of the play buttons on the toolbar. Not sure how that can fail.
-
Did the crash occur after the save button was pressed , and if so could it be possible that the save to the fseq is still in progress, the buttons still protected and then the enablement attempted ?
The vast majority of my crashes or xl hanging is when save is being done , but in almost all cases the xml is fine and a subsequent save is okay. There is only one seq where the save still fails.
-
Sorry for the late response. yes I pushed the save and waited quite a while (30 min) and then closed out with task manager.
-
The xml was ok except no sequence. I couldn't get it to save until I started over with a fresh setup with 60 universes and redo the models without the 128x256 matrix.
-
As we start to add those large P10 matrix's with 256*128 (98304 channels) or greater with P5/P3 panels it makes sense to me to run it from a BBB with octoscroller cape by itself and not clutter up your main sequence for your other models. I tend to sequence each model anyway. I guess the only drawback would be in your preview window in that you will not see your matrix and other models together in the same sequence.
With more and more folks using the P10's like this, I'm wondering if we need to do two things:
1) 64bit Windows builds. P10's suck up a lot of channels.
2) A "null" output that can reserve a massive number of channels on the setup page, but not actually output anything if output to lights is on. For sequences that will run from the BBB, we don't REALLY need 20+ universes defined.
-
Both sound good
-
I feel so insignificant with only a 160x96 matrix. :)
I need a bigger house!
-
There is nothing requiring the versions on the Slaves to duplicate all the models from the Master or other slaves. The file name and sequence length just needs to match so the start and stop together.
So , on the FP of the BBB with the octo, you would define only the channels pertaining to the matrix and not all of them ? Making sure that the channel numbers were the same eg start at say 8000 , nnnn channels and nothing else ?
Currently I have defined them to exactly match those XLIGHTS ie all universes.
-
no one has ever asked this. ill look into the code, but why not put all other display elements first?
If you have 50000 channels of other stuff and start your 128x256 at 50001 it works. in fact you can have nearly 100,000 stuff and still get it to have a starting of channel of 99,999.
Hi Sean - did this ever get changed? I want to make sure I'm hitting it and it's not just some artifact from me switching back and forth between xl 3 & 4.
Daryl