Jump to content
Light-O-Rama Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About mwilson6192

  • Rank

Profile Information

  • Location
    Syracuse, New York
  • Occupation
    Information Technology

More About Me

  • How I learned about Light-O-Rama -
    Researching the Internet
  • Favorite Decorating Holiday?

LOR Software

  • LOR Software Version
    A Beta Version
  • License Level

Recent Profile Visitors

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

  1. Since I have put things away for awhile, I just picked them back up and I feel (quite a bit) like I am starting from scratch. I have a full preview in S5 containing all of my planned eventual props. I was reviewing where I left off (I actually had completed my preview), and it dawned on me that the physical attributes of the entire display is required to be figured out in advance to adequately map to a network. I still have my house pictures with Sharpie markers in various colors outlining areas with which I intend to outline (windows, roofline, column trim boards). It was meticulous and had all measurements in inches, and all ribbons down to the pixel, where they would be cut, etc. Example: I intend to outline my windows with pixel ribbons (CCR's). One of my windows will contain parts of two (2) ribbons ("CCR's") to maximize my ribbon usage, and I calculated every window dimension using "lines unconnected" to maximize CCR coverage and to calculate the exact pixel counts (e.g. divide each window or roof line length by 4 to calculate WS2811 CCR pixel counts). Then, I carefully mapped every single side of a window or section of a roofline to a given network (I have Aux A through Aux D), ensuring to stay around a 2400-pixel population for each LOR enhanced network. Then I created groups of each window side into a given window, or a given set of roofline. This times lots of windows and lots of rooflines (a total of 22 ribbons). What a pain! I relied on the "Channel Summary" function to tell me when I overlapped a previous circuit count, and it was very good at doing that - but it doesn't tell you if you skipped a set of circuit count. I mapped all planned props, but I will not have anywhere near the props be a physical reality this year. I guess if one grew slowly through the years, adding to a preview wouldn't be too bad, but if you have a lot of props that involve complex utilization of pixels (ribbons, bullets, nodes, whatever) that are cut and soldered for maximum efficiency, this is a tedious exercise which requires one to map the props to a physical network laboriously. Anyone safely use more than 2400-pixels in a LOR enhanced network? With the latest generation of Pixie 8, Pixie 16 and Pixcon16 boards, can one exceed the 2400-pixel "recommendation"? Also, with the latest LOR sale I purchased the plug-n-play LOR 10W Flood set. When you map dumb RGB's in S5 Preview, do you use circuit 1 thru 3 for the first flood; 4 thru 6 for the second flood, and so on until you reach the eighth and final flood using circuit 22 thru 24? Thanks.
  2. Brian, that is quite generous of you. However, while that will help me, it will only help me - and no one else. I would think a video or tutorial of the same topic be created such that the next person, or the next 10 people, or 100 people, etc. could benefit from the knowledge that would be gained. In no way do I not appreciate your gracious offer - but I would like to pay forward the assistance that I have received via other tutorials, or from members of this forum, so the experience gained benefits the community, and a video or tutorial of sorts will do just that. Kind Regards.
  3. Alan, Thank you for your thoughtful and well-intentioned reply. To be clear, I have licensed LOR S5 Pro level -and- have licensed SS 60_CCR count on top of that. I have the latest S5.0.18 beta, and I believe I may need a slightly higher CCR license count. I do understand the basics (and your explanation is a very nice summary), and speaking only for myself, I have no problem with buying additional CCR counts if need be. To baseline this discussion, after researching all of the market options I chose the LOR-based market for software sequencing/control and hardware (read controller boards), and intend to stay as I have made the investment in both dollars and time. You are correct, my use case is to take the entire S5 Preview (constructed under the S5 Preview use case rules), and import the entire preview containing props into SS and have the props look like what was created (visualized). Jim is spending lots of time performing trial-and-error to get a candy cane to look like a candy cane in SS (and the poor chap is losing his hair in the process - and again thank you for sharing your experiences). Each of us have a tolerance for the time and effort (and expense) one is willing to put into a hobby. I am willing to learn and spend time and money gaining knowledge, knowing that there is no "magic button" to make things work perfectly, but my personal line is drawn at what Jim is doing. I have no desire to disparage either S5 or SS, as I have licensed both and want to use both. However, the present state of the S5 and SS interface (they are not integrated) is that the "visual programming" capability of S5 is lost when utilizing an S5 prop within SS, which seems like a step backward from S4 functionality from my perspective and thus there is the root of my frustration. The reason for focusing on SS includes not only on what you identified in your post above, but it would appear that using SS to sequence props comes easier to some folks versus PE (or Motion Effects in S5 vernacular), and this is certainly true for me and is why I have opted to use SS for the majority of my effects. I have to get better at using S5 PE/Motion Effects, and this is on me. But as I stated earlier, I have reached a "decent" level of utility using SS in a 16-ribbon "CCR" tree for example, and would like to extend this SS knowledge to all of my props, as long as I can recognize them instead of some blobs on a grid - like with an SS "CCR" ribbon tree. And therein lies my frustration. Thank you for your assistance, and I myself am beginning to start my busy season in my other hobby, which prioritizes above Christmas light displays because it is "good weather" based. I'm not walking away from this hobby, as I have invested too much money at this point and frankly I don't wish to walk away because the end result is what I desire, but for my own sanity I have set my expectations very low and whatever I produce will be "good enough" for this year - even if only 1/4 of my investment makes it into the display for this year.
  4. I am SOOOOOO frustrated and not following this discussion. I am dense, because I am not following how to properly utilize S5 Preview props and sequence the entire display into SS. I spent quite a few hours drawing the props in S5 Preview, with properly counted and assigned networks, channels, and groups (grouping multiple CCR strings into windows frames, etc.). I see Jim pulling his hair out over many trial-and-error attempts to get props to "display" and "act visually" in SS. I have no desire to get that deep into trialing items, and appreciate the time and patience that other members have spent and have joined this forum to learn from members experiences (and thank you in advance!). I understand the concept of getting SS .sup files back into S5, but how about going the opposite way? I put things away for awhile to let my frustration subside. You know what would be grand? A video showing a sample house with a sample set of props, such as the following: Some RGB roof lines (ribbons or pixel nodes, doesn't matter) Some RGB window outlines Some number of RGB candy canes A 16 RGB ribbon (or pixel tree) with an RGB star of arbitrary pixel count (say 170 pixels of six nested stars) Some number of RGB arches (or circles, whatever) Some number of RGB mini trees Some number of dumb RGB floods (say 8 floods - I just bought the LOR 8 - 10W flood kit, so I'm a bit biased here ... ;-)) Take this sample S5 Preview and show how to import the entire display into SS so that it LOOKS like the props that were laboriously drawn visually with S5 Preview. I have read the S5 documentation several times, and have understood the concept of VISUALLY designing the "stage" which is the S5 Preview. I also have firmly understood the concept of using SS to sequence the entire show. But this is where I repeatedly get lost. I have done really well with SS in sequencing a 16-ribbon CCR tree ... but I am missing how Default's method (or any other method) gets the S5 entire Preview "visually" into SS - not just creating a prop within SS and sequence that single prop. I just am not getting it ... so a video of this entire process using a sample of the above suggested props, correctly created from S5 Preview, showing how to get into SS visually so it LOOKS like S5 Preview, showing some sample sequences, then getting the entire SS display sequence back into S5, would be grand. If the capabilities of the software do not allow for this at this point, I'll just put things away (again) for a future date when the capabilities of the software advance to a point where this task can be accomplished, because I simply don't have the time (and more importantly the patience) to do what Jim and others are doing. I do follow these forums and read them regularly, and I know Default, k6ccc, and many others have contributed regularly, and for those of us who follow their lead and experiences, thank you for your contributions. It is appreciated, and I hope my frustration with my own lack of understanding doesn't come across negatively and reflect on others. Thanks.
  5. Thank you for providing that information. I will have to study the method outlined by @default and become one with it.
  6. So where do we stand with creating a "visualizer like" file out of the S5 Preview, and then importing into Superstar like the S4 version? I was hoping the S5.0.18 release would enable this function, and perhaps I am missing that functionality, but a quick check this morning doesn't appear to include this feature. Somewhere along the line I thought the .18 release was to enlarge matrix size in Superstar beyond 64 rows; provide pre-define props for S5 preview and "share" with Superstar; and enable visualization files to be created from an S5 Preview and imported/consumed by Superstar like the S4 release. There are no release notes that I see with .18 at this time. It's a good thing I have cut my expectations of myself in half for this year, so I don't make myself go crazy.
  7. Good question, Jim. I plan to mount my ribbons using HolidayCoro's Pixel Strip Mounts with Diffuser Cover (I bought a zillion of these at their Pre-Sale price). I was intrigued with the mounting of strips to an aluminum channel, and also was intrigued by the diffuser cover - same concept as place ribbons/strips in opaque PEX or HDPE pipe that some member are doing (same as I am with my Johnson arches). I am still configuring the mounting method with which to mount the HC Pixel Strip Mounts to EMT conduit, but I plan to build my roof lines, window frames and column "runs" using 3/4-inch EMT conduit. I will permanently mount the HC Pixel Strip Mounts to the EMT. Where the Arlington quick latch is located on a given run, I plan on building a very small raised section with gentle "slopes" where the "open" position on the latch clip will slide easily under the raised section, then snap securely closed. I really like the full grip circle of the latch clip as it encompasses the entire diameter of the pipe it is gripping. RBG Strips (ribbons). This is the exact same concept with the Arlington quick latch clips. While they are not clear, they are UV rated and are intended for permanent installation. I plan to paint each clip to match my house color and permanent mount the clips. As others have pointed out, repeated installation and removal of clips can strip a given mounting hole over time - more so for wood installation in fascia, etc. Being UV rated and painted to match my fascia, window frame and columns, they should be relatively "invisible" at the street. Snaps in place easy peesy as caniac said. I sure hope these work. I want them to work.
  8. ^^^^ Price is ~$0.81/latch clip (only available in bags of 100 count). As I noted in my post, I did look at the HC clips but they are only available in 1/2-inch size for PVC. I was interested in EMT conduit and larger sizes, so I did not compare price points.
  9. Look what I found today: Arlington QuickLATCH Non-Metallic Quick Latch Fittings for PVC, EMT or Rigid Conduit I have been searching for a while for a solution to permanently mount a fastener to my house fascia, columns, windows, etc. that would mount 3/4-inch EMT conduit, but not be extremely obtrusive as well as securely mount the EMT conduit and easily release it. In my research, many folks use PVC pipe to mount pixels/CCRs to your house fascia, columns, windows, etc. For mounting PVC pipe, the best solution I found was HolidayCoro which sells clear polycarbonate (UV rated) PVC pipe clips for 1/2-inch PVC pipe. I was looking for something similar but for 3/4-inch EMT conduit, because I personally prefer EMT over PVC (but note that the manufacturer indicates it is for PVC as well). Roaming around Home Depot and Lowes, I bought a couple of different "fasteners" but didn't like any of them. Then I stumbled across these fasteners today, made by Arlington Industries (link above). They are UV rated and come in sizes from 1/2-inch to 4-inch for EMT, Rigid and PVC conduit. The great thing is the ease of installation and equally the ease which one may remove EMT conduit. I intend to paint these hangers the same color as my fascia and windows (beige), permanent mount them, and simply snap the EMT conduit runs into place (just like the PVC pipe clamps). They look like they will be easy to mount (one of my runs is 17-feet), and importantly they look like they grip solidly. I ordered a bag of these from Amazon today, and will try these out when the weather gets better (11 below zero this morning in Syracuse, NY). I attached a video of this product as well.
  10. I just made my first large purchase from HolidayCoro during their January Pre-Sale. 50 x 50-pixel 8mm/12mm WS2811 12V black square node "lay flat" strings 40 x 50-pixel 8mm/12mm WS2811 12V black bullet node strings 40 x 30m/10m 5m WS2811 12V ribbons (equivalent to CCR-II ribbons) 3 x 60m/20m 5m WS2811 12V ribbons (for my Johnson arches) Lots of other supporting stuff (4 pairs candy canes w/rectangular WS2811 12V modules), lots of 5, 10 and 20 foot extension cables, 3 of the new HC 2500 enclosures, large RGB star, etc. Spent waaaay too much money, but the savings from buying in bulk with the pre-sale prices when compared to "other" pricing is just staggering.
  11. I made a major mistake ... I fell into this thread and have been following it (that was my mistake ). So today, I just couldn't help myself any longer and ordered an Amazon Pi 3 Kit (CanaKit), and snagged the last P10 Panels from DIY Express (I wanted 4 but there were only 3 available and they are now sold out). I decided on the Pi and Nano PiHat versus the BeagleBone and Octoscroller, just because I wanted to see what all the rage over the Pi was about. Now I'll be forced to learn DMX via LOR (as I want to control everything via LOR). I plan on using the P10 panel for a Tune To sign among other things. Now I'm into this hobby for even more money ...
  12. FYI ... I just received my Pixie 8 controller this evening, and it is a V4 (Version 4). The LOR Website picture for the Pixie 8 shows a V1, and the feedback racerc20 received from the LOR Help Desk (above in this thread) indicated that the Generation 2 controller was shipping. I have no idea of the significance of the V4 designation (I would have thought it would be V2 for Version 2 or Generation 2). Thought I would just communicate this information. Matt
  13. Thank you for the feedback. I just ordered a Pixie 8 and will build an enclosure with power supply to experiment with the various props I am beginning to build.
  14. I've only used SuperStar CCR Mode and not Visualization mode. Ready to learn the difference(s)!
  15. Rather than starting a new thread, I'll add to this thread. Brian, in this thread LOR Hardware - PIXIE4 Post, I was asking about the LOR Gen 2 Pixie controllers (Pixie 4, 8 and 16) and whether they can support a WS2811 60m/20m ribbon. This is a 100 pixel ribbon versus a standard WS2811 30m/10m 50 pixel ribbon (you can see some additional context to my question here). Along the same lines, I was asking whether SuperStar (v5.0.16) can "natively" support a WS2811 60m/20m ribbon. I have been happily sequencing a 16 CCR string at the "standard" density of 30m/10m (50 pixels). LOR sells a CCR II 100 pixel count CCP and CCB node strings. This would necessitate a grid length of 100 pixels versus 50 pixels. I was playing around with the Layout function, and did not seem to be able to generate a grid with a length greater than 50 pixels. I am in the stages of building a 16 CCR ribbon pixel tree, and was reconsidering utilizing a WS2811 ribbon density of 60m/20m versus the "standard" 30m/10m ribbon density pixel strings. Does/can SuperStar support a 16 CCR pixel tree but at a "native" density of 60m/20m (100 pixels, 300 channels)? If yes, how do I do that? Thank you! Matt
  • Create New...