pythan wrote:Bug??
The end channel number in custom models is not correct. I have 150 RGB channels listed on this model, yet it shows the start channel at 451 and the end channel at 492. As a matter of fact all my models show the same number of channels 41 regardless of layout. They all have more than 41 channels in them.
This will be fixed in version 3.2.2
Matt Brown
xLights Developer
Electrified3 wrote:A huge benefit would be able to copy and paste to/from Excel to nutcracker custom grid and vice versa, can mathematically fix this stuff quick in there and if you could copy and paste the re-calculated cells back and forth to the model would make changes so much easier.
Cut/copy/paste for the custom grid will be available in version 3.2.2
Matt Brown
xLights Developer
Electrified3 wrote:A huge benefit would be able to copy and paste to/from Excel to nutcracker custom grid and vice versa, can mathematically fix this stuff quick in there and if you could copy and paste the re-calculated cells back and forth to the model would make changes so much easier.
i have an excel worksheet that makes this REAL simple!
after you have your drawing the way you want it
scroll down to A75 and copy that one cell
make sure xlights is CLOSED
then open xlights_rgbeffects.xml (in notepadd++)
find the line with your custom item in it
in that line find "CustomModel=" and highlight and replace everything in the parenthesis marks"" with what you have copied from excel. [CTRL] V
save it
open xlights
your custom design will be there waiting for you
enjoy
if there are any issues or comments please let me know
K
The cut/copy paste would be awesome, I have been using the spreadhseet, works good, but would be nice to cut out the extra steps of the spreadsheet.
Is there any way the "Start Ch /End Ch" that shows up in the custom window can be looked at? From what I have seen so far it just takes the start channel and adds the (number of rows *3) for the total channel count. I have been thrown off by this a few times, a custom model with 70 rows x 48 colums just throws up start of 1 and end of 210ch if you set the start channel to 1 of course, but in my case I have 75 RGB's which would actually be 225 channels.
In some where I have 250RGB's in my custom model it would be nice to see how many channels the actual display is occupying and have it correctly configure the channels to RGB etc. It isn't a huge deal, just have to do the math off to the side to keep track of it right now since that part of the display is not quite right and try to correct it if converting to another format. If I set my 70 row display to 75 rows and just leave the rows not required empty my channel count seems to total up correctly and my rgbs configure correctly. Of course my 250 pixel custom means I need to set 250 rows but I may only be using 50 of them, but then at least my channel count adds up at the end, RGBs configure correctly to channel assignments and conversions seem to work then.
Not sure if this is an easy fix or if it could be quite complex with the multitude of configurations and channels a custom display could occupy.
Electrified3 wrote:The cut/copy paste would be awesome, I have been using the spreadhseet, works good, but would be nice to cut out the extra steps of the spreadsheet.Is there any way the "Start Ch /End Ch" that shows up in the custom window can be looked at? From what I have seen so far it just takes the start channel and adds the (number of rows *3) for the total channel count. I have been thrown off by this a few times, a custom model with 70 rows x 48 colums just throws up start of 1 and end of 210ch if you set the start channel to 1 of course, but in my case I have 75 RGB's which would actually be 225 channels.
In some where I have 250RGB's in my custom model it would be nice to see how many channels the actual display is occupying and have it correctly configure the channels to RGB etc. It isn't a huge deal, just have to do the math off to the side to keep track of it right now since that part of the display is not quite right and try to correct it if converting to another format. If I set my 70 row display to 75 rows and just leave the rows not required empty my channel count seems to total up correctly and my rgbs configure correctly. Of course my 250 pixel custom means I need to set 250 rows but I may only be using 50 of them, but then at least my channel count adds up at the end, RGBs configure correctly to channel assignments and conversions seem to work then.
Not sure if this is an easy fix or if it could be quite complex with the multitude of configurations and channels a custom display could occupy.
if i understand what you are saying..
you are getting incorrect channel counts when using the custom model. is that correct?
in your example - you have a custom model that is 70 rows x 48 columns
are you using every point in that grid?
if so, it may be easier to use a matrix fitting that grid.
if it is actually a picture (or image) within the grid
yeah i can add a function that will count the pixels that you have and add that to "string" you add to the XML file.
as for the extra steps, that i cant help you with.
i am not on the development team, merely an avid fan of nutcracker and when i see something i can do to help i generate what i can. sadly my "fixes" will probably not ever get incorporated into the actual builds - meaning that people that use my fixes will have extra steps to use them... - sorry
