Jump to content
Light-O-Rama Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


Orville last won the day on December 12

Orville had the most liked content!

Community Reputation

327 Excellent


About Orville

  • Rank
  • Birthday 11/18/1956

Profile Information

  • Gender
  • Location
    Orlando, FL
  • Occupation

More About Me

  • Interests
    Photography, Garden Railroading, Gardening
  • How I learned about Light-O-Rama -
    2009 watching holiday displays with lights set to music.
  • Favorite Decorating Holiday?

LOR Software

  • LOR Software Version
  • License Level

Recent Profile Visitors

2,950 profile views
  1. Orville

    What's Next!

    My bad, stated this was from trying to recall, thanks folks for clearing up the error. DATA should have been CLOCK. But for the life of me, the word DATA kept popping into my head. Guess I've been watching too many Star Trek TNG episodes with Lt. Commander Data in them. LOL
  2. If it's the loop back causing the blink, yes, extend the sequence, but also extend the loop so that it covers the extra empty off cells you'll need to add in to extend the off time by 2 to 5 seconds so the lights don't go off, then come back immediately. But even with an animation loop, the light shouldn't really have a "blink" to them, they'd turn off, then turn right back on and start the loop over. Only reasons I can fathom you'd have a "blink" is the lights go off at end of loop, then when they immediately come back on, you have a section at the beginning of the sequence with lights on for a very short duration, then off cells, then back on again. That would cause a blink, or like stated, having stray lighting commands at the end of the loop, at the end of the sequence could cause a "blink" to occur. This could also happen if both the start and end parts of the sequence has any stray lights on commands in the sequence. Believe me, those small intensity commands, such as with fades or intensity in a cell can be very difficult to find, spot and remove. I've had my share of these very issues, so I know from experience on stray on commands that can barely be visible to the you, but the sequence sees them and will turn on a light{s}.
  3. Orville

    What's Next!

    The main thing you need to know is what type they are, as in what IC Chip controls them and what their voltage rating is, 5V? 12V? And yes, you could use them, you just have to know what they are, also are they 3 wire or 4 wire? To my recollection 3 wire DOES NOT have a DATA signal line, but 4 wire do and would require a controller that also has 4 wire outputs of the proper voltage and/or a data line for the RGB lights you want to use. As for their length, they should be able to be cut down to the appropriate size to work with whichever controller you'd decide on to use with. But make sure the controller is one you can use with them.
  4. Bad idea, as others said, if moisture gets in there, it'll stay in there, even on the hottest day here in Florida, it won't dry out completely. Like others have suggested, but some cheap green ground Christmas light stakes and get the cord connections off the ground, try and use two or more stakes if needed. On my triple taps, I have one stake at the cord end and 1 on each cord coming into it, so 4 stakes in use. I also try and have all the female cord end pointing downward as well. Also on any open pass through, and end female plugs on light strands, I use those electric outlet plastic child proof caps on them, and even in any unused channel dangles from my controllers get capped off with them. Prevents dirt, mud and debris getting into the plug from rain or sprinkler splash. Been using this emthod for years now. My show will continue to run in conditions like yours, my first year I was having GFCI trips galore, brand new GFCI too, added the above to my cords and dangles, and I have yet to have my GFCI trip in any type of rainstorm to date. And where I live, when it rains, sometimes the yards will flood and retain water for long periods. I've had cords get submerged that had the child proof caps on them and my show still went on without a hitch.
  5. What you stated in the text I put in bold in your comment above is EXACTLY how it should work, except it won't start the program there when you close it, and then re-open it later, it will always default back to the very beginning of the song. You have to set the start and end times for the song in the Tapper Wizard every time you reopen any of the Wizards to use them. So, if you tell the tapper Wizard to start at the 28 second mark and go to the 1 minute mark, that should be where the song plays and then ends. So if using the Tapper Wizard, and you had set it up that way in the Tapper Wizard settings, it should have allowed you start the song right where you want to start at, then end at the end time you put in the start/end boxes. Then once you have the Taps set, click Apply and it should only add the taps from 00:28.00 to 01:00.00. But if you EXIT the wizard, it will default back to the beginning of the song, you have to SCROLL forward in the cells to find the Taps you just "tapped in", then when you start the Tapper Wizard again, if working on that same section, you'd have to enter the times all over again. None of the Wizards retain anything you have set once you Exit out of them. You should not have to shorten or edit the song to accomplish this in the SE, that's why there are two boxes to put the song start and end time do just put taps in a specific part of a song you may be working on. So if it was doing this, it was working as it should. If it's not, something either isn't set right in the Tapper Wizard for the start and end song time to use or the SE isn't working properly, I use this method all the time to do just short sections of a song I'm working on in the SE. Especially when I'm working on a song that over 1-2 minutes long.
  6. Orville

    What's Next!

    First off let's clear up CHANNELS when it comes to RGB lights, smart and dumb pixels are all 3 channels per node, so a 50 count strand of pixels = 150 channels {300 channels for 100 strand count of pixels}. Now, smart pixels each color is INDEPENDENTLY Controlled, that is each bulb can be a completely different color than another on the same strand. Dumb pixels the entire strand is still 3 channels per bulb, but the entire strand can only be a single color at any given time. Most pixel controllers, depending on voltage output to the strand will control either a total of 2 strands of 50 RGB nodes for 5VDC, 12VDC you can have 2 strands of 100 RGB Nodes or 4 strands {2 strands on each port of the controller} of 50 bulbs. Voltage of the nodes to the controller is important, as you can NOT mix 5V and 12V strands together, there are exceptions, but that is lot more complex using multi-voltage controllers like the Pixcon 16. And getting into pixels, with some controllers WILL REQUIRE a PRO License level to use them, a PRO license is ALWAYS recommended when getting into pixels because they are intensive, so a red high speed USB-RS485 adapter is required as most require 500K speed and an Enhanced Network. And DMX IS NOT required for all pixel controllers, some folks use that method, others just use the standard LOR protocol, that is up to you. If anything else needs to be added to this to help simplify it further, I'm sure someone else here will chime in with additional detail.
  7. Since that is what you've always used, have you tried closing down the software and restarting it. I've had some issue where I have had to close {and lose what I've done} and restart the software, then things worked again. That's the only 2 things I know that fixed some of the issues I've encountered from time to time. The one above this posting and this one, although option 3 might be to upgrade to the latest version of the LOR software you're using. Also don't know if you saw DevMike's post about the latest version of S5 {I don't use S5}, but the newest version is 5.3.12 and has fixed a lot of bugs and issues in previous versions of S5 from what I had read in his post. So you may want to go and download the newest version of S5. That can be downloaded here: ShowTime Sequencing Suite Download - Light-O-Rama Hope this might help.
  8. During checkout, you can state a change in shipping, on small items than can ship regular mail {USPS}, LOR will send it that way, but YOU MUST REQUEST IT. You do this in the comment section{box} where you can ask or tell them how you need it shipped, special instructions, etc. Believe me, it won't be anywhere near that default shipping charge. When I order small items I always request please ship USPS. And unless it's something that's really large, all small items I've ever ordered from LOR has always came in USPS, the regular shipping charge will show up on your invoice at first, but BEFORE LOR Ships it, that shipping fee will change and be much less than UPS or FedEx shipping. And it WILL be adjusted BEFORE they do the actual charge to your credit, debuit card or paypal account. Just some info to let you know there are other options, you just have to know how to ask for them.
  9. Do you always have an unnamed timing grid selected? When I forgot to set timings in my version of the sotware, the tapper wizard WOULD NOT apply the taps to an unnamed timing grid, once I changed to my default of .05 timing grid, it worked fine. Not sure if this could be the problem, but it's the first thing I noticed in your screen capture.
  10. You WILL definitely need to upgrade your license, Basic Plus only allows a maximum of 4 Controllers, and since you're at 64 channels, that's 4 CTB16PC style controllers or a mix and match of no more than 4 Controllers, and this, is again, your maximum limit with your current license. As others have stated, getting into Pixels, best to go with the PRO license, as some of the Pixel Controllers REQUIRE a PRO License, anything less and you'll be on here asking a million questions as to why Pixel Controllers aren't working or being found in the HU. I'm not sure if the License level affects the HU, since that is a backdoor to the Controllers for testing purposes only, just to make sure they can function, as it is. So the new controllers {pixel} may work in the HU, but when you start adding them and their high channel counts to the Sequencer, and you have a Basic License, only the first 4 Controllers will operate until you get a higher license level to handle those controllers. Again, Pixels are a bit more complex in their sequencing and some Pixel Controllers, again, WILL REQUIRE a PRO License to operate. So best to go ahead and UPGRADE your license to PRO, that is the least expensive way to do it. Use the Upgrade option and NOT the one that shows you're buying a new license, choose the wrong one, and you'll pay a higher price. So make sure you choose the UPGRADE LICENSE option when updating your license level.
  11. And if you do buy *used* equipment like LOR Controllers off E-Bay or other auction type sites, make sure they don't have a NO RETURNS ACCEPTED, too me, that'd be a red flag warning you may be buying a Controller that is already dead in its tracks. I NEVER buy from anyone or any company that has a NO RETURN POLICY, that's just asking to get burned when purchasing items from them. However, if the item is a clearance item that a reputable company has up for sale, usually due to being outdated and outmoded due to newer products that perform better, I will take a chance on those, because most clearance items I've purchased have worked fine, but they may have scratches or slight damage to something like a box may be broken and need replacing, but usually nothing that is a big deal. But again, make sure when you buy clearance items you're sure it's what you wan,t and be sure it's from a reputable company with excellent ratings, Like Light-O-Rama! Used equipment is not always a bad deal, just have to be careful of the sellers policy when doing so.
  12. Check your sequence, it sounds like you have a light on command at the end of your sequence that causes this. Do all lights blink or just one? When I create my sequences, I make sure that at least one to two cells at the end of the sequence have NO LIGHTING commands in them. if you have that and still get a blink, there is still a stray lights on command somewhere at the end of the sequence causing this, You need to find the culprit{s} and eliminate them out of the sequence. Sometimes this can just be a small intensity that is easily missed, like when you fade down the lights, and then you might change it to a shorter fade down, but what happens is the extra fade down on command is still in the sequence, anytime I change a fade down like that, I also use the lights off command and find the end of the new fade down, then turn off those small fades that could possibly cause a blink to happen. Just check all the light commands near the end of the sequence and you may find the problem causing this occurrence. Good Luck!
  13. Even the Verifier can show something as wrong that could have been done on purpose. When I run the verifier, it shows I have a "Channel Conflict" and it gives me the files that are in conflict, which is my Shut Down and Background sequence, Shut Down has all channels from every controller I have in it, ALL OFF, no lighting commands, this is so once my show ends, it turns off ALL lights on ALL Controllers. But the verifier says it is in conflict with "sequences in my show", but in reality, the Shut down Sequence DOES NOT RUN during the show, only once everything has played until the Scheduler hits the END TIME of my show, then it runs the Shut Down Sequence at that time. My conflicts were mainly my Background Sequence and the Shut Down Sequence showing Controller 06, Channels 14 & 15, Controller 07, Channel 8 having a conflict with the same channels in them. The Background Sequence controls my handicap walkway lights, snowman L.E.D. Tune To spotlight and Snowfall lights that run constantly during my show to keep those lights on, the Shut Down Sequence has those channels added so that it turns them off after the Show. But the Verifier thinks this is a conflict, but in reality, there is no conflict at all. Since a Shut Down Sequence NEVER runs until the END TIME is met, so there really IS NOT, and WAS NO conflict. So you have to be very watchful, and careful, that you don't change the Shut Down Sequence, by not removing any conflicting channels in that sequence. Because those channels NEED to be there to do what is supposed to happen during the Shut Down of the show, turn all lights off. So always make sure that each sequence is set how YOU know it is supposed to be to do the job at hand, as sometimes a conflict error in the Verifier, is really not a conflict at all. Just make sure that any sequences RUNNING during a show together, such as Background and Musical/Animation sequences ARE NOT in conflict, and everything will run smoothly. p.s. I don't understand why the Verifier even compares a Shut Down Sequence to ANYTHING in a RUNNING SHOW. Seems Shut Down Sequences could have just been ignored when Verifier Background, Animation or Musical Sequences. Even Start Up Sequences get compared, why? They only RUN ONCE during initial Start Up and are NEVER used again after that. Just as the Shut Down only RUNS ONCE at the END of the show. So why compare the Startup and Shut Down Sequences to those in the actual show tab areas in the Verifier? Seems this part of the code could be eliminated, as I can see no real rhyme or reason for it to even compare these two SPECIFICALLY TIMED {Start Show/End Show} sequence files.
  14. I missed that one where a person was charging $21 entrance fee to gat in. To me, that is just downright appalling for someone to do. Asking for donations is one thing, but demanding a fee to see YOUR display is a bit outrageous too me. But I totally agree, if you have to "pay to see it", then it SHOULD NEVER be allowed in the competition. Only shows OPEN TO EVERYONE {at NO CHARGE!} should be allowed to compete! So totally agree with you on that.
  15. Well you may have at least one option over it being a "boat anchor", LOR usually has a buy back program {if they still have it?} that allows you to get a discount toward the purchase of a new controller. yes, it will cost you some money, but wouldn't it be worth the discount exchange over just having a boat anchor? Personally, too me, as long as the unit works, it's NEVER too old, but when it dies and may not be repairable once LOR gets it and sees whether anything can be done, then it's time to take advantage of the buy back discount program, as I would think this would still apply. But the folks at LOR would have to really chime in on the buy back discount exchange program on a non-repairable controller. LOR is usually fantastic with their customer service, even when you buy used equipment from another person or happen to gain things from an estate sale or inherit them from a family member that may have been in the hobby.
  • Create New...