Jump to content
Light-O-Rama Forums


  • Content count

  • Joined

  • Last visited

  • Days Won


k6ccc last won the day on May 21

k6ccc had the most liked content!

Community Reputation

653 Excellent

1 Follower

About k6ccc

  • Rank
  • Birthday 04/19/1959

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Glendora, California (Los Angeles area)
  • Occupation
    I run a regional Public Safety 2-way radio system.

More About Me

  • Interests
    You mean besides lighting? Ham radio, Geocaching, flying, target shooting.
  • How I learned about Light-O-Rama -
    The web somewhere
  • Favorite Decorating Holiday?

LOR Software

  • LOR Software Version
    A Beta Version
  • License Level

Recent Profile Visitors

4,326 profile views
  1. Absolutely not. Each flood will behave independently (unless of course you set them all to the same Unit ID). I'm back to my previous statement - almost certainly a channel configuration issue. Since the floods work properly with the LOR Hardware Utility, it is very likely that they are working properly. Just to make sure I understand your setup, as I understand it, you are using a Falcon F3 controller and using one of the Falcon outputs as a DMX universe. You would use with either the DIP switches to set the starting DMX address or set the DIP switches to all 0 and then use the Hardware Utility to set the LOR Unit ID (and therefore the DMX starting address when using DMX to drive it). Check out pages 21 - 26 of the CF50D manual to see what the relationship is between LOR Unit ID and DMX starting address. As far as the CF50D is concerned, you can use any DMX starting address for any particular flood. I have no idea if there are limitations in xLights. In the event that xLights assumes a RGB device is three channels and you can't vary that, the simple solution would be to start for example flood #1 on DMX address 1, and then flood #2 on DMX address 7 (instead of 4), etc. You "waste" one address, but that is not a problem. Not that I know of, but there is no reason to do so.
  2. RGB star stays on after each sequence

    Make sure that the very last time element has all channels off. Personally I NEVER depend on the "Turn all lights off at the end of the sequence". In fact, I intentionally have a few lights that do NOT turn off at the end of any sequence.
  3. You Need These Pliers

    Agreed that good tools are well worth the cost. That is a lesson I learned in reverse from my dad. He grew up during the great depression (he was born in 1927), so money was ALWAYS very tight. As a result, even though he always had a job after getting out of the service after WW2, he almost always tended to buy the cheapest tool that would do the job. That was usually followed by years of bitching about how much of a piece of crap it was. I pretty much never buy cheap tools as a result. BTW, either don't start, or get out of the habit of stripping wire with your teeth. Your dentist will thank you...
  4. You Need These Pliers

    Yes, flush cut pliers are wonderful.
  5. Brian provides GREAT service with SuperStar. He will bend over backwards to get it working for you.
  6. View a Sequence

    In addition to what SPaschall said, if you decide that you don't want to upgrade to Pro and continue to use Sequence Editor, you will still need to upgrade. The Pixie16 controller uses 16 Unit IDs and the Basic Plus license level can only control 4 Unit IDs. You would need to upgrade to Advanced level license in order to use the 16 IDs. With that said, I would recommend that you make the jump to Pro and then you are covered for anything.
  7. S5 to SuperStar Visualization Process?

    Personally I MUCH prefer SuperStar over Pixel Editor, but either can program a pixel tree. in S5 it is FAR easier to mix effects fro PE and SS in the same prop and song.
  8. At least I was able to watch it all the way through - unlike the fox...
  9. S5 to SuperStar Visualization Process?

    A true matrix would be some number of rows of pixels. For example 24 rows of 50 pixels forming a rectangle that has a pixel every two inches (for example) in both the horizontal and vertical axis..There are some other props that also are at least matrixish. For example a pixel tree is often 12 or 16 vertical strings of 50 pixels. Although tapered towards the top, you can do graphics and text on it fairly well. What I mean by non-matrix props is most everything else. Examples in my yard are individual lights (either RGB or single color), strips or strings of dumb RGB lights, strings of traditional l.ights, strings of pixels in a row (roofline for example), candy canes, singing faces (can be done on a matrix, but I'm talking about traditional string based faces). Make sense?
  10. Trip Wires with inputpup

    One issue I have run into with a reflecting light beam. I had tried a reflecting light beam on the path in the left of the photo I posted above. The problem was that if someone was wearing light colored pants or was wearing shorts and had very light legs, there would be enough reflection that the receiver would not detect that they had crossed the beam. This was particularly true if the person was close to the transmitter / receiver. Yes, they are easier to install since there is only a reflector at one end and you don't need to get wires to it.
  11. LOR XLights Pixcon and/or Falcon

    Both Pixel Editor and SuperStar do that just fine. I agree that if you are sequencing large amounts of pixels in Sequence Editor, you are torturing yourself. Yes, I know that there are people who do pixels in SE (George for one as I recall), but personally I would not even consider trying to sequence a matrix type prop in SE. Either SuperStar or Pixel Editor is FAR easier (I'm partial to SS). BTW, a string of pixels (for example a fenceline or roofline) may not be too bad in SE, but for example trying to do text on a matrix using SE would take a massive amount of time compared to either SS or PE.
  12. LOR XLights Pixcon and/or Falcon

    I have never played with either a Pixcon nor Falcon controller, so no personal use of either one. Yes, the service from LOR is second to none. With that said, I have heard that the Falcon controllers are some of the easiest to setup of any pixel controllers (second or third hand information). Personally I started using SanDevices controllers when there weren't a lot of choices for pixel controllers. I love them and have no plans to switch to anything else - bought another one a few months ago. As for the software, I have never played with XLights, but my understanding is that it is very similar to Pixel Editor (or actually the other way around). As I really don't like Pixel Editor, I don't see any reason to believe that I will love XLights. I am dipping into the Falcon Player world this year because I will be adding a couple P10 panels which will use FPP to drive the panels. However at least so far, planning on driving FPP in bridge mode from LOR. I pretty much do everything in LOR in SuperStar, and AM making the jump to S5 this year. Part of that is because I am making a LOT of hardware changes which is requiring a major "conversion", and switching to S5 would also require a big "conversion" so might as well combine the two "conversion" projects. I'm still not overly thrilled with the SuperStar integration in S5, but it is SLOWLY getting better. It will likely never get to where I can sequence the way I have in the past in SuperStar (which will likely at least double my sequencing time). My two cents worth...
  13. 1/4 Barrel Prop, How I made it.

    100% agree with this, but don't do what I did five years ago. Most drill presses that consumers are going to buy are not designed for continuous operation. I drilled 50 holes in PVC half pipe for my pixel tree. As soon as one strip was done, I started the next for a total of 600 holes. The motor was never given a chance to cool down and failed when I had five holes to go. Lesson learned - if I do the same process again, I will split one pipe in half, and drill the 100 holes. Then split the next pipe while the drill press motor cools down.
  14. No motivation yet - help!

    That's what I do. One or two new ones every year and re-do the existing ones for whatever hardware changes. This year I don't expect to get any new ones in - the re-do of the existing ones will take enough of my time since I'm adding about 61K channels this year. As I have said before on the forum, sequencing is about one short step above torture. Love doing the hardware and running the show, but not the sequencing.
  15. John, Confirm which software you are using for sequencing - Sequence Editor, Pixel Editor, or SuperStar? I gather it’s SE since you used the Beat Wizard. i wanted to clarify something you said in your second post. You gave time examples of 1:00.00 vs 1:00.78 on the other. 3/4 of a second is beyond “noticeable “ What I wanted to clarify is is those timings were just an example or were they timings taken by examining some particular light element. The reason I ask is that the SE file format as it gets saved to disk specifies the time for each element in an exact time (measured in hundredths of a second). It does not care about timing marks or the music. In other words if the file says a sequencing element is at time 6000, I will be at 1:00.00 So what all that gets down to is the sequenced element timing getting skewed or is the music in the wrong place? Like the other comments, I’m betting that this is an audio issue.