Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by scodavis

  1. Thank you to everyone who responded.  My desire was to have the pixel placement be as precise as possible.  I, thus, was able to develop the following strategy:

    1. In Visualizer S4, create a new prop with the required number of pixels (in this case, I did 5 strings of 50 CCR pixels).
    2. Through testing, I was able to find that the coordinates of the PSD file and the Visualizer prop file (opened in a text editor) are different by a factor of 15.
    3. So, for EACH pixel, I did the following:
      1. Using the marquee tool and Info window in Photoshop, I opened my background PSD and got the X,Y coordinates of a single pixel
      2. I multiplied each coordinate by 15
      3. In the Prop file (in a text editor) I put the new coordinates.
    4. Rinse and repeat, 250 times total.  Attached is my final product.

    It was a lot of work and time (about 2 hours) but the end result is a perfectly accurate representation.



  2. Hello,

    I still use (and intend to continue using) LOR S4 because it works very well to me.  In a couple years I will be adding some pixel props using Pixie 16's and Pixels from LOR and the various coro products from HC.

    As you can see from the image below, I plan to put my pixel props into the visualizer (most are less than 50 pixels per string, and I will use DMX channels for the rest for programming purposes.

    I have noticed there doesn't seem to be a way to select a single CCR pixel and nudge it (yes, you can drag it with the mouse, which is poorly implemented).

    I have no problems with manually editing the fixture or prop file with a text editor, and getting the pixel coordinates from the original Photoshop image, but I notice that the X,Y grid of the Visualizer files is completely different than the X,Y grid of the Photoshop resolution.

    Are there ANY good ways for precision placement of individual pixels so they exactly cover the dots on the screen?



  3. I am trying to make some final decisions before ordering some products.  Right now, what I need to know is the dimensions of the Pixie16 controller that comes ready to go.  I was provided a photograph of what it looks like but I really need the dimensions.  If somebody can take a photo of the controller laying next to a couple rulers (length and width) that would be extremely helpful.  The depth (height when laying down flat) doesn't matter.  Also, visible in the photo is a metal bracket with three holes, two of which are clearly visible.  If you can include the spacing between those two holes that would also be helpful.

    Thank you.



  4. 11 hours ago, Orville said:

    What I find amusing it does say that in the Network Configuration utility, but in the HUB, it says the Pixie can run at 1,000K.  Wonder why those 2 programs don't agree? LOL   But I could set the Pixie to 1,000K in the Network Config and it worked, even though it says 1,000K is only for PixCon16 only.   Does make you kind of scracth your head and go hmmmmm? LOL

    Even more amusing is that if you look at the LOR network speeds page:  http://www1.lightorama.com/network-speeds/

    Scroll down to "Pixel Controllers" and you'll see a blue checkmark in the 1000K column for every type of Pixie device.

  5. I have had a history of strange behaviour with the Pixie2D stand alone functionality.  I have a Pixie2D (as the LOR CCC-II) running the most recent firmware (1.05).  I have two sets of 100 bullet pixels (100 per output of the Pixie2D).  I upload a very simple sequence of color blinking which takes 10,085 bytes (maximum states 100,000 according to the Hardware Utility).  The sequence is only 5.6 seconds long, and I've attached the file I'm using.

    The best way I can describe the issue is that it seems to play more slowly than I program it to, and when it hits the end of the sequence it loops there is a quick jolt as if it resets to the beginning without having gotten through the whole sequence to begin with.  It's almost like the internals can't keep up with the sequence.

    Worth noting - if I hook up a computer and play this exact sequence it works perfectly.  The issue only happens when I use it as stand alone.

    Please assist - thank you!


  6. @dibblejr Thank you so much!  That is some excellent information.  I know that the Pixie controllers support 500K and 1000K, but why your statement that Enhanced is required?  By the way - I do have a Pro level license.

    And yes - if I go with Pixie16, I plan to set the first one at Unit 50 and let the rest be 51-5F (I do understand the hexidecimal numbers).

    My other three pixel features are done with Pixie2 controllers so I do have that experience.  I also work in IT, and LOR has made their products quite friendly.  Helps a LOT.


  7. @PhilMassey My current configuration is as follows:

    Regular Network:  North Side Flood Controller (CMB24D), North Side AC Controllers (16 Total), and Garage AC Controllers (3 Total)

    Aux A:  Pixel Controllers (Pixie2 w/ 200 Pixels, Pixie2 w/ 200 Pixels, Pixie2 w/ 100 Pixels)

    Aux B:  South Side Flood Controller (CMB24D)

    I could change the South Side Flood over to Regular Network (with some creative rewiring) which would then free up Aux B entirely.  All three networks are using USB-RS485 Isolated adapter with booster.  I would not be running any more than 100 pixels per controller output.

    I don't think I'm going to have a ton of future pixel expansions, but I was considering E1.31 due to the number of pixels and the significantly higher speed of Ethernet.

  8. Believe it or not, my preference for pixel programming is directly within the S4 Sequence Editor.  I don't use Pixel Editor or SuperStar at all - I find them limiting to the way I like to program.

    I have no problem with creating a new network - whether E1.31 or LOR.  I just want to make sure I'm doing this the best way possible.

    Another related question - what is the maximum length of a pixel extension before voltage drop becomes an issue?  I was thinking of having my Pixie/Pixcon power pixels on quite a few different features, spread out across my house.

  9. @k6ccc Yes, I am running my show from a computer.  My non-pixel networks are running at 500K.  My pixel network is running at 1000K non-enhanced (I didn't like the way that the Enhanced network handled the shimmer effect compared to the non-Enhanced networks).  How many pixels can be on a single 1000K network - is adding yet another network absolutely necessary?  Obviously I want to do this the right way and not have problems later.

  10. I am seeking advice.  I am planning to expand my show with features that are decorated with pixels (most of my show is standard string lights).  Come the summer sale, I plan to buy a set with a 16-channel RGB smart pixel controller and 16 x 100 pixels.  I am currently trying to decide between the Pixie16 and the Pixcon16 option.

    I know that the Pixcon gets a reputation for being more advanced because it supports E1.31 (which doesn't bother me).  I work in I.T. for my full-time job, so working with networks is not a problem for me.  My question is - which device will give better performance?  I want to make sure my show remains lag-free.

    Right now, I run my show on three LOR networks - one for string lights, another for additional string lights and some RGB dumb pixels (flood lights), and one for my pixels.  My pixel network currently controls a total of 500 pixels, a mix of CCB and CCP attached to three different Pixie2 controllers.

    Feel free to ask questions.  Thank you!

  11. 22 minutes ago, dibblejr said:

    last I knew and still in NP - 1000K is for the Pixcon16 only


    I use the 1000K speed for my Pixie2 controllers and they work great.  Also works on the Pixie 4, 8, and 16.  Here is the LOR list showing what supports what speeds:


  12. 5 minutes ago, k6ccc said:

    How is the network set up in Network Config?  Primarily looking for speed and enhanced vs non-enhanced.


    That was it - it was set to 1000K (non-enhanced) for the Pixie.  I forgot that the CMB24D didn't support that speed.  Dropped it down to 500K and now everything is working properly.

    Thank you, Jim!  Hope all is well with you!


  13. Hello everyone,

    Today I brought in my CMB24D so I could start testing my Dumb RGB pixels.

    In my office, I have my programming computer and a USB485-ISO dual port adapter.  In the adapter outputs, I have a cable going to:

    • A Pixie2-based rgb smart pixel star
    • A Pixie2-based rgb smart bulbs (2 x 50)

    I unhooked the wire to the smart bulbs and plugged in my CMB24D.  I have the Comm Listener running, Visualizer on, and my Sequence Editor open with a test sequence.  Channels and networks are set correctly.  However, the CMB24D constantly flashes red.  The Pixel Star, on the other hand, works perfectly.

    Making matters even more confusing - when I close everything down and run the Hardware Editor, and do a scan, it detects both controllers, the CMB24D light goes solid red, and I can control the channels no problem.

    When I exit Hardware Editor, the CMB24D light resumes blinking and does not go steady when I start the Comm Listener and SE.

    As troubleshooting, I have tried:

    • Rebooting the CMB24D controller
    • Unplugging/plugging in the USB adapter
    • Switching the two Ethernet cables in the USB adapter, and only running one at a time
    • Switching the Ethernet cable to the CMB24D to the other port on the controller
    • Confirmed the controller is running the most recent version
    • Confirmed that the network (Aux A) setting is correct, and confirmed that the Unit ID is correct.  But even if these aren't, I believe the light should still go solid.

    None of these steps changes the outcome at all.

    My show has 20 controllers - I've never had this happen - what's going on?


  14. Thanks to everyone for their responses.

    What I'll probably end up doing is connecting both sets of dongles (LOR and HC) to the headers of the CMB24D board, and just use what I need for each show.  I say that because my Halloween elements are wired to the LOR pinout already.  My Christmas show RGB dumb pixels will be from HC because LOR doesn't sell dumb pixel strings.


  15. Hello everyone,

    I have a CMB24D controller with the dongles provided by LightORama.  I plan to decorate six bushes with dumb RGB bullet pixels.  Light-O-Rama doesn't sell dumb RGB pixel strings (otherwise I'd buy them), so I plan to buy the ones from HolidayCoro.  I have information on their Pinout (it's the EasyPlug4 configuration) but no information on whether I can use these with the CMB24D without having to wire it differently or fabricate some kind of adapter for the plug styles.

    Does anyone have experience with this?



  16. Good morning,

    I need assistance building a Visualizer fixture.  Here are the basic parameters:

    LOR S4 Version 4.4.4 (Newest Version)
    Matrix:  83 wide by 18 tall (I am using these numbers because I am changing an existing coro Tune-In Sign)
    Hardware:  PixCon16 with 16 x 100 bullet pixels.  I will be using 15 of the 16 outputs where each output is one DMX universe.

    First pixel will be at upper left of matrix.  I will then go in a horizontal zig zag pattern, using all 100 pixels for each output.  This is a complete list of what it will look like:

    Row 1 - Left to Right, DMX Universe 1 Pixels 1-83
    Row 2 - Right to Left, DMX Universe 1 Pixels 84-100, Universe 2 Pixels 1-66
    Row 3 - Left to Right, DMX Universe 2 Pixels 67-100, Universe 3 Pixels 1-49
    Row 4 - Right to Left, DMX Universe 3 Pixels 50-100, Universe 4 Pixels 1-32
    Row 5 - Left to Right, DMX Universe 4 Pixels 33-100, Universe 5 Pixels 1-15
    Row 6 - Right to Left, DMX Universe 5 Pixels 16-98
    Row 7 - Left to Right, DMX Universe 5 Pixels 99-100, Universe 6 Pixels 1-81
    Row 8 - Right to Left, DMX Universe 6 Pixels 82-100, Universe 7 Pixels 1-64
    Row 9 - Left to Right, DMX Universe 7 Pixels 65-100, Universe 8 Pixels 1-47
    Row 10 - Right to Left, DMX Universe 8 Pixels 48-100, Universe 9 Pixels 1-30
    Row 11 - Left to Right, DMX Universe 9 Pixels 31-100, Universe 10 Pixels 1-13
    Row 12 - Right to Left, DMX Universe 10 Pixels 14-96
    Row 13 - Left to Right, DMX Universe 10 Pixels 97-100, Universe 11 Pixels 1-79
    Row 14 - Right to Left, DMX Universe 11 Pixels 80-100, Universe 12 Pixels 1-62
    Row 15 - Left to Right, DMX Universe 12 Pixels 63-100, Universe 13 Pixels 1-45
    Row 16 - Right to Left, DMX Universe 13 Pixels 46-100, Universe 14 Pixels 1-28
    Row 17 - Left to Right, DMX Universe 14 Pixels 29-100, Universe 15 Pixels 1-11
    Row 18 - RIght to Left, DMX Universe 15 Pixels 12-94

    Pixels 95-100 of Universe 15 Not Used
    Universe 16 Not Used

    Can anyone assist me with building a Visualizer S4 Prop with these parameters?


  17. 4 minutes ago, k6ccc said:

    Can't help on the no matching channel thing.  As for the layout, check out zig zag.  However, not sure if that will work right without each string being an even number of wired strings.  In other words, (for example) 100 count string broken up into five segments.


    Yeah, that's why I was using the custom setting.  I'll probably just put in a ticket with LOR support.

  • Create New...