Hi All -
First time poster here...and first year with a lighting display. I must say...I've learned a huge amount by reading this and other forums. Thanks for all the discussion.
Also, Vixen 3 and Nutcracker have made me a hero with the wife. Thanks to everyone that has worked to develop them!
I'm running 700 technicolor pixels via an E-682, a few 10w DMX floods and some incandescent icicles via a Lynx Express. Pretty simple, but effective layered display. Ran out of time to get the mega-tree up. Will just have to add that next year.
Now to my question....
I've got 5 windows and a door on the front of the house that are outlined with pixels modeled as simple linear groups. So, of course, I can address Window-1, Window-2, Door, etc. in Vixen. That's all good...but I'd like to be able to address the sides of the rectangles (verticals) as linear elements themselves. That would give me the ability to model guitar frets or keyboard keys, or even create a histogram across the front of the house.
So, I've added some "vertical" elements and patched them to the appropriate output channels...and they display correctly. But, those outputs appear to become unlinked from the previously defined "window" elements. So, if I turn on the windows, the sides are not lit.
Is it not possible to "patch" multiple elements to the same outputs? It seems like "last patched" wins and prior patching is forgotten.
My windows are currently defined as groups of 36 pixels. Do I have to define left side, right side, top, and bottom groups first, and then build window groups from those?
I hope its clear what I'm trying to do. Thanks in advance for any advice.
btw - here are a couple videos of what I've done so far, so you can see the basic outline of the house.
Wizards in Winter - http://youtu.be/PYA82lF0W4s
Christmas Canon - http://youtu.be/sSaZ0Jw9acM
Thanks again,
pcb
I don't know the definitive answer about multiple elements to the same output. I've wondered that myself. BUT...
Element Grouping is so easy and you can definitely have one element in multiple groups and that all seems to work quite nicely. In the windows/doors example, you probably should define each side, top, bottom as a unique element and patch those elements to outputs. THEN define groups Window1, Window2, Door1, which are made up of the respective side, top, bottom basic elements.
If you have a basic element called "Window1LeftSide", that element can then be put in a "Window1" group as well as put in a "GuitarFrets" group. You can have groups of groups so all individual window groups (Window1, Window2, etc.) can be in a bigger group-of-groups called "AllWindows".
All this grouping can be changed and modifided without ever having to change any ouput patching as long as the "basic" elements never change.
matree wrote:I don't know the definitive answer about multiple elements to the same output. I've wondered that myself. BUT...Element Grouping is so easy and you can definitely have one element in multiple groups and that all seems to work quite nicely. In the windows/doors example, you probably should define each side, top, bottom as a unique element and patch those elements to outputs. THEN define groups Window1, Window2, Door1, which are made up of the respective side, top, bottom basic elements.
If you have a basic element called "Window1LeftSide", that element can then be put in a "Window1" group as well as put in a "GuitarFrets" group. You can have groups of groups so all individual window groups (Window1, Window2, etc.) can be in a bigger group-of-groups called "AllWindows".
All this grouping can be changed and modifided without ever having to change any ouput patching as long as the "basic" elements never change.
Thanks for this feedback. I didn't realize that elements could be in multiple groups. So, instead of making new elements and patching them to already assigned physical outputs, I just needed to copy the low level elements to additional groups.
I also found this discussion on another thread....
http://doityourselfchristmas.com/forums/showthread.php?33155-Patching-Mixed-Channel-Assignments
Thanks again. I'll try this out tonight.
pcb
Yes multiple elements can be patched to the same outputs. However this causes mixed results with the display setup form and how it shows you the patches. If you do this, it will certainly be patched both ways, but the display setup form will probably not display what you expect to see. On the other hand, if you use the graphical view, and select the elements on the left, it should show the patching chain properly to the outputs. But selecting the output channels and asking it to find the elements will probably only show you the first element that's patched to it.
Another down side to doing it this way is that you will end up with a filter chain for each element, as opposed to per controller channel. This is an unneeded waste in processing resources.
As matree mentioned. The better way to do this is to use the same element and copy it into multiple groups. This uses one element, one set of patching, and one filter chain, but allows that same sequencing flexibility of having the element in different groupings.
I'm trying to make the most of groups because its really one of the main powers of Vixen.
But I've been wondering if there is a performance penalty. How deep can I nest groups-of-groups without having to worry about performance? Or does every new level of groups take and hit where I should really try to minimize nesting as much ast possible?
For example, I've debated definine the most basic element as each single pixel and then patch it to the correct output port. Then this mapping would (almost) never change. I could group each pixel element into multiple different display elements and make all sorts of different display elements (trees, windows, frets, violin strings, piano keys..) out of the same pixels that could be members of many different virtual elements that I would reference different in different sequences without changing any of the patching or filters.
Effectively, this would completely virtualize my whole display unless I change the physical pixels and what ports/controllers they connect to.
