Jump to content
Light-O-Rama Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About morden11

  • Rank
    New Forum User
  • Birthday 09/26/1974

Profile Information

  • Location
  • Occupation
    President / CEO

More About Me

  • Favorite Decorating Holiday?

LOR Software

  • LOR Software Version
  • License Level

Recent Profile Visitors

161 profile views
  1. Okay, so about 3 months ago I upgraded from version 3 to version 5. I did this because I had to, I had replaced a bunch of the older CCD/CCB/CCRs that I had from earlier seasons after a power surge fried a bunch of the boxes. I got the three prong pixels, and the older software didn't support them, at least not in the hardware utility. So of course, S5 is a million years different than my old version S3, and it was like learning Light O Rama all over again. And like most Light O Rama software, the instructions are as useful as one written in another language, but with some previous knowledge of the older system, I was able to find what changed and where. Here's what I love! - The motion rows are amazing! I can do in seconds what previously required minutes or in some cases hours with the old system, having to use Super Star only - When I do use SuperStar though, I can select the timing in the motion row that will include the segment, and then Superstar automatically gets brought into the main LOREDIT file. I don't have to save it in SuperStar separately anymore and then import it later. Also, the Superstar elements are included as separate 'files' that just need to be in the same folder with the LOREDIT file. - The way props work allows me to really set up the show how I'd like using a 'prop template' (with each prop basically being either a channel or a Pixel/RGB Controller). So I set up the show using the props and then every subsequent show, I can just select the same template, vs. the more cumbersome effort to get a new show going using the older system. - All this bakes into so much less time to create a show now. I can do a new show in a few hours instead of days (due to the # of pixel controllers I have the CCB/CCD/CCR controllers required infinitely more time in the past) I hope everyone is enjoying S5 the same. And while again the instructions were crap, once I got the hang of it S5 is hands down 500% superior to how I was creating shows previously.
  2. Never mind all just figured it out. I have to click at a very specific area of the channel name in order to move it (not on the text but right next to the text to the right, and then I can drag it). Too far left or right of that point and it doesn't move. Weird, but figured out.
  3. Hey there, So I'm on the grid view (not the preview view), and I'm trying to drag grid items so I can get all the Green channels together in a specific order (I can't use the 'sort' feature or they get out of order due to how they're all named). I used to be able to drag these but can't anymore. I forget what I did previously to be able to drag channel names up and down on the list. Anyone know how to do this?
  4. No I didn't do that Mr. P, at least I don't think I did. Every time it rains now my hardware utility loses about half the network and half the network shuts down. The breakers don't blow so it's not a power issue I don't think. Just weird.
  5. Mega Arch can you tell me what Standalone mode is in regard to the Floods?
  6. So between this and the pixie controllers having the dip switch issue, it seems I’m the only person here who has problems with the hardware. That will make getting advice difficult.
  7. Hey all, Next problem. I ordered a bunch of the 50W floods (RGB) and set the unit IDs and plugged them into the network. All was fine on night #1. Night #2, one of the 8 floods I deployed stopped working Night #3, a second one of the 8 floods I deployed stopped working I tried swapping power packs with other floods that 'are' working (no effect) I swapped out ethernet cords (no effect) I plugged other floods into the network spot that the malfunctioning ones are at and they worked fine Is it normal for these things to crap out within days or is there something in the network setup I should watch for to prevent it?
  8. Mr. P, I'm a layperson, that paragraph might as well have been written in hieroglyphics. The only reason I know what a dip switch even is is the result of exhaustive research and self-teaching on the concept. What I'd prefer is that the instructions are written for a small child, or a golden retriever, and not with the assumption that a user has fundamental understanding of the hardware involved before picking up the manual. Then I might have had the light bulb go off before running into this issue. TLogan, Thank you kindly for the feedback. I learned this by accident using the SE5 system and it just happened to show the Unit ID of X+1 as a property of the 'Prop' when I double clicked Port #2. Absent that, I'm sure I'd be trying to also figure out why I set one Pixel controller to 0E, another to 0F, and then things don't work right since it should be 0E, 0F and then 0G, 0H. This is another topic that should be in plain english in the manuals.
  9. Alright I figured it out. It unfortunately wasn't any of the above nor was it the solution proposed by the technical support team at Light O Rama. A combination of Youtube research and trial and error led me to the right fix. Here is what happened: I sat down with each controller in our house to set the Unit ID with the Hardware Utility, one at a time. When I did this, and then did 'Refresh', it found the unit correctly with the ID I had set. Like an assembly line I did this with 8 more Pixel (2 Port) controllers. Then I put them all outside and attached them to the network via Daisy Chain and the 'black' USB 485 unit. However, when I fired up the Hardware Utility 'after' plugging in power to the entire network, that's when I saw the issue I noted above. All the Gen 3 16 channel controllers appeared, all the 50W floods appeared, but none of the 9 Pixel controllers appeared nor did the CMB24 (which was Unit #1). Instead it showed that Unit 1 was anything from 'InPup' to 'Bootloader'. Well, here is the rub and I'm a bit salty that the instructions for the new Pixel controllers aren't more clear. Apparently the factory sent me these things with a dipswitch pushed into the 'On' position, so the unit defaults back to '01' as a Unit ID. This didn't happen though when I had the controllers set up by themselves, it only happened when they were plugged into the network with other controllers. Not sure why that is, why the manual doesn't say with a picture to move the dipswitch to the 'off' position so they're all off (as I don't think everyone wants controllers to all be Unit ID 01). Anyway, once the network reset all the controller IDs, then the Hardware Utility was detecting '9' Pixel controllers with unit ID 01 as well as the CMB24 which also had unit ID 01. I'm guessing the software didn't know what to do with that information so it showed weird readouts for unit ID 01 and nothing else. So I went controller by controller outside, resetting each and pushing the dipswitch to 0. And now everything works great. I clearly need the 'Red' 485 unit as the Black one just can't keep up with the pixel controllers, but that's a much easier fix. I'd ask for the Light O Rama folks to not presume that people using the software and hardware have understanding of the fundamentals of this stuff and instead produce instructions that assume the least common denominator, like me. It would have saved me days of needless troubleshooting.
  10. Mr P, The license and software versions are now updated.
  11. Summary of what's going on: Current network (Call it the Regular Network) is set to 500k Enhanced and has the following controllers daisy chained: 5 16 Channel Gen 3 Residentials 1 Ancient CMB24 10W RGB light controller 8 50W RGB Floods and 9 Cosmic Color Devices (ordered this year with the summer sale) with 2 ports each as follows: 4 CCB with each port having 100 C9 bulbs 2 CCP with each port having 100 bullet bulbs 3 CCR with each port having 1 ribbon I have the most recent version of Light O Rama software and renewed my license as of 4 days ago. I have Pro level software. I checked every controller by itself on the hardware utility before putting out into the yard. All of them registered in the Hardware Utility. **************************************************************************** I set all of them up with power, and daisy chained all of the controllers using Cat5 cable ***************************************************************************** I use the Hardware utility to check all controllers on the network. It bounces back only 14 of them: a) The 5 Gen 3 16 channel units (all firmware 1.09) b) The 8 50W flood units RGB (all firmware 1.05) c) The CMB24 (though it's not calling it that anymore it's calling it interpup or bootloader or something) ***************************************************************************** Absolutely none of the CCR / CCB / CCP controllers bounce back on the hardware utility now (even though they did when they were by themselves) I look at the 5 Gen 3 16 channel units inside the case and it's a 'solid' green light I look at any of the CCB / CCP / CCR units inside the case and it's a flashing red light which it shouldn't be of course And, here's the really weird thing. Even though the CCB / CCP / CCR controllers don't register, it 'still' sends the signal from hardware utility down the daisy chain as I have the some 50W flood units and Gen 3 16 channel units both before 'and' after the Cosmic Color units in daisy chain order. I don't even know where to begin with figuring this out.
  12. Okay, so I figured it out. I did not do a show last year (did one in 2017 though). Simply put, my software was out of date. Once I updated the software license and version, they tested fine. I have a different issue with them that I'll describe in a separate thread but for this one, I didn't realize the new CCP/CCR/CCB controllers required a software update when I posted.
  13. Hey all, So I unboxed the CCC controller and have plugged in 2 sets of '50' CCP strings that came in the box with it. Specifically, each string is 100 pixels, with two strings of '50' connected so a total of 200 bulbs on the controller when all is said and done. This was how the unit was purchased online. When I do a hardware test and when I fired a live Sequencer test, what happens is the first 50 pixels on each string show one color (the color dictated by the show) and the second 50 pixels on each string show something else. Any idea why all 100 pixels aren't showing the same colors?
  14. Hey all, My wife and I built a new house last year and the show got a lot bigger as a result. We quadrupled the number of CCRs and CCDs we had going. When the show goes, it does work, but, there's a weird effect going on with some of the RGB devices. As the show goes, they just flash/blink quick for some reason at random intervals, and sometimes the RGB devices try to fire but don't and just blink out, like with the CCR lights going from the center out and back in, it just flashes the entire bar, blinks out, then continues. It's like there's too much for the network but we didn't break the single network upper limit. Some of the 50W lamps also had a flicker issue (we have 5 total). Overall, the shows performed at 99% effectiveness, and all of the regular non RGB LEDs worked perfect. Just the RGBs had these issues, and it takes away from the show when they blink like that. Any thoughts? Also unrelated, last year two of my CCD boxes burnt out, like dangerous burnt out. The inside of the little green boxes had black burn marks on the lid and when I plugged it in after the season, the circuit board shorted out in a fantastic display of sparks which thankfully didn't burn 'me' but still the unit's dead. Anyone else seen this happen?
  15. I have a show where I am not using any of the cosmic color devices but the strips keep flashing randomly during the show, like they're glitching? Any ideas? one LOR network 8 CCR controllers and ribbons 4 CCD controllers and 8 strings. 1 CCB controller and 2 strings 7 standard 16 channel controllers 5 50W floods 4 10W floods and controller Using 500k network speed About 600' of Ethernet cable daisy chained.
  • Create New...