I'd love to contribute as well as keep it WAMP/LAMP. So far everything seemed to work (other than the install itself, and a couple other things) on my LAMP install. I'll keep track of anything I change (I'll put it in my own revision control to track things).
Thank YOU for this great project! I have many projects/hobbies, so I might return to lurk-only mode for a few weeks at a time.
Ok, I have a couple more questions... I need clarification on the following:
What is the difference between "Nutcracker Pixel#" (for column 3) and "User pixel" (for column 8)?
What is the difference between "Strand number" (for column 2) and "User string" (for column 7)?
My roofline configuration I'm trying to configure looks like the following:
_______33________ _____24____
| | |
| | |
|37 37| |38
| | |
| |___________|
|_________________| 27
33
I wrote some python code to generate the file based on what I *think* your target layout is. The code basically iterates on a multidimensional array. Each array is the bulb count, starting X/Y (which are translated to X/Z for the purposes of nutcracker's 2D projection) and a direction from that starting X/Y point. The direction is based on what direction the bulb count is as the string travels outward from the E681. Here is the code:
strings = [[ 33, 33, 38, 'w' ],
[ 24, 33, 38, 'e' ],
[ 38, 57, 1, 'n' ],
[ 27, 33, 1, 'e' ],
[ 33, 0, 0, 'e' ],
[ 37, 0, 0, 'n' ],
[ 37, 33, 0, 'n' ]]
count = 0
bulb = 0
for string in strings:
count += 1
(bulbs, x, y, direction) = string
for i in range(0, bulbs):
bulb += 1
if direction == "n":
_y = y+i
elif direction == "s":
_y = y-i
else:
_y = y
if direction == "e":
_x = x+i
elif direction == "w":
_x = x-i
else:
_x = x
print "TEST", count, i+1, _x, 0, _y, i+1, count, "Materdaddy", "TEST"
It generates a test file I redirect to a "TEST.dat" which I placed and generated some images for, however I don't think it's exactly what I'm intending. Here's a butterfly on this layout:

(If you're curious about the bulb counts being off, it's because certain segments of the roofline have "features" (like chimney) that the bulbs go around that I simplified for planning purposes.)
Materdaddy wrote:Ok, I have a couple more questions... I need clarification on the following:What is the difference between "Nutcracker Pixel#" (for column 3) and "User pixel" (for column 8)?
What is the difference between "Strand number" (for column 2) and "User string" (for column 7)?My roofline configuration I'm trying to configure looks like the following:
_______33________ _____24____ | | | | | | |37 37| |38 | | | | |___________| |_________________| 27 33I wrote some python code to generate the file based on what I *think* your target layout is. The code basically iterates on a multidimensional array. Each array is the bulb count, starting X/Y (which are translated to X/Z for the purposes of nutcracker's 2D projection) and a direction from that starting X/Y point. The direction is based on what direction the bulb count is as the string travels outward from the E681. Here is the code:
strings = [[ 33, 33, 38, 'w' ], [ 24, 33, 38, 'e' ], [ 38, 57, 1, 'n' ], [ 27, 33, 1, 'e' ], [ 33, 0, 0, 'e' ], [ 37, 0, 0, 'n' ], [ 37, 33, 0, 'n' ]] count = 0 bulb = 0 for string in strings: count += 1 (bulbs, x, y, direction) = string for i in range(0, bulbs): bulb += 1 if direction == "n": _y = y+i elif direction == "s": _y = y-i else: _y = y if direction == "e": _x = x+i elif direction == "w": _x = x-i else: _x = x print "TEST", count, i+1, _x, 0, _y, i+1, count, "Materdaddy", "TEST"It generates a test file I redirect to a "TEST.dat" which I placed and generated some images for, however I don't think it's exactly what I'm intending. Here's a butterfly on this layout:
(If you're curious about the bulb counts being off, it's because certain segments of the roofline have "features" (like chimney) that the bulbs go around that I simplified for planning purposes.)
Nutcracker has this internal coordinate system, rgb devices are made of strands that run from the top of your device downward.
a Nutcracker pixel starts at the top of each strand and counts downward. In other words any nutcracker pixel #1 is always the top of your rgb target.
String and user pixels are the physical string and pixel of your device.
say you had one string with 100 pixels.
you start it at the bottom of your tree, go up 50 pixels and then foldit and come back down. Your string will make 2 strands of 50 pixels each. Those 2 strands in Nutcracker space will be
Strand #1, pixel 1 is the top of the strand, pixel 50 is bottom
Strand #2, pixel 1 is the top of the strand, pixel 50 is bottom
so for the first pixel of your string
User Nutcracker
String Pixel Strand Pixel
1 1 1 50
1 2 1 49
....
1 50 1 1
1 51 2 1
1 52 2 2
...
1 100 2 50
Your pixture of the butterfly is probably what it is going to look like.
You take whatever you have and imagine making vertical stripes from left to right.
The first strand looks like it would have all 50 pixels, the second strand would just have pixel 1 and 50, .etc.
My effects are looking for pixels next to each other. They will work on yours, but i am not sure how good the effect will be.
Now if i were to make an effect that is a color chase and you then connect each line of your window to a strand, then you would get chases going around the window.
i like the discussion, we will see where it takes us. i am happy to make a chase effect class if you want.
What are the bounds/limits on the X/Y/Z planes? I tried a simple doubling of the values in my python script so the pixels are more spaced out than the demo GIF I posted and things are cut out of view. Do I need to keep it within a certain frame?
Materdaddy wrote:What are the bounds/limits on the X/Y/Z planes? I tried a simple doubling of the values in my python script so the pixels are more spaced out than the demo GIF I posted and things are cut out of view. Do I need to keep it within a certain frame?
i should be autoscaling.
you can see for this image

you can view the dat file for it by changing th gif to dat
i create 80 frames. The dat file for frame 80 is
http://meighan.net/nutcracker/effects/workspaces/2/AA+FLY_0_0_d_1.dat
to
http://meighan.net/nutcracker/effects/workspaces/2/AA+FLY_0_0_d_80.dat
givr mr ur login name and the effect name
thanks

