Jump to content

MattBrown

Administrators
  • Posts

    1,801
  • Joined

  • Days Won

    16

Everything posted by MattBrown

  1. An explanation of the Carryover column with examples can be found at the bottom of this page: https://www1.lightorama.com/help/prop_definition.htm
  2. The channels assigned to props in your preview must match the channels used in your S4 sequences. https://www1.lightorama.com/help/upgrading_sequences.htm After converting your sequence, do the channels in the sequence grid have an "@" sign in front of them? If they do, then they have been archived and will not control lights. More about archived props here: https://www1.lightorama.com/help/concept_archived_props.htm If there are a lot of archived props/channels, modify the preview to better match your S4 sequence, then try upgrading the sequence again. Matt
  3. If someone has a sequence that consistently displays this issue in version 5.6.6, could they please open a help desk ticket and attached the problem sequence file? Thanks! Matt
  4. You could attach a problem sequence to a help desk ticket and we can investigate. Be sure to reference this forum topic.
  5. What you see on your computer screen is always going vary to some degree from what is shown on your actual lights. A proper purple on my pixels is almost black on my monitor. And not just color - white at 40% brightness is medium gray on a monitor, but is still white on pixels. Setting the dimming curve to "pixel curve" in prop definition will put you in the right ballpark. But if you are after a specific color, testing on the actual lights is required... as was described in the first post.
  6. When you say "the last release", what version was that? Could you just reinstall that version?
  7. Yes I can. It looks to me like that is a bug that has existed in the S5 Sequencer for a long time. It is triggered when you enable, then disable output for an LOR network that is not enhanced. Matt
  8. In version 5.6.2, there was a change to improve the calculation speed of movie effects with WMV files. If you want to create a help desk ticket and attach (or provide a link to) your sequence and WMV files, I would be happy to investigate. Please mention this forum post in the ticket. Something else to try would be converting your WMV files to AVI format. Or changing the frame rate to 20 fps. Matt
  9. I should clarify that I am using the 5.6.6 Sequencer to control those PixCon16's.
  10. I'm controlling 3 PixCon16's at the moment via E1.31 with 5.6.6. Tested this configuration on 2 separate computers. Matt
  11. Yep, you could use FreeFileSync anywhere I mentioned TreeComp above. I would add that FreeFileSync has better performance than TreeComp - so if you are copying large numbers of files, then FreeFileSync is the better choice. I continue to use TreeComp because I like the simple interface and I have used it for many years. Matt
  12. Thanks for the feedback! We hope to have a feature like you describe next year. There are many ways to make life easier with the current capabilities of the software. This is my personal approach: My show computer stays offline in order to keep software updates, One Drive, DropBox, etc from interfering with shows. That means I have to use a flash drive to update the show computer. Picture files for all sequences are kept in "Light-O-Rama\Sequences\Pictures". This way I can easily share pictures across sequences. Sequences are stored in a folder for the year -- "Light-O-Rama\Sequences\2021" for this year. My media files (audio or video) are transferred to the show computer ahead of time -- my playlist is decided early in the year (definitely gonna have + might have if I get around to it). I recommend keeping these in the "Light-O-Rama\audio" folder. A sequence that references media in the audio folder can be moved to another computer and still find the media file - as long as that media file has been copied to the audio folder on the second computer. I use a free utility called TreeComp on my sequencing and show computers to transfer files on and off the flash drive. TreeComp compares the contents of 2 directories/folders, shows you the differences, and makes it easy to copy the files that have changed. So directory A would be on the show or sequencing computer and directory B would be on the flash drive. TreeComp shows me which files have changed and I just copy those files (all within TreeComp). https://lploeger.home.xs4all.nl/TreeComp.htm So when I need to update the show computer: I plug my flash drive into my sequencing computer. It has 2 folders on it: "2021" and "Pictures" Use TreeComp to compare "Light-O-Rama\Sequences\2021" on the sequencing computer to "2021" on the flash drive, then copy any changed files onto the flash drive. Use TreeComp to compare "Light-O-Rama\Sequences\Pictures" on the sequencing computer to "Pictures" on the flash drive, then copy any changed files onto the flash drive. Close TreeComp on the sequencing computer and Eject the flash drive. Plug the flash drive into the show computer. Use TreeComp to compare "2021" on the flash drive to "Light-O-Rama\Sequences\2021" on the show computer, then copy any changed files onto the computer. Use TreeComp to compare "Pictures" on the flash drive to "Light-O-Rama\Sequences\Pictures" on the show computer, then copy any changed files onto the computer. Close TreeComp on the show computer and Eject the flash drive. If you have questions about which files are being used by your sequence: with your sequence open in the Sequencer, select Sequence > File References from the menu. This will tell you all of the files used by the sequence. https://www1.lightorama.com/help/file_references.htm If you plan to open your sequences with the Sequencer on the show computer, you will probably also want to sync the "Light-O-Rama\CommonData" folder between the sequencing and show computers. You can use TreeComp for that too. I hope that helps :) Matt
  13. Usually, this indicates that the starting location in Prop Definition does not match with the way the matrix was actually wired. Try specifying a different corner in Prop Definition.
  14. 1) Restart your computer. After the restart, make sure no LOR software is running. In particular, if the LOR Control Panel is set to load on computer startup, you will need to right-click on the light bulb icon in the system tray, then select "Unload Light-O-Rama". 2) Uninstall the current version. In Windows 10, this is done from Settings > Apps. In prior versions, go to the Control Panel > Programs and Features. 3) Verify that all LOR programs have been removed. If running a 64-bit version of Windows, go to "C:\Program Files (x86)". On 32-bit versions, go to "C:\Program Files". If there is still a Light-O-Rama folder there, delete it. 4) If needed, download the software installation file at http://www1.lightorama.com/sequencing-software-download/. Look for your version of software. The latest is at the top of the page. If you have trouble with the download, try using the 'Alternative Download' button. 5) Restart the computer again and make sure you're logged in with the administrator privileges. Find the file you downloaded above and run it. Follow the prompts. When the installation is complete, run your tests and you should be good to go.
  15. Thanks for the feedback Jim! We will get the version number added to the forum.
  16. Jim, I'm not seeing any issues with sending E1.31 from the Sequencer in the 5.6.4 release. You might need to create a ticket and attach a sample sequence so we can narrow down the problem. Matt
  17. Thanks for the feedback. It looks to me like this happens when a non-enhanced LOR network is enabled during playback. If you are playing back to enhanced LOR and/or DMX only, then things work ok. Would you mind installing 5.6.2 one more time and confirming that is the case with your lights? We will get a new release out as soon as possible. Matt
  18. Speed in the S5 picture effect controls the movement - left/right, up/down. There is no control over GIF playback speed - you would need to adjust that using an external program.
  19. Thanks for reporting the issue! This will be fixed in the next release.
  20. I agree that there is something odd in your first screen shot. It looks like a color sample did not get drawn at all for "Snowman Eyes Wide" - note the timing mark is still visible in the first column. Feel free to create a ticket with the help desk and attach your problem sequence. I will be happy to take a look at it. Please reference this forum post in your ticket. Also, go to Help > About in the Sequencer and copy the information shown into your ticket (use the Copy To Clipboard button). Thanks!
  21. The channel level isn't enabled by motion effect row, it is enabled for the entire prop -- your RGB channels will not be grouped by motion row. Just right-click on the prop name and select "Enable Channel Level on Pixel Prop". More about the right-click menu at the bottom of this help page: https://www1.lightorama.com/help/item_list.htm
  22. Those aren't actually MP3 audio files, they are a result of the S4 Sequence Editor analyzing your audio file. You can delete them if you want to.
  23. No. When you create the SD card, it's going to insist that the media file is an MP3.
  24. The WAV files under LORInternal\CanonicalAudio are only created when you use an MP3 as your media file. This is done so that when you are editing a sequence and start playback in the middle of the file, the audio starts playing from precisely the correct time - the S4 Sequence Editor and the S5 Sequencer both use the WAV file instead of the MP3 for playback. The Show Player uses the MP3 file for playback because it always starts playing the audio file from the beginning -- it never has to seek to the middle.
×
×
  • Create New...