What Determines SuperStar Row Order of Visualizer Fixtures

[Ed K]

I apologize for this duplicate topic here, but I had originally posted this comment in the Pixel Editor forum, but then realized immediately that I should have posted it in the SuperStar Sequencer forum.

 

I created a very simple set of four, 50 RGB pixel string fixtures in Visualizer only to understand how SuperStar display each fixture when I import the Visualizer file.

First, using the pixel string function in Visualizer, I created four sets of 50-string RGB fixtures, one each for my four eaves/rooflines.  From left to right, lets call these strings (fixtures) 1, 2, 3, and 4.   I don't think this matters in what I am asking about, but in Visualizer, I assigned these fixtures the following universes/pixels: Univ 1: 1-50, Univ 1: 51 - 100, Univ 2: 1 - 50, and Univ 2:  51 - 100.   None of these four fixtures overlap.

In SuperStar, I import this Visualizer file.  The fixtures in the bottom half of SuperStar are displayed in the correct order:  1, 2, 3, and 4.  However, in the top half where the rows are displayed for each fixture, the rows are in this order (top to bottom); 4, 2, 1, 3.

Why is that, and how do I change the rows so that they are in sequential order?  Heck, I'd take descending order (4, 3, 2, and 1).

 

[wbaker4]

Did you happen to cut and paste (copy) one fixture to another?  That happened to me.  I ended up creating each new fixture/prop rather than the copy and paste.

[Ed K]

No, I drew each of the four 50-pixel props by hand, using the pixel string tool in Visualizer. My four sets of eaves/rooflines have different shapes, so I just drew each one.

I saw Brian’s other post about this same issue, so I decided to try the solution he suggested.

I’m running Pro v4.2.12.

I opened my Visualizer file, and for each of the four Props (50 RGB pixel strings, one for each eave/roofline), I opened the prop, clicked on the SuperStar button, selected “No” in the “This is a SuperStar Matrix” drop-down list, clicked OK, and clicked Ok.  I did this for each of the four props.

I saved the file with a new name, and then imported into SS, with maximum detection lines set to 6 (for future props).  I get the same odd ordering of the four sequencing rows for my four props (top to bottom):  4, 2, 1, and 3.  Again, the actual props shown in the bottom area of SS are in the correct order (1, 2, 3, and 4).

I also noticed one other anomaly in the sequencing grid (again, four rows of 50 boxes).  For two of the props, the sequencing box order is the same as my pixel order:  1 – 50 (left to right in the sequencing row).  However, for the other two props, the order is 50 – 1 (left to right).

I made one more change:  In Visualizer, I also checked “Use My Order rather than SuperStar’s” in the SuperStar parameters area for each of the four props.  I saved as a new Visualizer file, and then imported into SuperStar.  I get the same result:  4, 2, 1, and 3 ordering of sequencing rows (top to bottom).  And, I get the same reverse ordering for two of the four 50-pixel props.

Then, I made one change to SS:  Imported with max lines set at 1.  The ordering of sequencing rows is now 4, 3, 2, and 1, but the props still show in bottom area in the correct order:  1, 2, 3, and 4.  The sequencing grid still has the same reverse ordering of boxes for the same two of four props.

[BrianBruderer]

When importing the visualization what is the sequencing grid "max length" set to? It defaults to 50 but I believe you will want to set it to 200.

Please email the visualization to brian@superstarlights.com and I will take a look at it. The visualization file will end with .lee and will be at

c:/ (your lightorama folder) / Visualizations / Editor

[Ed K]

It was set to the default 50. Thanks for the suggested change.   I changed to 200, and then imported the Visualizer file.  Now, I get one sequencing row, 200 pixels (squares) long, and the props are shown in the correct 1 - 2 - 3- 4 order.   Two of the four props still have a reverse pixel order. 

I'll email you my Visualizer file. You'll notice I assigned each string to its own universe, thinking that was a cause.  I'll change that back to grouping two props into one universe later (so, two universes).

I can live with a 200 box row for my four eave/roofline prop -- I actually like it because it lets me control the eave/rooflines as a single "prop" in SS.  It's a better tool for me, thanks.

My next incremental test will be to add a fifth prop (one window, with one CCR), and determine where that gets put when I import to SS.  As you know, it was adding props to my Visualizer in the past, which messed up the sequencing row order, that got me into Visualization pairs that you told me about (but, I digress).