Jump to content
Light-O-Rama Forums

DevMike

Administrators
  • Content count

    3,601
  • Joined

  • Last visited

  • Days Won

    63

Everything posted by DevMike

  1. http://forums.lightorama.com/topic/46168-s5-helpmanual/?tab=comments#comment-426645
  2. DevMike

    2018 Expo FOOD!

    So 2017's Nashville's highlight for food (at least for me) was Nashville Hot (chicken). Delicious! If ever back in town I will definitely hit that up again. It was so good in fact that I skipped a trip to White Castle just so I could have it twice! So it's been 3 years since we've been to DFW. The two places I will definitely be going to are: In-N-Out Burger (Double Double, fries animal style). My plane get's in at 8:30PM, and what better way to break in a rental car than with takeout! Babe's Chicken Dinner House Both were stand outs from the 2015 show. I really liked Babe's - not so much because I can't get good fried chicken here in FL, but because it was a fun time. If you can, get a group together and go. In fact of all the Expo's I've gone to, Babe's is about the only place that stood out enough that I want to go back! If you re from the DFW area, please let us know some of the great places to eat YOU know of. They don't have to be sit down, or even a restaurant (Tacos at a gas station? WHY NOT!). Any regional specialties that expo people just can't miss?
  3. No problem, I'll set the correct bit. FYI: This has been around since the Net Prefs initial release: S3.5.0 - July 12, 2012 <Programmer Rant> I really don't understand why the Microsoft Flex Grid (which is what you are actually looking at when you see almost all lists in S4, and most in S5) has an 'Auto' justification. It is NOT common for a column to display BOTH numeric and alpha numeric at the same time. When it does, 99 out of 100 times the numeric data should be displayed as if it were alpha data. Sure, Auto makes it easy at design time (read: allows for a lazy programmer). We test, it looks OK and get's released. 6 years later someone uses a number and we look foolish. Had the control forced you (me, the programmer) to pick an alignment, this would not have happened. Sometimes EASY is not correct. </Programmer Rant>
  4. Release Notes For ShowTime 5 Beta Version 5.0.20 18 June 2018 The beta testing period will end on June 30, 2018 *** UPDATES TO THE SEQUENCER *** VERY IMPORTANT The format of the preview file is changing slightly in 5.0.20. Your preview file will be upgraded automatically to the new format. However, once upgraded, 5.0.20 preview files cannot be used with prior versions. If you think you might downgrade, make a backup copy of the files in the "\Light-O-Rama\CommonData" folder before installing 5.0.20. If you later downgrade, restore the backup copies. Changes To Preview Management: In Prop Defition, removed "Advanced" from the list of predefined shapes. Users should go to the "Advanced" tab when defining an advanced shape. Reported by Light-O-Rama. Fixed: When creating a 360 up and over tree in "channel per color" mode, if the total number of colors is even, then half the colors go on the "up" side of the string and the other half go on the "over" side. Reported by user bdwillie. http://forums.lightorama.com/topic/46130-what-am-i-doing-wrong-360-up-and-over-tree-in-preview/ Changed Preview Management from a menu item to a dockable window. By default it will be listed in the far right margin and fly out when click on. Reported by Light-O-Rama. Combined Preview Design, Preview Info, and Channel Summary into a single window, with tabs for each set of information. Icons on the "Channel Conflicts" and "Other Warnings" tabs will immediately indicate whether there are issues with the preview. Reported by Light-O-Rama. Added the ability to import an SE animation from the Preview Management window. Also fixed the animation import to deal with RGB channels correctly. Reported by Light-O-Rama. Importing a dumb RGB fixture from Visualizer caused an error when the red, green, and blue channels do not all share the same unit id (or DMX universe). The user now gets a warning and will need to fix the Prop Definition in S5, but the import will complete. Reported by user Trickyd. http://forums.lightorama.com/topic/46145-problem-importing-visualizer-in-s5/ In Preview Design, the Item Layout screen for props was enhanced to clarify what a "node" is and what the information is on rows 1 and 2 for each node. Reported by Light-O-Rama. Added the ability to import and export previews. Requested by user k6ccc. http://forums.lightorama.com/topic/46194-preview-management/ In Preview Design, moved preferences menu (Format > Preferences) to its own menu under a gear icon. Preferences used for creating new props have been moved from Preview Management to Preview Design (gear icon > New prop defaults). Reported by Light-O-Rama. Added new predefined shape: Tree 360 spiral. Requested by user jamills706 and others. http://forums.lightorama.com/topic/45906-spiral-rgb-mini-tree-prop-for-s5/ Fixed code that should have been detecting circular definitions in preview groups. Updated Preview Design to ensure circular definitions are reported and fixable. Reported by user Septon. http://forums.lightorama.com/topic/46239-5018-crash-after-adding-groups-consistantly/ The group edit screen now displays the buffer size of the group as changes are being made, giving the user a clue about the effects of their changes. Reported by Light-O-Rama. In Prop Definition, the Custom and Advanced tabs have a new menu that enables you to: select all cells, add a numeric offset to the selected cells, flip selected cells vertically, flip selected cells horizontally, or transpose the grid. Reported by Light-O-Rama. The Preview Design canvas now has a right-click menu. Currently, the menu items are the same as the Format menu. Reported by Light-O-Rama. The Preview Design, the Item menu has a new "Copy Prop to Advanced Shape" option. This will copy an existing pixel-based prop to an Advanced shape, which can then be customized beyond what can be done with a pre-defined prop shape. Reported by Light-O-Rama. Below the ImportExport folder, there is a new Light-O-Rama folder where you can find predefined props for SuperStar sequences (e.g. CCR trees), as well as the 16x25 pixel tree sold in the LOR Store. Reported by Light-O-Rama. In Prop Definition, the Help button on the Custom tab displays a different message depending on whether RGB pixels are selected or not. Reported by Light-O-Rama. The String Summary tab of Preview Design can now be filtered by device type. Also, rows sort in a more useful order when clicking on any column heading. Reported by Light-O-Rama. Changed the default traditional string type to "Multicolor string 1ch" for new props so that channels will calculate without any colors being selected. Reported by Light-O-Rama. Fixed crash in Prop Definition that occurred when editing the channel grid, then changing parameters for the shape, then going back to the channel grid. It could also occur when changing channels using the Channel Summary page. From bug report DD06. http://forums.lightorama.com/topic/46288-dd06-channel-summary-editing-crashes-editor/ For pixel-based props, you can now create a set of default motion effect rows that will be stored with the preview, and applied whenever that preview is used to create a new sequence. This is most useful when you want to always divide a pixel-based prop into subsections. This eliminates the need to export the grid configuration from one sequence and import it into another just to copy the motion effect row definitions. To define the defaults, click the new "Motion Effect Rows" button on the RGB tab of the Prop Definition screen. You can also define them for groups; use the "Motion Effect Rows" button on the group definition screen. Reported by Light-O-Rama. New props using Dumb RGB strings can specify the channel information for each color. This allows for creation of RGB props where the channel numbers are not consecutive. Reported by Light-O-Rama. New buttons in Preview Design allow you to incrementally increase and decrease the zoom level. Reported by Light-O-Rama. In Preview Design, "Create Prop" and "Create Group" buttons have been combined into a single "Add Item" button. Reported by Light-O-Rama. In Preview Design, you can add an LOR device, similar to the way you could "insert device" in the S4 Sequence Editor. Just click the "Add Item" button, then select "Add LOR Device". Reported by Light-O-Rama. In Preview Design, you can now download prop definitions from online sources like Boscoyo Studios and SuperStar Lights. Just click the "Add Item" button, then select an online source. Reported by Light-O-Rama. In Preview Design, improved the handling of props with shape of "hidden" and groups that contain such shapes. Reported by Light-O-Rama. After importing a prop file into a preview, a new window displays all of the props that were imported along with their starting channel numbers, and gives the user a chance to make changes. Reported by Light-O-Rama. A Device Type field was added to the New Prop Defaults window (click the gear icon, then select New Prop Defaults from the menu). The specified device type (LOR, DMX, or Undetermined) will be used when creating new props. Reported by Light-O-Rama. Strings can now be created and drawn interactively instead of having to go into the Prop Definition window first. This approach creates a lines-connected shape. There are 2 ways to get at it: 1) click the Add Item button and select "Draw new string" from the pop-up, or 2) right-click in the preview area and select "Draw new string". Stop drawing by either: 1) double-clicking, or 2) type Esc, Space, or Enter key (typing any of these keys before any points are created will terminate string drawing mode). While drawing, you can use the Backspace key to delete the last point. Reported by Light-O-Rama. New vertices/anchor points can be added to Lines-connected, Lines-closed, and bulb shapes without going into Prop Definition. Simply select a prop, then right-click on a red vertex/anchor point and choose insert or delete from the pop-up menu. Reported by Light-O-Rama. Undo/redo now works when you change a prop's bulb size. Reported by Light-O-Rama. Changes To Sequencing: When upgrading sequences, users now have a choice in how beat channels are identified. Reported by Light-O-Rama. Improvements when upgrading S4 previews: removed extraneous warning message, fixed problem that caused some Pixel Editor props not to be upgraded to S5. Reported by user NJ Malenke and others. The sequence upgrade process can now upgrade a sequence where no channels have circuit numbers set. In this situation, it is best for every channel to have a unique name. Reported by Light-O-Rama. The sequence upgrade process now does a better job of auto-generating a preview from a sequence with RGB channels. Reported by Light-O-Rama. When upgrading a sequence, the default grid view now gets set (usually "Track 1"). Reported by Light-O-Rama. Fixed bug in the skew function: crash occurred when user opted to skew timing marks but not effects. Reported by user PCRail. http://forums.lightorama.com/topic/46106-skew-timing-marks/ Using the "skew" function to move timing marks now runs much faster. Reported by Light-O-Rama. Added a built-in grid view called "Show All Items". This will make the Sequencer easier for users with smaller displays who did not use the S4 track feature. Reported by Light-O-Rama. Upgraded docking features so they work more smoothly. Users can now double-click a window heading to undock or re-dock. Motion effect selection window can auto-hide or can be pinned to stay open. Reported by Light-O-Rama. Users can now dock sequence windows to different positions within the main window, allowing sequences to be viewed side-by-side. Reported by users arnolddeleon and dougd. http://forums.lightorama.com/topic/45485-two-sequences-open-and-visible-at-the-same-time/ 3 themes (colors used in the Sequencer user interface) are now available: light, dark, and blue. Changeable from Tools > Preferences > Theme. Some of the icons on the toolbar have had their colors adjusted so they are visible under all 3 themes. Reported by Light-O-Rama. In order to accommodate theming, the different text colors on the list of props on the left side of the grid for archive channels, beat channels, etc has been replaced by symbols for each row type. A triangle for motion effect rows, an "@" sign for archived props, 3 bars for an RGB channel, a "ยง" mark for subsequences, an 8th note for beat channels, and a circle for normal channels. Reported by Light-O-Rama. In the Sequencer, right click on a motion effect row and select Motion Effect Properties. In previous releases, the prop would show in the large black area in the lower right of the dialog box when you select "Apply effects in the row to a rectangular subset of pixels in the prop or group". This was an aid in selecting the area you wanted. In v5.0.18, the prop does not show at all. From bug report JMW-S5-009. http://forums.lightorama.com/topic/46129-jmw-s5-009-no-prop-display-in-motion-effect-row-properties-dialog/ During playback, the area on the left side of the grid is now used to display channel intensity - for regular channels and RGB channels. This is a close substitute for changing the color of the channel buttons during playback in S4. Reported by Light-O-Rama. Requested by multiple users. The movie effect can now use compressed AVI files as well as WMV files. Files with a frame rate of 20 frames per second still work best, but any frame rate will be displayed at the correct speed. Reported by Light-O-Rama. The Effect Generator now displays the playback time of the effect as well as the effect duration. Reported by Light-O-Rama. Added new menu item: Sequence > View Sequence Folder, which opens a Windows Explorer window for the folder containing the sequence. Reported by Light-O-Rama. "Insert SuperStar Effect" now handles props with traditional strings correctly -- as long as there is one channel per string (no bundles). However, it will not work as expected when the prop's string type is set to "channel per color" and there are multiple colors selected in Prop Definition. Therefore, props with bundled strings, like RGBW, will need to be defined as separate props for each color if the user plans to sequence them with SuperStar. From bug report JRW16. http://forums.lightorama.com/topic/46224-jrw16-prop-groups-with-single-pixel-elements-not-displaying-after-creating-in-superstar/ On the Sequence menu, "Add Loop Level", "Add Subsequence", and "Add RGB Aggregate" have been moved to an "Add New" submenu. This submenu has also been added to the grid view menu, so these actions can be initiated from either place. Reported by Light-O-Rama. The Sequence > Grid Configuration (import/export) has been copied to the grid view menu, as several users had trouble locating this function. Reported by Light-O-Rama. Resolved issue with paste performance that was introduced in the 5.0.16 release. From bug report DD05. http://forums.lightorama.com/topic/46089-dd05-copy-and-paste/ When inserting a SuperStar effect, the user's SuperStar license is now checked for the number of allowed channels, instead of pixels. For example, a user with a 2 CCR license was checked for 100 pixels; now it is checked for 300 channels. Also, SuperStar does not support elements that are more than 360 nodes wide, or 360 nodes high. This is now checked before the Sequencer starts the process of inserting a SuperStar effect. Reported by Light-O-Rama. When right-clicking on a motion effect row name on the left side of the grid, the "Motion Effect Row Properties" and "Add Motion Effect Rows" menu items have been combined into "Add/Modify Motion Effect Rows". Reported by Light-O-Rama. If a group is deleted from a preview, then a sequence which uses that preview is opened; any motion effect rows for that group will now be archived. Previously, they were deleted/lost. Reported by Light-O-Rama. Removed Open Sequence and Close Sequence icons from the toolbar. Closing the sequence can now be accomplished by clicking the "X" on the sequence tab. Reported by Light-O-Rama. A progress dialog is now displayed when saving a sequence file. Reported by Light-O-Rama. Added "Convert media to WAV file" to Sequence menu. Reported by Light-O-Rama. The Playback window now has a right-click menu which can be used to start and stop sequence playback. Reported by Light-O-Rama. When right-clicking on the grid, all of the items under the "Existing Effects (foreground)" sub-menu now apply to RGB channels as well as regular channels. In addition, the "Scale Intensity..." function has been added (which was in S4, but missing from S5). From bug report JRW17. http://forums.lightorama.com/topic/46254-jrw17-increase-decrease-intensity-does-not-effect-rgb/ Fixed bug when adding color fades to the grid: the "A" shortcut key and the "N" shortcut key did not produce the same colors on RGB channels when the maximum intensity was less than 100. Reported by Light-O-Rama. When entering a numeric value in a pop-up window, highlight the number automatically so that all the user needs to do is type the new value and hit enter. This applies to Subdivide Timings, Insert Multiple TImings, Beat Channel Row Count, Scale Intensity, and Offset Intensity. Requested by Drew Hickman. After a paste operation, if the user subsequently does an up or down arrow key, the cell at the beginning is now selected. Previously the cell at the end was selected. Requested by Drew Hickman. Increased the maximum number of motion effect rows per prop to 32 (from 20). Requested by Drew Hickman. Added "solid" mode to twinkle effect (no twinkling). Random pixels just stay on for the duration of the effect. Looks especially nice when the density changes over the course of the effect. Requested by Drew Hickman. Disabled the Sequence menu while calculating. Accessing File References dialog while background calculations were in process could cause an error. From bug report DF006. http://forums.lightorama.com/topic/46425-df006-can-cause-intensity-error-while-loading-sequence/ Bug fix: If the Sequencer reports an inadequate OpenGL version, the message could be displayed behind the startup splash screen. Reported by Light-O-Rama. *** UPDATES TO SUPERSTAR *** Added support for 100 pixel LOR strings in the Configuration dialog box Fixed a bug where inserting a SuperStar effect from the Sequencer on Dumb RGB strings was not working Bug fix: SuperStar effects that were copy/pasted within the Sequencer could not be edited by double-clicking the pasted effect and opening SuperStar. *** OPEN ISSUES *** Clipboard files from S4 (.LCB) can now be used in S5. They import correctly into single color channels, but not into RGB channels. In the Sequencer, subsequences will play back to lights only on LOR enhanced and DMX/E1.31 networks. They will not play to un-enhanced LOR networks (playback works fine on all networks in the Show Player). S5 Sequencer Help file needs a major update. Motion effect rows get duplicated during channel config import/export http://forums.lightorama.com/topic/43916-multiple-copies-of-same-prop-after-migration/ Show vertical cursor bar in the timeline area for animation sequences http://forums.lightorama.com/topic/43944-feature-request-waveform-vertical-bar-on-animation-sequence/ Support CCR macro channels during preview playback (on screen) http://forums.lightorama.com/topic/43877-s5-not-supporting-ccr-macros/ Add a "Cue mode" in the Sequencer for use in live performances. http://forums.lightorama.com/topic/45537-running-a-show-to-live-music/ Display numerical angle when rotating props in preview design. http://forums.lightorama.com/topic/45596-enhancement-request-angle-indicator/ Pixel Editor previews imported into S5 require manual adjustments to props that have been rotated. Props with no rotation in PE import correctly. Props with rotation in PE are in the correct location but may have the wrong rotation and scale). http://forums.lightorama.com/topic/45546-s4-pixel-editor-show-in-s5/ *** MOTION EFFECT ENHANCEMENT REQUESTS *** Would like an option in the spiral effect where you could do a fill like a true spiral tree would do. Requested by SPaschall. Add ability to set text size on individual letters in text effect. Requested in Pixel Editor forum. Add movement options to the Picture effect that are essentially the second half of the Peek-a-boo movement. So exit_left, exit_right, exit_top, and exit_bottom would be the new options. Requested by Little_b. http://forums.lightorama.com/index.php?/topic/43699-feature-request-using-picture-effect/
  5. Release Notes For ShowTime 5 Beta Version 5.0.2 28 July 2017 Updates To The Sequencer Enhancement: move the "Insert SuperStar Effect" right-click menu item up a level. Requested by Light-O-Rama. In version 5.0.2 the "Insert SuperStar Effect" menu item appears twice due to an error. The second entry is the one you should use to invoke SuperStar. Enhancement: when a sequence is open and the user selects Tools > Effect Generator from the main menu, the Effect Generator is now opened in the context of the sequence. Requested by Light-O-Rama. Enhancement: improved display of the favorites tree in the Effect Generator so that highlighted nodes are much more visible. Requested by Light-O-Rama. Enhancement: add an option to disable the message displayed when creating playback files: "The sequence uses 1 LOR network, and according to Network Preferences Regular is enhanced". Requested by user brichi. Enhancement: add a Christmas tree shape to the Simple Shapes effect. Requested by user stevehoyt. Enhancement: install the additional dimming curves that are available in the Pixel Editor forum. Requested by Light-O-Rama. Fixed: a white twinkle effect on RGB pixels or dumb RGB lights looked different when played on a regular LOR network versus an Enhanced LOR (ELOR) network or DMX. Reported by users Bry and brichi. http://forums.lightorama.com/index.php?/topic/43632-s5-twinkle-only-on-white/ http://forums.lightorama.com/index.php?/topic/43605-random-twinkle-effect/ Fixed: there was a delay the first time the media was played for a sequence (would happen with media). Reported by Light-O-Rama. Fixed: if you try to start the sequence with the spacebar sometimes it will "stall" and you will have to hit the stop button and hit it again to get it to play. Only applied to MP3 files. From bug report TC02. http://forums.lightorama.com/index.php?/topic/43590-tc02-starting-with-spacebar-stalls/ Fixed: opening an LMS or LAS sequence directly from Windows Explorer instead of opening the sequence from the S5 Sequencer will leave the Light-O-Rama splash screen on the display, blocking the box underneath. You have to hit alt tab and click on the x to clear it out. From bug report TC01. http://forums.lightorama.com/index.php?/topic/43562-tc01-lor-banner-wont-go-away/ http://forums.lightorama.com/index.php?/topic/43568-s5-sequencer-stuck-at-initializing-effect-generator/ Fixed: when setting your user folder, the user folder cannot be the root folder of a drive, e.g. "L:\". From bug report JRW12. http://forums.lightorama.com/index.php?/topic/43541-jrw12-unable-to-assign-lor-default-drive-to-network-drive/ Fixed: "Add Grid View" should not prompt for props/groups and instead save the current grid view. Renamed "Add Grid View" to "Save Current View As". Removed "Copy View" as it did almost the same thing. Reported by Light-O-Rama. Fixed: the "Mix Overlay" mode in the Effect Generator changed from the Pixel Editor to the S5 Sequencer, which caused some Pixel Editor sequences to import incorrectly. "Mix Overlay" in S5 has been changed back to the original Pixel Editor logic. The new mixer function in S5 has been renamed "Mix Alpha Blend" which takes into account alpha blending. Reported by user Bry and others. If you have created new effects in S5 that use "Mix Overlay" mode, they should be changed to use the new "Mix Alpha Blend" mode. From bug report JMW-S5-001. http://forums.lightorama.com/index.php?/topic/43600-jmw-s5-001-curtain-effect-not-working-properly/ http://forums.lightorama.com/index.php?/topic/43569-effect-mixer-issues-with-imported-pe-props/ Fixed: many Visualizer import bugs -- improved handling of DMX fixtures, pixel string orientation, detection of strobes and multicolor strings, bulb sizing, and bulb color. Reported by user K6CCC. http://forums.lightorama.com/index.php?/topic/43587-jrw13-using-preview-that-was-created-by-importing-visualization-error/ Fixed: buttons on Preview Management screen were not sized correctly on Windows XP. Reported by user K6CCC. Fixed: "Delete Grid View" function was not working. Reported by user stevehoyt. http://forums.lightorama.com/index.php?/topic/43618-v5-delete-view-not-working/ Fixed: an LMS file created by SuperStar does not import correctly into the S5 Sequencer, moving many channels to the Archive area. Reported by users K6CCC & RocketCitySanta. http://forums.lightorama.com/index.php?/topic/43645-opening-superstar-generated-lms-in-s5-sequencer-problem/ Fixed: crash when reading motion effect rows from archive props. Reported by Light-O-Rama. Fixed: appending props to current grid view didn't flag the sequence as having unsaved changes. Reported by Light-O-Rama. Fixed: crash when reading some custom preview props with no data. Reported by Light-O-Rama. Fixed: upgrading a sequence with a fixed grid spacing of less than 0.05 seconds got converted to a grid of 0.05. Fixed timing grids in upgraded sequences will now retain their spacing down to 0.02 seconds. However, the minimum spacing for new timing grids created within S5 will remain at 0.05 seconds. Reported by user dgtlpro. http://forums.lightorama.com/index.php?/topic/43625-s5-timing-grids/ Fixed: the drop-down list of props in the Effect Generator wasn't getting populated sometimes when the Effect Generator was opened. Reported by user stevehoyt. http://forums.lightorama.com/index.php?/topic/43622-motion-effect-generator-has-no-choices-in-far-right-window/ Fixed: after creating a new group in preview design, the group wasn't selectable. Only affected new groups with arrangement=none. Reported by Light-O-Rama. Fixed: unable to open 2 sequences with the same file name that exist in different directories. Reported by user RocketCitySanta. http://forums.lightorama.com/index.php?/topic/43641-multi-copies-of-same-sequence/ Fixed: when upgrading a Sequence that includes a Pixel Editor file, the Pixel Editor props did not appear in the grid. Pixel Editor props are now appended to the first grid view. Reported by user JamesWright. http://forums.lightorama.com/index.php?/topic/43546-500-how-do-you-edit-the-rgb-lights/ Fixed: users with an Advanced license can't see the Sequencer's motion effects window or use an enhanced LOR network in beta. Reported by users attending Expo 2017. Fixed: bug when pasting multiple rows with condensed mode off. From bug report SCC04. http://forums.lightorama.com/index.php?/topic/43648-scc04-copy-paste-losing-objects/ Fixed: in the Beat Wizard, after applying a beat pattern to a beat channel, clicking undo does not clear the beat marks. The same issue was also fixed in the VU Wizard and the Tapper Wizard. From bug report SCC03. http://forums.lightorama.com/index.php?/topic/43647-scc03-beat-wizard-undo-not-clearing-beat-channel/ Removed "File References" item from the toolbar's preview menu - as the preview menu is for actions that apply to the preview, and this item applied to the sequence. The function is still available from the Sequence menu. Reported by Light-O-Rama. Removed "Export to SuperStar" link in Preview Management screen. This function is not fully implemented yet. Reported by Light-O-Rama. Updates To SuperStar Fixed a bug in the Load/Save Clipboard dialog box. The effect counts were not being defined if you have navigated to a folder. Fixed a bug where the export of a sequence would only export the effects from where the time ruler is currently at. Fixed it so it always exports all the effects in the sequence. When launched from the S5 Sequencer the time ruler would always be at time 0:00. Fixed it so it is within 1 second of the start time of the request. When launched from the S5 Sequencer SuperStar would sometimes display a message box saying "Enter a value between -64 and 64" When launched from the S5 Sequencer as a musical file, SuperStar would sometimes fail to launch, and if it did launch the audio file would fail to load. Fixes That Will Be In The Next Release (version 5.0.4) Removed duplicate "Insert SuperStar Effect" menu item Sequence > Channel Configuration > Import now works when the import updates the currently selected view. Open Issues Add support for multiple clipboards and ability to import/export clipboard file (same functionality as S4) Add "Foreground Effects" Fade up and Fade Down (from S4) http://forums.lightorama.com/index.php?/topic/43643-foreground-effects/ Add support for props sharing the same channels Add support for SuperStar globe topper Make it easier to create a CCR Tree Add to grid's context menu options to create motion effect rows with subregions automatically based on columns or rows Add support for S4's Color Fade tool and a history of color fades used No way to chase across 8 pixel arches http://forums.lightorama.com/index.php?/topic/43556-no-way-to-chase-across-8-arches/ Improve SuperStar integration S5 LORVerifier needs to be updated. S5 Sequencer Help file needs a major update. Restore toggle tool functionality from S4 http://forums.lightorama.com/index.php?/topic/43620-toggle-button/ Improve performance of the Motion Effect Generator http://forums.lightorama.com/index.php?/topic/43570-s5beta-1-fx-generator-locking-up-a-lot/ Motion Effect Enhancement Requests Would like an option in the spiral effect where you could do a fill like a true spiral tree would do. Requested by SPaschall. Add ability to set text size on individual letters in text effect. Requested in Pixel Editor forum. Waiting For Feedback Issues with subsequences http://forums.lightorama.com/index.php?/topic/43557-opening-subsequence/
  6. Light O Rama is proud to announce the next release of Showtime S5 software 5.0.20 Beta Important Information about Beta Releases Please note that this is a beta release, not an official production release. For important information about beta releases, including what it means, who should participate, and how to participate, please see this post. How To Check If Your License Covers This Version Please note that your license may or may not cover this version. Anyone with an active S4 license can download and run the S5 Beta. You may be warned that the software will expire in June, however you can re-register and that will go away. For a list of changes in this version from the previous version, please check the release notes in the Open Beta Forums. How To Get the Latest Version The new version can be downloaded from: http://www.lightorama.com/downloads/5.0.20/LOR-5.0.20.exe Or http://www1.lightorama.com/downloads/5.0.20/LOR-5.0.20.exe Thank You! As always, thanks to all of those who choose to help us out as beta testers. Before deciding to download and install the beta, please take some time to read this post for some important information: What is meant by "beta" and "open beta" An entirely new "Pro" license level (above Advanced) How licensing will be handled during the beta period Information about the help files How to download the installer can be found at the end of this post, but please take the time to read this information before deciding to download and install itWhat is beta software? Beta software is code that has been tested by the programmers who have written it and has received some internal testing by other members of the company. The software is stable enough to be tested by a rather large group, but it is not software that is ready for general released.Why an open beta? We have received many requests from people asking to join the beta testing group. In the past, we have kept that group closed, and have always had a backlog of people wanting to take part. To make management of the beta group simpler, we are going to open the beta to everyone.Who should use beta software? Beta testing is not for everyone. By nature, beta software will have more problems in it than generally released software. Testing beta software allows a user to find out if an enhancement does what they need, and if not, provide suggestions on how to fix or improve the software. Do NOT use the beta software if you are not ready to uncover bugs/problems with it. People who volunteer to test beta software must report problems, but please do not complain that there are problems - problems are expected! When testing beta software, please make sure to save often so that if something crashes, you'll minimize your loss.How can I report issues, make suggestions, or ask questions about the beta? There is a set of forums for the open beta, where you can report bugs or give other feedback, here. Please do not open help desk tickets for S5 issues, instead post a message in one of those 2 forums.The new "Pro" license levelAt this time, the differences between Advanced and Pro are that the Pro license level enables the use of Motion Effects. These new features are intended to improve the experience of using very large numbers of circuits (though they can be used with small numbers of circuits too).During the beta period, certain users' licenses will act as if they were Pro level licenses. Please see the next section of this post, "Does my license cover this release?", for details.Does my license cover this release?Depending upon when you purchased, renewed, or upgraded your license, it may or may not cover version 5.0. However, during the beta period (which will last through June of 2018), some licenses that do not really cover version 5.0 will act as if they do cover it: If your license is valid for version 4 or higher, then during the beta period it will act as if it covers version 5.0.Also, during the beta period, Advanced licenses will act as if they are Pro licenses.In this way, even if you don't have a license that really covers the new version or the new Pro license level, you can try them out during the beta period without committing to purchase them.After the beta period is over, if your license does not really cover version 5.0, it will stop acting as if it does. Similarly, if you have an Advanced license, it will stop letting you use Pro level features. At that time, you could either: Purchase a license upgrade, if you want to continue using 5.0 and continue using Pro features; or: Purchase a license renewal, if you want to continue using 5.0 but do not wish to continue using Pro features; or: Uninstall version 5.0 and reinstall version 4.3.26 (or an earlier version). Please note that if at the end of the beta period you decide not to upgrade or renew, not everything that you created during the beta period will necessarily be usable afterwards. Specifically: Any "intensity files" that you create during the beta period (such as by the Pixel Editor or SuperStar) will not be usable afterwards unless you upgrade. Any motion effects/Sequencer files created in S5 can not be used in the PIxel Editor of S4. Also, please be warned that although the above list is intended to be complete, it is possible that there are other incompatibilities that were overlooked here and not listed. It is always wise in any case to back up any of your data files, even those that you have no reason to believe will be affected by the upgrade (such as your sequence files).You can check whether or not your license covers version 5.0 by using the Software License Retrieval page. Please note that if your license covers 4.0 (or higher) but not 5.0, the Software License Retrieval page will not mention to you the fact that your license will temporarily work for 5.0 during the beta period.Special information about the help filesIn this initial beta release, the help files are not completely updated. We are working on updating our help files.What's new in this versionS5 was announced at the 2017 Christmas Expo. We have several presentation files available that are full of information on what is new in S5. "PowerPoint Presentations / ShowTime 5". http://www1.lightorama.com/tutorials/How do I get this new version? The Important Announcements forum will have the latest beta release. Look for the most recent post (usually located at the top of the forum) titled "Light O Rama version 5.0.XX released as an open beta"Thanks for your help!
  7. Don't worry if your next version of LOR S4/S5 comes with a warning from your security suite about accessing the internet. S4 has started, and S5 is expanding, downloading files from the internet to update functionality. If you do get a warning, please ALLOW the program through your firewall. Before we explain why we are doing this, let us say the following: NO! YOU DO NOT NEED TO BE ONLINE TO RUN THE SOFTWARE! EVERYTHING WILL WORK LIKE IT ALWAYS HAS! If however you are online, the software will now download several files to keep it self UP TO DATE. We started doing this with S5, and now we are moving some of that functionality down into S4 as well. We plan to continue to expand this in the future. For this first baby step in S4, we'll be downloading 2 files for the hardware utility - the LOR Device file (which tells the Hardware utility how to deal with controllers), and another file to support some up-and-coming new Pixie firmware (not yet released). In order to minimize any security issues, these files are going to be downloaded into your Light-O-Rama data folder. If you did not change that when you installed that will be My Documents\Light-O-Rama\LORInternal. Most of the files will be plain text human readable. In fact, most will be XML based. While you can see them, you should NOT modify them or delete them. Really. Don't touch anything in there. To support those who work offline, the most current version available at the time of release will also be distributed with the software. So if you have a computer that is not normally on-line it will still work with the software -- however you may just have outdated files that need to be updated manually. This is exactly how the software works today - there is no way to update it once it is installed. So again.... If you get a warning about LOR programs going out onto the internet, please let them. If you are off-line, don't worry things will still work.
  8. Today we released version 4.3.30 of the Light-O-Rama Software Suite. This is an official production release, not a beta release. This release fixes an issue with SuperStar. How to check if your license covers this version To check whether or not your license covers this version, please go to the license retrieval page, and enter your email address (the one you purchased your license with). An email should then be sent to you with information about your license. The "Summary" section of the email will tell you whether or not your license covers the latest version. If the email says... Your license covers the latest version, 4.3.*. ... then your license already covers this version. You can use it without making any additional purchase. Please note, though, that your computer may not yet understand that your license covers this version, so when you install, it might tell you that you are running in Demo mode. In this case, simply reactivate your license (for example, via "Upgrade Light-O-Rama" on the Sequence Editor's "Help" menu), and your computer will then learn that your license is valid for this version. On the other hand, if the email instead says... Your license does not cover the latest version, 4.3.*. ... then your license does not cover this version. In that case, you have several options: Upgrading or Renewing Your License (1) You can continue using whatever version your license does cover (for example, perhaps your license covers version 4.1). (2) If you want to take this opportunity to increase your license level to take advantage of additional features, you can purchase a license level upgrade. This counts as a license renewal too - that is, your license will now work with this new version (and some future versions too). So, if you do this, there is no reason to also purchase a license renewal. (3) If you already own a Light-O-Rama license, but you do not currently own Light-O-Rama SuperStar, or if you want to upgrade SuperStar to a higher number of CCRs/channels, you could purchase or upgrade SuperStar. This also counts as a license renewal for the rest of the Light-O-Rama software suite, so if you do this, there is no reason to also purchase a license renewal. Please note that you must already own a license for the rest of the Light-O-Rama software suite in order to take this option. (4) If you do not want to purchase a license level upgrade or Light-O-Rama SuperStar, you can purchase a license renewal. Your license will now work with the new version (and some future versions too), at the same license level as it currently does. For example, if you have an Advanced license, it will remain an Advanced license, but it will now cover the new version of software. What's New in Version 4.3.30 This release is a single bug fix for Superstar. 4.3.28 added new functionality for new Pixie Hardware, Dynamic update of certain files, and addresses several issues in the software: Update Pixel Editor to use same support packages as S5 Pixel Editor Now Shows an error message if intensity data failed to save The Configuration of Cosmic Color Devices and Pixies has been split Support for 'Dynamic Files' Support for new upcoming LOR Props Support for new upcoming Pixie Firmware Bug Fixes How To Get the Latest Version You can download the new version from the software download page. If that page lists a different version number as the lastest version, please click your browser's refresh button. Thank You!
  9. DevMike

    LOR 4.3.28 crashes after install

    Of course, with all that said, a 4.3.30 is already being built by me. Apparently there is a bug in SuperStar that needs to be addressed. Keep on eye out.
  10. DevMike

    LOR 4.3.28 crashes after install

    Does sound like there are 2 things going on here. 1 - is definitely that MS update. I had several of them come through in the last few days including on our build machine and the installer test machine. I like W10 a lot more than I ever liked W8, but this "update when WE say so" (MS) is starting to give us heartburn. 2 - The other is most likely the new code for Dynamic files. AV programs can be jerks about false positives, which was one of the reasons why we have spent a few thousand dollars on digital signing certificates for our programs (find one of our EXE's and then right click on it. Check the Digital Signature tab, and you'll see our certificate). Having a certificate, issued by a trusted authority which ours is, is supposed to tell the AV program to back off a little bit. They don't. I did test the installer (we test ALL installers) and didn't have any issues - but I did have all the updates installed. I think Windows Firewall did warn me about HWU wanting to go out on the net, and I just let it through. If you do have an AV program that won't cooperate, please let us know what it is. We will try to contact them, but in the end you will probably need to talk to them. When we do we never hear from them or worse: they want us to buy their p roduct just to have access to their help desk and THEN they don't get back to us.
  11. DevMike

    2018 Expo FOOD!

    A few years ago here in W Central FL (Tampa Bay), there was an old shut down burger place in St. Pete. Someone took the time to create a very good (should I say, PERFECT) sign that they stuck up on the old sign saying In-N-Out coming soon! People went BONKERS! The newspaper picked it up, everything. There was dancing in the streets! Well, maybe not literally but everyone who knew what/who they were was very happy. A few days later it broke that it was a hoax. Never heard who did it. Apparently last year someone pulled the same prank in NYC. And just to clarify if you are going to bring me lunch: it's a Double Double extra everything with chilies, fries animal style (cheese, onions, spread), and diet coke (can't have too many calories!!!! ). Actually, hold the drink.
  12. DevMike

    2018 Expo FOOD!

    Check this out! Awesome! My plane leaves later Sunday, so I have a lot of time to kill from checkout till 8PM. I have been dying to try conveyor belt sushi. I'll make it one day to Japan, I swear. There are none here in FL, but TX has them! https://kurausa.com/ Sunday dinner is SET!
  13. DevMike

    2018 Expo FOOD!

    Absolutely. I do have to say (sorry TX) that Cincinnati chili is my favorite. 5 Way ALL the way!
  14. Today we released version 4.3.28 of the Light-O-Rama Software Suite. This is an official production release, not a beta release. This release fixes some issues in the software and adds support for new Pixie hardware. How to check if your license covers this version To check whether or not your license covers this version, please go to the license retrieval page, and enter your email address (the one you purchased your license with). An email should then be sent to you with information about your license. The "Summary" section of the email will tell you whether or not your license covers the latest version. If the email says... Your license covers the latest version, 4.3.*. ... then your license already covers this version. You can use it without making any additional purchase. Please note, though, that your computer may not yet understand that your license covers this version, so when you install, it might tell you that you are running in Demo mode. In this case, simply reactivate your license (for example, via "Upgrade Light-O-Rama" on the Sequence Editor's "Help" menu), and your computer will then learn that your license is valid for this version. On the other hand, if the email instead says... Your license does not cover the latest version, 4.3.*. ... then your license does not cover this version. In that case, you have several options: Upgrading or Renewing Your License (1) You can continue using whatever version your license does cover (for example, perhaps your license covers version 4.1). (2) If you want to take this opportunity to increase your license level to take advantage of additional features, you can purchase a license level upgrade. This counts as a license renewal too - that is, your license will now work with this new version (and some future versions too). So, if you do this, there is no reason to also purchase a license renewal. (3) If you already own a Light-O-Rama license, but you do not currently own Light-O-Rama SuperStar, or if you want to upgrade SuperStar to a higher number of CCRs/channels, you could purchase or upgrade SuperStar. This also counts as a license renewal for the rest of the Light-O-Rama software suite, so if you do this, there is no reason to also purchase a license renewal. Please note that you must already own a license for the rest of the Light-O-Rama software suite in order to take this option. (4) If you do not want to purchase a license level upgrade or Light-O-Rama SuperStar, you can purchase a license renewal. Your license will now work with the new version (and some future versions too), at the same license level as it currently does. For example, if you have an Advanced license, it will remain an Advanced license, but it will now cover the new version of software. What's New in Version 4.3.28 This release adds new functionality for new Pixie Hardware, Dynamic update of certain files, and addresses several issues in the software: Update Pixel Editor to use same support packages as S5 Pixel Editor Now Shows an error message if intensity data failed to save The Configuration of Cosmic Color Devices and Pixies has been split Support for 'Dynamic Files' Support for new upcoming LOR Props Support for new upcoming Pixie Firmware Bug Fixes How To Get the Latest Version You can download the new version from the software download page. If that page lists a different version number as the lastest version, please click your browser's refresh button. Thank You!
  15. DevMike

    2018 Expo FOOD!

    I love a good burger- OK, who am I kidding here? I love ALL food! Just look at me! I have gone out for burgers many times, including to some of these 'premium' burger places like Five Guys, Red Robin, etc. Are they good burgers? Sure - but you end up dropping $15. For $15 I can go get a 'real' sit down meal. For $7 I can (or at least I could) walk out of an In-N-Out with a burger and fries just as good - if not better. Steak-N-Shake (what is it with the 'N'?) would be the only other burger that comes close to the deliciousness per dollar that In-N-Out does (Double-n-cheese w/fries or tripple no cheese with fries - $4!!!!). It is NOT the same style burger, but is just as awesome taste/value wise. If you have not been to one, there are several in DFW (most appear to be north of the city, but there are some within about 10 miles).
  16. DevMike

    How many universes per port on a pixcon16?

    The PixCon16 with proper firmware supports 2 universes per port. What version PixCon do you have?
  17. DevMike

    Clarification on Pixie16 12v 16x100 pixels

    We don't have any plans to support 100 pixel strings in S4 Visualizer. You should move to S5.
  18. DevMike

    Maximum props reached 512

    You may have deleted the fixtures associated to the prop, but not deleted the prop. Those are 2 separate actions. Go to the properties of the prop and press DELETE.
  19. DevMike

    Controllers and pixels/rgb for sale

    This is not entirely true. The Dip Switches will tell you if this is a V1 PIXIE or V2 PIXIE based CCC - both of which are considered CCC2. The easy way to know if you have a factory CCC1 or CCC2 is to look at the dangle connector. If it has 4 pins/sockets, it is CCC1 (Original Cosmic Color devices were 5V). If it has 3 pins/sockets, it is CCC2 (New Cosmic Color Devices are 12V). The pic rcktp posted just above is a CCC1.
  20. DevMike

    You Need These Pliers

    The Hakko's that Rcktp posted are my go-to side cutters, and LOR's as well, when dealing with small gauge wire and trimming leads on PCBs. They stay very sharp (I'm still on my first 2 pairs), and are inexpensive. Walking around the LOR factory you will find (literally) a hundred of these exact ones. You also talked about wire strippers. I am not a fan of the self adjusting ones, or ones like this. Unless you already own a pair, don't even bother with these. Instead I use a pair similar to these (I don't own this particular brand, and I don't remember where I purchased mine from). The end plate gives you an exact idea of how much you are stripping, and is labeled for correct gauge. Also remember that how well a tool works depends on how you like it. I know people who swear by the pliers looking one (2nd link) and the one I recommend they compare to a medieval torture device. A good set of tools go a LONG way when DIY-ing.
  21. DevMike

    1/4 Barrel Prop, How I made it.

    Protip that I have used before: A piece of masking tape on the drill bit at the stop point can help. You may need to replace the tape if you go too far but it should stop you (or at least give you the time to let go of the button). If you are going to be doing a lot of drilling for pixels, I would recommend a small cheap bench drill press. That's a great looking prop! Nice build
  22. I just posted another topic in the sticky at the top of this board: There is nothing going on at this moment that prompted the post. 99.9% of the people out there are honest, but there is that .1% you need to protect yourself from.
  23. No one. It was just time to re-iterate some simple steps you can take to protect yourself. While we are not responsible what happens between 2 private parties, we still like to try to keep our users safe.
  24. I thought I had posted something like this before, but I can't find it. Let me make a quick hit on media issues. To decode ANY media in Windows, you need a thing called a CODEC. CODEC is an acronym that means COder/DECoder. A codec is really nothing more than a program that takes media data and puts it into a form that windows can display/play/etc. You could think of it as a 'driver' in the Windows sense. Every media file on your computer requires a CODEC to be rendered (played and/or displayed for video). Some files require multiple CODECs. For example you could have a video file that needs codec X to render the video, codec Y for the audio, and neither are related. To add misery on top of that, there are multiple CONTAINERS as well - the container holds the encoded files, which may or may not specify how to actually decode the media within them! So for example you could have an .MKV file. MKV is the container. It specifies how the audio and video are stored in the file - NOT how they are encoded. The video could be encoded with x.264 and the audio with AAC. Or other combinations/etc. So you would need an x.264 codec to decode the video, an AAC codec to decode the audio, and software that understands how things are stored within the MKV (so it can get them out properly). So now in general MP3 is both an encoding (CODEC) as well as a container. It is well documented. One would think that an MP3 will play identically on 2 different things (computers, MP3 players, etc). Of course nothing in computers is ever that simple and you would be wrong. Forget for a moment the different parameters you can specify for an MP3 (like fixed or variable bit rate, sampling rate, encoding rate, how stereo is encoded, etc). The MP3 specification does not actually tell you exactly how to encode OR decode the actual audio of an MP3 file. Yes, it does tell you how to format a frame of data, etc - but how you compress the data into MP3 data is left up to the programmer of the codec. So while the data may be in a constant format, the contents of that data can be remarkably different. You can take the same input (WAV for example) and output different MP3s by using different codecs - and they should sound the same! But that also means that different codecs can interpret the SAME MP3 data in different ways! If you have Codec A on computer A that claims to be the MP3 decoder, and Codec B (written by a different programmer) on computer B that claims to be the MP3 decoder, you can get TWO different results if you play the same file on both. There are also additional gotchas: The output of one codec may actually be the input for ANOTHER codec. Or two (or more) codecs may both claim to decode a particular type of media. In Windows, codecs are 'Chained' - Windows will ask each codec on the computer if it does something with a particular format and then pass it to them one by one. Even if you have the identical codecs installed on 2 machines, they may be installed in a different order which means they are ran in a different order. From the video example above, you would have 1 CODEC that knows how to handle MKV, which then takes the data and sends it to 2 different codecs, 1 each for sound and video. Those in turn could pass their data to other codecs. Or possibly the computer has additional audio processing. The same way that codecs are chained, audio is pipe-lined: It goes from 'device' to 'device' (device here used in a way that can mean either software or something physical) which could additionally process the audio. That processing can take time and so you get a delay. I'm sure everyone by this time has been frustrated with a digital TV station/program where the audio is out-of-sync with the video. That happens because audio and video are processed in 2 separate pipelines and one is adding more of a delay than the other. The LOR software does not install any codecs - for us that would be a nightmare of licensing agreements, require us to create audio and video editing software, etc. Instead we rely on what you (or Windows out of the box) have installed on your computer. This is the most common reason we get tickets for Video - someone edited video on one computer which means they installed the video editing software which most likely installed it's codecs. Now they attempt to run it on another computer where they did not install that software and nothing works. LOR software relies on the CODEC to tell us exactly what time (down to 1/1000th of a second accuracy) the codec is playing. Different codecs could be interpreting the file in different ways giving 2 different results. Or the identical file is decoded by identical codecs, but 1 computer has different devices in it's audio pipeline than the other. We get the correct time signatures, but one computer is delaying the audio more than the other. Thankfully issues like this don't occur often. Encoding an audio file with MP3 at 128kbps, 44.1 khz sample, mono or stereo works for 99.9% of the CODECs out there - that is a 'standard' that has been out long enough that everything supports it. Usually.
  25. Dealing with low voltage wiring brings with it a new set of challenges. We tend to be more lax when it comes to things like wire strip length, how tight we make the connection, and a host of other things. Since we are dealing with low voltage connections, the terminals are usually much closer to each other. All of these things conspire together and lead to controllers that won't work, or boards that are blown, and a lot of hair pulling. I have previously talked about being able to burn down your house as quickly at 12V as you can at 120V, so we are going to skip talking about that. Instead I want to focus on channels/ports that don't work, work improperly, or worse: you blow them up because of a short. It is very easy to short a port on a CMB24, Pixie, or Pixcon: The screw terminals are located close together, and you may have over-stripped the wire by only a few millimeters. You lightly pull on the cord, the wire slides out a little from the terminal, touches another and BZZZT....Or, you don't twist all the strands of a wire tight enough. One strand gets loose ends up near the next terminal, BZZT. Now you've blown a Mosfet, a fuse, or worse - damaged the board itself. What happens the most with me is I try connecting things with the proper strip length, and the wire from a different terminal will 'pop' out. I put that wire back and really honk down on the screw. There is just not a lot of wire for that connector to grab on to. Blam. I just busted the connector. Most of the wire leads LOR supplies are stripped to the proper (short) length and 'tinned' - dipped in solder to prevent the stray strands from escaping. That is usually enough. But what about wires you strip yourself? I am guessing that many of you don't have a solder pot around. Or what about if you want a little MORE security than just tinning a wire? There is another way: insulated ferrules. What the HECK is a ferrule? It is a small metal tube that you crimp onto the end of the wire that holds all the strands together. Because it is a sold piece now it is much easier to insert into a connector. It is large enough that you can make a good connection without over-tightening the screws. The insulated end protects you from shorts. Here is a good video on how to use them: Ferrules are CHEAP. I recommend an assortment of sizes from 10-22/24 AWG as your first purchase (or these) - that should cover both power leads as well as leads from pixels/etc. When you run out of the smaller ones, just purchase that size in bulk. The person in the video is using a different kind of crimp than I would suggest for smaller gauge wire - like what we deal with on pixels and dumb RGB strips. Instead, I would recommend a 'self adjusting square' crimp. Do not use any manual crimp (the strip tool in the video) or ones like this. You don't need to break the bank, but do purchase a 'better' (more expensive) crimp. Yes, you can add ferrules to wires that are already tinned, if you like. There is one thing I would like to add/correct/comment on from the video. If I remember it correctly in there he says to only strip the wire to the length of the ferrule. I personally don't like that suggestion. Instead, I like to strip mine a little longer than the barrel part, and then trim the excess. When you insert the wire, do so until it 'bottoms out'. If you are using a ferrule of the right size, that will be the insulation hitting the inside top of the barrel, and you should see the wire come out the bottom of the barrel. Now crimp and then use a sharp pair of side cutters and remove the excess wire flush to the ferrule. Just don't forget to do the cut. My reasons: If you strip a little too short, you don't get a full connection on the entire barrel length when you crimp. You won't be able to tell. If you use a ferrule that is too small, you may only catch a few strands, which you'll see instead of the actual full wire come out the bottom. If you use a ferrule that is too big, the insulation won't 'bottom out', and instead you will see it exit the bottom of the connector. If the ferrule slips during crimping, you'll be able to tell. If you don't see wire out the bottom after the crimp, cut it off and re-crimp a new ferrule. Oh, and make sure you CLOSE that container! Don't do what I just did about 10 minutes ago. I was putting some ferrules on some CCR II ribbons for testing, and knocked the box on the floor. 1000 small ferrules on the ground, and they need to be sorted by color. Some one kill me now! Do a professional job: Ferrule your wires! (4/5/2017 edit note: I combined several of my messages into this one, and removed some others to keep things clear)
×