Jump to content
Light-O-Rama Forums

DevMike

Administrators
  • Content Count

    3,858
  • Joined

  • Days Won

    63

Everything posted by DevMike

  1. Today we released production version 5.3.10 of the Light-O-Rama Software Suite. This is an official production release, not a beta release. S5 fully integrates the Pixel Editor, Sequence Editor, and Visualizer into a single program and adds many enhancements to help you program large channel count stages. S5 uses a different methodology called 'Visual Sequencing' to create amazing sequences and has new automatic programming tools called 'Motion Effects' that will speed your sequencing. For more information on S5, please see the "Sequencer (Showtime 5)" section of our Tutorials and PDFs page on our main website. The latest S5 help can always be found online here: http://www1.lightorama.com/downloads/5.3.10/help/ How to check if your license covers this version To check whether or not your license covers this version, please go to the license retrieval page, and enter your email address (the one you purchased your license with). An email should then be sent to you with information about your license. The "Summary" section of the email will tell you whether or not your license covers the latest version. If the email says... Your license covers the latest version, 5.3.*. ... then your license already covers this version. You can use it without making any additional purchase. Please note, though, that your computer may not yet understand that your license covers this version, so when you install, it might tell you that you are running in Demo mode. In this case, simply reactivate your license (for example, via "Upgrade Light-O-Rama" on the Sequence Editor's "Help" menu), and your computer will then learn that your license is valid for this version. On the other hand, if the email instead says... Your license does not cover the latest version, 5.3.*. ... then your license does not cover this version. In that case, you have several options: Upgrading or Renewing Your License (1) You can continue using whatever version your license does cover (for example, perhaps your license covers version 4.1). (2) If you want to take this opportunity to increase your license level to take advantage of additional features, you can purchase a license level upgrade. This counts as a license renewal too - that is, your license will now work with this new version (and some future versions too). So, if you do this, there is no reason to also purchase a license renewal. (3) If you already own a Light-O-Rama license, but you do not currently own Light-O-Rama SuperStar, or if you want to upgrade SuperStar to a higher number of CCRs/channels, you could purchase or upgrade SuperStar. This also counts as a license renewal for the rest of the Light-O-Rama software suite, so if you do this, there is no reason to also purchase a license renewal. Please note that you must already own a license for the rest of the Light-O-Rama software suite in order to take this option. (4) If you do not want to purchase a license level upgrade or Light-O-Rama SuperStar, you can purchase a license renewal. Your license will now work with the new version (and some future versions too), at the same license level as it currently does. For example, if you have an Advanced license, it will remain an Advanced license, but it will now cover the new version of software. What's New in Version 5.3.10 Fix for Looping Show Player - On some Windows Systems, usually but not limited to Windows 7, the LOR Show Player would crash upon trying to start a show. When it crashed, the LOR Control Panel would attempt to recover and restart the Show Player. This would cause the Show Player to loop on these machines and not actually play a show. Other Bug Fixes How To Get the Latest Version You can download the new version from the software download page. If that page lists a different version number as the latest version, please click your browser's refresh button. Thank You!
  2. This. And it's what we recommend too. With pixel controllers coming way down in price (especially ones like our Pixie controllers), it makes more sense to de-centralize. Yes, you may end up spending a little more when you factor in quality power supplies, but the benefits far outweigh that. Now that is not to say that giant controllers don't have their use. For example, a large pixel tree can consume 16 ports of a pixel controller without a sweat. That is what I would run there, not 8 * 2 ports. But if I'm putting pixels on a couple of bushes [or anything with some distance between them], a 2 port pixel controller goes there. Plan and use the right size for the job
  3. This is a known issue with Windows 7 and the show player. A release will come out shortly that addresses the issue.
  4. ABSOLUTELY NOT! You are the informed consumer all companies wish they sold to. You and I shop the same way: based on VALUE not on COST. Let's talk shoes for a moment. My shoe of choice is a loafer (well, actually a boat shoe). Shoes come in vastly different qualities and vastly different costs. I discovered long ago (when I was much harder on shoes) that I could spend $20 on a pair, or $80 on a pair. The $20 pair would fall apart after a year. The $80 pair would fall apart in 3. The $20 one is the much better value - even though it is the lowest quality.
  5. The help file probably has all the information you need. You need to have a Deluxe MP3 director. That is an MP3 director that has a real-time clock built in. http://www1.lightorama.com/help/index.html?differences_between_mp3_direct.htm Scheduling shows for different days/times: http://www1.lightorama.com/help/index.html?select_sequences_and_show_opti.htm
  6. It is not fair to discount ALL of China as 'cheap Chinese' . Most mfgs in China can make product and either adhere to your specifications, or will produce several different 'grades' of a product on speculation. Take fictitious USA companies "H" and "L". They may both order from a Chinese manufacturer some product "X", also fictional. In fact they could order from the exact same mfg. "H" orders the least expensive version of "X" available from the mfg. This product is made 'on spec' IE, the factory makes this version (and probably several others) as a kind of 'default' product. Knowing that there are some companies in the world where price means EVERYTHING, they make it as cheap as possible. "L" on the other hand contracts with a mfg specifying that they want "X" to be made to their higher tolerances, using these upgraded (higher price) parts, and these optional additional processes (which add durability). What "H" gets is low quality: Sure, it does what it says it will do - but it may not last long, support everything it should support, etc. "L" on the other hand gets a much higher quality product - because they specified their requirements. If product X doesn't meet the specific high requirements, "L" doesn't pay. If it does, 'L" paid a little more and so in the end will charge a little more. "L" may even have negotiated with the mfg to offer some business-to-business warranty: IE, if more than Y% of an item fails, the mfg is on the hook for the failures and will compensate "L". So in the end what you have are 2 companies that have product X. The product "H" sells is less expensive and offers no warranty. The product "L" sells costs more, but is made to a higher specification. It may even have additional features. Because "L" contracted with the mfg for higher quality products it can offer a warranty. Both were made in China, and may have even been made in the same factory. Moral of the story: Just because it's made in China does not mean it is cheap or low quality. You can not compare the product "H" has to the product "L" has. Yes, they may perform the same function, but they could be completely different in quality. Side bar 1: Keep this in mind - Never ever let price alone dictate your purchase. "H" may sell you something for $10 and every year you have to replace 90% of them. "L" on the other hand may sell you the same item but made to higher specifications for $22. The failure rate may be 5% per year, but the item has a 2 year warranty. On the surface, "L" is more than twice the price. Why buy something for $22 when "H" sells it for $10? And this would be true IF you only expect to use an item once. Yes, sometimes the cheap way is the best way. But if you are looking to reuse the item, is it REALLY? Think about it. Between years 2 and 3, you will have most likely purchased from "H" twice and spent $20, and it is all but guaranteed that at the end of 2 years, your item is broken AGAIN (90% failure rate). At year 3, you have to purchase AGAIN - $30. Sometimes you may get lucky, most of the time you will not. If however you spent $22 at the start - even if you were unlucky and hit the failure on year two, you start year 3 with a new item - at no cost, and with something that is designed to last at least 2 years (or why would "L" offer a warranty?). At year 3 you save (make a 'profit') of $8. Let's say that item only lasts until year 4. That's $18 in your pocket for that one item compared to "H". Over 4 years: "H" = $40 (and a high probability it is broke AGAIN - 90% failure rate). "L" = $22 and a high probability it is probably STILL WORKING (5% failure rate) Naturally your situation should dictate which you buy. If you are changing a part on your car and expect to do it once in a lifetime, do you buy the $50 tool from Lang, or do you buy the same tool for $2 from Harbor Freight? Harbor Freight for the win - use it once, throw it away. Side bar 2: The sad thing is that the profit margin "H" has is usually much higher than the one "L" will have. Let's say "H" purchases their item for $5 each, and sells them for $10 each - a profit of 100%. "L" on the other hand will spend $15 each, but can only sell (due to market pressure) at $22. The profit there as a percentage, is around 50% - they sell a better product but make less money per sale.
  7. Hey here we are again! The season is off to an early start. Let's see what's happened so far: We're only trying to be nice: We are more than happy to send parts to our customers to repair controllers/etc. Some customers are shy and will ask us for part numbers, etc and somewhere they can buy the parts. We always turn around and tell them - Hey! We'll send you the parts, usually at no cost. Just tell us what you need (and tell us that you know how to actually change the part in question). They are being polite, and we appreciate that! So a certain customer (a Dr. of something or other) recently asked us for a part number for the RJ45 jacks on a controller. We send him the obligatory 'Are you sure you can do this work, and if so just tell us what you need'. 9 days later he replied that he can in fact do the work and he asked for 20 RJ45s and 20 Triacs. Now, that is a lot of parts. This person would have AT LEAST 10 controllers that have both RJ45s broken. Most likely it would be more - typically only 1 jack gets busted on a controller. So in my eyes, this HAS to be one of our bigger customers. He's also asking about the jacks and triacs for EVERY generation of controller we have ever sold. Now at this point, it's not really about the cost of the parts. At the quantities that we purchase, each one of those is a few cents. The RJ45s are probably around $.40 each, and the triacs are around $.80 so we are talking at most $25 + shipping. In other words, we are not going to go bankrupt even if this is not on the up and up. What is odd is that this is the first ticket we have ever got from this person, and the person to whom he wants the parts shipped is not him. You would think with that many different controllers, that many different generations of controller, and that number of parts he would have had some contact with us at some time in the past. I go searching for this person in our orders system and get NOTHING. Not a single hit. I also search for orders from the person he wants these parts shipped to. Nothing. Again, it's not a question of cost. But we also don't want to be sending parts to every Tom, Dick or Dr. David that asks, we want to send them to our customers. As soon as we opened (he replied at around 1AM) I asked the person what name the controllers were ordered under. 2 more days pass and the reply comes that I am wasting his time. Now in his defense he did ask for part numbers initially - But we would much rather send a customer the parts. We get them for a lot less than he can (Those jacks are going to be around $1.25 each, and the Triacs around $2.25 each if he buys them - $65 plus around $15 shipping - $80), AND it's just good customer service. So in the end we sent him the part numbers and have not heard back from him. However it's still a strange situation. Frankly I think my initial gut reaction was right - despite saying he wasn't looking for freebies, I think that is EXACTLY what he was looking for. Does it make sense to berate someone who is trying to save you $80 and just wants a little more info? I guess sometimes, just being nice get's you yelled at. PS: To everyone out there that has higher education, the MDs and PHDs and the like, I respect the heck out of you. I will call you Dr. But when you stomp your feet like a little kid, say someone is wasting your time, and then sign your eMail with DR. SO-IN-SO, as if somehow you THINK you are more important, you will get laughed at - and get absolutely NO respect from me
  8. You need to first configure the board (which requires communication). Your Pixel type may not be set correctly which will not allow the pixels to work even with the hardware test.
  9. That's a Windows thing.... Something, somewhere on your computer is running an installation process - it could be another program trying to automatically update itself, or it could be Windows itself trying to do an update. Since Windows wants to track changes by install, only one install can run at one time. Ensure all your Windows Updates are done. Then restart your computer by using the window's start button, power, and then 'Restart'. Don't just power off or select power off - those are not true re-starts in the world of Windows. You must select the 'Restart' option. Once you have done that, give the install another try.
  10. The issue is Windows 7 Windows Media Player and/or Win 7 itself. From what I could gather from Matt's description of the issue, both Windows Media Player and S5 want to use two different DLLs that just happen to have the same name. The problem is these are actually two very different libraries (IE: That other guy you know named Mike is not this Mike :P) That should not be a problem (and isn't in any other version of Windows and or media player or whatever goofy combination this is caused by) since they are in different locations. When a program needs a DLL, usually Windows will search the registry first for DLLs that have been registered. This uniquely identifies them system wide. If they can't be found in the registry, Windows will next look in the folder the program is executing from, again which should be unique (this Mike and that Mike can't be in the same exact space at once). In every other version of Windows: Windows Media Player needs ITS DLL. Windows is returning to it the correct location of its DLL - either because it is registered, or it's in the same folder as Media Player/etc. In Windows 7: Windows is returning the location of OUR DLL to Windows Media Player, not the one it should be. WMP then goes to use something in the DLL and ITS NOT THERE (because it's the wrong one). Bad thigns happen. In this case the 10054 error you are seeing is probably caused by this issue, but not directly. When WMP can't find the routine in the DLL it wants, it panics, barfs up errors and then crashes. When we catch that crash, we panic, barf, and attempt to recover by restarting the show player process. When we do that, all the previous connections become invalid and have to restart - you then see that 10054.
  11. Connect the controller to the USB adapter and start the hardware utility. Status light should go solid after a few seconds. Press the 'Refresh' button and wait. The top center will show the unit once the scan is complete. The first 2 digits are the unit ID hardware utility found the board at. Is it the unit ID you set, or is it different? Remember, ports are units. The first port is the unit you set. The next port is unit +1, then unit +2, etc. Don't forget HEX.
  12. Ok, so let me break this down as best as I can using the PixCon as an example. There are 2 things you need to have a good grasp on - one is 'Protocol', the other is 'Transmission Medium'. Let's talk first about transmission mediums. In the LOR world, there are TWO that we are mainly interested in. RS485 Ethernet There are pros and cons to each of those, as well as differences in how the physically work - we won't get into those at the moment. While both use the same type of cables, sockets, etc they are not physically the same. You can NOT directly connect one to the other. Connecting RS485 to Ethernet (or vice versa) will probably cause bad things to happen as they are VERY different electrically. Notice there is no mention of PROTOCOL here. Let's now talk about Protocol. There are several of them in the LOR world: LOR ELOR DMX A protocol is nothing more than an agreed upon standard to encode and decode data. Basically, protocols are rules: Put this data in this position, use this data to determine what the next X pieces of data are, etc. Notice that there is no mention of TRANSMISSION MEDIUM. The protocol you want to speak is dependent on the systems you are connecting to. These two groups of things, transmission and protocol, are independent of one another and so they can be combined - 1 from A, 1 from B. The thing to remember here is that RS485 was FIRST (historically speaking). That means a lot of times when we talk about things, if it is being sent of RS485 we 'forget' to mention that part. It's implied. When we combine 1 from transmission medium, and 1 from protocol, we give that combination a new name. That new name also comes with additional rules about how the data is sent (we call that 'encapsulation' or 'wrapping' or putting data into an envelope. While there is nothing wrong with making any combination of 2, at this time only some combinations are actually supported. So for example, when we talk about LOR and ELOR protocol, we are always talking about something sent over RS485. Not because there would be anything wrong with sending LOR/ELOR over Ethernet - we simply don't do it because we have not written code to make it happen. If we did, we would give it a name, probably something along the lines of LOR/ELOR ACN. Which leaves us with DMX. DMX can be transmitted over BOTH transmission mediums. When we send DMX over RS485, we call it (simply) 'DMX' - Remember, RS485 came first. Back then DMX described BOTH the protocol and the transmission medium. It probably would have been better to rename it something like DMX-SERIAL or E1.11 (which is the standard name for DMX over RS485). But several years later, the need for more channels and more speed meant that DMX was running out of bandwidth. So the ESTA decided to divide DMX into two pieces. The fist piece would be called 'DMX' and is identical to what has been out there for years and years. The other is called E1.31 (More correctly called 'streaming ACN', but no one uses that). E1.31 is simply DMX protocol that is transmitted over Ethernet. Summary: When talking about LOR or ELOR, we are always talking about a protocol that is transmitted over RS485. When we are talking DMX, we could be talking about RS485 transmission, OR Ethernet transmission. Most people will make the distinction by saying DMX or E1.31, but not always. If you are unsure from context you should always ask. Continuing... Transmission Medium is something PHYSICAL. By that we mean there are very different physical attributes of the signals on the wires. This could mean differences in voltage, amperage, etc, so transmission media are kept to SEPARATE physical connections. On a PixCon16, you will see several RJ45 ports - those keystone looking sockets. One of these is metal, the others are plastic. There are reasons why the one is metal, but they are technical and don't need to be discussed. The metal jack on a PixCon16 is for Ethernet (only). The 5 plastic jacks are for RS485 (only). So in order to run E1.31 (which is DMX over ETHERNET), you need to use the metal jack. It is the only jack capable of Ethernet. If you are running LOR or ELOR protocol, you'll be using 2 of the 5 PLASTIC jacks - the two stacked one on top of the other. You still didn't answer my question, Mike OK, so now you are really shaking your head. What I have just told you is that you are either going to use the metal jack (for e1.31) and NONE of the plastic ones, or only 2 of the 5 plastic jacks for LOR/ELOR. WHAT?! Why have all those jacks? So we know that long ago there were these DMX devices that ran on RS485. In fact, 95% of theatrical lighting devices STILL run on DMX over RS485. Wouldn't it be nice if we had some kind of board that let you go from E1.31 (so you could take advantage of the higher speeds/etc it offered), and then convert that to DMX over RS485 to be able to use all these other devices? THAT is what those other jacks are for. You can configure a Pixcon that is running E1.31 to act as a 'BRIDGE' to go between E1.31 (DMX over Ethernet) and DMX (DMX over RS485). Since there is no such thing as LOR protocol over Ethernet, even though those jacks that can run RS485, you won't connect LOR devices to them (at least, not in LOR protocol mode. Keep reading). Oh Cool! I can run 4 regular DMX devices from a PixCon16 then? Nope. You can run 4 UNIVERSES of devices! One more thing to learn about RS485. if you think about LOR controllers in general, like our 16 channel controllers, etc, you'll see that each one of them has TWO RJ45 jacks on them. One is for IN (from a previous controller) and the other is OUT (to the next controller). The PixCon is no different in this respect when it comes to using it - it has an IN and an OUT. Physical DMX can do the same things - you can 'daisy chain' multiple devices together to the same universe. So each one of those 4 jacks is the START of a separate DMX Universe And since it is the START of a string, it only needs 1 jack per universe. Only one of the 'double stacked' plastic jacks is going to be used. So can I DRIVE the PixCon16 with DMX over RS485 data? No. And the reason for that is because DMX protocol itself does not allow for the number of channels required to drive pixels. There are only enough channels in the DMX protocol to handle 170 pixels. The PixCon16 can drive over 5,000. What about the other 4800+ pixels? So then I can only drive 170 pixels on the PixCon using ELOR? Nope again. Remember the limitation we talked about is on the Protocol, not the transmission medium. ELOR protocol allows for many thousands of pixels since it is designed to handle them. Want to learn a little more about DMX, E1.31? Read the "An Introduction to DMX and E1.31 for Pixel Control" document we created several years ago. What's the catch? If I can drive as many pixels on ELOR as I can with E1.31, why would I go through the expense of adding network switches, routers, etc? Actually that is not what we said. I said we could drive many thousands of pixels on ELOR (RS485), but I never said you could drive as many pixels as on E1.31 (DMX over Ethernet). The reason you go with E1.31 is that it has a HUGE advantage when it comes to Bandwidth over RS485. You can transmit the data for 100,000 pixels over Ethernet and not break a sweat. Ethernet is MUCH MUCH faster. If E1.31 is so much better, why support RS485 at all for Pixels, IE, PixCon16 in ELOR mode, or PixieXX controllers? Because E1.31 can get complicated in a hurry, and not everyone needs more than a few thousand pixels. Is there ANY way to drive LOR controllers over E1.31? Yes. Almost all of our controllers understand BOTH LOR and DMX protocols! So let's say you have a PixCon16 and 3 LOR 16 channel controllers. You are already running the PixCon16 with E1.31. Address your LOR controllers NOT as LOR controllers but as DMX devices (see the manual for your controller). Your PixCon16 takes the E1.31 commands, BRIDGES them to RS485. Taking it full circle.... So why doesn't everyone buy PixCon16s? Why sell Pixies at all? The PixCon16 is a VERY powerful board. On a single network with a single cable per device you can run hundreds of thousands of channels of all types: pixels, AC, Servo, DC. You could have strings of hundreds of AC controllers, a pixel tree that required 4 PixCon16s itself. When it comes to flexibility and functionality the PixCon is second to none. But all that flexibility comes at a VERY steep cost - learning how to use it. The PixCon has so many features, and different ways that those features can be used, that is quite easy to get it into a state where it does NOT do what you want.
  13. You may occasionally see 10053/10054/10061 (and others) errors in the log for the LOR Comm Listener. These errors are usually followed with some error description text that is similar to " An existing connection was forcibly closed/rejected by the remote host". The text can be different, but the general gist is that someone closed a connection to someone else. These errors are transient and a normal part of Ethernet communication. They happen all the time on your LAN without you noticing, or even between different software on the same computer using TCP/IP to communicate. In almost ALL instances, simply ignore the error. If you are having an issue with the LOR software, this is most likely not a cause or a symptom. What those errors boil down to is that someone tried to send data to someone else, and something happened to that data. Either it was corrupted, the transmission timed out, the connection went down, etc. When this error occurs, the connection is closed by the side detecting the error, a new connection is automatically established, and the data is re-transmitted. If you are seeing a few of these, or even more than a few over a long period of time, there is nothing to worry about. Nothing is wrong, and things are working exactly as they should. If however you are seeing hundreds of these a minute, then there is an issue with your network somewhere, or possibly with the computer itself that does need to be looked at.
  14. I don't see a 719009 either.... I do see where you have 2 tickets (neither ending in 009). I'll use the new one to get you replacements. Just leave the other one closed please.
  15. In his PM to me , he typoed the ticket as 709009. That was what I checked. I'll make sure Dan knows about 719009 then.
  16. Wow, sure would be nice if there was a company that stands behind their strips and warranties them, huh?
  17. Today we released production version 5.3.8 of the Light-O-Rama Software Suite. This is an official production release, not a beta release. S5 fully integrates the Pixel Editor, Sequence Editor, and Visualizer into a single program and adds many enhancements to help you program large channel count stages. S5 uses a different methodology called 'Visual Sequencing' to create amazing sequences and has new automatic programming tools called 'Motion Effects' that will speed your sequencing. For more information on S5, please see the "Sequencer (Showtime 5)" section of our Tutorials and PDFs page on our main website. The latest S5 help can always be found online here: http://www1.lightorama.com/downloads/5.3.8/help/ How to check if your license covers this version To check whether or not your license covers this version, please go to the license retrieval page, and enter your email address (the one you purchased your license with). An email should then be sent to you with information about your license. The "Summary" section of the email will tell you whether or not your license covers the latest version. If the email says... Your license covers the latest version, 5.3.*. ... then your license already covers this version. You can use it without making any additional purchase. Please note, though, that your computer may not yet understand that your license covers this version, so when you install, it might tell you that you are running in Demo mode. In this case, simply reactivate your license (for example, via "Upgrade Light-O-Rama" on the Sequence Editor's "Help" menu), and your computer will then learn that your license is valid for this version. On the other hand, if the email instead says... Your license does not cover the latest version, 5.3.*. ... then your license does not cover this version. In that case, you have several options: Upgrading or Renewing Your License (1) You can continue using whatever version your license does cover (for example, perhaps your license covers version 4.1). (2) If you want to take this opportunity to increase your license level to take advantage of additional features, you can purchase a license level upgrade. This counts as a license renewal too - that is, your license will now work with this new version (and some future versions too). So, if you do this, there is no reason to also purchase a license renewal. (3) If you already own a Light-O-Rama license, but you do not currently own Light-O-Rama SuperStar, or if you want to upgrade SuperStar to a higher number of CCRs/channels, you could purchase or upgrade SuperStar. This also counts as a license renewal for the rest of the Light-O-Rama software suite, so if you do this, there is no reason to also purchase a license renewal. Please note that you must already own a license for the rest of the Light-O-Rama software suite in order to take this option. (4) If you do not want to purchase a license level upgrade or Light-O-Rama SuperStar, you can purchase a license renewal. Your license will now work with the new version (and some future versions too), at the same license level as it currently does. For example, if you have an Advanced license, it will remain an Advanced license, but it will now cover the new version of software. What's New in Version 5.3.8 Various Sequencer Enhancements Bug Fixes How To Get the Latest Version You can download the new version from the software download page. If that page lists a different version number as the latest version, please click your browser's refresh button. Thank You!
  18. There is a planned (by the power company) outage in Hudson Falls which is affecting manufacturing, distribution, and main offices of LOR today 9/20/2019. We will not be shipping today, and phone support is not available due to the power outage. Help requests are being serviced on the helpdesk at http://helpdesk.lightorama.com/ should you require any assistance. We should be back to normal operation on Monday 9/23/2019. We are sorry for any inconvenience.
  19. I'm glad that got it working, but I am still worried about Network Preferences in 5.3.6. Is anyone else seeing anything weird with it like runtime errors? The only runtime errors I remember seeing in there where from newer firmware not playing nice with the IP troubleshooter long long ago.
  20. If you are still experiencing this error, please open a help desk ticket. Usually that is caused by 1 of 2 things: 1 - You have an incomplete install/uninstall that has killed some DLLs. A full uninstall/registry wipe/re-install will fix it. 2 - You have a bad registry value. This was fixed years ago, so I doubt it is your issue. In any event, following #1 will also fix this (if you use the registry wipe)
  21. I'm also going to reply to your ticket, but I wanted to let others know here. The RunTime error 9 in the Network Preferences was a bug that was fixed in newer versions of S4/S5. I don't remember which exact version it was fixed in, but 4.4.4 should definitely have it. I suggest you upgrade to that version.
  22. Ok fellow residents of the great state of FL, let's check in and be safe out there this coming week. I know a lot can change in 3-4 days, but Dorian looks like it's going to affect pretty much all of us. Prepare. Be safe. And most importantly - check in NOW with your neighbors and then again after the storm when it is safe.
  23. The secret sauce is: TRUE SINE WAVE. Your inverter or generator MUST output true sine wave. Not 'Modified Sine Wave', not 'Square Wave', not 'Safe for electronics'.
  24. The only reason Jim and I disagree on this (and even then, see below) is that I have to take an official stand - when you support this stuff, you need to have some firm rules. In the interest of full disclosure - yes, we have VERY RARELY recommended to customers that they use a Y. Typically it's an emergency situation where the customer simply can't remove a controller with a bad RJ45 from their chain. We also tell them that once the emergency is over, they need to send it in for repair. Other than that, we say no. We especially say no when it's to run in 2 directions. So if you have a broken RJ45, AND you are stuck, we'll tell you that you can temporarily do it. But if you ever ask us for support and tell us you have one, that will be the first thing we tell you to remove. Otherwise we end up chasing ghosts (reflections).
  25. LOR Controllers, along with DMX universes have a hard cap on the channel number of 512. The issue you are having is that you are 'packing pixels'. You should not 'pixel pack' (IE, use EVERY address available to you) as it just leads to this kind of frustration - EVEN IN DMX mode (which you are not using if you have Pixies). Early pixel controllers FORCED you to pixel pack. Newer ones (like ours) do not. Let's look at an example of a theoretical pixel controller. This pixel controller has 8 ports, and each port can support up to 170 pixels per port. To this pixel controller you connect only 100 pixels per port. Not Pixel Packing: Each string starts at it's own network identifier (in the case of LOR, that would be NET and UNIT, in E1.31 it would be universe). Pixels on that port are numbered from 1-100, and therefore consume 300 channels (1-300). 212 of the possible 512 channel IDs will simply not be used (301-512). Pixel Packing Pixie controllers do not allow you to pixel pack. For E1.31 controllers (DMX over IP) the first string starts at the network identifier (Universe). Pixels on that first port are numbered 1-100 and consume channels 1-300. The SECOND string on the SECOND port however continues from the first. The first 70 pixels will have the SAME network identifier (Universe) as the first string. The first 70 pixels will be numbered from 101-170, and will consume channels 301-510. But what about the last 30 pixels? Those will move to the NEXT network identifier (universe), and will start over with pixel 1-30 (channels 1-90) - your network ID just changed in the middle of a string. You next full string will be on the next port but start at that network identifier, and the first pixel is number 31 and will run through 130. The next string is on the next physical port, starts at pixel 131. It will run for 40 pixels at which time the network identifier changes again. Are you confused? Yes you are. Remember what I said about being able to QUICKLY identify a particular pixels address correctly? Not packing makes it SUPER easy. Packing on the other hand requires that you know how to do a lot of math. The ONLY advantage pixel packing has is that it allows you to use LESS network identifiers (Network and Unit ID). There is no reason for that - long before you run out of network identifiers, you'll run out of bandwidth. So REGARDLESS of what protocol you are using (LOR or E1.31), DON'T PIXEL PACK. It is OK TO WASTE those channel IDs.
×
×
  • Create New...