Jump to content
Light-O-Rama Forums

DrWizard

Members
  • Content count

    49
  • Joined

  • Last visited

Community Reputation

2 Neutral

About DrWizard

  • Rank
    Member
  • Birthday 06/22/1963

Contact Methods

  • Website URL
    http://wizlights.com

Profile Information

  • Gender
    Male
  • Location
    Orange Park, FL
  • Occupation
    Retired Programmer

More About Me

  • Interests
    Computers in general, Lights in general, Microcontrollers
  • How I learned about Light-O-Rama -
    The Wizard's of Winter viral video from 2005.
  • Favorite Decorating Holiday?
    Christmas

LOR Software

  • LOR Software Version
    4.3.24
  • License Level
    Pro

Recent Profile Visitors

311 profile views
  1. Extension Cord for pixels

    It should work fine if the cords are fairly short. Anything longer than 15-20 feet and you may start having data corruption issues. Longer than 20' I suggest you used twisted pair (cat5, cat6, ethernet). I use 1 colored wire for data, the other 3 colored wires for +5V or +12v, and the 4 white wires for ground. I sometimes used 18/3 extension cord wire for power injection. But cut off the 120 volt plugs and use some other kind of plug. You don't wanna accidentally plug the pixels into 120 volts!
  2. Question 1: It appears that dimming curves or advanced configuration are not supported on the CTB24D. I'm guessing that is because the D board uses ordinary PWM (Pulse-Width-Modulation) to "dim" the low-voltage direct-current, whereas the alternating-current uses a type of PWM that has to be coordinated with the zero crossing of the voltage. Yet I fail to see why that would preclude the use of dimming curves. Is there a way to do dimming curves on a DC controller? Question 2: I have some old 1602W's with the blue boards. What would be the cheapest and easiest way to get them to do dimming curves? Will the current CTB16K boards fit into the old 1602W cases, or is there an easier way? I have no incandescent lights left, everything I am controlling is either LED and/or something that should be strictly on or off, both conditions suited to dimming curves.
  3. This topic has been brought up before... in like 2008-2009. I'm sure things have changed a bit since then. So what is the current differences between the PC and K versions? From the photos, they both seem to have the same components. The boards look a little different, and use different connection methods, but that no doubt is because they are intended to fit in different cases. Is there any difference in the functionality or capabilities of these 2 boards? Do they currently both do dimming curves?
  4. I've spent a good many hours tinkering with version 5. Here's my 2 cents--- View Fades As Ramps: I miss this! I routinely go back and forth in v4. The main reason is that for long slow fades, it is hard to tell exactly where it starts (ramp up) or ends (ramp down) and it is more obvious with the ramps display. As an alternative (or in addition) a way to visualize where each individual effect starts or ends, perhaps by making the grid lines a little thicker, or darker/lighter? Adding a prop to the grid is not at all intuitive. I eventually memorized how to get to it, but the first batch of props I added, I had to keep clicking around trying to find it again. I think there should be more than one way to do this, and something more obvious than being in a drop-down box. Also, after creating and saving a brand new prop, prompt the user to add it to the grid. Pixel Strips: I don't (yet) have any grid or grid-like pixel displays. But I have loads of strips and strings. Most of the effects in the pixel editor are grid-oriented and pretty much useless for strips. Show us some love! I'd like to see more pixel editor tools for complex chases and patterns. I realize I'm just used to v4, but I find v5 confusing and overall not very intuitive. One final suggestion, and I know this is a complex one... A visualizer or live preview viewer that can be run (and opened and closed as needed) while a show is running, Preferably across the network. Good for a [remote] status check and to see where it the show it currently is at. Alternatively or in addition, a simpler status viewer with the name of the show, name of the song, current time within the song, perhaps which song is queued up next, controller status and any comm errors...
  5. [Admin Edit] - Sorry Audio was located on this share. It has been removed. You may share sequences, but not audio.
  6. Looking for Minions jingle bells

    Heh Heh! I was not aware the Minions had done a rendition of this. Just googled and found the YouTube video. Hillarious! May I get a copy of this sequence too please? wizard@wizlights.com Thanks in advance!
  7. Pink Floyd Time

    I probably won't use it in my show, but being a HUGE Floyd fan, I'd like a copy anyway please! wizard@wizlights.com
  8. Sugar Plum Fairy- remix

    Ooh, Ooh, over here, me too please! wizard@wizlights.com Who's the artist(s) or orchestra?
  9. I have a utility that I wrote for v4 of sequencer that does global search-replace of RGB colors. I plan to update it for v5, although not till after Christmas. v5's files are COMPLETELY different. I will have to rewrite all whole utility suite.
  10. Woo-Hoo! I'm thrilled to see support for the play/pause and stop keys have been added to the 5.08 beta! Thanks! Uh, hate to be greedy, but... Could you have FFWD increase the play speed, RWD slow it, SKIP-NEXT jump maybe 30 seconds or so ahead, and PREV jump 30 seconds back?
  11. Ok, So I just started working with the beta, I got started a few days ago with 5.0.6. When I load my old S4 sequences, it informs me that quite a few of my channels are being archived. At first, I thought this was just channels which did not have a corresponding prop in the ver 4 visualizer file. I have about a dozen of those that for various reasons I never put into the old visualizer. Example: Channels that control non-visual things such as the motor on the mirror ball, or that supplies 120V power to all the low-voltage power supplies so I can cut them off when the show isn't running. However, on closer inspection, I have found that it DID archive quite a few channels from my old files that were in ver 4 visualizer, including but not limited to the first 50, and last 50 pixels of a 600 pixel strip (DMX across 4 universes). I suspect this may be a bug. 1) What are the requirements for a channel to be properly recognized and NOT get archived? Does it just need to be in the old visualizer (.lee) file? Anything else? If I go back and add EVERYTHING to my old visualizer files, can I avoid archiving? 2) Would someone please elaborate on the process to salvage or recover an archived channel? I downloaded and viewed the "Expo 2017- Traditional Lights" powerpoint PDF which mentions this only briefly on slide 36.
  12. I have been playing with X-Mouse and have configured it to translate the pressing of the media keys on media center keyboards and remotes into the necessary keystrokes to control playback in the sequence editor. The idea being that I can stand in the yard watching the show as I make final adjustments and tweaks, and by pressing the buttons on my infrared media center remote, to pause, play, rewind, fast-forward, etc. thru the sequence. Much like you might do while listening to a song in Windows Media Player on a media center PC. My solution works, more or less, but it could potentially work better if the sequence editor supported this directly. The same idea could be applied to the show player as well.
  13. Merge two SE files

    I am working on a suite of utilities for manipulating sequence files. I was planning to announce a call for alpha testers soon. Amongst the utilities is one to split a sequence, and only keep selected channels, and another to merge sequences. Also in the suite is a util to perform a smart apply of a channel configuration, a util for sparkle effects, an RGB color changer, one that does polyphonic transcription, and more. So this is a little premature, as the utility suite is not ready for the public yet, but if you are interested in alpha or beta testing them, message me on this forum or email me at dev.utilorama@wizlights.com.
  14. Visualizer via LAN

    OK, so I see that this is not officially supported. Nonetheless, I would like to try and get it to work, but so far have been unsuccessful. I would consider myself to be pretty adept at computers, LOR, and networking. Perhaps someone can tell me what I've overlooked... The machine that plays the shows is an old Dell Laptop in the garage, on the LAN at 192.168.7.15. I'd like to be able to open the visualizer on my main desktop machine in the bedroom to just check the status every now and then. It's at address 192.168.7.7. The whole network is hard wired. The ethernet does pass thru 3 switches between the garage and bedroom, but note that I said switches, not routers, and no NAT or other translation is taking place. The machines can directly ping each other, share files, and run remote desktop without a problem. The entire LAN is gigabit. Control Visualizer is turned on in the LOR control panel and in the Sequence Editor on the laptop. I added a windows firewall rule on the bedroom machine to allow UDP port 30303 through and to send it to C:\Program Files (x86)\Light-O-Rama\Visualizer.exe. Windows firewall normally allows all outbound traffic without restriction, but after not being able to get it to work, I added an outbound rule on the laptop specifically allowing UDP port 30303 through. LOR software is version 3.1.12 Visualizer works fine locally, on the laptop. But remotely, on the bedroom machine, nothing happens. Suggestions???
  15. Reverse channel creation order

    nmiller: I have written a little utility I call the "Universe Creator" which I use to create channel configs for pixel strips on a DMX pixelnet controller. I can do them in RGB order, GRB order, BRG order, etc. and can do them in forward or reverse order. Alas, the utility program is very much "alpha" software and very quirky, so I can't share it (yet, I have plans to eventually). If you give me all the details, I will generate a channel config for you.
×