A proposed sequence builder for rgb megatrees. meighan.net/seqbuilder/index.php

[smeighan]

New release meighan.net/seqbuilder/index.php

This version has some more documentation in the header of the webpage.

I added a new column with half of a mega-tree. I basically took a 16 segment tree and built only the front half.

Web page will load faster now.

I also checked the web page on my ipad safari browser, it works fine.

thanks
sean

[Rod R]

Sean,

My hats off to you you're really banging away at this.   

[sebjsan]

When i get to RGB i will have you tho thank Sean. Keep up the great work.

[smeighan]

Copy of a thread from the LOR forum. I am looking for input from Vixen, LSP and LOR users for the tool. I will occasionally cross post.



Thanks. I am putting in the forms that will allow you to vary the math models now. I just  created a new model for doing what you describe. I now have a model for rotating the spirals both cw,ccw
Example:
You will be prompted:
Math model? Spirals on a cone
Number of Spirals? 3
Size of Cone? 10' high, 5' diameter
How many steps to rotate thru 360 degrees? 36 (so 10 degrees per rotation)
Direction of rotation (CW,CCW)? CCW
How long for one full rotation? 6 seconds
What target to project on? 16 segment mega-tree

The web page will then calculate the model and the target. With 36 steps there will be 36 output target X,Y,Z objects created. It will calculate the delay between rotations as
delay per rotation = 6 seconds/36 steps
delay per rotation = 166 ms
I believe i then need to round this to the nearest time quantum. So if you have set the time quantum as 50ms, i would delay each rotation as 150ms.

I should have this all working by next week and released.

To Do:
1) Get models with a form prompting all parameters for source and target models.
2) get the xml outputs working.
3) Modify the matching logic to be better for the bottom of the megatrees
4) Create a new orthographic projecting matching routine. This will be especially good when projecting on to flat walls
5) Create the models for snowflakes, garlands
6) Allow icon files (*.ico) to be used for projection
7) Allow users to input their own math models and targets
Document all of this.
9) Get code setup on sourceforge so can have more users help in the development
10) Setup MySQL database to store individual users setups. A user will not want to tell me their mega-tree specifics more than once.

In my spare time ....

thanks
sean



[user=15014]gizmomkr[/user] wrote:

Verry cool - nice work. Not sure if you found your xml answer yet, but I would love to see it when its outputting a lor friendly XML.

(I'd REALLY love if lor built the "math" in so objects like trees and other high channel counts were shown as a single item and could be modified as such.

I THINK there is a basic tree wizzard... but I hate that if I want to do something like just make it spin faster, I have to erase the timing grid and start over.

IF lor put the math into the code, then one day when I want the tree to spin faster, I just have to turn a knob - instead of re-making a whole section of sequence.

But still - verry nice work. Kudo's

BTW, i also posted the link to the Nutcrackers on the rgbsb main page.  These are the 9' tall nutcrackers my sons and I made. We plan on putting lights on them next year.

[smeighan]

I have added a poll to the this thread. I plan on writing the code for outputting to all three, LSP,LOR and Vixen. I need to decide which one i do first. The poll will give me a direction.

I have already written parsers that can read Vixen and LOR. I am working on the routines to write the output xml now.

I believe i should be working on the production versions for these.
Vixen 2.1.1 instead of Vixen 2.5 or 3.0. I don't know if the xml files have changed.
LOR S2 instead of S3
LSP V2.0  (corrected from thinking v1.8 was latest)



thanks
sean

[holland lights]

I voted for light o rama s3 because i can import that into lightshowpro 2.0. But what about lightshowpro 2.0?

[tng5737]

current LightShowPro is v2 not 1.8   Anyone using 1.8 ought to upgrade as the performance  and bug fixes are significant

[smeighan]

Thanks, I added v2.0 to the poll choices

sean

[smeighan]

Now that i am writing the output code for XML. It would really help if i could get a small file for
Vixen 2.1.1, 2.5 and 3.0 and LOR S2 and S3

Here is what i would like:
On whatever device you have  a string of RGB pixels,
1) Turn on Pixel#1 RED for 1 second
2) Turn on Pixel#1 GREEN for 1 second
3) Turn on Pixel #1 BLUE for one second
1) Turn on Pixel#2 RED for 1 second
2) Turn on Pixel#2 GREEN for 1 second
3) Turn on Pixel #2 BLUE for one second

Send your LMS,VIX,MSQ file that has this 6 second sequence to me at You are not allowed to view links. Register or Login

This will speed up my output routines.

It looks to me that
LMS(LOR) will be the easiest to code, followed by VIX (Vixen) and finally MSQ (LSP). Does anyone have a code snippet for reading MSQ binary files? For LSP i may just have to produce LOR S2 files since LSP can import those

thanks
sean

PS; A side affect of this code is that i may end up with a converter between all of these file types, who knows?

[smeighan]

I found a thread saying lsp *.msq files are xml files that have been compressed with 7-zip. I took and msq and ran it thru 7-zip. I do see the xml file.

So i need an msq file withe the two pixels set to three colors as requested above.

thanks
sean

[sirloinofbeef001]

This is gonna be great....... Im gonna need all the help I can get considering I still dont know why the chicken crossed the road...

[Rod R]

This is gonna be great....... Im gonna need all the help I can get considering I still dont know why the chicken crossed the road...

That one is easy to get Blinky Flashy

[RJ]

This is a great project and I am looking forward to having it to help.

RJ

[smeighan]

I have gotten the first XML file to load without errors for LOR. Their XML format was easier for me than Vixen. I think Vixen will be next

Can someone tell me the number of pixels and lengths that you would be using. My current target trees have pixel #1 at the top of the tree. I am adding three new target models to support LOR
1) Wedge
2) Edge to Center
3) Up and over

These topographies could be used by anyone, they are just saying how you string your lights on the tree.

I think I read a smart string as 127 lights and 27' long?

I need to create target models knowing the physical dimensions.

Please reply with any strings you would be using

I think in LOR they have 50 pixels on a string, I have asked what the length will be

On my trees, I plan on cable tieing the lights to a rope and set spacing something less that what the wire is. This will relieve strain and give me a reliable grid.

Fr example if a smart string is 127 pixels on a 27' length then the spacing is 2.55" apart.

So please reply with the number of pixels and string length so i can make sure my web page can model all.

thanks
sean

[Steve Gase]

I have gotten the first XML file to load without errors for LOR. Their XML format was easier for me than Vixen. I think Vixen will be next

Can someone tell me the number of pixels and lengths that you would be using. My current target trees have pixel #1 at the top of the tree. I am adding three new target models to support LOR
1) Wedge
2) Edge to Center
3) Up and over

These topographies could be used by anyone, they are just saying how you string your lights on the tree.

I think I read a smart string as 127 lights and 27' long?

I need to create target models knowing the physical dimensions.

Please reply with any strings you would be using

I think in LOR they have 50 pixels on a string, I have asked what the length will be

On my trees, I plan on cable tieing the lights to a rope and set spacing something less that what the wire is. This will relieve strain and give me a reliable grid.

Fr example if a smart string is 127 pixels on a 27' length then the spacing is 2.55" apart.

So please reply with the number of pixels and string length so i can make sure my web page can model all.

thanks
sean

48 strings of 85 in a tree...  node #1 starts from the bottom and goes straight up to the top with #85 (no folding)
the back of the tree starts string #1 and the strings are numbered in counter-clockwise order -- as you look at the ground.  so the front center is #24.
The trunk of my tree is 20.53'  the string length is 21.5' and the radius 6.36'
These are smart string pixels, and they are 3" apart on the strings.


btw, the smart strings can be up to 128 nodes (aka pixels) long.  Pixels on the strings are 3" apart.  The length can be up to 32' long.