Jump to content
Light-O-Rama Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About LightshowNoober

  • Rank
    New Forum User

Profile Information

  • Location
  • Occupation
    Field Service

More About Me

  • Favorite Decorating Holiday?

LOR Software

  • LOR Software Version
  • License Level

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks Ebrown. Unfortunatley that didn't work. I think I did it correctly and here's a screen shot of the destination height and width. Any other thoughts? I think I could always run it as a sub-sequence, or export the intensity data once I've created playback files. I was hoping for an easier solution. Megatree S5 Issue1.pdf
  2. Hello everyone. I've got an issue w/ S5 and I'll try my best to explain it. I've also attached a file to see what it's doing. I have created a 180 megatree prop for my megatree. The megatree I have is a 180 degree tree, 16 strands w/ 100 pixels in each strand. I do have a pro license level. I created a sequence two years ago in SS and I used to export the intensity data into my S4 files but I know that S5 can do SS effects w/o doing the intensity data export and the effects ran fine during the show. When I'm in S5, and adding an effect to the megatree prop line, it will open Superstar (as normal). Once SS opens, I then open and click on the sequence that I want to have on that line and it inserts fine. The problem is w/ the playback on the viewer. All of the effects I created in the original SS file were done w/ the 100 pixel option and done in full mode. Using the insert SS effect in S5 gives a message that it changes everything w/ colors over 100 down to 100 and I"m not sure if this is why it only plays the effects on the upper half of the tree? Also, the configuration option in SS is not allowed when using the insert SS effect into S5. Any help would greatly appreciated. Thanks in advance! Megatree S5 Issue.pdf
  3. K6, I am exporting from Superstar into existing SE files as intensity data. I'm not using S5 this year. I'm using 4.4.2
  4. Hello everyone, I'm hoping that someone can answer this one cause I can't figure out why this is happening. I'm getting a very "glitchy" effects on my megatree, which is all done in Superstar for this year. I've run a test sequence through Pixel Editor to see if i get the same glitch and the PE effects come out nice w/ no glitching. My mega tree has 16 strands of 100 pixels in each strand. I have the 40CCR Pro license level on S4, 4.4.2. i am using the enhanced network speeds. The Superstar configuration is set to 100 pixels, and the Pixie16 controller is also set to 100 pixels. I save the intensity data into the original SE file to keep the file sizes down as well. The firmware version is 1.01 and unfortunately I have to ship these into LOR to get the firmware updated as the HU won't do it on the particular model of Pixie16 i have, but i can't do that till after the holidays. I'm not sure if the firmware version is the issue or not but i'm hoping a Superstar expert can help me w/ this issue. I don't have any videos to post yet but will soon if need be. Thx in advance.
  5. Good idea! i'll do that and maybe Brian may have some insight. Thx Orville!
  6. Hey Doc, I've updated mine too and i'm using 4.4.2 now but still have the same problem. It could be that my Pixie 16 firmware is not up to the latest due to my Pixie16's being two years old and LOR has to have them shipped in for them to manually update the firmware as it cannot be done through the HU w/ those particular boards. Either way, i'm hoping someone can answer the glitchy cause it only happens in Superstar. Pixel editor effects still come out nice and smooth.
  7. Aidan, I've had this same issue. I'm using a Pixie16 to control my mega tree. It does have a "glitchy" and almost strobe effect at times during every sequence. I hope someone can give us an answer.
  8. So what was the solution to this? I am receiving the same error now when I try to create new props using Holidaycoro wreaths. Each wreath has 54 nodes and three "rings". I'm using one long strand to populate the three rings and when I try to save it, I get the same error message.
  9. Very interesting to know and thank you! Well I hit a snag...I've been using the visualizer to try and create my mega tree, but it too is limited to only 50 pixels per strand. You mentioned my license isn't enough for my tree? Do I need to get the 40CCR upgrade? What's weird is I can do that many in PE, but as you know the effects aren't as good so I may have to do that for this year. Uggh. lol. I appreciate the info though. I'll look into upgrading as well. Thx again!
  10. I did set it up in CCR mode so I'll try it again w/ the Visualization mode, although I need to do some more learning on the Visualizer. Do you have to import the visualization file into superstar in order to get more than 50 pixels/strand to work? I've downloaded the new S5 beta but I haven't had time to experiment w/ it yet. Thx K6! I do appreciate your help!
  11. K6, I cannot get the Superstar to control more than 50 pixels per CCR so that's how I know. Here's my setup. I'm putting in a 10' megatree this year, with 16 strands of the bullet LED's. Each strand has 100 pixels in it. I also have the pro level license and can control up to 24CCR's with Superstar. I'm using a Pixie16 to control my tree, and i've set the parameters in HU to do 100 pixels and I can get all LED's in each string to light up in HU. I can also get them to work using effects in PE, but I want to use the morphs and other tools from Superstar for my tree effects. When I create test sequences and merge the intensity data, and then play the sequence, only half of the LED's on each strand light up. Any suggestions I might try?
  12. Hello all! I've looked through most of the threads under S5 and I haven't seen the issue of Superstar only controlling 50 pixels being addressed. i haven't got the beta yet and I'm going to wait until it's full release so I don't know if this issue has been fixed. Will the new S5 Superstar control more than 50 pixels?
  13. Thx Matt! I've read that article and I must have missed the section on page 13 that says "leave start circuit set to 1". I've tried the sequence again w/ these changes and it works fine now. Thank you!!!
  14. Matt, thx for your reply. I thought the starting circuit refers to the physical "port" on the Pixie16. Does the starting circuit refer to the first pixel instead?
  15. Hello all, I've got a weird issue I cannot figure out and I'm hoping someone has some insight. I've created a test sequence in both SE and PE and created simple effects for my props. Every prop seems to work w/ the exception of three stars. I'm using Pixie16 controllers, and each controller has the correct unit ID's, networks, com ports, etc. and the controller pixel settings are both at 100 and the Pixie16 has the latest firmware version. Each star has 50 pixels, and every color lights up just fine when I test it in HU. However; when I run the actual sequence, the last four LED's don't do anything, (see the attached pics) regardless of the type of effect. I've changed the prop settings numerous times, specifically the channel section information, but still have the same result. I've even tried lowering the "max circuit" number to 150 instead of 175 (so there's no carry over) and it had no change. I don't know exactly what the carry over column is, and LOR has NO literature or reference to this section and what it does, even in the help guide or tutorials. I've even changed the options in the channels section, "separate unit # for each string" instead of "individual start channels", and I get the same result. I've even tried checking both options and again, same results. I know the LED's are not bad because every color will light up in the HU pixel test. I always save the file in PE and then save the intensity data before running the sequence from SE. Any help would be greatly appreciated. I'm at my wits end! Thx in advance.
  • Create New...