Sequence builder for rgb targets. meighan.net/rgbsb

[AussiePhil]

Sean


Couple of feedback items for you.


1. I echo Kel, having this in metric would be good, centimetres may be the best single unit to use, us metric countries find it far easier to work in metres and cm.


2. LOR CCR or Lynx Smart Strings, I use neither and would like to see at least a Generic Intelligent Pixel selection.


Lets expand that a little.
The models so far seem based on a single LED (node) being a pixel, that is a single point of light.
The current options are
Intelligent Pixels were one point source LED = a Pixel. usually with 100mm (4") spacing
Intelligent Strip 36IC's per meter, One point source LED = a Pixel
Intelligent Strip 12 IC's per metre, THREE point source LED's = a pixel, in this case a pixel has a linear length of 83mm (about 3.5")


There are other possible combinations driven by hardware of course but the above covers most of the out of the box strings or strips.


Oh one other option for building the tree that needs serious inclusion is a continuous snake, in that the snake as you call it for up-down-up-down etc till you run out of pixels.
This year with some hardware firmware that is likely to come out very soon, i will be able to have a single data input to my 1344 Pixel tree, hence the term continuous snake.
Just flagging this as a possibility that will be available for people to wire their tree up.


Cheers
Phil

 

[smeighan]

could we pls have this in metric?

Sure. I will ask what units you will enter in the begining an dthen you just either enter everything in inches or in cm. Will that work.


I assume the americans could enter everything in inches and the rest of the world could use cm? I originally had tyhe form have a unit of measure on every prompt. The first oass of testers (all american), did not like having to click the unit. Get one of them wrng and the tree gets created wrong.


so how about
o inches
o cm


as a prompt at the very beginning?

 

[AussiePhil]

Sean


that would be great


in an cm that is


Cheers
Phil

 

[Superman]

Yes please Sean. the google converter could have a rest then.

 

[smeighan]

I know that I'm one of the few, but I decorate for many more holidays than Christmas. That being said, I wonder if you would consider as part of your long term plan some models using different shapes: a heart 2d/3d, a clover 2d/3d, a rainbow with a pot of gold, a flag, a tombstone, a pumpkin 2d/3d, a skull 2d/3d.


-Rimist (via Tapatalk)

Short answer is yes.




To handle these, I will either build a web page template or give the user the ability to upload their own file.


After a target gets made, there is a file that looks like this. The bottom center of a tree is 0,0,0, vertical axis is the Z axis
This is an 8 strand megatree, with 35 pixels each strand.


The file order is
ModelName String# Pixel# X Y Z


With this file, i can project all the effects so see so far on rgbsb. When you "create a model", you give me answers that allow me to build this physical tree.






# t1_88.dat
t1 1 1 0.000 0.849 116.605
t1 1 2 0.000 1.698 113.209
t1 1 3 0.000 2.547 109.814
t1 1 4 0.000 3.395 106.418
t1 1 5 0.000 4.244 103.023
t1 1 6 0.000 5.093 99.627
t1 1 7 0.000 5.942 96.232
t1 1 8 0.000 6.791 92.836
t1 1 9 0.000 7.640 89.441
t1 1 10 0.000 8.489 86.045
t1 1 11 0.000 9.338 82.650
t1 1 12 0.000 10.186 79.254
t1 1 13 0.000 11.035 75.859
t1 1 14 0.000 11.884 72.463
t1 1 15 0.000 12.733 69.068
t1 1 16 0.000 13.582 65.672
t1 1 17 0.000 14.431 62.277
t1 1 18 0.000 15.280 58.881
t1 1 19 0.000 16.129 55.486
t1 1 20 0.000 16.977 52.090
t1 1 21 0.000 17.826 48.695
t1 1 22 0.000 18.675 45.299
t1 1 23 0.000 19.524 41.904
t1 1 24 0.000 20.373 38.508
t1 1 25 0.000 21.222 35.113
t1 1 26 0.000 22.071 31.717
t1 1 27 0.000 22.920 28.322
t1 1 28 0.000 23.768 24.926
t1 1 29 0.000 24.617 21.531
t1 1 30 0.000 25.466 18.135
t1 1 31 0.000 26.315 14.740
t1 1 32 0.000 27.164 11.344
t1 1 33 0.000 28.013 7.949
t1 1 34 0.000 28.862 4.553
t1 1 35 0.000 29.711 1.158


t1 2 1 0.600 0.600 116.605
t1 2 2 1.200 1.200 113.209
t1 2 3 1.801 1.801 109.814
t1 2 4 2.401 2.401 106.418
t1 2 5 3.001 3.001 103.023
t1 2 6 3.601 3.601 99.627
t1 2 7 4.202 4.202 96.232
t1 2 8 4.802 4.802 92.836
t1 2 9 5.402 5.402 89.441
t1 2 10 6.002 6.002 86.045
t1 2 11 6.603 6.603 82.650
t1 2 12 7.203 7.203 79.254
t1 2 13 7.803 7.803 75.859
t1 2 14 8.403 8.403 72.463
t1 2 15 9.004 9.004 69.068
t1 2 16 9.604 9.604 65.672
t1 2 17 10.204 10.204 62.277
t1 2 18 10.804 10.804 58.881
t1 2 19 11.405 11.405 55.486
t1 2 20 12.005 12.005 52.090
t1 2 21 12.605 12.605 48.695
t1 2 22 13.205 13.205 45.299
t1 2 23 13.806 13.806 41.904
t1 2 24 14.406 14.406 38.508
t1 2 25 15.006 15.006 35.113
t1 2 26 15.606 15.606 31.717
t1 2 27 16.207 16.207 28.322
t1 2 28 16.807 16.807 24.926
t1 2 29 17.407 17.407 21.531
t1 2 30 18.007 18.007 18.135
t1 2 31 18.608 18.608 14.740
t1 2 32 19.208 19.208 11.344
t1 2 33 19.808 19.808 7.949
t1 2 34 20.408 20.408 4.553
t1 2 35 21.009 21.009 1.158


t1 3 1 0.849 0.000 116.605
t1 3 2 1.698 0.000 113.209
t1 3 3 2.547 0.000 109.814
t1 3 4 3.395 0.000 106.418
t1 3 5 4.244 0.000 103.023
t1 3 6 5.093 0.000 99.627
t1 3 7 5.942 0.000 96.232
t1 3 8 6.791 0.000 92.836
t1 3 9 7.640 0.000 89.441
t1 3 10 8.489 0.000 86.045
t1 3 11 9.338 0.000 82.650
t1 3 12 10.186 0.000 79.254
t1 3 13 11.035 0.000 75.859
t1 3 14 11.884 0.000 72.463
t1 3 15 12.733 0.000 69.068
t1 3 16 13.582 0.000 65.672
t1 3 17 14.431 0.000 62.277
t1 3 18 15.280 0.000 58.881
t1 3 19 16.129 0.000 55.486
t1 3 20 16.977 0.000 52.090
t1 3 21 17.826 0.000 48.695
t1 3 22 18.675 0.000 45.299
t1 3 23 19.524 0.000 41.904
t1 3 24 20.373 0.000 38.508
t1 3 25 21.222 0.000 35.113
t1 3 26 22.071 0.000 31.717
t1 3 27 22.920 0.000 28.322
t1 3 28 23.768 0.000 24.926
t1 3 29 24.617 0.000 21.531
t1 3 30 25.466 0.000 18.135
t1 3 31 26.315 0.000 14.740
t1 3 32 27.164 0.000 11.344
t1 3 33 28.013 0.000 7.949
t1 3 34 28.862 0.000 4.553
t1 3 35 29.711 0.000 1.158


.etc.


I will be crreating a chapter in the future manual, to talk to how to model other shapes besides a tree or grid.


Remember my original title for this tool "RGB Sequence Builder for Megatrees/Planes or any other arbitrary object"


that has been my architecture design


thanks

 

[smeighan]

Release a new target builder, now it allows inches/cm as a unit of measure.


On another thread, i said sometime this year i plan on supporting Google Sketchup as an input for the target models.This resulted in this threadHi;"So if I send you an .ipt or .dwg, that's cool?"it will be when i write the parser. i use google docs and have thought of expanding the places i can get a source file. i was thinking these three sources for target models.1) rgbsb builds the target model2) User provides and ascii file , they do all the work3) take google docs, dwg files .etc. Today, (1) is the only choice. I said i would look into google docs after i get some major milestones done1) Build targets using rgnsb, Mostly Done. Need to allow user to delete models they dont want and to edit an existing model2) Allow users to create effects into their library, In Progress3) Allow user to select from a pull down of effects from their library and also select a target, this week4) Produce an animated gof so user can see what that effect will look like on their virtual tree by next week5) produce xml files for sequencers, 2-8 weeks6) Create models for other rgb targets , maybe by june7) New effects, movies, snowstorms, fireworks i will do this as a break from (5) Write a user manual, before june9) Look to using a google docs file as a target summer, fallI am working on 2 & 3 now. I hope within the week people will be trying effect son their trees and seeingg the result on the web page.I expect #5 to take 2-8 weeks.,I want to be done with 1-5 by june.thanks

 

[smeighan]

Released new target builder code Feb 27This release now has1) editing (yeah!0. Click on a model name and it will laod the form, edit and save. Still dont have the ability for you to delte models.2) a unit of measure (inches or cm)3) There is a summary at the bottom for the form showing what sequencers the users want to support.4) Changed fields to light blue in form. I had a hard time seeing wher ei should type.5) Fixed bug where "Ho will you build your tree" = UP/DOWN 180 was not working.6) modified wording of this prompt.old: **Total number of Pixels on this string new: **Total number of Pixels on this string (Note, this is NOT the total pixels on your tree, just the count on one string): Some people had inputted the total pixel count of their tree. Sorry, if it was not clear.The hyperlink for editing was not complete and caused people to have a blank user name. I believe this is now fixed since editing should work.thanks

 

[Tallahassee Dreamer]

Does not seem to be working for me, when I hit save the page pops up again unpopulated. Message says no models saved. Am I missing something here?

 

[smeighan]

Does not seem to be working for me, when I hit save the page pops up again unpopulated. Message says no models saved. Am I missing something here?

I removed the message and pause that said target saved.


now when you save it , it shoyld come back and list your models. the most recent one should show up in your list.


pm your username to me and ill go look


thanks
sean

 

[Tallahassee Dreamer]

Working now thanks

Does not seem to be working for me, when I hit save the page pops up again unpopulated. Message says no models saved. Am I missing something here?

I removed the message and pause that said target saved.


now when you save it , it shoyld come back and list your models. the most recent one should show up in your list.


pm your username to me and ill go look


thanks
sean

 

[smeighan]

Hi all;


All of the original mega tree targets on the web page were 32 strands of lights, each strand had 35 pixels.
http://meighan.net/rgbsb/index.html


i am getting ready to release the next phase of rgbsb.


Phase 1) user can create a target modeling their tree. DONE
Phase 2) User will select from the effects classes (Spirals, Bands, text, Pictures, Meteors, .etc.) , customize the effect and save it in their private library. IN PROGRESS. Probably will be finished within next 7 days.
Phase 3) User select a target model and and effect and produces an animated GIF. IN PROGRESS, This is 75% complete, it will come one oine within next 14 days. This will be a big deal for the users. With this release you can try hundreds of effects on your tree and get a visual idea of what different effects look like. I think this ability to simulate your tree will be popular.
Phase 4) User now chooses to output their data into an xml file for the 3 different sequencers. 2-12 weeks.


I will also start writing a user manual when Phase 3 comes online.


So to give you an idea of what this might look like, i built a different target model. Instead of 32 strands x 35 pixels, here is effects projected onto a 48 strand by 60 pixel tree.


6 spirals, 100ms delay, only show front half of tree

The pictures, as expected, project with better clarity.

And finally, text looks better

thanks

 

[smeighan]

Question/suggestion:


Should "pixel size" be introduced into your model?


With the current visualizations I see these nicely done pictures projected onto a tree and I think "that's nice!" but I suspect when this is applied to my tree that the images may not be as recognizable. My reason for suggesting this? When I look at the nutcrackers I see one tree with a pixel size that is just as big as the gap between that pixel and the next. in another nutcracker, the is very little gap. i reality the smart pixels are about .39in... and the gap between pixels is 2.61in.


In a different element -- like a coroflake, the pixels sit behind corrugated plastic, and there is no "gap"... instead light from one pixel blends into the area of the pixels around it.


there are other coro examples -- like david moore's candy canes -- where pixels are segregated into separate compartments so that there is little blending/bleeding.


...in the coro examples we might define a pixel as a much larger visible area... maybe 3" circles or 3" squares.

yep, never any lack of tasks. We get one idea, it opens 3 more.


The answer is yes to all of your questions. They can be modeled more and more accurately. as Phase 3 of rgbsb (The ability to have your tree display your effects on an animated gif) comes online, I think people will want to use the tool to do some initial sizing.




So in gnuplot you can specify how big the dots are drawn (in world coordinates).


So i removed the background skeleton that i draw in gray. This was so people could visualize the tree.


Here are 4 images drawn in different dot sizes


0.3" dots

0.6"

1.0"

let gnuplot pick the default dot size

I dont think i can draw them exactly to size, because a gif images is not glowing like a light. maybe 0.6" is closest to real life?

 

[smeighan]

I have decided on a new name.


Someone in these threads made the comment that why not Nutcracker since it has special meaning to me. The nutcrackers that i built with my sons do have special meaning and since we have Vixen and Grinch, I have decided that the new name of my tool will be Nutcracker: RGB Effects Builder.


I have already created new favicons and released them onto the web page.


thanks everyone for the input.


Now, I need a catchy name for the class that I will give on the Nutcracker software at the Academy.
http://www.theultimateacademy.com/

 

[smeighan]

New release of target modeler. Many people were getting some of the prompts wrong.I have added logic to check ranges on a number of fields. I build a calculated tree given that you told me how long one string is. Your string is the hypotenuse of the triangle. If you are doing "UP/DOWN NEXT" or "UP/DOWN 180", i cut the hypotenuse in half.Still, Alpha. Tool may break, data may be lost. I did need to reset at least half of the models. I am backing up the user and model table every few days.so ...Please try to create 1 or 2 models.I have also removed these 3 prompts1)orientation (Where is the front of the tree . I will add this back in later this summer. really not needed for now)2) direction of rotation of strings , CW or CCW. Again this really does not affect us getting a model out. It will only affect if you want text scrolling right to left or left to right.3) Type of string, CCR or smart string. again , i may need to add it back this summer, but it does not affect generating sequencesThe secret to getting the model tool to work is to get the number of pixels per string and the distance between the first and last string correct. You can now let the tool calculate some of the other dimensions for you.Being RED on the tool is like the tool saying "I don't believe you but i will build the model that way". Your dimensions will always be used, not my suggestions.If people could give some feedback on my ranges1) Number of strings you will build a megatree from (1-100)2) Number of pixels on a string (40-130)3) Spacing between pixels (2-6" or 5-30cm)thanks

 

[joeengler]

Not sure if it is just me, but I have not been able to connect to the web site for the last 2 nights.