Jump to content
Light-O-Rama Forums

BrianBruderer

LOR Programmer
  • Content count

    2,537
  • Joined

  • Last visited

  • Days Won

    23

Everything posted by BrianBruderer

  1. I found the problem. The fix will be in the next release.
  2. BrianBruderer

    Morphing from On to Off

    I found the problem with the multi-color light strings. The fix will be in the next release. Thanks for reporting the problem!
  3. Thanks, I received the visualization files. I will look into it today.
  4. BrianBruderer

    Morphing from On to Off

    I know multi-colored strings worked at one time, but I have not tested that for a while. I will look into it later tonight.
  5. BrianBruderer

    Change in exported data using visualization mode.

    The problem does not occur when running S5. The problem only occurs if exporting intensity data from a sequence using a sequence that is using a visualization which is something you only do in S4.
  6. BrianBruderer

    Change in exported data using visualization mode.

    Good, glad it is working. The fix will be in the next release. Until then, anyone who needs the fix can email me.
  7. BrianBruderer

    Change in exported data using visualization mode.

    I found a problem in the export of intensity data when using a visualization. Send an email to brian@superstarlights.com and I can send you instructions on how to get a new SSEdit.exe and you can test to see if it fixes the problem you are experiencing.
  8. BrianBruderer

    Change in exported data using visualization mode.

    Thanks for finding and reporting the problem. I will look into the problem tomorrow or Monday. If I have trouble duplicating the problems I will have you send your visualization to me.
  9. BrianBruderer

    Issue with shockwave width when scaling up

    In the next release I will increase the limit of the message that tells you to enter 50 or less. As you indicate, it is an arbitrary limit, it will work fine with larger limits. I think I will increase it to 200
  10. You are very welcome. I forgot to mention, when you import the visualization, set "Max Detection Lines" to 36
  11. Attached is the completed visualization 36x36_matrix_dmx.lee
  12. Good! I will do the rest of the rows.
  13. Attached is a visualization for the bottom 12 rows of a 36x36 matrix. Copy it to: c:/ (your lightorama folder) / Visualizations / Editor Take a look at it and confirm this is what you want and I can do the remaining rows. 36x36_matrix_dmx.lee
  14. Other kinds of strings could be easier to make a visualization, but making the visualization using the CCPs with 2 - 100 pixel strings is doable. I can start making it for you, but I first want to make sure I understand how you want to do it. Are you planning on having the controllers in the middle of the two strings and have each string go outward from there? And you would probably need to do a "snake" pattern to cover all the rows. Is that how you plan on doing it?
  15. Hmmm, I can't think of an easy way to draw a 36x36 matrix using 100 string pixels. As you say, in the matrix wizard uses DMX strings of 170 pixels. So the only option is to use the Draw Pixel String tool as K6cc mentioned. You will need to draw each string manually and specify a Universe and starting pixel number. And there will be some strings that will be partial lines. And you will need to make each row be a Prop. And some rows will have two fixtures, and you will want to put the two fixtures into the same prop. This lets superstar know they belong together. And make sure the direction of the pixels matches how your actual display will be. For example if you have a controller that will be in the middle of two strings, you need pixel 1 to be the pixel that is closest to the controller for both strings and have the pixels increasing from there. the first string will be 36 pixels using Universe 1 and starting with pixel 65 (Prop name = Row 01) the second string will be 36 pixels using Universe 1 and starting with pixel 29 (Prop name = Row 02) the third string will be 28 pixels using Universe 1 and starting with pixel 1 (Prop name = Row 03) the fourth string will be 8 pixels using Universe 2 and starting with pixel 1 (Prop name = Row 03) It is hard to describe it all using words, It would be a lot easier to draw a picture. Let me know if the above makes sense.
  16. Even with the most recent release which is 4.3.26 the visualizer does not support 100 pixel LOR strings. But there is a workaround. Create your strings as 100 pixel DMX strings. You can then import them into SuperStar, create your sequence, then export it to the Sequence Editor. In the Sequence Editor you can add a Pixie device that has 2 strings, each of 100 pixels. Then you can copy/paste the exported 100 pixel DMX strings onto the 2 Pixie strings. Note that in S5 this will all be addressed. But in S4 that is what you need to do.
  17. BrianBruderer

    SS Keeps crashing - Could use some Advice

    Breeze emailed me a copy of the sequence he was using. To duplicate the crash I simply opened the sequence and clicked on the "Play All" button and it would crash. It turns out the bug happens because pixels in the scenes in the sequence extend beyond the 16 ribbons. This is a bug I found myself back in December and the bug is fixed on my computer and the fix will be in the next release. But until then, the workaround is to do the following: 1) launch superstar 2) open the sequence 3) click on the Tools menu and select "Layout", and change the number of ribbons to something larger like 30 4) click on the "scene" button on the toolbar. In the "Scene Setup" dialog box there is a list of the scenes. Click on top scene in the list. Erase any pixels that go beyond the 16 ribbons, then click on the "Modify" button. Do this for each scene in the list. 5) After erasing all the pixels that go beyond the 16 ribbons you can set the layout back to 16 and the sequence should now play without crashing Also, "Breeze" says he is a newbie, but the sequence he sent me is very good! Keep it up, and sorry you ran into this bug!
  18. BrianBruderer

    SS Keeps crashing - Could use some Advice

    Crash bugs are my highest priority to investigate and fix. The fact that you are using the demo version is not related to the bug. The demo version executes the exact same code, the only difference is that you cannot export your sequence. What version are you running? Send an email to brian@superstarlights.com and I can set up a time to remote into your computer and see what is happening.
  19. BrianBruderer

    SuperStar Questions - New to SS need some help

    In the long run you will want to go with S5. But for this year if you are comfortable with S4 then stick with S4. I am not authorized to say when S5 will be released, but you can use the beta now. The beta has bugs but it is functional and you could start using it now.
  20. BrianBruderer

    SuperStar Questions - New to SS need some help

    In S4 there are to use Intensity Data from SuperStar do the following: launch SuperStar Open the sequence Click on the Tools menu and select "Configuration". In your case since you are using E1.31 controllers you would click on DMX and then set the first Universe you are using, and the type of addressing you are using. Click on the File menu and select "Export to Sequence Editor". Select "Export in New Format (as intensity data)". Then select "Add Intensity Data to existing sequence" Click on Ok and when the file select dialog box comes up, select the sequence that you want to add the intensity data to. Launch the Sequence Editor Open the sequence that you added the intensity data to. You should see your main sequence and at the bottom you should a blue row that represents the intensity data exported by superstar. As for the purchased sequences, when you purchase them from my website at www.superstarlights.com you will get the .sup file and you can modify the .sup file if you wish and then you can export the sequence so long as you have the appropriate superstar license. If you do not have a superstar license then you can export the purchased sequences so long as they have not been modified. This is because the purchased sequences are special files that can be exported by any license level including the free demo version, but only if you have not modified them. If you modify them you can export them only if you have the appropriate superstar license.
  21. BrianBruderer

    Trying to understand the licensing for SS

    Yes you can.
  22. BrianBruderer

    RGB Arches controller location

    Sorry about that, what you are observing is a bug. The screen does not always "clean up" after itself. Whenever this happens, the workaround is to click on the "View" menu and click on the "screen" line that has a check mark on it. Doing that will force the screen to redraw and the spurious lines will go away.
  23. BrianBruderer

    RGB Arches controller location

    Glad you got it working!
  24. BrianBruderer

    RGB Arches controller location

    Hmmm, not sure why "Arch_1_line_4_50PixelArches.lee" is not working. It is working for me. I would be happy to remote into your computer and see what is happening.
  25. BrianBruderer

    RGB Arches controller location

    Attached are two visualizations. Copy them to: c:/ (your LOR folder) / Visualizations / Editor The first one puts each arch on a separate line on the sequencing grid. And the layout should match the CCR layout you are using except that there is a controller between 1&2 and a controller between 3&4. Note that the sequencing grid mapping is the same, in other words, you do not need to change your sequence. The reversal of the pixels for some of the arches is handled by the software. The second visualization has all 4 arches mapped to one line on the sequencing grid. For future sequences you may want to use this visualization. It is easier to do a morph across all 4 of the arches. When you import this visualization into superstar be sure to set the sequencing grid "max length" to 200 and set "horizontal" Arches_4_lines_50PixelsPerLine.lee Arch_1_line_4_50PixelArches.lee
×