queenidog wrote:Okay, I understand but it doesn't make sense... To me, a pixel is the smallest ELEMENT in a display, ie ONE LIGHT, just like a pixel is the smallest thing on my computer screen. A pixel is not (to me) a combo of 3 "things". An element, like in chemistry is also the smallest thing (well okay, atoms, protons, quarks are smaller) , so it can be one pixel, or one stepper or one servo. I'm okay with "universe" being a collection of elements, like a serial addressable LED string is a "universe". I would prefer the term "device" which is just "a thing" that can consist of one element or many elements. I like the way Vixen allows user to define a serial string as "elements can be any color, they are full RGB". There's no ambiguity there.
Thanks for replying, all of you.
Yes but the "pixel' on your computer is actually composed of three dots -- a red, a blue, and a green one, that can be mixed to generate millions of colors, just like the pixel lights used in Christmas displays only they are much larger and use individual LEDs for the 3 colors
A Universe actually comes from DMX lighting control, it is 512 channels, on/off/dimming. And since each pixel has 3 colors they require 3 channels to function so you can fit 170 pixels (510 channels) in a single universe
queenidog wrote:Okay, I understand but it doesn't make sense... To me, a pixel is the smallest ELEMENT in a display, ie ONE LIGHT, just like a pixel is the smallest thing on my computer screen. A pixel is not (to me) a combo of 3 "things". An element, like in chemistry is also the smallest thing (well okay, atoms, protons, quarks are smaller) , so it can be one pixel, or one stepper or one servo. I'm okay with "universe" being a collection of elements, like a serial addressable LED string is a "universe". I would prefer the term "device" which is just "a thing" that can consist of one element or many elements. I like the way Vixen allows user to define a serial string as "elements can be any color, they are full RGB". There's no ambiguity there.
Thanks for replying, all of you.
A pixel is far from the smallest element we work with. A pixel has a driver chip plus a tri-color led and each of those LEDs has an independent control channel. In vixen you could define down to the individual LED level. This is how Vixen 2 works and is what drives the explosion in the number of channels you need to manage. In V3 it is simpler to stop at the pixel level. Imagine this. My show has 14000 pixels. That is 42000 channels of information that needs to be managed. It is much simpler to apply an effect to the 70 props (upper level elements) I have instead of all of those channels.
I think you are getting the point that there are lots of definitions of elements. For example, if a prop is made up of single color strings of lights then the prop is an element (group of parts of the prop), each part of the prop is an element and is (most likely) a single string that uses a single channel on the output controller.
FYI: When you mark a leaf element as RGB can be any color, you are assigning three channels to it. You can see this by creating an element, highlight it, look at the number of patch points in the next panel to the right you will see a count of one. Now make it an rgb item, highlight it again and look at the patch count. It should be three
This brings up something I have always wanted to know. WHY is 170 pixels= 1 channel, ie 510. Why can't it be more then 170 pixels?? Why is it dedicated this way,example why can't it be 200 pixels in a channel?? What makes this finite??
mister softee wrote:This brings up something I have always wanted to know. WHY is 170 pixels= 1 channel, ie 510. Why can't it be more then 170 pixels?? Why is it dedicated this way,example why can't it be 200 pixels in a channel?? What makes this finite??
Simply put, it’s for the same reason there’s 12 inches in a foot. Someone made that decision a long time ago and now that’s how things are divided.
There are 512 channels in a universe. A universe is nothing more than a group of 512 channels. Why 512? Because that’s been the limit of dmx for decades, and that was retained in sACN for universal backwards compatibility.
Why 170? Because it takes 3 channels to drive a pixel. 512 is not evenly divisible by 3. So the greatest number of full pixels you can get in a universe is 170, and that uses 510 channels. Technically you can put 170 1/3 pixels in a universe. If you’re spanning multiple universes and using 512 channel universes, one pixel can span across universes.
How many 5” pieces could you cut out of a 1’ piece of stock? Two. But you still have 2” left over. If you had a 3’ piece, you could get seven 5” pieces out of it (not 6)
Sent from my iPhone using Tapatalk
mister softee wrote:This brings up something I have always wanted to know. WHY is 170 pixels= 1 channel, ie 510. Why can't it be more then 170 pixels?? Why is it dedicated this way,example why can't it be 200 pixels in a channel?? What makes this finite??
I suspect you mean to say 170 pixels = 1 universe.
The answer is: The two have nothing to do with each other. A universe is not aware of pixels and pixels are not aware of universes. They do NOT have a relationship to each other. A DMX Universe can deliver 512 channels of lighting information from a data source to a data destination. That's it, End of definition.
The limitation of 512 channels is a holdover from when 250Kbps serial lines were used to transport DMX data and a specific refresh rate was desired for stage lighting. That relationship resulted in 512 channels. When the E1.31 specification was developed it maintained that grouping and wrapped the channels from a serial line into universes. Ethernet can support many universes over a single cable.
When we use a E1.31 to transport pixel data, we find that a single E1.31 universe can transport enough data to drive 170.6667 pixels. If you want to use E1.31 to move channel data from a show player (data source) to a controller (data destination) you define enough universes to carry the number of channels of data the controller needs to drive your strings of pixels.
For example, In my show I use 22 E1.31 universes to deliver 11264 channels of data to one my F16s. Then on my F16 I assign groups of those channels to the string ports to drive my pixels. Notice that using a flat memory model like this means I don't care whether a pixel has some of its channels in one universe and other channels in another universe. As long as the data makes it to the controller in the correct order, all is good. The controller also does not care about the relationship between the pixels and universes. The controller sees an E1.31 universe as a source of 'N' channels of data that will eventually get used for something interesting. It just wants enough channels of data delivered to it to satisfy the needs of the string and serial output configurations.
