Jump to content
Light-O-Rama Forums


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by DevMike

  1. 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.
  2. 4.3.24 has been released and addresses this issue. Thanks everyone!
  3. 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.
  4. 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.
  5. 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!
  6. 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)
  7. "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."
  8. 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!
  9. 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.
  10. 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.
  11. New look?

    We've updated the forums and Tapatalk again. Please see if you can now get to the forums via Tapatalk and let us know. Thanks!
  12. New look?

    Ok, so that is one down, one to go. Yes, I had forgotten that we also enabled the ignore function on Sequence Sharing.
  13. 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/
  14. Release Notes For ShowTime 5 Beta Version 5.0.4 31 July 2017 Updates To The Sequencer Fixed bug introduced in 5.0.2: removed duplicate "Insert SuperStar Effect" menu item. Reported by Light-O-Rama. Fixed bug introduced in 5.0.2: track names are not converted to grid views during the sequence upgrade process. Reported by Light-O-Rama and others. http://forums.lightorama.com/index.php?/topic/43557-opening-subsequence/&tab=comments#comment-406239 Fixed bug introduced in 5.0.2: cannot save an upgraded sequence using the original filename (but with LOREDIT extension). Reported by Light-O-Rama. Fixed bug introduced in 5.0.2: custom props are not displayed correctly. In some cases, it might prevent the sequence from being opened or played at all. Bug report JMW S5-002. http://forums.lightorama.com/index.php?/topic/43680-jmw-s5-002-02-startup-problem/ Fixed: Sequence > Channel Configuration > Import can now safely update the currently selected grid view. Reported by pyrotech. http://forums.lightorama.com/index.php?/topic/43661-copy-views-across-different-sequences/ Fixed: when upgrading a sequence with a subsequence, an error occurs. Reported by ebrown1972. http://forums.lightorama.com/index.php?/topic/43557-opening-subsequence/ Fixed: When the user modifies a subsequence row and chooses a different subsequence file, the new file is now loaded. Reported by Light-O-Rama. Fixed: When upgrading a sequence where RGB channels get archived (the channels exist in the legacy sequence but not in the S5 preview), those archived RGB channels are now included in the "track to grid view" conversion. Reported by Light-O-Rama. Fixed: in a sequence with lots of text effects, some the text effects might not get displayed on the preview or to lights. Reported by Light-O-Rama. Fixed: When a user assigns a different preview to a sequence, channel names and colors are now updated. Reported by Light-O-Rama. Fixed: Sorting channels by color was only working within channels assigned to a single prop or group. It now works across props. Reported by user stevehoyt. http://forums.lightorama.com/index.php?/topic/43683-view-sorted-by-color/ Fixed: Spacebar playback now starts and stops, instead of starting and pausing. This replicates the S4 experience and makes the grid editable after stopping with the spacebar. Reported by user John Slade. http://forums.lightorama.com/index.php?/topic/43686-502-can-not-add-effect-after-using-space-bar-to-stop-sequence/ Fixed: Increased the maximum number of allowed segments in Lines-Connected and Lines-Unconnected shapes, as some Visualizer files used more than what S5 was previously allowing. Reported by user John Slade. Enhancement: When opening a large S5 sequence, the progress bar now accurately reflects load progress. Requested by Light-O-Rama. Updates To SuperStar Fixed: "Insert SuperStar Effect" encounters an error when using the SuperStar text effect. Reported by user brichi. http://forums.lightorama.com/index.php?/topic/43664-insert-ss-effect-text-not-working-or-something-wrong-in-setup/ 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 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. Add movement options to the Picture effect that are essentially the second half of the Peek-a-boo movement. So exit_left, exit_right, exit_top, and exit_bottom would be the new options. http://forums.lightorama.com/index.php?/topic/43699-feature-request-using-picture-effect/
  15. Light O Rama is proud to announce the next release of Showtime S5 software 5.0.4 Beta Important Information about Beta Releases Please note that this is a beta release, not an official production release. For important information about beta releases, including what it means, who should participate, and how to participate, please see this post. How To Check If Your License Covers This Version Please note that your license may or may not cover this version. Anyone with an active S4 license can download and run the S5 Beta. You may be warned that the software will expire in October, however you can re-register and that will go away. For a list of changes in this version from the previous version, please check the release notes in the Open Beta Forums. How To Get the Latest Version The new version can be downloaded from: http://www.lightorama.com/downloads/5.0.4/LOR-5.0.4.exe Or http://www1.lightorama.com/downloads/5.0.4/LOR-5.0.4.exe Thank You! As always, thanks to all of those who choose to help us out as beta testers. Before deciding to download and install the beta, please take some time to read this post for some important information: What is meant by "beta" and "open beta" An entirely new "Pro" license level (above Advanced) How licensing will be handled during the beta period Information about the help files How to download the installer can be found at the end of this post, but please take the time to read this information before deciding to download and install itWhat is beta software? Beta software is code that has been tested by the programmers who have written it and has received some internal testing by other members of the company. The software is stable enough to be tested by a rather large group, but it is not software that is ready for general released.Why an open beta? We have received many requests from people asking to join the beta testing group. In the past, we have kept that group closed, and have always had a backlog of people wanting to take part. To make management of the beta group simpler, we are going to open the beta to everyone.Who should use beta software? Beta testing is not for everyone. By nature, beta software will have more problems in it than generally released software. Testing beta software allows a user to find out if an enhancement does what they need, and if not, provide suggestions on how to fix or improve the software. Do NOT use the beta software if you are not ready to uncover bugs/problems with it. People who volunteer to test beta software must report problems, but please do not complain that there are problems - problems are expected! When testing beta software, please make sure to save often so that if something crashes, you'll minimize your loss.How can I report issues, make suggestions, or ask questions about the beta? There is a set of forums for the open beta, where you can report bugs or give other feedback, here. Please do not open help desk tickets for S5 issues, instead post a message in one of those 2 forums.The new "Pro" license levelAt this time, the differences between Advanced and Pro are that the Pro license level enables the use of Motion Effects. These new features are intended to improve the experience of using very large numbers of circuits (though they can be used with small numbers of circuits too).During the beta period, certain users' licenses will act as if they were Pro level licenses. Please see the next section of this post, "Does my license cover this release?", for details.Does my license cover this release?Depending upon when you purchased, renewed, or upgraded your license, it may or may not cover version 5.0. However, during the beta period (which will last through October of 2017), some licenses that do not really cover version 5.0 will act as if they do cover it: If your license is valid for version 4 or higher, then during the beta period it will act as if it covers version 5.0.Also, during the beta period, Advanced licenses will act as if they are Pro licenses.In this way, even if you don't have a license that really covers the new version or the new Pro license level, you can try them out during the beta period without committing to purchase them.After the beta period is over, if your license does not really cover version 5.0, it will stop acting as if it does. Similarly, if you have an Advanced license, it will stop letting you use Pro level features. At that time, you could either: Purchase a license upgrade, if you want to continue using 5.0 and continue using Pro features; or: Purchase a license renewal, if you want to continue using 5.0 but do not wish to continue using Pro features; or: Uninstall version 5.0 and reinstall version 4.3.18 (or an earlier version). Please note that if at the end of the beta period you decide not to upgrade or renew, not everything that you created during the beta period will necessarily be usable afterwards. Specifically: Any "intensity files" that you create during the beta period (such as by the Pixel Editor or SuperStar) will not be usable afterwards unless you upgrade. Any motion effects/Sequencer files created in S5 can not be used in the PIxel Editor of S4. Also, please be warned that although the above list is intended to be complete, it is possible that there are other incompatibilities that were overlooked here and not listed. It is always wise in any case to back up any of your data files, even those that you have no reason to believe will be affected by the upgrade (such as your sequence files).You can check whether or not your license covers version 5.0 by using the Software License Retrieval page. Please note that if your license covers 4.0 (or higher) but not 5.0, the Software License Retrieval page will not mention to you the fact that your license will temporarily work for 5.0 during the beta period.Special information about the help filesIn this initial beta release, the help files are not completely updated. We are working on updating our help files.What's new in this versionS5 was announced at the 2017 Christmas Expo. We have several presentation files available that are full of information on what is new in S5. "PowerPoint Presentations / ShowTime 5". http://www1.lightorama.com/tutorials/How do I get this new version? The Important Announcements forum will have the latest beta release. Look for the most recent post (usually located at the top of the forum) titled "Light O Rama version 5.0.XX released as an open beta"Thanks for your help!
  16. New look?

    Please check the ignore function again. Remember, it should only be available in the Coffee Shop.
  17. Old Visualizer with S5.0.2

    Please remember that we do intend on removing all the back end code that supports things like the Visualizer. That could come at any time in the future. Visualizer is not supported in S5.
  18. The same bug that is in 4.3.20 in regards to creating SD cards is also going to be present in 5.0.0,5.0.2, and 5.0.4 (when it is released). If you attempt to create an SD card with any of those, results will be unpredictable.
  19. New look?

    Ok, thanks for trying. We'll let you know when we think it is fixed.
  20. New look?

    Can you guys please re-try Tapatalk and see if it is now working? They re-released their beta, and we have installed the new version. TY!
  21. New look?

    We are still working on Tapatalk. They currently don't have a version that is working with this version of our forums. We tried to install their beta version, and that didn't work - and now even that is gone from their site. We will get it installed as soon as Tapatalk gets the next version out.
  22. New look?

    Ok. I let the webteam know and they will work on it. FYI - if you have not visited the forums for a while using a mobile browser (like Chrome for your phone), give it a try. Invision has made some big changes in how it renders forums on mobile devices since the advent of Tapatalk.
  23. transfering software license

    Licenses are non-transferable.
  24. SS gone from 4.3.20

    We re-released 4.3.20 yesterday with the fix.
  25. New look?

    That may have got uninstalled as well during the upgrade. I'll have web team look at it. FYI:Tapatalk should be working now. Please give it a shot.