|Top Previous Next|
Updates Made to Older Versions
What's New in the Latest Version
The LOR Hub program can now create SD cards with a full range of options, including triggers, filler sequences, starter sequences, etc. In a future release, SD card building will be removed from the Hardware Utility and the Simple Show Builder will be removed from the suite.
Previously there was no way to stop an SD card show from running on a particular day, except by using a workaround of setting the start and end times for a particular day the same. LOR Hub can now properly turn OFF a schedule for a particular day.
When creating an SD card in Advanced mode in Hub, a new option has been added to configure the MP3 Director's ports the same way as those ports are defined on the computer. This can help with ease of setup of MP3 directors.
LOR Hub has taken over all functions of the old Simple Show Builder program. In the next release this program will be removed from the suite. Instead, use LOR Hub to create your shows.
•Added support for group modify of "average time length of effects" and "skip inactive grid squares"
•Added the "Do Scene Thinning" option in the "Move or Scale Selected Effects" dialog box
•Added "Orientation" setting in the Preferences dialog box
•Added support to convert 6 channel star effects to white effects on RGB stars from other vendors (previously it only worked for the standard 200 pixel RGB star)
•In LOR Hub and Hardware Utility, sequences with DMX Fades when written to the SD card could cause the MP3 director to go out of sync.
•LOR Hub was not able to properly create an SD Card schedule. The schedule would always revert back to the defaults instead of what the user specified.
•LOR Hub would crash if the user attempted to create an SD card show with no sequences in the create list.
•During installation, the Post Install process was not creating 3 new superstar visualization samples.
•In Superstar, text masks were not working in visualizations where some of the mask is outside of the matrix.
•In Superstar, fixed a bug where the white color control was not appearing if the only white that existed was in images.
•In Superstar, changed it so you can do "merge intensity data files" even in the demo version
•In Superstar, fixed a bug where scene pixels were getting clipped out if the clip region was on the right half of the wrap around screen
In the "Image Setup" dialog box, a new button was added called "Add +". The "Add+" button adds the current image to the image action, selects the next image, and bumps the time ruler selection forward. This makes it easy to add a series of images for an animation.
2.It is the replacement for Simple Show Builder. Simple Show Builder is still available in this release, however it will be removed in a future release. If you previously used Simple Show Builder you should move to Hub.
In future releases, Hub will continue to grow and will be taking over all 'show' type functionality including things like the Show Editor, Show Scheduler, and Building advanced SD cards for MP3 Directors from the Hardware Utility.
Support for Holiday Lights Designer is being removed from future versions of S4. The need for Holiday Lights Designer was removed when S3 was released with the LOR Visualizer.
•The Post Install process failed to copy 3 new examples for Superstar.
•The configuration for PixCon16 MKII devices was incorrectly showing 32 ports.
•In Superstar, if the preview uses horizontal orientation and you go into "floating windows" mode, the program could crash.
•In Superstar, the first time beat marks are created they are created without issue. Creating beat marks a second time incorrectly deleted them.
•In Superstar, if you changed timings the program may not prompt you to save your work.
•In Superstar, when using Text Masks along with scenes or morphs, it was possible that the mask was not applied.
•In Superstar, when using a Text Mask or an Image Mask, if Layer Priority was disabled, foreground effects would be incorrect and background effects would not be rendered.
•In Superstar, if the program was launched from S5 changes would not be saved if "Save" or "Save As" was used to save the sequence as a .sup file.
•In Superstar, when using Autosequence effects, the displayed timings may be incorrectly changed to the most recently used Autosequence settings.
•In Superstar, when using Autosequence if "average the time length of effects" was selected then the last few seconds of an autosequence effect may not generate triggers.
•In Superstar, when using Autosequence if "Burst and Return" was used, there could be a compile issue. This happens most frequently with low sensitivity settings such as 1 or 2.
•In Superstar, when using Autosequence morphs with transparency set to transparent were not being saved properly.
•In Superstar, when shrinking using the pixel extender and smooth effects, the shrink did not occur properly.
•In Superstar, the "Center X,Y" control in the Smooth Effects dialog box the buttons were not oriented properly when creating a horizontal sequencing grid.
•In Superstar, if the pixel extender is enabled and a visualization with a sequencing grid was imported with a "max length" , a crash could occur.
•In Superstar, if the pixel extender is enabled and a sequence was being shunk, only half of the effects would get applied.
Some versions of the LOR S4/S5 uninstaller can leave behind unwanted programs in the user's Program Files(x86)\Light-O-Rama folder. This can lead to installation problems the next time the user tries to install the software. Registry Wipe can now clean those entries up.
Several new options and effects have been added to Superstar's Auto Sequence tool including effects 'Folding Ricochet', 'Snake Up/Down', along with options to 'Skip Inactive Grid Squares' as well as 'Average the Time Length of Effects'.
•The following bugs or small improvements have all been fixed or made in Superstar
oIn the Auto Sequence dialog box if the user did not select one of the 8 custom colors, a message is now displayed.
oWhen saving in the Demo version, the file added to the recent files dialog was incorrectly specified as ',supe.sup'.
oWhen saving in the Demo Version, the suggested filename was incorrectly defaulted to '.supe.sup'.
oIn some cases, opening a valid .supe file would cause an error stating the file was not created on this computer.
oImproved export speed of sequences that use large Visualizations
oIncreased the number of images allowed from 1500 to 3000.
oWhen automatic modification of Star Scenes occurred, it was incorrectly changing the archive status of the file.
oIncreased the width of every 5th long tick mark on the edge of the sequence grid
oIn sequences with effect groups, after a 'select all' effect groups could no longer be expanded.
oIncreased available memory for both 32 and 64 bit systems.
oThe number of channel elements has increased from 8 million to 50 million.
oWhen using Single Step, if the stop button was pressed the first selected effect was not made active. This could lead to a warning or error.
oWriting large images could cause the program to crash.
oThe number of fonts has been increased to 30 to allow for user created fonts to be used.
oWhile using the Pixel Extender, if the Layer Priority feature was active pixels were extended too far.
oWhen using the Move or Scale effects tools while in wrap around mode, some effects were not wrapped properly.
•When installing 4.3.32 on a new computer (one that has not had S4 installed on it previously), The Post Install program would error out on creating the Downloads directory.
•When installing 4.3.28 or 4.3.30 over the top of an older version of the software (an upgrade) the install would appear to work successfully. However on some computers starting any of the LOR programs would then re-start the install process as if it had not completed or had an error. The installer for this version should fix that behavior.
•In Superstar, opening a file with the extension .supe, making changes, and exiting the program could sometimes cause an error that the filename did not end in .sup
•In Superstar, in some cases when scenes are part of a group, grouping could be incorrectly changed.
•In Superstar, fan effects longer than 1:51.3 would not display on time layers
•In Superstar exporting in half ribbon CCR mode was not working properly.
•In Superstar the colors of scenes did not render properly when used on a visualization.
Several support libraries were updated to use the same packages in Pixel Editor as in the upcoming S5 Sequencer for compatibility. This should be transparent to the user.
It was possible in previous versions of the Pixel Editor that the user was not notified if the save of Intensity Data failed.
In order to better support new hardware, several files can now be downloaded automatically from the internet by the software if the user is online. As of this release, the software can now download the LOR_DeviceFile.txt file, as well as a new file for supporting Pixie based Props in the Hardware Utility. These new files are downloaded into your LOR Data Directory. They can be found in LORInternal/Downloads.
You should not modify any of the files in the LORInternal folder.
Even though the software can download these files, it is not required that your computer be online. If you are not online, the LOR software will still work, although it may be with outdated data.
The Hardware Utility has been updated to allow for the configuration of new LOR Props. These props will be physical items you can purchase, like Singing Faces, and quickly integrate into your show.
New firmware for the LOR Pixie controllers will be released that allows for Props as well as by port Triplet Ordering.
Previously Scenes and Morphs did not have a clip rectangle. That has now been added so all effects now have a clip rectangle. The Modify Selected Events button was also modified to support these new clip rectangles.
•In the Hardware Utility when working with the configuration of a Pixie, changes may not have been picked up until the Refresh button was pressed.
•In Superstar if the .sup file opened has more ribbons than is currently displayed, and the audio file fails to open, the program would crash.
•In Superstar the Shockwave maximum for the head and tail are now 200. Formerly it was 50.
•In Superstar when using Instant Sequence Trigger Size could exceed the maximum.
•In Superstar a left single click on time scale may not have marked the beginning of the selection.
•In Superstar when using the Image dialog box. If "Apply X,Y in Preview" was selected and an image was selected, the image would not be drawn at X,Y unless the user pressed "Modify".
•In Superstar when using the Text dialog box occasionally no font would be selected
•In Superstar the state of some controls in the Scene, Morph, Smooth Effects, Image, and Text dialog boxes were not being saved/restored when switching between modes using the toolbar buttons.
•Fixed a bug where if you do a "move or scale selected group" then immediately do a "group modify move" and it moves everything to the location of the first selection. This has been fixed.
•Fixed a bug where if a scene has pixels that have been moved to the left of the visible sequencing grid it could cause the program to hang when playing the sequence or exporting to sequence editor
•Added the button "Set Grid Bitmap and Add Image" to the image dialog box
•Increased the maximum number of Intensity data files that you can merge from 10 to 15
•Images with a preRamp or postRamp in wrapAround mode could cause superstar to crash when played or exported to sequence editor.
•Group Modify of Text preRampLength, PostRampLength, FadeToBright, FadeFromBright, and clipRectangle, were not working.
•Changed it so if you do "Select All", "Select All Right", or "Select All Left" and you are not in a group, then it selects things in all groups in addition to things that are not in a group.
•Fixed a bug where if you have a sequence with star effects and you import a visualization without a star and it removes the star effects, it removed the star effects but it did not update the Scene dialog box, so the effects still showed up in the dialog box.
LORNetworkPreferences supports PixCon16 MkII boards.
•The Hardware Utility when started would occasionally not send heartbeats to controllers, leading to seemingly erratic behavior: not being able to detect units, only detecting some units not others, etc.
If the current license level does not support exporting the current layout, the associated .sup and .scb files are encrypted and can only be opened on the computer that created them.
Users can now change and create folders in the dialog.
When this checkbox is selected the effects on low time layers will render in front of effects on higher time layers. For example, if you place a morph on time layer 1 and you place a scene on time layer 3, then if the morph goes across the same area as the scene then the morph will render on top of the scene. In other words it will look like the morph is above the scene. Added Transparent, Semi-Transparent, and Solid in the Effect dialog boxes. These settings are used when the "Time Layer Priority Feature' is enabled.
•In SuperStar the export of a sequence would sometimes only export the effects from where the time ruler is currently at.
•In SuperStar in the Load/Save Clipboard dialog box, the effect counts were not being updated if you navigated to a folder.
•In SuperStar the number of rows for the Timing Map was being incorrectly set to 3.
•In SuperStar when using Instant Sequence, the program was not taking into account if the number of rows changed, so the Timing Map also did not reflect the correct rows.
•In SuperStar improved the Image Group Modify dialog as well as the added a Preferences Box.
•In SuperStar When saving a clipboard to a file, the file that was added becomes selected in the list.
Firmware 1.4.13 of the PixCon board has been released. There are no new features - this is only a maintenance release.
•In some cases if a board that was not in the DeviceFile was searched for in the Hardware Utility, the hardware utility could incorrectly log debug information as if the device were a Pixie board. This did not affect the end user, but should not have been occurring.
•In Pixel Editor the OpenGL version on certain computers was not being detected correctly, leading to a race condition.
A new File Format is now created when writing an SD card with the Hardware Utility when a Network contains Enhanced Light O Rama commands. This new file format improves the performance of the MP3 director when using high speed (500K, 1000K) networks. To take advantage of this performance enhancement, you must re-create your SD card using the Hardware Utility, as well as update your MP3 director to the latest firmware.
New firmware for G3 MP3 directors has been released to support the New Enhanced File processing above. This firmware also corrects a bug that would sometimes cause a PixCon16 running at 1000K to misfire/not connect.
•When writing an SD card with the Hardware Utility, in some rare cases where the first sequence only had REGular LOR commands and a non-G3MP3 director was selected, a blank Enhanced file could be written to the SD card instead of regular commands.
•In the Hardware Utility, the progress bar when writing an SD card was not correctly reflecting actual progress.
Hardware Utility support for Pixie16, Pixie 8, and Pixie 4 controllers has been added. You can now configure these devices for use. Please note that the Sequence Editor has not been updated to include Pixie devices, and the Visualizer will only support 50 pixels on a Unit ID until a future update.
In support for the new 4 port MP3 director and other future improvements to SD card handling, the way SD cards are written in the Hardware Utility has changed somewhat. The old 'Final Options' screen has been replaced with a wizard. There are no functionality changes.
•In Superstar, if you clicked on an effect in the list box and the effect was in a group, the grouping would be corrupted.
•In Superstar, if you right clicked to bring up the color picker dialog while moving the mouse, the dialog was not updated.
•In Superstar, on some computers, saving sequences to audio files to the desktop was not working.
•In Superstar, spiral and fan effects that were part of a group would not stay as part of the group when saved.
•In Superstar, in some cases importing a matrix wizard with the origin set at the top were not working.
•In Superstar, Star hotspots were being incorrectly drawn when in CCR and Floating window mode. The hotspots are no longer drawn, matching the behavior when floating windows are turned off.
•In Superstar, changed an error message instead to a warning if an effect were added that straddled a text action mask. The action is now allowed.
•In Superstar, saved state of the "Pixel Extender" if it was active, and warn the user that it is ON the first time they try to run a sequence.
•In Superstar, when using the Pixel Extender, morph coordinates were being incorrectly clipped if the Pixel Extender is shrinking effects.
•In Superstar, if you exceeded 64 columns by using force row/column in a prop and/or fixture, the program would crash instead of producing an error.
•In Superstar, in some cases groups were not saved to clipboard files properly.
•In Superstar, while doing a copy/paste between two different instances of the program, the groups were not pasted properly.
•In Superstar, the maximum number of image actions has increased from 5,000 to 10,000.
•In Superstar, the 'Scene Group Modify' wrap check box now supports 'no wrapping'.
•In Superstar, properly convert star scenes to RGB scenes when importing a visualization that has a Superstar RGB star.
Firmware version 1.4.11 (filename PixCon16 Firmware Showtime (S4)-V1.4.11.nhx) has been released and includes support for the new pixel types and test mode entry from above.
Firmware version 5.36 has been released for the MP3g3 (filename: MP3g3-V5_36.lhx), uMP3 (filename: uMP3g3-V5_36.lhx), and LOR1602g3MP3 (filename: MP3g3-V5_36.lhx) MP3 directors. This firmware allows for faster show start-up when using DMX output exclusively.
•In some cases if a PixCon16 board were connected and searched for and the 'Minimum Required Version' for the board was higher than the software could handle, it would not be shown at all when it should have been shown in red.
•In SuperStar, a bug was fixed that was limiting Visualizer locations to 50 in the y direction. This has been increased to 360.
The ServoDog Utility now adjusts servo parameters relative to the channel's neutral trim and not with absolute values.
•SuperStar's mapping of visualization colors to the four basic colors has been improved. In particular, 128,0,128 was being mapped to red, and now maps to purple.
•In the past, if you launched two instances of SuperStar and used a different audio file in each one, the first one launched would use the other one's audio file. This has been fixed.
•When the Hardware Utility created a show for an MP3 Director with DMX channels, the DMX channels would always be turned off at the end of the sequence regardless of what the value of the "Keep lights ON at end if using DMX" option was.
This version contains no functional changes, only some textual changes.
Version 1.05 of the firmware for the CF50D has been released (filename CF50D-V1_05.lhx). This version fixes problems with delayed response when attached to an Enhanced LOR network. It is the first version of firmware for the CF50D to be included with the LOR software suite installer.
•If you did an "Export to Sequence Editor" in SuperStar when in CCR mode with DMX selected in Configuration dialog box, then the first time you played to the screen, the effects would get shifted and scrambled.
•If you used an imported visualization in SuperStar, and the visualization contained a DMX Prop name that contained an ampersand or quote character, then the Sequence Editor would fail to open the exported file, displaying the error "Expected entity name for reference".
•If a sequence has the white color in it, SuperStar now displays the white color even if the display only has red, green, and blue in it. This is so that you can remove the white color if you want.
•In SuperStar, white lights that were on a row that was below an RGB matrix could not be sequenced. The effects could be added, but nothing would happen when you played it back.
•In very rare circumstances, the Visualizer could fail to start because of an issue with detecting the Network Adapters available on the computer.
•If a computer had more than 32 Network Adapters, or more than 32 IP addresses assigned to a network adapter and the user selected 'Local' as the IP adapter to use, the Visualizer would incorrectly report that the IP address could not be found, was blank, or was 0.0.0.0 when going into simulation mode.
•In SuperStar, if a smooth effect with white in it painted to the first pixel of a CCR, then it would write to the pixel resolution macro and cause the CCR to blink.
•SuperStar's clipboard was fixed so that you can copy from one instance of SuperStar and paste into another.
•A PixCon16 reboot is highly dependent on how fast a network DHCP server responds to the IP lease request. On certain networks with slow DHCP servers, an update of the configuration of a PixCon16 with the Network Preferences program could sometimes throw an error. More time is now given to the update process, and should that still not be enough an informational message is generated rather than an error.
•When an update of a PixCon16's configuration failed, only a single error was used regardless of the reason. Additional errors have been added to the update process as well as debug information in some circumstances.
•On computers that are set up to use Japanese, and probably various other languages, the Comm Listener would often put out strange error messages (ostensibly about having received malformatted messages) and fail to work properly.
•SuperStar was not detecting the largest screen resolution, and was setting the wrong view size.
•The maximum number of RGB strings in SuperStar has been increased from 160 to 200.
•SuperStar no longer saves the enable state of the pixel multiplier. Instead, it will always launch with the pixel multiplier disabled. This is because if you were to launch with it enabled and start sequencing, it would be very confusing because the playback of the sequence would be different than expected, and it would look like things were broken if you didn't realize it was enabled.
•If RGB dumbstrings in a visualization are assigned the same DMX addressing, then when imported into SuperStar, each RGB dumbstring was being assigned to its own square on the sequencing grid. This has been fixed so that all RGB dumbstrings with the same DMX addressing will be treated as if they are one fixture, and that one fixture will be assigned to only one square on the sequencing grid.
The Pixel Editor's "About" window now has a "Copy to clipboard" button to make it easy to paste the displayed system information into forums and help tickets.
•In some cases, the second time that a sequence was played during a run of a show, it would fail with an error message saying "ERROR WITH SEQUENCE (Invalid play state (3) for InitializeForPlay)", and the sequence would never successfully play again during that run of the show. Now, if the Show Player notices a sequence in this invalid play state, instead of giving up on trying to play the sequence, it will attempt to reset the sequence to clear out the problem so that it can be played again.
•In some cases, a seemingly random string of Chinese characters (seemingly not actual meaningful Chinese text) would appear in LOR Control Panel's Status window. At least some instances of this have been fixed.
In the Channel Configuration screen of the Sequence Editor, the Delete Controller function used to remove the channels of the selected controller from the track. You can now choose whether you want that to happen or instead to leave the channels in place but blank out their settings (such as unit ID and circuit).
In the Sequence Editor, there are now keystrokes to move the display to ensure that the start or end of the current selection is onscreen. Shift-Alt-Up and Shift-Alt-Down will display the first or last row in the selection, respectively, and Shift-Alt-Left and Shift-Alt-Right will display the first or last column in the selection, respectively.
Three SuperStar font files have been modified: The characters i, j, u, v, and w have been modified in 10-12x12_Thin.custom.font and 10-12x12_Thin.system.font, and the characters u, v, and w have been modified in 10-12x12_Thin_Vertical.system.font.
Three new effects were added to the Pixel Editor: LinesVertical, LinesHorizontal, and Twinkle. LinesVertical can be used to create marquee-style chase effects on rooflines, arches and frames. You can use the Twinkle effect for a very slow twinkle, or a very fast strobe, and everything in between.
You can now create new sequences directly in the Pixel Editor using the File > New menu item. You no longer need to switch to the Sequence Editor to do this task. If your preview has props where the Sequence Method=Sequence Editor, the channels for those items will automatically be created in the LMS/LAS file and will be grouped by prop.
In the Pixel Editor, prop groups have a new arrangement option of "nested". In particular, this allows nested stars to be grouped together and sequenced as a single item. Using this arrangement, the Bar effect with direction=up moves from the inside out. Bars left/right will move around all of the nested props.
As you move your cursor across the Pixel Editor's sequence grid, a marker is now displayed on the timeline/waveform.
In the Pixel Editor's Preview Info warnings box, all props are now checked for channel conflicts. Previously only props with Sequence Method=Pixel Editor were checked.
For the Pixel Editor's picture and text effects, a repeat parameter was added. Default is "on" to emulate previous functionality. Repeat=off causes just one scroll of the picture or text across the screen.
Changed the minimum number of props in a group in the Pixel Editor from 2 to 1. This allows you to create a preview group (a prop group where the arrangement setting=preview) for a single frame or wreath, which can be useful for certain effects like fire.
When effect thumbnails are displayed in the Pixel Editor, bulb size is now taken into account. This is especially helpful for RGB floods.
Better thumbnails are now generated for Curtain and Fireworks effects in the Pixel Editor.
Prop and group definitions can now be viewed in the Pixel Editor by right-clicking on a prop name in the sequence grid and then selecting "View Prop Definition" from the pop-up menu. It is no longer necessary to go into preview design just to check on the definition of a prop.
In the Pixel Editor, icons are now displayed in the Effect Generator's favorites tree so that folders can be easily distinguished from effects. Also, organizing the favorites tree is now accomplished by right-clicking on any item in the tree. New actions have been added that allow items to be moved up or down, copied, exported to a file, or imported. There is also now a help icon in the favorites area - clicking on it provides detailed instructions on how to use and manage effect favorites.
In the Pixel Editor's Preview Design, the prop list no longer scrolls if you modify a prop (as long as the prop name is unchanged).
Columns for Sequence Method and Dimming Curve have been added to the Pixel Editor's Preview Info grid.
When switching to manual brightness for the first in time in the Pixel Editor's Effect Generator's mixer, the default brightness value has been changed from 0% to 50%. Previously, when switching to manual brightness, nothing was displayed in the middle window because the brightness value was 0.
The Pixel Editor's Effect Generator's Preview and Prop selection drop-downs were made wider, so that longer names are visible.
•When the maximum number of sequencing rows has been exceeded, SuperStar will now display an error message and suggest increasing the sequencing grid's "Max Length".
•Setting SuperStar's manual clip rectangle was only working correctly if you did the mouse drag from upper left to lower right.
•Users who participated in the original S4 beta releases (4.0.0 - 4.0.38) and who had Advanced licenses were granted access as if they had purchased Pro. That access would have allowed the user to set the 'Enhanced Network' for an LOR network ON. At the end of the Beta period, their licenses reverted back to 'Advanced', but the 'Enhanced Network' setting was still incorrectly set.
•If you selected 1000K for the speed of an LOR network in Network Preferences, the "Enhanced" checkbox would automatically become checked (as 1000K is currently only supported for Enhanced networks). However, Enhanced networks are not supported if the license level is less than Pro, and so the network would not work, but also you would have no way to turn off the Enhanced setting.
•In SuperStar, if you had a scrunched visualization, and were doing instant sequence, there were cases where it would only use red, green, and blue; if there were white strings they would never get any effects.
•If a sequence's filename, or the name of the directory path it was in, contained any of various characters such as a parentheses, and the sequence were used in an interactive group in a show, the sequence would not properly be loaded when the group's trigger was pressed.
•If using a visualization of a mega-tree made with the S4 Visualizer Tree Wizard, the auto-clip region for SuperStar images was only using 12 rows of the mega tree. This caused images to get clipped to the first 12 rows.
•If the audio path was not in the default path, SuperStar was not storing the path properly in the sequence file exported to the Sequence Editor, and so the Sequence Editor would fail to find the audio file.
•On some computers, the Pixel Editor's text effect would display text in the entry box but not in the preview area. This has been fixed.
•If errors occur in the Pixel Editor while calculating intensity data, a more detailed error message is now displayed.
•For picture and text effects in the Pixel Editor, if movement is not "none", the initial positioning has been fixed so that the text or picture starts off-screen and scrolls on-screen.
•For picture and text effects in the Pixel Editor, Peak-A-Boo movement now starts immediately. Previously, the effect waited for a "peak-a-boo hold time" before the text or picture was first displayed.
•When the selected prop is changed in the Pixel Editor's Effect Generator, the current effect now restarts.
•The mouse wheel and keyboard shortcuts now work while a tooltip is displayed on the sequence grid in the Pixel Editor.
•A potential Pixel Editor crash after double-clicking on a blank cell in the sequence grid was fixed.
•A Pixel Editor crash when any arrow key is pressed and nothing is selected on the sequence grid was fixed.
•Preview Info warnings in the Pixel Editor now show network name instead of network number (i.e. Regular, Aux A, etc), and unit id's are now displayed in hexadecimal notation.
•A Pixel Editor crash in the Effect Generator when bulb size is invalid was fixed.
•The Pixel Editor's Visualizer import so that it no longer generates invalid bulb sizes was fixed.
•Fixed string assignments for the Fan shape clockwise layout (-CW) (previously the strings were reversed) in the Pixel Editor.
•When double-clicking on an effect favorite in the Pixel Editor to recall it, if that effect had manual brightness, the brightness value was not being restored.
If a PixCon16 is using Network Settings that are not compatible with the computer you are using, you may not be able to configure it. The PixCon16 will appear in the list of devices, however selecting it will produce an error stating that the board cannot be configured. When this occurs, the Network Preferences now offers to start an IP troubleshooter which can try to fix the issue.
LOR Diagnostic now collects additional information that may be useful for troubleshooting purposes, via Windows Management Instrumentation (WMI). It collects some by default, and also now has an "Advanced" screen that allows other WMI-based information to be collected.
•The Pixel Editor's Fire, Fireworks and Meteor effects could have locked up (i.e. the effect freezes) during the intensity calculation that occurs when a sequence is loaded. Once this happened, those effects would be permanently frozen until the program was restarted.
•SuperStar's vertical matrix string pattern with the origin in the upper right or lower left was importing backwards.
•The Pixel Editor could crash in rare instances while starting up.
The Pixel Editor has a new menu option: Tools > Preview Playback > Playback window is always on top. If you are displaying the preview in a separate window and you press one of the play buttons, when this option is enabled it will cause the playback window to immediately gain focus. Testing has shown that this will help on some computers, but on others it will cause playback to be worse (more jerky). Use with caution!
•The Light-O-Rama Control Panel can be set to automatically launch when Windows starts up. It was not doing this in exactly the manner that it should have, and if some other program (unrelated to Light-O-Rama) were doing it in the same incorrect way, that program and the Light-O-Rama Control Panel would interfere with each other's automatic launching settings.
•In SuperStar's Image mode, if you had manual clip set and did a left mouse click while holding the Shift key to get the color of a pixel, it would also set the manual clip rectangle to that one pixel. This was fixed so that you would now need to click and drag more than one pixel to do a manual clip rectangle.
•In SuperStar's Scene mode or Image mode, if you do a left or right mouse click while holding the Ctrl key, it sets or clears all the pixels. A warning box was added to ask if you want that to happen.
•The Pixel Editor would hang while pasting when the number of rows in the clipboard was greater than the number of writable grid rows.
•The Pixel Editor's calculation of intensity data for groups of traditional strings has been fixed.
•Playback in the Pixel Editor is now halted when switching tabs (i.e. when moving between sequences).
The Pixel Editor's sequence grid now displays tooltips similar to the way the Sequence Editor does. In fact it uses the same set of tooltip display preferences. So if you want to change the way the Pixel Editor is displaying tooltips on the grid, then you will need to open the Sequence Editor and select Edit > Preferences > Display Preferences from the menu. Updated tooltip preferences will be read by the Pixel Editor whenever you open a sequence.
•When displaying props whose sequence method is "Sequence Editor" in the Pixel Editor's sequence grid, in some cases the channel name would show "no matching channel" even though the PE and SE physical channel information matched.
When updating the configuration of a PixCon16 board, the Network Preferences program can automatically create the E1.31 multi-cast settings necessary to run the universes defined. However some users may have already created these settings and may not want them created again. Setting this option will bypass that automatic creation.
In some situations, when the lights for a DMX universe using E1.31 are all off, the Comm Listener will now deliver fewer E1.31 packets than it had previously. This will result in less comm traffic on the ethernet network, especially during long stretches of time when the lights are all off (for example, idle time between shows).
Two new sample visualization files, 24x50Tree_8RowGlobe_BottomControllers.lee and 24x50Tree_8RowGlobe_DMX_BottomControllers.lee, have been added.
"Cool White" and "Warm White" selections were added to the Configuration dialog box in SuperStar. Some ribbons/strings are a cool white (they look bluish white when fully on) and some are a warm white (they look yellowish white when fully on). Set this setting appropriately to best get your lights to have colors that match the colors you saw on the computer screen when you made the sequence.
The various programs now have new main icons. It should now be easier to tell apart the various programs in your task bar (and elsewhere). For example, here is an image of the taskbar with icons for the Comm Listener, the Sequence Editor, the Hardware Utility, the Visualizer, and the Pixel Editor:
In prior versions of the Pixel Editor, the order in which props were displayed in the sequence grid was fixed. You still can't change the order of individual props, but now you can change the order by type of prop. To do this, click on the "Props" button - located just to the left of the timeline, above the sequence grid. In the "Select Props" window you can change the "Display Order" drop-down selections to suit your needs. As an example, this feature can be used to move your beat track from the bottom of the grid to the top.
In prior versions of the Pixel Editor, when using File > Save As from the menu a suffix of "-Copy" was added to the end of the original file name. This suffix is now configurable by going to Tools > Preferences > Save As. One of the options is to add a suffix that contains the date and time, which makes it very useful for creating backup copies of your sequence.
•When updating the configuration of a PixCon16 board, the Network Preferences program may occasionally throw an error 523 - Update Failed. If you subsequently check the configuration of the board, you'll see that the configuration actually succeeded. This is due to an incorrect check that was being performed.
•The Pixel Editor no longer crashes if the "Arial" font is missing or corrupted, although you will be unable to add or edit props until the Arial font is restored.
•The logic that refreshes the Pixel Editor's sequence grid during playback has been improved. As a result, playback's "Force Refresh" option is no longer required and has been removed.
There's nothing stopping a Windows user from trying to start a program any number of times, but only one instance of the LOR Control Panel should be running at any given time. So, in previous versions, if the Control Panel were started while another instance of it was already running, the newly-started instance would simply stop, allowing the already-running instance to continue being the sole running instance.
In some situations, this could be confusing, because it might seem to the user that they told the Control Panel to start, and nothing happened. To address this issue, now, instead of just stopping, the newly-started instance will first send a message to the already-running instance, causing the already-running instance to display its status window, and also to refresh its icon in the computer's system tray, in case it had disappeared for whatever reason.
In the Sequence Editor, the Ctrl-Left and Ctrl-Right keys now operate as Page Left and Page Right. Ctrl-Shift-Left and Ctrl-Shift-Right do the same but expand the selection instead of moving it. Also, although Page Up and Page Down functionality was already covered by the Page Up and Page Down keys, for the sake of consistency, Ctrl-Up and Ctrl-Down now operate as Page Up and Page Down (similarly, Ctrl-Shift-Up and Ctrl-Shift-Down as Shift-Page Up and Shift-Page Down).
Please note that unlike in the Page Up/Page Down case, there is not necessarily any relationship between a "page" and the cells. That is, for Page Up/Page Down, one "page" consists of a certain number of cell rows - i.e. a certain number of channels. But for Page Left/Page Right, one "page" consists of a certain length of time, not a certain number of cell columns - i.e. a certain number of timing marks. Timing marks can be anywhere, willy-nilly, or even nowhere, and do not necessarily have any relation to the page. So, as compared to Page Up/Page Down, it may be more difficult to predict exactly where your selection will move or expand to after a Page Left/Page Right.
Several changes have been made to the process and dialog boxes for PixCon16 configuration in an effort to simplify them. Boards that were configured with earlier versions of Showtime will be automatically converted to the new configuration. However there could be some incompatibility between the old version and the new. You should carefully review your boards configuration the first time it is edited in this new version.
To prevent future incompatibilities, once you have edited the configuration of a PixCon16 in the Network Configuration, you should not use the PixCon16 assistant program in the future. If you do use the PixCon16 Assistant program, be sure to double check your configuration to ensure that settings were not changed.
The Network Configuration program used very conservative timing when searching for PixCon16 boards and during the load/save of the board's configuration. Those times have been shortened and improve performance.
•Tightly Packed: Uses all 170 channels available in each universe. Strings can have transitions to the next universe in the middle of the string.
•Semi Packed: Puts as many full strings as will fit into each universe. Strings will not have a transition to another universe in the middle of a string.
•Not Packed: Each string starts with a new universe.
The new Pixel Extender in SuperStar's configuration dialog box makes it so you can export 50 pixel CCR sequences to DMX strings of any length from 50 to 170 pixels. This will make all the 50 pixel CCR sequences that have been written transportable to displays that have DMX strings that have more than 50 pixels.
•After configuring a PixCon16 board, the user is asked if they would like to create the E1.31 entries in the Network Configuration for the DMX Universes in use on the board. However in versions previous to this, the 4 bridge port entries were not created even if they were in use.
•Using Instant Sequence rapid fire on 13 or more rows would cause a crash in SuperStar.
•If a DMX fixture that was not part of a prop were used in SuperStar, it could cause an invalid name to be put in for the fixture, leading to the Sequence Editor being unable to load the exported sequence.
•If SuperStar were unable to load the visualization at startup, it would cause a "failed to load visualization" error every time it was launched. It will now instead change to use the default visualization (which is "Sample.lee").
•If you had entered an invalid number in the "Sensitivity" or "Length of Effects" fields in SuperStar's Timing Map dialog box, the invalid value would get saved to a file, and every time you launched or shut down SuperStar, you would get a warning message saying that the value needs to be in the range 1-10.
If your trigger (no matter whether a show startup trigger or an interactive group trigger) is configured to use a network that does not have a comm port set in Network Configuration, the Verifier will now warn you with the new warning message number 53, "Trigger uses undefined network".
Also, since triggers are not supported on LOR Enhanced networks, the Verifier will now issue the new warning message number 54, "Trigger uses LOR Enhanced network", if a trigger using such a network is found.
Finally, despite the fact that triggers are not supported on LOR Enhanced networks, they can still be tested on such networks by using the Hardware Utility. They will not, however, work during your show. Therefore, if you have any LOR Enhanced networks designed, the Hardware Utility's input testing screen will warn you about this fact.
A new speed of 1000K has been added to the Hardware Utility when creating SD cards for G3 MP3 directors. To use the new speed, you must have a G3 MP3 director with updated firmware. The only device that can currently run at 1000K is the PixCon16 in Enhanced LOR mode.
In previous versions of the Sequence Editor, there was a "Paste from Foreground" option. If it were turned on, then when you pasted, only the copied effects that were not completely off would be pasted. This sort of control has now been expanded into the "Paste From/To" options: In addition to Paste from Foreground, you can now also Paste from Background (i.e. pasting only the copied effects that are completely off), and also Paste to Foreground (paste only onto effects that are not completely off) and Paste to Background (paste only onto effects that are completely off). You can even combine the "from" and "to"; for example, paste from foreground to foreground.
In SuperStar, you can now put the sequencing grid and the visualization each in their own floating window. Before, there were cases where the visualization would be very small. This gives control over the size of the region used for the sequencing grid, and the size of the region for the visualization. Also, if you have two monitors you can move the sequencing grid to one monitor and the visualization to the other monitor.
To activate the feature, click on the "View" menu and select "Floating Windows".
Memory used by the Pixel Editor has been dramatically reduced. This should allow you to easily open longer sequences with more pixels and more prop groups. Memory used is now proportional to the total length of the effects populated in the sequence.
There is a new menu option in the Pixel Editor: Sequence > File References. This will open a window that lists all files referenced by Movie and Picture effects. It also has an option to specify a new location for those files - which can be useful if you move your sequence directory.
The Pixel Editor is now compatible with Windows' "Jump List" feature. If you pin the Pixel Editor to the task bar and right-click on it, you will see a list of recently opened LMS/LAS files from which you can select.
The Hardware Utility now is able to correctly identify 50W Cosmic Color Flood controllers.
The Pixel Editor's "snowflake" effect has an additional parameter to control snow accumulation. Please note that in order to accommodate this change, the meaning of the first and second palette colors in the snowflake effect have changed. Now, the first color is always the main color and the second color is the highlight color. In versions 4.1.2 and prior, the first color was the highlight color the second color was main color for flake types larger than single-pixel flakes.
When needing to update the configuration of a PixCon16, the Network Configuration program would look at the Firmware Revision of the board to decide if it could be used to update that board or not. However, in the future there could be firmware updates that do not require changes to the Network Configuration program. This would force a user to update LOR Showtime for no other reason than to use a new PixCon16 firmware.
Now if the board revision is found to be greater than 1.4.6, additional checks are performed to see if an older version of software can successfully update the board.
•If the SuperStar configuration file SSEdit.cfg did not exist when SuperStar was launched, the program would crash. This could happen on a fresh install to a computer that has never had the Light-O-Rama Software Suite installed on it.
•If a sequence having a Windows shell command were changed to no longer use any such command, the command would be eliminated from LOR's internal list of known commands. This would have the intended effect that the sequence would no longer cause the command to run, but it would also have an unintended side effect: If you were to restore a backup of your sequence save file, which still was supposed to use the command, that restored old version would also not run the command. Moreover, if any other sequences had been using the same command (which would have required manual modification of the save files), they also would no longer run it. Now, instead of eliminating the command from LOR's list of known commands, the command is merely eliminated from the sequence itself.
•In the Sequence Editor, if you tried to copy, cut, or paste in a loop level, a bizarre and minimally comprehensible error message would appear. It now more clearly states that you cannot copy, cut, or paste loop levels.
•The Comm Listener port, as well as the 'Send To' Port on a DMX Universe when using E131 was not validated and could be set to nonsensical values. The value is now checked to ensure it is numeric and between 0-65535.
•In very limited circumstances after an upgrade from a beta version, the Network Configuration program would refuse to start and give a cryptic 'Runtime Error 380' and/or 'Invalid Property' error. This error has been resolved.
•Depending on the source sequence, an SD card written by the Hardware Utility could have been incorrectly throttled leading to out of sync sequences when run on a MP3 director. SD cards created by earlier versions of S4 should be re-created with this version.
•In the Insert Device dialog of the Sequence Editor, the DMX Universe option would not pay attention to the "Name" field. It would instead always name the channels as if you had selected a name of "DMX".
•When using the Advanced Rendering Engine, the Visualizer was ignoring the Max Opacity setting of RGB Flood Light fixtures. A bug fix in Version 4.1.2 for the same root cause failed to fix the problem for RGB floods.
•In SuperStar, group modify for scenes used in the star were not being modified.
•When exporting the SuperStar display as intensity files, all the channels in the 16 channel controller that controls the star were being exported. Now, only the six channels used to control the star are exported. This is important because if the other channels in the controller for the star are used to control other lights, then the blank intensity data for those channels would make them shimmer and blink.
•In SuperStar, when using morphs with a visualization, only the 1a and 1b morph anchor labels were being displayed in the visualization. This has been fixed so that the 1a, 1b, 2a, and 2b labels are drawn. In addition, lines are drawn between the labels in the same manner as they are drawn in the sequencing grid. If using a matrix or tree made of RGB lights this can make it easier to specify morphs by clicking on the visualization instead of the sequencing grid.
•Bugs in the Pixel Editor's drawing of the red playback marker have been fixed. Users have a new menu option: Tools > Playback Options > Fast Playback Marker. Normally, this option should be enabled/checked, as it uses the least system resources. However, if you are using a tool such as Screencast-O-Matic, the red playback marker may still display incorrectly. In this case, turn the "Fast Playback Marker" option off (uncheck), and the grid and playback marker will display normally - even during screencast recording.
•If you built the sequence that is part of the Pixel Editor Introduction (video or PDF presentation), in the final version with the cross-fades the effects reset at the end of the ramp up and at the start of the ramp down. This is especially noticeable in the Countdown effect. This has been fixed - so the ramp-up, full intensity, and ramp-down are considered one continuous effect.
•Improvements to the Pixel Editor's Spiral effect: no more gaps on 100% thickness, fully consistent as rotation is changed, Show 3D can now trail either left or right, and spirals are spaced more evenly.
•A Pixel Editor crash could occur while audio was being loaded if the audio contained a sample with the absolute minimum value. This has been fixed. It was noted in the "Open Beta Bug Reports" forum as bug SC08.
•Fixed a few remaining Pixel Editor screen layout issues on high resolution displays - any time Windows' "Text Resolution" setting is greater than 100%.
•The firmware for PixCon16s was using the LHX extension, however these firmware files can not be loaded by the Hardware Utility, they must be loaded by the Network Configuration program. The extension was changed to NHX to prevent confusion.
A consolidated list of all props with their associated channel information has been added to the Pixel Editor's Preview Info window (accessed from the Tools > Manage Previews menu). There is a Copy button that will put all of the channel information on the clipboard so it can be pasted into Excel, or a similar spreadsheet program.
Documentation for the Pixel Editor, which was previously distributed as a standalone file, is now integrated in this help file.
Previously, there was a separate option the Tools menu where you could delete/copy/rename your Saved Palettes in the Pixel Editor. This function has been moved to inside the Effect Generator's 'Star' menu and called 'Manage Palettes'.
The naming of the wrapped tree visualization file and the wrapped guide text file in SuperStar have been enhanced so that all parameters of the wrapped tree are encoded in the name.
•In some situations, for sequences that have animations, deleting a controller or channels in the Sequence Editor would lead to various errors, for example a "subscript out of range" error. Such errors would not necessarily occur only in the Animator; the fact that the sequence had an animation would cause the problem elsewhere as well.
•The Pixel Editor's startup check for the correct version of OpenGL has been fixed. The user can no longer open sequences if the version of OpenGL is less than 1.5.
•The Pixel Editor would not correctly handle when a pixel string had more channels than the "max channels" setting.
•The "More Info" button in the Pixel Editor's Sequence Editor migration tool now displays messages in a scrollable window. Previously, if there were a lot of messages, the window size could exceed the screen size.
The Pixel Editor's preview design now has undo and redo capability. This applies to prop movement, but not to adding or deleting props.
The Pixel Editor's prop definition window is now resizable.
Documentation for the Pixel Editor is now available. It has not yet been worked into this help file document, but can be found on the web at:
A copy of the document is also distributed by the installer. It can be found in the Light-O-Rama program files directory, which is typically, but not always, either C:\Program Files\Light-O-Rama or C:\Program Files (x86)\Light-O-Rama.
•The Pixel Editor was unable to load some large sequences when attempting to migrate channels.
•Drawing of timing marks in the Pixel Editor was not working correctly on high DPI displays.
•The Pixel Editor would crash when the device type was set to Unconnected/None in the prop definition.
In previous versions, when simulating Cosmic Color Devices, the Visualizer required that the fixture when assembled had exactly 50 pixels with no gaps. CCDs now instead follow the relaxed rules that DMX Pixel Universe fixtures follow. That is, you can skip pixels and/or use less than 50 pixels.
When using the Visualizer's 'Force to Front' option along with channels that required the use of the Listener, the Visualizer could not be set back into the background. This was because of periodic data messages the Listener is required to send, even if no data is changing. These periodic updates would force the Visualizer back to the top even if no sequence was currently running. Instead now the Sequence Editor sends a separate message to the Visualizer to tell it that you are starting play of a sequence. This will only happen once when you start the sequence, allowing the Visualizer to be pushed back into the window stack afterward.
When the Visualizer is placed in Simulation mode, two new buttons have been added that allow you to start and stop playing the active sequence in the Sequence Editor. To start the active sequence press the 'Play SE' button. This performs the same action as if you went to the Sequence Editor's 'Play' menu and then selected 'Start This Sequence'. To stop the play of a sequence, press the 'Stop SE' button.
Version 4.0.34 introduced changes that decreased the loading times of sequences (for example, in the Sequence Editor). Unfortunately, these changes also increased the length of time that various other things took, including, notably, saving, exporting, importing, and opening the right-click popup menu on a channel group button. These things have been sped up again, including some that are now even significantly faster than they had been before version 4.0.34 slowed them down. For example, on a certain huge sequence on a certain machine, saving took about 16 seconds before 4.0.34, but 142 seconds in 4.0.34, and is now back down to about 16 seconds again; importing a certain huge configuration file took about 518 seconds before 4.0.34, 663 seconds in 4.0.34, and now takes about 85 seconds; opening the right-click popup menu took about seven seconds before 4.0.34, and about 39 seconds in 4.0.34, and is now basically instant.
"Clip Rectangle" has been added to SuperStar's Image Group Modify dialog box.
"Rotate Selected Image" has been added to SuperStar's Image setup dialog box.
In the Pixel Editor's preview design, props are now displayed with a rotation handle to the right of the selected prop (similar to the Visualizer). Just grab the handle and drag it with your cursor to rotate the prop. Note that only one prop can be selected for the rotation handle to be displayed.
The brightness of the Pixel Editor's preview's background image can now be adjusted from the main window. With a sequence open, click on the small down arrow next to the preview name. Select "Background Image" from the dropdown menu, then select the desired brightness (10% - 100%). Note that this setting only affects image brightness during preview playback; image brightness during preview design is a separate setting.
Zoom in and zoom out buttons have been added to the Pixel Editor's sequence toolbar (the same buttons that are in the Sequence Editor). You can still zoom in and out using the previous methods - dragging over the waveform to zoom in, and right-clicking on the waveform to zoom out - but there are now two ways to zoom.
Changes have been made to improve performance related to channels, RGB channels, and other channel groups. For example, a certain enormous sequence which previously took 143 seconds to load on a certain machine now takes 81 seconds on the same machine. The vast majority of the remaining time is taken by loading effect events within channels, as opposed to loading the channels themselves, and the Smooth to Fades tool can be put to good use on the effect events of this particular sequence: The same sequence, but modified via the Smooth to Fades tool, used to take 82 seconds to load before this performance improvement (as opposed to 143 without Smooth to Fades), and now takes 19 (as opposed to 81 without Smooth to Fades).
Various small changes have been made to the Network Configuration program to simplify its use. For example, the X10/Dasher and Options tabs have been combined into a single new tab called 'Misc'. These changes are cosmetic only and do not change any functionality.
The Sequence Editor now has a Change Intensities command, which can be used to change the intensities in the selected area in a wide variety of ways. For example, you can add to or subtract from intensities, impose caps or floors, and scale them (for example, double them or halve them). The tool can be set up to apply to all channels or only to certain types of channels (for example, to RGB channels' red channels).
Version 1.21 of the Cosmic Color Bulb/Cosmic Color Pixel firmware has been released. This version fixes a problem with LOR Enhanced mode and the last channel (310) of the unit not working when in Extended ID Mode.
Version 1.34 of the CMB16D 16 Channel DC controller firmware has been released. This new firmware will continuously read the status of the address switches so the Hardware Utility can no longer be used to update the Unit's ID. This change also allows for the CMB16D to now have a speed setting while in stand-alone mode. Setting an address that starts with F (F0-FF) will actually make the unit's ID 01, and the second digit (0-F) will control the speed of the stand-alone program running from 0:Slow to F:Fast.
The Show Player options Use Compressed Sequences and Show Player Memory Restarts (both accessible via the LOR Control Panel's right-click popup menu) both, when enabled, give possible benefits while causing no drawbacks. They are thus both recommended to always be enabled. The only reason the option to disable them is given is as a sort of "safety" in the case of some hypothetical, unforeseen bug, so that if you have some very specific reason to believe that one of them is causing a problem, you can turn it off. The Verifier now checks to see whether or not they are enabled, and if not, issues warning messages saying so (messages number 51 and 52, respectively).
In the Pixel Editor's Effect Generator, many effects use a slider to control effect behavior. In this release, the slider has been upgraded to allow the setting of a start value (effective when the effect begins) and an end value (effective when the effect completes). This allows you to do such things as having a spiral slow down or speed up during the course of the effect.
The top of the slider (green) represents the start value. The bottom of the slider (red) represents the end value. By default, the start and end values are locked together. To specify different start and end values, the slider must be unlocked. This is done by double-clicking anywhere along the slider. When unlocked, the top and bottom pointers can be moved independently. To relock, just double-click the slider again.
•In SuperStar, strings of lights that are not CCDevices or DMX pixels were always being given the incandescent dimming curve. Now the strings use the LED dimming curve if they are RGB dumb strings or if they are specified as LED in the channel dialog box of the Visualizer.
•The Pixel Editor requires video drivers supporting OpenGL version 1.5 or later. If a PC did not support this, the Pixel Editor would crash when opening a sequence. Now, the Pixel Editor instead detects this situation, gives the user an informative message when the Pixel Editor starts, and disables the opening of sequences.
•A bug in the movement of scenes when using the Rapid Fire trigger in SuperStar's Instant Sequence was fixed. If it was more than one pixel, the scenes could get messed up when traversing over an unused area.
The Sequence Editor's right-click context menu now has a "Change Effect Type" submenu that can be used to change the effect types of all the events in the selected area of the sequence, while keeping their intensities the same. For example, a fade up from 0% to 37% followed by an intensity of 37% can be changed to a twinkling fade up from 0% to 37% followed by a twinkle of 37%.
The Sequence Editor's right-click context menu on a track grid now has a new submenu "Test Track's Physical Lights". Using the various items in this submenu, you can make the physical lights for all of the channels in the track turn on, off, shimmer, or twinkle, or else do whatever the sequence says they are supposed to do at the time that you clicked in the track grid.
In the Pixel Editor, the background image for the preview can now be displayed during main window playback. This feature is controlled via a new menu option: Tools > Preview Playback > Show background image.
•If the Sequence Editor's "Test Physical Channels" command were used on a Cosmic Color Device, commands would be sent not only to its pixels, but also to its macro channels, potentially leading to strange results. The commands are now only sent to pixels, skipping the macro channels. However, note that it is possible to control an actual physical Cosmic Color Device from the Sequence Editor without the Sequence Editor knowing that it is a Cosmic Color Device; the macro channels will only be skipped if the Sequence Editor knows that the channel group represents a Cosmic Color Device (for example, if it had been added to the sequence as a CCD via Insert Device).
•If the Sequence Editor's "Test Physical Channels" command were used on a channel group or RGB channel (as opposed to on a single channel), it would be needlessly inefficient with the commands it sent to the lights over the comm line. This wouldn't have a noticeable effect in most cases, but it could possibly cause lagginess if a very large number of channels were in the channel group.
•In the Pixel Editor's prop setup window, the maximum allowed segments per line has been increased.
•During the Pixel Editor's sequence playback, pixels were often not square when playing back on the main window. Now, pixel dimensions are even recalculated if the playback window is resized during playback.
The "Test Physical Channel" commands in the Sequence Editor's right-click popup menu on channel buttons used to apply only to actual channels, as opposed (for example) for RGB channels. You could use them on the individual channels comprising an RGB channel, but not on the RGB channel as a whole. You can now use these commands on RGB channels and other channel groups, turning on or off all channels in the group in one fell swoop.
Sometimes, sequences (especially those created with the help of various automatic tools) will have sections wherein a channel will have many very rapid consecutive effect events. For example, "From time 0.00 to time 0.05, 10%; from time 0.05 to time 0.10, 30%; from time 0.10 to time 0.15, 40%; from time 0.15 to time 0.20, 70%". If done on many channels, this sort of thing can lead to laggy or bursty behavior. Moreover, it's often more or less indistinguishable (to the human eye) from the simpler "From time 0.00 to time 0.20, fade up from 10% to 70%", which is significantly more efficient. The Sequence Editor now has a "Smooth to Fades" tool which will attempt to automatically smooth out effects in this way, which can improve the performance of the sequence (reducing lagginess) and also decrease loading and saving time. You can get to the Smooth to Fades tool via the track grid's right-click context menu.
•Consecutive picture effects in the Pixel Editor would not display the correct images.
•When creating a new prop in the Pixel Editor, an error would occur if the user selected the string type as "strobe string 1 ch" or "multicolor string 1 ch" before selecting a color.
The Pixel Console in the Hardware Utility could previously only test PixCon16 devices when running in E1.31 (DMX over Ethernet). It can now also test PixCon16 boards, or any other LOR controller that are connected to the REGular LOR Enhanced network running at 500K.
In the Pixel Editor's Visualizer import function, string, single bulb, and flood fixtures now default the Sequence Method to Sequence Editor. CCR and DMX fixtures default the Sequence Method to Pixel Editor.
Pixel Editor prop groups can now contain any prop, not just those with a Sequence Method of Pixel Editor.
"More Info" buttons were added on the Sequence Editor-to-Pixel Editor migration tool, to show exact channel mismatches.
•In SuperStar's Smooth Effects dialog box, if the Enter key were pressed while the tab pane had the focus, the pane would go blank. It now does not go blank, and sets the current values to the screen.
•When importing or exporting a network configuration in the Network Preferences program, if the filename contained a special character (such as a space), the import or export could fail silently or the file could be saved with an incorrect filename.
•When changing the Unit ID or Universe ID in the Pixel Console, the pixels displayed should have reset to show the first pixel. However this was not happening.
•When changing a DMX universe to use E1.31 in the Advanced Network Configuration, if there were no previous settings the IP is set to Multicast with the correct address rather than Specify with an IP of 0.0.0.0.
•If the user previously configured a DMX Universe in the Advanced Network Configuration, those values are used as the defaults for the next DMX Universe edited if that universe has no previous settings.
•The Pixel Editor would crash when opening some sequences.
•The Pixel Editor would sometimes have incorrect channel assignments on custom props.
•The Pixel Editor's preview playback would not update when in a separate window.
•The Pixel Editor's Effect Generator was not detecting the "none" effect correctly.
If you right click on a physical channel in the Sequence Editor, you can now send an ON command directly to that channel. This will allow you to test if you have properly configured and connected your equipment, and that you have correctly set the channel's parameters. The channel will remain ON until you select to turn the channel OFF, or you play a sequence.
You can now import Visualizer files (*.lee) into the Pixel Editor. In the Pixel Editor, select Tools > Manage Previews from the menu, then click on the "Import Visualizer" button. This functionality is preliminary - only fixtures get imported at this time. It is intended that in a future release, Visualizer props will also get imported as Pixel Editor prop groups.
The performance of sequence playback has been improved in the Pixel Editor.
•In the Pixel Editor, the timing mark display no longer bleed through if the user switches to another window/application during playback.
Only one program can have a comm port open at any given time. For ports associated with LOR Enhanced networks and DMX networks, typically the Comm Listener will have the port open. In previous versions, this meant that if you wanted to use the Hardware Utility on such a port, you would have to ensure that the Comm Listener was not running, which is typically done via "Unload Light-O-Rama" in the LOR Control Panel's right-click popup menu. Now, instead, when the Hardware Utility cannot open a port and it suspects that the reason might be that the Comm Listener has that port open, it now offers you the choice of whether or not it should ask the Comm Listener to temporarily give up control of the port. Thus, you can use the Hardware Utility on such ports without completely unloading the LOR Control Panel.
Two things should be noted: First, if you ask the Comm Listener to give up control of the port, then no program other than the Hardware Utility will be able to control lights on that port (until the Comm Listener retakes control of it). Notably, this means that if a show is running, any lighting commands from the show for the lights on that port will not take effect. Similarly with lighting commands from the Sequence Editor or Pixel Editor.
Second, the Hardware Utility does not really know that the Comm Listener is the culprit that is preventing it from opening the port; it just has a good guess that this might be the case. The culprit might instead be some other program entirely; for example the Sequence Editor might have the port open, or even some program completely unrelated to Light-O-Rama. So, if the Hardware Utility asks you if you want it to ask the Comm Listener to give up control of the port, and you say yes, this might not cause the Hardware Utility to be able to take control of the port. In some cases, you might still have to (for example) close the Sequence Editor.
When configuring the PixCon16, the only way to automatically have the board assign ascending Universe or LOR Unit IDs previously was to use the 'Advanced' configuration and manually create the parameters for each port. The PixCon16 configuration can now perform this task automatically in simple or advanced mode. In simple mode, select the 'One UID/Universe per port' radio button. In Advanced configuration use one of the 2 buttons which automatically update all lower ports with ascending unit IDs.
•In the Hardware Utility the 'Lights Off' button on the bottom right of the main screen was not turning all lights off on Cosmic Color devices
Previously, when finished drawing a DMX Pixel Universe or a CCR String, it was always required to create a new prop. However many times these wizards are used to continue adding pixels to existing fixtures. These wizards now ask if you want to create a new prop or not.
The PixCon16 has 2 operation modes: It can be used as an E1.31 controller on an Ethernet network, or it can be used as an LOR controller on an LOR RS485 network. Now the user can specify which mode to use the board in, and will change its operation accordingly (Unit IDs instead of Universes, Circuit IDs rather than Channels, etc.)
When the PixCon16 is in E1.31 (DMX) mode, saving the configuration will bring up an option to automatically create the necessary DMX Network configuration changes. If the user selects yes, for each DMX universe in use on the board the system will create Multicast entries in the network configuration.
Previous versions took a very conservative approach when reading or writing to the board, including during firmware updates. Now the read/update process will retry more often and at a faster rate in an effort to reduce the number of errors the user has to deal with.
•When creating DMX Pixel Universes using a Wizard, the Visualizer would not correctly display fixtures with available pixels. Instead the wizard would crash and leave the Visualizer in an inconsistent state.
•The Hardware Utility main window was improperly sized allowing for controls that should have been hidden to be visible.
There is a small colored square in the bottom right corner of the Sequence Editor which indicates the status of various networks: Blue means everything's OK, red means some sort of problem exists, and orange means other (for example, if Control Lights is off). This has been improved in several ways in this version of the Sequence Editor:
•In S3, it would only indicate the status of LOR networks. In earlier beta releases of S4, it would actually indicate less than that: It would only indicate the status of non-enhanced LOR networks. It now also indicates the status of non-enhanced LOR networks and of DMX networks (although see below for a caveat).
•Previously, if an error existed on some network, its tooltip would simply say that there is an error. It now indicates which network or networks have errors.
•Previously, starting play would in some cases make the panel turn from red to blue even if some network still had an error.
•It now updates in close to real time when some sort of status change happens.
Two things should be noted: First, for LOR enhanced networks and for DMX networks, the status describes whether or not the Sequence Editor is successfully communicating with the Comm Listener; it does not necessarily indicate that the Comm Listener is successfully communicating with the network. Check the Comm Listener itself for that information. Second, only the statuses of LOR and DMX networks are taken into account at this time; the statuses of Dasher, X10, Digital IO and BSOFT Digital IO networks are not reflected.
Previously, the Hardware Utility Test screen could only test up to 32 circuits on a device. Cosmic Color devices however can have 150 or more circuits, which could lead to user confusion. Now when a Cosmic Color device, like the Cosmic Color Ribbon or Cosmic Color Bulb, is selected the test screen changes to testing the entire device with a particular color rather than circuit by circuit.
On the Pixel Editor's prop definition window, the details of setting up a traditional string have been moved to a separate tab from RGB strings.
In the Pixel Editor, traditional strings can now have a custom bulb color (defined with the rest of the string colors). Press the "Custom" button to set the color.
Bulb shape and bulb transparency were added to the Pixel Editor's props. These can be set in the preview design window after one or more props have been selected.
The Pixel Editor has a new prop shape of "Bulbs". Each bulb in the prop can be individually positioned.
The maximum possible bulb size in the Pixel Editor has been increased so as to better accommodate flood lights.
It is now possible to override the default channel settings for every channel in a prop with traditional strings in the Pixel Editor. For example, a traditional megatree with red and green strings can now have a channel configuration of RRRR...GGGG.... Previously, it had to be RGRGRGRG....
The Pixel Editor has a new comment field for props, which you can use to enter your own notes about the prop.
The Pixel Editor's "Traditional" sequence method has been renamed to "Sequence Editor".
Color selection palette hidden for effects that do not use it
The color selection palette on the Pixel Editor's Effect Generator window is now hidden for effects that don't use the palette (e.g. Picture and Movie effects).
The Pixel Editor's Movie effect can now read uncompressed AVI files produced by the ffmpeg program.
The Pixel Editor's "Remove prop channel data from Sequence Editor" migration tool defaults to checked if the Pixel Editor and Sequence Editor channel counts match and the Has SE Events column is Yes.
You can now create your own dimming curves for the Pixel Editor, placing them in the "Pixel Editor\Curves" directory within your LOR data directory.
The Pixel Editor now shows a wait dialog while saving intensity files.
•The Pixel Editor would hang after pressing play when the audio file was missing.
•The Pixel Editor would crash if a sequence was opened, closed, re-opened, and then the preview was changed. A memory leak related to this was also fixed.
•A bug in the Pixel Editor's onscreen playback of strobes was fixed.
•A Pixel Editor bug dealing with custom RGB props with multiple strings has been fixed.
•After a "Save As" was done in the Pixel Editor, the Pixel Editor file (LPE) had a timestamp that was current, but the new LMS/LAS file's timestamp was the same as the original file. Now both files will have a timestamp that is current.
The Pixel test Console in the Hardware Utility has been improved to now be able to test DMX pixels. DMX Pixels can only be tested when the Comm Listener is running and if your software is registered at the Advanced level or higher.
In previous versions of the Sequence Editor, if any particular comm port for an LOR network could not be opened, the Sequence Editor would automatically turn off Control Lights and therefore not attempt to control lights on any network. The reason for this was that it would be very resource-intensive to keep trying to open a comm port that just could not be opened, to a degree that would noticeably affect play. Now, instead, the Sequence Editor will leave Control Lights on, but not attempt to control the specific problematic network (or networks). If you find yourself in this situation, and you fix the problem with the comm port, you can get the Sequence Editor to attempt to open the port again by manually turning Control Lights off and then on.
There are two new buttons on the Network Preferences Advanced configuration that allow for the export and import of user network configurations. These functions can be used to keep multiple configurations on the same computer, or to move configurations between computers.
In the Pixel Editor, you can right-click on an effect thumbnail and select "Copy" from the popup menu. This puts the effect on the clipboard, from where it can be pasted anywhere on the grid.
In the Pixel Editor, you can drag an effect thumbnail onto a grid cell, and that cell will then be populated with that effect.
In the Pixel Editor's Preview Management window, clicking the "Info" button now lists warnings where channel assignments overlap (in addition to listing basic statistics about the preview). This is a great way to check whether you have any errors in creating your preview.
The Pixel Editor's prop types "Line-Horizontal" and "Line-Vertical" have been replaced with "Lines-Closed Shape", "Lines-Connected", and "Lines-Unconnected", which can be used to create a much larger variety of shapes. Any Line-Horizontal props in your preview will be automatically converted to a Matrix-Horizontal that is one string high. Line-Vertical props will be automatically converted to a Matrix-Vertical that is one string wide.
When doing a "Create Timings" in SuperStar, a dialog box now appears, giving control over the range that the beat interval can be. The default range is what it used to be a year ago so that Carol of the Bells is given a short beat interval that matches what is in the first SuperStar tutorial.
•In some very limited cases, the Network Preferences program would produce an error stating that a COM port and a DMX adapter were in conflict but were not. This same bug could also manifest itself as an 'Error 9 - Subscript out of Range' error and crash when starting the Network Preferences program.
•The position of the Visualizer Advanced Rendering Engine window would not be remembered between executions.
The Pixel Editor now shows a checkmark in the menu next to the currently selected waveform size.
•In some situations, the Light-O-Rama Control Panel would issue an error message saying "Error in Form_Unload: (91) Object variable or With block variable not set".
•The way that SuperStar's configuration is saved has been changed for better backward compatibility.
•On some computers, if the Pixel Editor's preview playback window lost the focus, the playback would be blank.
•The Pixel Editor would only allow one universe for custom props.
•Media files longer than twenty minutes were not loading in the Pixel Editor.
A new option has been added to Hardware Utility when creating SD cards for MP3 directors to either leave channels on DMX Universes at their current intensities or else turn them off when a sequence ends.
The Light-O-Rama Control Panel's right-click popup menu is now also accessible from its Status window, as the "Commands" menu. Generally speaking, this may (or may not) be more convenient in some situations, but it could be very useful in certain situations where Windows repeatedly keeps closing the popup menu automatically before you get a chance to select the menu item that you want to use from it.
In previous versions, the Light-O-Rama Control Panel would not start up the Comm Listener unless at least one network was configured in Network Preferences to use the Comm Listener. It now no longer requires any such networks to be configured. This allows commands to go through the Comm Listener to the Visualizer even if no networks at all are configured to use the Comm Listener.
The Pixel Editor migration tool to remove channel data associated with Pixel Editor props from the sequence file (LMS or LAS file) is now operational. This tool should be used only after you have first imported your sequence using the Sequence Editor import and/or the xLights import. The benefit of this tool is that it eliminates any overlapping channels between the sequence file and the intensity file, which is necessary for proper playback outside of the Pixel Editor. It can also greatly reduce the size of your sequence file.
The Pixel Editor previously stored the preview data file under the hidden AppData directory. It now stores it in the standard LOR data path, and no longer stores any data under AppData.
The Pixel Editor's Design & Playback window has been split into two separate windows, one for design and the other for playback. This was a prerequisite for solving other playback issues.
The Pixel Editor's toolbar above the sequence grid has been revamped to look more uniform. Also, playback buttons were added, as were some options that were previously in the Sequence menu.
The Pixel Editor's preview playback can now be hidden, shown on the main window, or shown on a separate window. Even when on a separate window, the grid remains interactive. The choice of which mode to use is under the new Tools > Preview Playback menu, and applies to all sequences.
Windows Media Player is now used for all media playback in the Pixel Editor. Previously, the displayed audio waveform (compressed audio) was used for playback on the main window, but this had low sound quality.
•The SuperStar star was not getting marked properly if it also had row/column coordinates.
•In the Pixel Editor's Preview Design window for "Dumb RGB" and traditional strings, moving an end point on such a string would cause the drawn string to collapse to a single point.
•The Pixel Editor's media file search was not locating files in subdirectories under the default LOR media directory.
Version 1.33 of the firmware for the CMB16D has been released (filename CMB16-1-33.lhx). This new version has no effect on functionality; it is being released because the recently released previous version 1.32 would incorrectly be displayed in the Hardware Utility as being version 1.31.
In the Pixel Editor, dumb RGB elements can now be members of a group.
In the Pixel Editor, the user can now specify Window Frame props to use clockwise (CW) or counterclockwise (CCW) pixel order. Users who have created Window Frame props with previous beta versions will need to go back into those prop definitions and update the Start Location value to match their prop.
In the Pixel Editor's prop creation dialog, the number box next to the DMX radio button (max channel/circuit number) now applies to both DMX and LOR networks. In particular, this resolves an issue when defining props based on the CMB24DC card.
•The Comm Listener is designed to shut down when the LOR Control Panel shuts down. In previous versions, this behavior relied upon the LOR Control Panel periodically sending "keep alive" messages to the Comm Listener; if the Comm Listener didn't receive such a message within a reasonable amount of time, it would shut itself down. This worked fine most of the time, but in some situations (typically involving very large shows), the LOR Control Panel would sometimes not get a chance to send such a message to the Comm Listener for a while, leading to the Comm Listener shutting itself down prematurely. Now, instead of relying on these messages, the Comm Listener periodically directly checks whether or not the LOR Control Panel is running.
•SuperStar's progress dialog box works smoother.
•In SuperStar, play of a song sometimes wouldn't stop until the end of the song was reached.
•The Verifier is supposed to check for the existence and correct version numbers of various program files (in Verifer message number 7 and number 16 respectively), but it was not doing so for several relatively new files.
•The Network Preferences program could incorrectly identify two or more networks as being in conflict when they were actually not.
•The Pixel Editor could crash during migration of custom props.
•The preview calculation for LOR channels in the Pixel Editor was producing a range of 0-100 instead of 0-255, which made them appear dim (both as part of the preview and as part of the Sequence Editor migration). Users should rerun any Sequence Editor migrations they performed using version 4.0.6.
In the Pixel Editor's table of effect thumbnails, the current thumbnail is now highlighted, making it easy to distinguish which thumbnail is playing in the right-hand window.
Previous versions of the Comm Listener required FTDI drivers to be installed on the computer, even if the Comm Listener weren't supposed to drive any lights that use FTDI-based adapters. It now no longer requires these drivers. If they are not installed, then the Comm Listener will not be able to control any lights on FTDI-based networks (such as LOR Enhanced networks and most types of DMX networks), but it will be able to control the Visualizer, and also control lights on E1.31 networks.
The Pixel Editor has a new Sequence Editor migration tool. From the menu: Sequence > Migration Tools > Import from Sequence Editor. It will allow sequences for RGB props to be copied into the Pixel Editor. The result will be an exact pixel for pixel copy displayed as a single effect that spans the length of the sequence (one effect per imported prop). Portions of that single effect can then be removed and replaced with Pixel Editor effects as desired.
The Pixel Editor has a new effect: Movie. This effect will play AVI movie files on your props (files with an "avi" extension). This effect is a bit limited in that the AVI movie files must be "uncompressed". Various third-party programs (such as VirtualDub) can be used to produce such uncompressed AVI files.
The Pixel Editor has received some performance improvements: There has been some modest improvement in the preview calculation speed, and a large speed improvement to the Pinwheel effect (meaning it now takes far fewer CPU cycles to calculate).
•In SuperStar, if you attempted to export an intensity file to a directory other than the sequences folder, the empty *.lms file got placed in the correct folder, but the associated intensity file always got placed in the sequences folder.
•Preview of text on SuperStar's sequencing grid was being clipped to only the matrix in a visualization that contained a matrix and other lights. It will now display the preview of the text to the entire sequencing grid.
•If the Comm Listener were configured to use some particular adapter, but it could not open that adapter, lighting commands sent to the Comm Listener for that adapter's network would build up without being processed until the adapter was successfully opened. This would result in the Visualizer unnecessarily not receiving the lighting commands either, and also potentially lead to an out-of-memory condition eventually.
•Ramp up effects on the left side of the Pixel Editor's grid were displayed incorrectly.
•The Pixel Editor's xLights 3 import tool is now located under the Sequence > Migration Tools menu.
•One of the things that the Light-O-Rama Post Install utility does is to give you a chance to choose the directory that Light-O-Rama will (by default) use to store your data files (such as your sequences and visualizations). If you previously had chosen a data directory, then ran Post Install again and told it to use a different directory, it would copy your data from the old directory to the new. However, it would not copy all such data; in particular, data files that you had stored in subdirectories would not typically be copied over to your new data directory.
The Pixel Editor has a new predefined prop shape called "Spokes", for props that have spokes that radiate from a central hub.
The Pixel Editor's pinwheel effect has new controls: Two sliders to control the center of rotation, and one to control the length of the arms.
The file format of Visualizer files has changed. When saving an S3 file in S4, the Visualizer will first back up the editor file. Should you choose not to move to S4, you can use this backup file to restore to an S3 format.
When issuing a log message about one of its clients (such as the Sequence Editor or Show Player), the Comm Listener would refer to the client via the IP socket that the client used to connect to the Comm Listener. For example, it might refer to a certain client as "Socket 127.0.0.1:57223". This is enough to uniquely refer to the client (at least until it disconnects and later reconnects), but it's not terribly informative for troubleshooting purposes. Now it additionally refers to the client by name (such as "Sequence Editor"), if the client has identified itself to the Comm Listener in that way. Please note that not all clients will necessarily identify themselves to the Comm Listener in all situations, so in some cases the Comm Listener will still only log the IP socket information.
Tracks and props now remember whether they are hidden
In the Sequence Editor, when you opened a sequence, all tracks and the props section would be unhidden, even if you had previously hid some of them while that sequence was open earlier. The sequence now remembers whether or not they should be hidden even after it is closed and reopened.
A new sample visualization file, 24x25Tree_8RowGlobe_dmxPixelTool.lee, has been added.
•When the Pixel Editor was displayed on a secondary monitor, the timing marks would display incorrectly during prop playback.
•In the Pixel Editor, when creating custom props that skipped node numbers, the program would crash.
•In the Pixel Editor, when creating custom props that used the same node number more than once, the prop would display some nodes in the wrong locations.
•When loading certain sequences into the Pixel Editor, the program would crash. This would happen with sequences that had more than one channel assigned to the same physical circuit. It would also happen with sequences that used the same channel name more than once.
•The version number displayed in the Pixel Editor's "About" box did not match the rest of the Light-O-Rama programs (it had an extra ".0" in it).
•The caption on the Pixel Editor's main window was missing some of the information displayed in the captions of other Light-O-Rama programs.
•In certain cases after unexpectedly disconnecting from and successfully reconnecting to the Comm Listener, a client may not have correctly told the Comm Listener whether or not lights should be turned off the next time that it disconnects.
•When the Pixel Editor displayed effect thumbnails in the left window, thumbnails for Firestick props were bunched too close together. A similar problem could occur for horizontal lines.
•When a log message is added to the LOR Control Panel's status window and it is beyond the end of the visible portion of the log, the log should automatically scroll to the bottom in order to display the message. In certain situations, this was not happening.
•The Pixel Editor was requiring unit IDs for LOR networks to be entered using their decimal value. Now unit IDs are entered with their hex value, just like every other LOR program. Users of version 4.0.0 will need to go back into each prop that is on an LOR network and update the unit ID to use the controller's hex value.
There is now an additional license level, "Pro", above Advanced. A Pro level license enables several new features designed to help with very large displays: The Light-O-Rama Pixel Editor, intensity files, and enhanced Light-O-Rama networks.
The Light-O-Rama Pixel Editor is a new program which can be used to produce lighting effects for sequences in a visual way. It produces intensity files, which can efficiently support large lighting displays.
Intensity files are a new way to store lighting commands. An intensity file, generated by the Light-O-Rama Pixel Editor or the Light-O-Rama SuperStar Sequencer, is associated with a sequence, and will play at the same time that the associated sequence plays. Instead of storing lighting commands in the traditional high-level way (such as "fade up over the next five seconds from 0% to 100%"), an intensity file stores large blocks of instantaneous intensity values for potentially many circuits. This allows the intensity file to be very efficient during play, and so enables better support for very large lighting displays.
Only Light-O-Rama controllers and native DMX devices can be used in an intensity file, and the Light-O-Rama controllers must be on enhanced LOR networks. The LOR Comm Listener must be running in order for the lights to be controlled. This feature only works under the Pro license level.
A Light-O-Rama network can now be set to be an "enhanced" network. This causes the network to use a new communications protocol (an extension of the standard Light-O-Rama communications protocol) which can deliver lighting commands for many channels efficiently. If an intensity file is used, any LOR controllers from the intensity file must use an enhanced LOR network, but enhanced LOR networks also support effects defined directly in a sequence.
The Hardware Utility can also write SD cards for G3 Directors for Enhanced Networks. Again, all controllers connected to a port must support the Enhanced Protocol, and the G3 directors firmware will need to be updated to at least version 5.32.
Not all Light-O-Rama controllers support the enhanced protocol, and some may require firmware updates in order to do so. The LOR Comm Listener must be running in order for lights on an enhanced network to be controlled when using a computer. Enhanced LOR Networks only work under the Pro license level.
In the Sequence Editor, converting channels to RGB channels would get slower and slower as the sequence got larger and larger, and eventually the sequence would become large enough that the conversion would take a very long time. This has been sped up significantly.
The Visualizer now supports a 'DMX RGB Pixel Universe' fixture. This fixture allows for up to 170 RGB pixels to be part of a single fixture which is defined as a DMX Universe.
Previously the Visualizer was limited to creating a single fixture for a symbol. This limited the selection of a font glyph to one that had less than 256 vertices. The Visualizer will now create a prop and as many fixtures as needed for a single glyph, up to a maximum of approximately 16,000 vertices.
•All drawing wizards that could previously be used with Cosmic Color Devices have been updated to be able to use the new DMX Pixel Universe fixtures as well.
•A new wizard for drawing DMX Pixel Strings has been added.
•A new option for 'Snake' layouts has been added to the Matrix Wizard, as well as a new selection that will show pixel ordering while the wizard is running.
Pressing SHIFT while pointing at a CCR or DMX Pixel Fixture in the drawing area will 'blink' the pixels in the order they are assigned. The speed of the blink can be controlled in the The Visualizer's Options window, Tab 2.
A new advanced rendering engine has been added to the Visualizer to greatly enhance performance of the program while simulating many channels, especially RGB bulbs. The new rendering engine takes advantage of the hardware acceleration available on nearly all modern video cards. This new engine is experimental, however it has been tested on several different cards. The new engine is enabled by default, however it can be disabled if needed.
When entering simulation mode, the Visualizer would give cryptic error messages if it was unable to assemble Cosmic Color Devices into meaningful groups. Those error messages have been improved and expanded to include DMX Pixel Universes.
The Visualizer will now more closely emulate how a real controller presents shimmers and twinkles. Due to differences between actual hardware clock speed and the visualizer, slight differences will remain, however the look is much improved over S3.
A new dedicated window has been added to both Fixtures and Props in the Visualizer to store SuperStar parameters. Previously, these parameters were placed as a keyword in the comments of a fixture/prop. They now have a dedicated area for ease of use.
Certain log messages that were output by the Comm Listener, associated with errors or other information about TCP/IP sockets, would include in their output some numbers that were essentially meaningless from the point of view of the end user. They now instead output the IP address and port of the socket.
Several new and updated pieces of firmware have been released:
•CCB100D-V1_20.lhx (CB100D Cosmic Color Pixel/Bulb Controller) : Added support for Enhanced LOR networks, and fixed a bug where the bulb self test did not correctly run while the reset button was held on the controller.
•CCR150D-V1_19.lhx (CR150D Cosmic Color Ribbon): Added support for Enhanced LOR networks.
•CMB24D-V1_02.lhx (CMB24D): This is the first version of firmware for this device that has been distributed with the LOR software suite.
•CTB04Dg3-V1_01.lhx (the new 4 channel CTB04g3 AC controller; also used in the new LOR400Wg3 and LOR400ELLWg3 controllers).
•CTB08Dg3-V1_02.lhx (the CTB08Dg3 controller card and the LOR800Wg3 controller): Added support for Enhanced LOR networks.
•CTB16PCg3-V1_08.lhx (the CTB16PCg3 card and the gen3 residential controllers): Added support for Enhanced LOR networks.
•CTB32Lg3-V1_12.lhx (the CTB32L card and the LOR16xxWg3 light controllers). Added support for Enhanced LOR networks.
•DC_MP3_V4-20.lhx (DC-MP3): This version of the firmware makes triggered shows start faster.
•iDMX1000_V1_50.lhx (the iDMX1000 controller). Fixed a problem with missed effects when running at 115.4K. Added support for 500K. Added support for Enhanced LOR networks.
•MP3g3-V5_32.lhx (G3 MP3 Dual Network Director): Supports Enhanced LOR networks, and fixes two bugs: (1) In some cases, the firmware would believe that the sound and lights were extremely out of sync when they were not. This would cause error detection code to be triggered which would stop the song that was playing and move on to the next song. (2) In some cases, the firmware would ignore a show's schedule. Instead, a show would start as soon as the SD card was inserted.
•RF-V4_v2-10.lhx (RF-V4 Easy Light Linker): This release allows the RF-V4 to use 115K comm speed.
•uMP3g3-V5_32.lhx (G3 Mini Director): Supports Enhanced LOR networks, and fixes two bugs: (1) In some cases, the firmware would believe that the sound and lights were extremely out of sync when they were not. This would cause error detection code to be triggered which would stop the song that was playing and move on to the next song. (2) In some cases, the firmware would ignore a show's schedule. Instead, a show would start as soon as the SD card was inserted.
In recent times, many customers with very large sequences who have been running into memory-related issues have been using a third-party tool known as the "4GB Patch" to modify the Sequence Editor and Show Player executable files. The effect of this is that Windows will allow the patched programs to use more memory than it would allow for the unpatched programs. Whenever a customer using the 4GB Patch upgraded to a new version of Light-O-Rama, they would have to remember to use the 4GB Patch on the new versions of the two executable files, or else they would start running into memory-related issues again.
Now, though, the Light-O-Rama installer distributes the Sequence Editor and Show Player executable files as if they had been patched using the 4GB Patch. Users therefore should no longer need to run the 4GB Patch on these programs.
Just in case something unexpected occurs because of this, the installer also distributes unpatched versions of the executables. The patched versions are what are used by default, without the user needing to take any action. If for whatever reason you want to use the unpatched versions, though, they can be found in the Light-O-Rama program files directory (which is typically, but not always, either C:\Program Files\Light-O-Rama or C:\Program Files (x86)\Light-O-Rama). They are called LORSequenceEditor-Unpatched.exe and LORMonitor-Unpatched.exe. To start using them, shut down your running programs, then rename the default patched versions out of the way (for example, rename LORSequenceEditor.exe to LORSequenceEditor-4GBPatched.exe), and then copy the unpatched versions into their place (for example, copy LORSequenceEditor-Unpatched.exe to LORSequenceEditor.exe).
The LOR PixCon16 is the first E1.31 and newest controller offering from Light-O-Rama. The board can control up to 16 170-pixel strings using various different chipsets, as well as be a bridge for 4 separate DMX universes all running on Ethernet.
The order of menu items in the LOR Control Panel's right-click popup menu has been changed so as to hopefully more clearly group sets of similar items. Also, the Control Panel would say things like "Light-O-Rama is Disabled" to mean that scheduled play of shows was not currently enabled; this has been changed to the hopefully less confusing "Scheduled Play is Off".
The Sequence Editor now allows MP4 files to be used as the media files for musical sequences. Please note that not all such files will work on all computers; for example, a particular MP4 (or some other type of media file) may be encrypted with DRM or may require a codec or filter that is not present on the computer.
•When using the Arch Wizard, changing from Arch to Fan or vice-versa the minimum number of segments was not being set correctly. This could lead to errors in the wizard which were caught and dealt with, but which should not have occurred.
•When using the Tree Wizard, the Pixels Per Segment spin control did not accelerate the longer the user pressed the up/down buttons.
•The Matrix Wizard was generating errors whenever the form was re-sized. This lead to errors in the wizard which were caught and dealt with, but which should not have occurred.
•Deleting a Prop did not always remove the Prop's definition from the program. In essence, a prop with no fixtures was saved/loaded each time. Any prop that is deleted now also deletes the prop's definition.
•If a sequence file could not be loaded due to an invalid end centisecond for one of its effect events, the Sequence Editor would issue an error message mistakenly quoting the event's start centisecond instead of its end centisecond.
•Some memory leaks (in various programs) associated with interacting with the Windows shell have been fixed. Most of these seem unlikely to have actually caused memory to leak in practice, but in theory they might have. One would definitely cause memory to leak in practice, but a relatively small amount.
•The Simple Show Builder and the MP3 tab of the Hardware Utility would incorrectly allow for more than 99 sequences to be added to a show. Hardware Directors can only handle a maximum of 99 sequences in a single show.
•The Network Preferences program was not correctly deleting old versions of the network configuration from the registry. This was due to a recent change in how Microsoft allows access to the registry.
•The Network Preferences program could incorrectly flag two ports as being in conflict even if they were not. If the ports were in conflict, there was also a chance that the incorrect ports/adapters were reported.
•The Network Preferences program could experience unintended behavior if the column header in any of the list displays were clicked.