Jump to content
Light-O-Rama Forums

k6ccc

Members
  • Content Count

    7,980
  • Joined

  • Last visited

  • Days Won

    160

k6ccc last won the day on August 3

k6ccc had the most liked content!

Community Reputation

950 Excellent

4 Followers

About k6ccc

Contact Methods

  • Website URL
    http://www.newburghlights.org

Profile Information

  • 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.
  • Favorite Decorating Holiday?
    Christmas

LOR Software

  • LOR Software Version
    5.4.2
  • License Level
    Pro

Recent Profile Visitors

6,875 profile views
  1. You started a new topic in the Sequence Sharing section of the forum that looks like it was supposed to be a reply to something else - I assume it was supposed to be a reply to your Free Sequence Downloads thread. I would suggest a copy and paste from here to that thread and then request that this thread be deleted.
  2. Make sure the video and audio drivers are up to date. Remember that when running a show, most of the video stuff is not needed - hence the reason that it works when playing a show as opposed to running Sequencer. Just my educated guess. I recently was having this computer regularly doing a Blue Screen of Death when running my video editing software. A search of that software forum suggested updating the NVIDIA drivers (which were two years old). Updating the drivers and problem seems to be solved. Note that video drivers generally are NOT updated with Windows updates.
  3. Thanks Matt. I have been 100% S5 for three years, and I still figure I might learn something. I will will be there!
  4. If you are sequencing in SuperStar, SuperStarLights.com also has sequences, and Brian keeps adding more.
  5. First of all, you don't do anything to a LOR controller to "put it into DMX mode". Most LOR controllers will accept DMX commands just as easily as they accept LOR commands. Some of the newer LOR controllers have switches or jumpers to select LOR or DMX pinouts. Those switches or jumpers have nothing to do with the controllers ability to process both LOR and DMX commands. What those switches do is select which wiring pinout the controllers use. For background, when LOR started building controllers, there was not a standard for DMX using a RJ-45 connector. At that time, Cat-5 cable was not overly available and it was expensive. As a result a lot of people used standard telephone cable with RJ-11 connectors, and LOR built the controllers to accept those connectors and used the center two pins. With RJ-45 connectors, LOR continued to use the center two pins for data (pins 4 & 5 on a RJ-45 connector). When the DMX standard expanded to allow RJ-45 connectors, they chose to use pins 1 & 2 for the first data circuit and optionally pins 3 & 6 for a second data circuit. Pins 4 & 5 are unused and pins 7 & 8 are data ground (if used). So, pins 1 & 2 on the DMX end, connect to pins 4 & 5 on the LOR end. Don't worry about the grounds, DMX does not require it (although it is often used), and LOR does not use it. LOR does use pins 3 & 6 for power on some controllers, so you could in theory connect the DMX ground to the LOR power ground (pin 6 if remember right), but it is not needed.
  6. I am not sure, but I THINK it would be the media, .play.lms, and .lid files for each song. I also sequence and run show on different computers, but for both computers, they are using the file server for the files. That way what each computer sees as L: is really the same folder on the server, so I don't have to do anything to move the files.
  7. Devan: The ELLs are LOR network only - No DMX. MikeToo: The Pixie 16 controller is LOR network only - No DMX or E1.31.
  8. I will go along with JR, just rebuild from scratch in the S5 review Editor. It's not that hard to do, and does not take all that much time - my 66K channel Preview took no more than an hour to create.
  9. Danger! Danger! Will Robinson! That saves the files on the same computer, on the same hard drive, in the same folder. It does not protect you from a hard drive crash, theft, fire, or computer virus. About the only thing that accomplishes is lets you go back to a slightly earlier version in case you REALLY mess up your sequence.
  10. For your show computer, you can get away with a fairly low end computer. Until 2 years ago, I was using an ancient XP desktop with a 6,000 or so channel show without any issues. Even though I am now running about 66,000 channels, I could likely still run that old computer, but I really wanted to get away from XP, and I did not want to attempt to upgrade that old computer to Windows 7 or 10. For what you are planning on running, your friend's computer should be fine for both sequencing and running the show.
  11. This is essentially a re-post (with a little editing and updating) from a six year old thread that has not had any activity in a couple years, so starting a new thread rather than rehash the old one. I'm going to bring this up (again), because we are seriously into sequencing season, and every year at least one person shows up on the forum after having lost all or part of their sequences due to a hard drive crash, home burglary, fire, accidental deletion, computer virus or ransomeware, or some other reason. I'm hoping this reminder will keep at least one person from being in this awful situation. The summary is: Backup! Backup! and Off-site Backup! I know that some of you have seen parts of this before, but take this as a reminder. I am a bit unusual in that I have a domain controller / file server and all computers log into the domain. Therefore, most of you can't do exactly what I do, but it should give ideas. On both the show computer and primary sequencing computer, there is a mapped network drive of L: that is really D:\Shared\LOR on the server. All the LOR files are stored on the server. My normal routine goes something like this. While I am sequencing, the file being worked on is saved with a new filename regularly with the date and a revision letter as part of the file name so it's easy to tell what is newer than what. For example a file might be: Jingle Bells 2020-08-03a.loredit I'll bet most of you can figure out what song it is, and what date that I edited it. The "a" after the date indicates that it was the "a" revision for that date. Every time I save the sequence, I save with a new filename and increment the revision letter. BTW, if I were to get to a z" revision, I figure I have spent too much time sequencing and it's time to quit for the day. I think I got to a "s" revision once. Usually when I am completed sequencing for an evening (and happy with it) or during the next session, I will delete the intermediate versions leaving only the last version of the night. The next step is to upload the last version of the night onto the cloud. In my case I use Google Drive. The D drive on the server is currently two 1 TeraByte hard drives in a RAID-1 configuration. This protects against a single drive failure. There is also a third identical drive as a hot spare (the server has room for eight drives), and when I need more space, I will add two more drives to the RAID array. Note that in the event that the RAID controller detects a problem, it will immediately send me an E-Mail. The hot spare drive will protect against a second drive failure (provided it happens long enough after the first failure that the RAID controller has moved it into an active role and fully rebuilt the array). The data on the server is backed up weekly to an external hard drive and taken into my office at work. I have two external hard drives that swap places as the off-site backup. In other words, there is always a backup drive at work that is no more than 8 or 9 days old. And as noted above, important files are copied to the cloud right away. In the event of a problem that takes out the server completely (house burns down, major theft, Sax's RansonWare, etc), the data is sitting somewhere else - usually more than one other place. One note on cloud storage. Some cloud storage solutions will create a drive letter on your computer. That way you can save or copy files to the cloud just as easily as a local hard drive. This is very convenient, but does come with one major gotcha. Because it appears as just another hard drive on your computer, malware (such as a virus or RansomWare) can access it just as easily as a local hard drive. In other words, your cloud storage could get wiped out at the same time as your local hard drive. Keep that in mind. You will note that I have made several references to having backed up data off site. I can not stress the importance of this. There are several things that are quite capable of removing or destroying your backup if it's sitting on the shelf right next to the computer. At least one person here on the forum had their home burglarized, and the bad guy took both the computer and the backup disks that were right next to it. A fire can easily destroy both as well. And yes, we had someone on the forum a few years ago that lost their house in a large brush fire that took out their backups that were in another building on their property. Just for good measure, this computer (what I normally use for sequencing), the LAN switch in this room, and internet modems are protected by a UPS that has about an hour of battery life. The server, show computer, routers, and LAN switch in the data cabinet, are protected by redundant UPSes that currently are good for about 90 minutes (each UPS feeds a different power supply in the server), and when that project is completed, will have about 8 hours of battery (unless it's during the day when the solar will extend that). I also get sent E-Mails in the event of loss of primary power for any of the UPSes. During Christmas show season, all the active LOR files are also copied onto a backup folder on the show computer. In case of a failure of the server, I simply change the mapped network drive of L: on the show computer so that it points to C:\LOR_Local, and all my files are there. I did have to use that in 2014 when my ancient server was dying and kept re-booting. In the event that the show computer dies, I can move the three LOR networks back to the server and run the show from there - which is how I run the year round landscape lighting show. In case you are wondering why I am so detailed in making sure stuff stays working, it comes from what I do for a living. I run a regional public safety two way radio system with the understanding that under the wrong set of circumstances, failure of the radio system could result in someone dying. We take system reliability VERY seriously at work! That mentality rubs off at home...
  12. Unit IDs ARE in hex, so set start ID to either 10 or 11 (depending on how you think). In my opinion, it is easier to think "All of this Pixie is 1n so string 3 is ID 13" as opposed to string 3 is ID 12. Yes, starting with 11 does result in string 16 being ID 20. Like I said, depends on how you think.... Lay out your Unit IDs in something that makes sense to you. In my case, my network 1 (called Regular network) is blocked off for IDs 01 - 1F (although only one ID is used on that network). My network 2 (called Aux A network) is blocked off for IDs 11 - 1F, and my network 3 (called Aux B network) is blocked off for IDs 21 - 2F. BTW, if you are running more than one LOR network, you CAN use the same controller IDs on different networks - for example: Regular Network, Unit ID 07 is completely different than Aux A Network, Unit ID 07 as far as the software is concerned. However, it is easier for us human beings to keep is straight if you don't duplicate Unit ID numbers on different networks.
  13. I don't have a website for one, but I do have an Excel spreadsheet saved that I found some while ago. I just stuck it up on my website. Download the spreadsheet and run it from your computer (does not run on the web page). http://newburghlights.org/share/Slowpoke/
  14. If you are doing it in E1.31, you must use the Pixcon 16 (assuming you are wanting to use LOR controllers). The pixie controllers are LOR protocol only. However, if you can run it over a LOR network, you could use the smaller (and quite a bit less expensive) Pixie controllers. BTW, changing a couple props in the S5 Preview Editor from E1.31 to a LOR network would take all of a minute or two. Then open each sequence so the Preview can update, AND SAVE the file, and you would be good to go.
×
×
  • Create New...