Jump to content
Light-O-Rama Forums

DevMike

Administrators
  • Content count

    3,489
  • Joined

  • Last visited

  • Days Won

    67

Everything posted by DevMike

  1. MC-P controllers. As far as we can tell, there are only around 30 of them still in use. Trust us, you don't have one
  2. Chris put a ticket in for this board, and it really does look like an IP config problem. Jim, you helped him and I trust your judgement. Can you PM me and let me know your thoughts so I can assist? THANKS!
  3. To my fellow Floridians

    Good luck to us all. Stay safe.
  4. Release Notes For ShowTime 5 Beta Version 5.0.2 28 July 2017 Updates To The Sequencer Enhancement: move the "Insert SuperStar Effect" right-click menu item up a level. Requested by Light-O-Rama. In version 5.0.2 the "Insert SuperStar Effect" menu item appears twice due to an error. The second entry is the one you should use to invoke SuperStar. Enhancement: when a sequence is open and the user selects Tools > Effect Generator from the main menu, the Effect Generator is now opened in the context of the sequence. Requested by Light-O-Rama. Enhancement: improved display of the favorites tree in the Effect Generator so that highlighted nodes are much more visible. Requested by Light-O-Rama. Enhancement: add an option to disable the message displayed when creating playback files: "The sequence uses 1 LOR network, and according to Network Preferences Regular is enhanced". Requested by user brichi. Enhancement: add a Christmas tree shape to the Simple Shapes effect. Requested by user stevehoyt. Enhancement: install the additional dimming curves that are available in the Pixel Editor forum. Requested by Light-O-Rama. Fixed: a white twinkle effect on RGB pixels or dumb RGB lights looked different when played on a regular LOR network versus an Enhanced LOR (ELOR) network or DMX. Reported by users Bry and brichi. http://forums.lightorama.com/index.php?/topic/43632-s5-twinkle-only-on-white/ http://forums.lightorama.com/index.php?/topic/43605-random-twinkle-effect/ Fixed: there was a delay the first time the media was played for a sequence (would happen with media). Reported by Light-O-Rama. Fixed: if you try to start the sequence with the spacebar sometimes it will "stall" and you will have to hit the stop button and hit it again to get it to play. Only applied to MP3 files. From bug report TC02. http://forums.lightorama.com/index.php?/topic/43590-tc02-starting-with-spacebar-stalls/ Fixed: opening an LMS or LAS sequence directly from Windows Explorer instead of opening the sequence from the S5 Sequencer will leave the Light-O-Rama splash screen on the display, blocking the box underneath. You have to hit alt tab and click on the x to clear it out. From bug report TC01. http://forums.lightorama.com/index.php?/topic/43562-tc01-lor-banner-wont-go-away/ http://forums.lightorama.com/index.php?/topic/43568-s5-sequencer-stuck-at-initializing-effect-generator/ Fixed: when setting your user folder, the user folder cannot be the root folder of a drive, e.g. "L:\". From bug report JRW12. http://forums.lightorama.com/index.php?/topic/43541-jrw12-unable-to-assign-lor-default-drive-to-network-drive/ Fixed: "Add Grid View" should not prompt for props/groups and instead save the current grid view. Renamed "Add Grid View" to "Save Current View As". Removed "Copy View" as it did almost the same thing. Reported by Light-O-Rama. Fixed: the "Mix Overlay" mode in the Effect Generator changed from the Pixel Editor to the S5 Sequencer, which caused some Pixel Editor sequences to import incorrectly. "Mix Overlay" in S5 has been changed back to the original Pixel Editor logic. The new mixer function in S5 has been renamed "Mix Alpha Blend" which takes into account alpha blending. Reported by user Bry and others. If you have created new effects in S5 that use "Mix Overlay" mode, they should be changed to use the new "Mix Alpha Blend" mode. From bug report JMW-S5-001. http://forums.lightorama.com/index.php?/topic/43600-jmw-s5-001-curtain-effect-not-working-properly/ http://forums.lightorama.com/index.php?/topic/43569-effect-mixer-issues-with-imported-pe-props/ Fixed: many Visualizer import bugs -- improved handling of DMX fixtures, pixel string orientation, detection of strobes and multicolor strings, bulb sizing, and bulb color. Reported by user K6CCC. http://forums.lightorama.com/index.php?/topic/43587-jrw13-using-preview-that-was-created-by-importing-visualization-error/ Fixed: buttons on Preview Management screen were not sized correctly on Windows XP. Reported by user K6CCC. Fixed: "Delete Grid View" function was not working. Reported by user stevehoyt. http://forums.lightorama.com/index.php?/topic/43618-v5-delete-view-not-working/ Fixed: an LMS file created by SuperStar does not import correctly into the S5 Sequencer, moving many channels to the Archive area. Reported by users K6CCC & RocketCitySanta. http://forums.lightorama.com/index.php?/topic/43645-opening-superstar-generated-lms-in-s5-sequencer-problem/ Fixed: crash when reading motion effect rows from archive props. Reported by Light-O-Rama. Fixed: appending props to current grid view didn't flag the sequence as having unsaved changes. Reported by Light-O-Rama. Fixed: crash when reading some custom preview props with no data. Reported by Light-O-Rama. Fixed: upgrading a sequence with a fixed grid spacing of less than 0.05 seconds got converted to a grid of 0.05. Fixed timing grids in upgraded sequences will now retain their spacing down to 0.02 seconds. However, the minimum spacing for new timing grids created within S5 will remain at 0.05 seconds. Reported by user dgtlpro. http://forums.lightorama.com/index.php?/topic/43625-s5-timing-grids/ Fixed: the drop-down list of props in the Effect Generator wasn't getting populated sometimes when the Effect Generator was opened. Reported by user stevehoyt. http://forums.lightorama.com/index.php?/topic/43622-motion-effect-generator-has-no-choices-in-far-right-window/ Fixed: after creating a new group in preview design, the group wasn't selectable. Only affected new groups with arrangement=none. Reported by Light-O-Rama. Fixed: unable to open 2 sequences with the same file name that exist in different directories. Reported by user RocketCitySanta. http://forums.lightorama.com/index.php?/topic/43641-multi-copies-of-same-sequence/ Fixed: when upgrading a Sequence that includes a Pixel Editor file, the Pixel Editor props did not appear in the grid. Pixel Editor props are now appended to the first grid view. Reported by user JamesWright. http://forums.lightorama.com/index.php?/topic/43546-500-how-do-you-edit-the-rgb-lights/ Fixed: users with an Advanced license can't see the Sequencer's motion effects window or use an enhanced LOR network in beta. Reported by users attending Expo 2017. Fixed: bug when pasting multiple rows with condensed mode off. From bug report SCC04. http://forums.lightorama.com/index.php?/topic/43648-scc04-copy-paste-losing-objects/ Fixed: in the Beat Wizard, after applying a beat pattern to a beat channel, clicking undo does not clear the beat marks. The same issue was also fixed in the VU Wizard and the Tapper Wizard. From bug report SCC03. http://forums.lightorama.com/index.php?/topic/43647-scc03-beat-wizard-undo-not-clearing-beat-channel/ Removed "File References" item from the toolbar's preview menu - as the preview menu is for actions that apply to the preview, and this item applied to the sequence. The function is still available from the Sequence menu. Reported by Light-O-Rama. Removed "Export to SuperStar" link in Preview Management screen. This function is not fully implemented yet. Reported by Light-O-Rama. Updates To SuperStar Fixed a bug in the Load/Save Clipboard dialog box. The effect counts were not being defined if you have navigated to a folder. Fixed a bug where the export of a sequence would only export the effects from where the time ruler is currently at. Fixed it so it always exports all the effects in the sequence. When launched from the S5 Sequencer the time ruler would always be at time 0:00. Fixed it so it is within 1 second of the start time of the request. When launched from the S5 Sequencer SuperStar would sometimes display a message box saying "Enter a value between -64 and 64" When launched from the S5 Sequencer as a musical file, SuperStar would sometimes fail to launch, and if it did launch the audio file would fail to load. Fixes That Will Be In The Next Release (version 5.0.4) Removed duplicate "Insert SuperStar Effect" menu item Sequence > Channel Configuration > Import now works when the import updates the currently selected view. Open Issues Add support for multiple clipboards and ability to import/export clipboard file (same functionality as S4) Add "Foreground Effects" Fade up and Fade Down (from S4) http://forums.lightorama.com/index.php?/topic/43643-foreground-effects/ Add support for props sharing the same channels Add support for SuperStar globe topper Make it easier to create a CCR Tree Add to grid's context menu options to create motion effect rows with subregions automatically based on columns or rows Add support for S4's Color Fade tool and a history of color fades used No way to chase across 8 pixel arches http://forums.lightorama.com/index.php?/topic/43556-no-way-to-chase-across-8-arches/ Improve SuperStar integration S5 LORVerifier needs to be updated. S5 Sequencer Help file needs a major update. Restore toggle tool functionality from S4 http://forums.lightorama.com/index.php?/topic/43620-toggle-button/ Improve performance of the Motion Effect Generator http://forums.lightorama.com/index.php?/topic/43570-s5beta-1-fx-generator-locking-up-a-lot/ Motion Effect Enhancement Requests Would like an option in the spiral effect where you could do a fill like a true spiral tree would do. Requested by SPaschall. Add ability to set text size on individual letters in text effect. Requested in Pixel Editor forum. Waiting For Feedback Issues with subsequences http://forums.lightorama.com/index.php?/topic/43557-opening-subsequence/
  5. For some reason, I would call it "latest and greatest syndrome", people love to upgrade firmware. You probably shouldn't. If your hardware is working, there is no need to update your firmware. If you just received your hardware, chances are it has the latest firmware on it already. There is no need to update the firmware. If the version of your firmware is HIGHER than what is posted on our website, DO NOT UPDATE. When checking firmware, or really any version number from us, each set of numbers is compared on it's own to the other set, left to right. Examples : 1.4.8 & 1.4.13 - 1.4.13 is NEWER as 13 is greater than 8. 1.5.1 & 1.4.32 - 1.5.1 is NEWER as 5 is greater than 4. If your hardware is not working --AND-- you see a new firmware that says it will fix the issue, then OK, consider upgrading the firmware. If you are at all unsure, ask us on the help desk FIRST. Our boot-loaders are pretty robust, so even if a firmware update goes wrong the board will probably still be recoverable. However whenever you update the firmware on ANY device, you risk 'bricking' the controller. If you brick the controller, it may not be recoverable except by the us - which could mean shipping and repair costs for you. Firmware updates on the PixCon are particularly troublesome. Since this is a pro level board, it requires some pretty in-depth knowledge on how to get it to talk on your network. When people can't reliably talk to the board, they immediately assume it is a problem with the firmware. That's bad for several reasons: A stable, always working connection is absolutely a must for updating firmware on any device. If you can't reliably talk to a board, the LAST thing you want to do is try to update firmware. Trust me when I say -- if you are having connection issues with a PixCon, it's not the firmware, it's your cofiguration/settings. All PixCons that have shipped in the last year have HIGHER firmware releases than what we have available for you to load. There are technical reasons for this. PixCons do not react very well when they are DOWNGRADED. Once downgraded, they require special software to recover. For version 1.1 and 1.2 boards we have procedures we can have you follow. New hardware revisions of the PixCon (V1.3) can only run on the absolute newest firmware that is loaded at the factory. We are still working on procedures to recover those boards, and it may be possible that they need to be sent in for repair instead. So please remember: unless you are having an issue --AND-- a firmware specifically states it takes care of that issue, don't update firmware.
  6. Pixcon16 Gigabit Speed??

    Thanks for not beating me over the head If for some reason you don't want them because I initially gave you wrong information, of course we will be happy to take them back. I doubt you want to do that, however I do want to offer it just in case.
  7. Pixcon16 Gigabit Speed??

    Thanks! I thought it was .5 not .25. That's why you are the networking king I did hear back and it is 10/100 on the board - which makes sense since it will never exceed that. sorry for the mis-information!
  8. Pixcon16 Gigabit Speed??

    Unfortunately, the engineer who worked on that board is out on vacation until around the 15th. If however I remember my numbers correctly, even a fully loaded PixCon16 (32 universes + 4 bridge ports all active) is only going to consume 18Mb (I need my buddy Jim to correct me on that). Even if the port on the board turns out to be 100, you still won't be anywhere close to the top. Remember too that you are 1Gb from the computer to the switch, which is the link that really needs it. As long as the switching fabric of your switch can take it, you should be able to run flat out as many Pixcons as you have ports on the switch.
  9. is next beta release coming soon?

    I have received word that we have started building the next beta release. Should be out later today or tomorrow.
  10. Pixcon16 Gigabit Speed??

    I'm sure that is what engineering told me it was, but now I wonder. FYI - I'm the one that told you it was Gigabit in the help desk, and supposedly I'm the PixCon expert. In my lab I only have 10/100 switches so I can't confirm it. I will send a note over to engineering to make sure they didn't tell me the wrong thing a couple of years ago. Sorry for the confusion. Give me a couple of days.
  11. is next beta release coming soon?

    Matt and Brian are both OK, however they could be indisposed for a little while while things settle down. We are looking at getting a new beta out Tomorrow, but things are fluid at this time.
  12. is next beta release coming soon?

    Hey Steve. We had actually planned on having another Beta release last Tuesday. Unfortunately, we had several other things happen that pulled our attention away from getting that out the door. The people that are the most crucial to the beta are both in Texas in the midst of all the flooding. We are now in a holding pattern until we hear from them.
  13. PixCon16 Hardware Test

    If EVERYONE understood how electricity works, that would be true. However for a majority of our customers, they don't. Which is why I worded what I said the way I did.
  14. Admin Assistance Please!!!

    Superstar pricing will still be based on the OLD CCR. Every 50 pixels/150 channels.
  15. PixCon16 Hardware Test

    FYI (and people are going to beat me over the head about the semantics of this). LOR (as a company) does not support Power Injection. What I mean by that is if you ask us how to do it, we tell you don't do it and won't give you instructions on how to do it. If we determine that a piece of equipment (string of pixels, controller, etc) was damaged by power injection (or other short) done incorrectly, your warranty will not cover the damage. --------- Now with that said, YES it is possible to safely power inject (obviously by the links/vids above). Just remember you assume all risk when doing so.
  16. Introducing Tor

    Just a quick note to all of you to introduce Tor. Tor is an LOR employee who is working on S4/S5/? with us. Tor has actually been around since the S1 days 15 years ago and has worked on bits and pieces of the software since then - when he was not out on another assignment. As some of you may have noticed, Bob retired last year from LOR. That left us short. Tor is now full time (almost) on development with us. Please extend the same courtesy to him that you do all of the rest of us on the dev team, and welcome him!
  17. I now have 2 separate reports that the Hardware Utility in 4.3.22 can’t reliably find controllers when using the refresh button, heartbeats not being sent, etc, and that going back to 4.3.18 fixes the issue (this is one). That does not make a lot of sense to me since all I touched was pixie testing between those 2 versions. I didn’t touch anything with heartbeats. Can you please fire up 4.3.22 attach some LOR controllers (pixies, CTBs, whatever you have that responds to the HWU), and try refreshing several times in 4.3.22. Make sure the status LEDs on the controllers go solid as well. I can’t duplicate the issue on my computer, so I don’t know if I just have 2 people that have something weird on their computer, or a real problem. Report back here if you are successful or not, along with the version of Windows you are using. If you do have a problem in 4.3.22, see if going back to 4.3.18 fixes the issue and let me know that too.
  18. 4.3.24 has been released and addresses this issue. Thanks everyone!
  19. Thanks to everyone for the information. With it, I did find an issue with 4.3.22. We will be releasing 4.3.24 shortly (probably in the next day or two) to fix the issue. If you don't need the HWU for now, just stay on 4.3.22 and then go to 4.3.24. If you absolutely need the HWU, go back to 4.3.18 - that will mean giving up pixie testing, but it will allow you to configure units.
  20. If you had your license in Jan 2015 when this was posted, you were automatically granted the next higher license (we did that with an update on our server). All you have to do is re-register. If you purchased your license/renewal AFTER this was posted, your purchase was made with the new lower prices. Either way, you would have received your free upgrade, or cheaper price.
  21. Introducing Tor

    It's funny, but we actually don't know how old we are. Or at least, when I asked the boss how old we were, he said 'I dunno!' I did do some digging for this year's expo presentation to see if I could come up with something. Looking at some of the saved S1 code, it dates back to 2004-2005. But that was when we started to 'save' things. It was on someones computer long before that. A whois lookup on lightorama.com shows it was registered by Dan on April 24, 2002. By using the Internet Wayback Machine, we see the first scrape of the site in June of that year (just a parking page). In September of 2003, we see the first 'real' pages of the company appear (which indicates the site went live sometime between June 2002 and September 2003). I consider April 24, 2002 our birthday. We were 15 in April. I joined in June of 2009, so a couple of months ago I could start saying "I've been with LOR longer than not!" (7 years without me, but now 8 years with)
  22. "If a man has good corn or wood or boards or pigs to sell, or can make better chairs or knives, crucibles or church organs than anybody else, you will find a broad hard-beaten road to his house, though it be in the woods."
  23. S5 is moving along very quickly in terms of bug fixes, functionality, etc. This means that a bug in an older version may have already been fixed by a newer one. When reporting an issue, please be sure that you are using the most recent version of the Beta. If you are using an older version of the software, please update to the newest and then try reproducing the issue. When we do release a new version, we will update the title of this post with the version number to help you identify what release we are on. We value all bug reports! Ensuring that you are using the latest version allows us to quickly find and squash them!
  24. August - December seems to be the busiest time both here and in our Help Desk system. It's probably your busiest time too, since many of you use our products for Halloween and Christmas. It is frustrating when something doesn't work, performs unexpectedly, or simply confuses you. We are here to help. We also know that if you are asking for help something has gone wrong and you want an answer as quickly as possible. Here are some general tips on what you can do to help us help you Naturally, the first thing you should do is review the documentation we have available here on the website. We have all of our user manuals available as PDFs as well as searchable copies of our help files. Many times your answer is there. If your question isn't answered, it's time to ask us. The number one rule to ALWAYS remember is this: It's better to give TOO much information than too little. If you think the issue is related to the color shirt you are wearing, include that information. More is ALWAYS better. In general, support requests come in 3 flavors: Pre-sale, Sales, Technical. Each has it's own set of information that is generally needed. Pre-sale questions are usually all over the board. That's because you are simply not sure if our products/services/etc will meet your needs. The best thing you can do is after taking a look at our literature, and ask away. It may take a few exchanges, but we will sort you out. Sales questions encompass things like order status, shipping cost questions, software purchases, etc. In general, anything you are or will end up spending money on. Typically you'll ask these questions via the help desk and not here on the forums. Please include as much information as you can about what explicitly you are asking, but never reveal personal information on public forums. Examples of information you should include in your help desk ticket: if you looking for an order's status, include the order number if you need international shipping costs, include your address if you have a software license question, include your license number and registration eMail. Where sales questions typically have quick cut-and-dry answers, Technical issues are a whole other ball of wax. They may be as simple as pointing you at the correct option, all the way to multiple exchange tickets that take some time. If you have a how to question, you may get a faster response here in the forums that you would from the help desk system. That's because we have thousands of users who have 'been there, done that', and only a limited number of people on the help desk. The added benefit is that you may help someone in the future who has the same question. We actively monitor our forums, so it may even be one of us who replies. Naturally, if you are not comfortable posting in a public forum, use the help desk system. We are here to help! If you do decide to use the forums, please try searching for your issue first. Believe it or not, 90% of the time you are not the first person to experience that issue. A quick search could find you an answer. Whenever asking about a technical issue, either via the help desk or the forums, the best thing to do is OVER share. The more information you include initially helps both us and the old-timers get the answer you need. Software Questions: Always include things like your operating system (XP, Vista, 7,8), the version of our software that you are running (S2/S3 V2.9.4, 3.8.0, etc), the feature level (Basic, Basic +, Standard, Advanced), and what you were doing at the time. If you attempted to get around the issue, what did you try? If you are getting an error message, include the EXACT message -- nothing is worse than working a trouble ticket where someone says 'I got an error, but I just clicked OK'. While it may not mean much to you, that error message means the WORLD to us Hardware Questions: Hardware issues can be very frustrating. That's because for most of us the hardware performs 'electronics magic' that we have no clue about. But even hardware issues have certain things and information that is always helpful. The best thing you can do is 'swap with known good working'. That means if you have another thing you know works, swap it with the one that does not. Then, and this is the most imporant part, tell us what worked, what didn't, and if the problem moved.
  25. The Canned Response Yes, we use them. In fact, we use them a lot. I know this since I write and re-write many of them many times each year, as do several other of the people on the help desk. We re-write/add/simplify these replies to keep them relevant as well as easy to follow. There is a fine line (which I admit to crossing over far too much) between making a reply too specific or to generic. That means sometimes customers catch us when we use them. The reason we have canned responses is that they are, well, canned. They are a fast way to reply to a ticket where a customer has a particular issue. But some of our customers, much like the ones who we tell to RTM, sometimes get upset that we use them. Again let us stress that we are not some third world help desk where all we are trying to do is close the highest number of tickets in the shortest amount of time. Trust that we have: Read your issue entirely Determined that the canned response either A: FIXES your issue, or B:gives us the information we need to continue to troubleshoot your issue.
×