Jump to content
Light-O-Rama Summer Sale Announcement! Read more... ×
Light-O-Rama Forums

Brad Stucky

  • Content count

  • Joined

  • Last visited

Everything posted by Brad Stucky

  1. I just downloaded S5 a couple weeks ago and have begun to switch over to it. It doesn't seem to be possible to rotate the Predefined Prop Shapes without them elongating at the same time? If I import the props from S4 Pixel Editor or the Visualizer with any rotation introduced at the time of their creation, they import showing elongation. Some of my Superstar programming requires a 24 spoke x 12 pixel per spoke prop where no spoke is directly up, down, left, or right. Just curious why I can do this in S4 but not S5. This sure won't keep me from using S5. There are so many nice things about it. Well done!!
  2. Brad Stucky

    Auto Sequence Feature

    Anxious to try this new feature, I applied it to a the inner most circle of a 16 spoke by 16 pixel/spoke circle prop created with the tree wizard in the Visualizer and then imported to SS, and after only 2 minutes of programming, it looks fantastic! This is really great! Guess I'm building another prop for Christmas this year. However, I noticed that I could not assign cyan to one of the color selections to cycle through. Perhaps that is still on your work list? This feature is going to be really great for doing those songs that I have less desire to hear over and over. Nice job, Brian.
  3. I believe something with exporting intensity data from SuperStar has changed from version 4.3.26 to 4.3.30. I have two E1.31 matrices planned for this year. One of them is a 3-year-running 50x24 built directly in Superstar and the other is a new 150x16 Visualizer import. For version 4.3.30, the 50x24 matrix built originally in 4.3.26 works fine when exported from 4.3.30, but the original 4.3.26 SUP file that was created with an import from the Visualizer ends up quite messed up when exported. I tried importing the visualization again and there was no change. When the two 4.3.30 intensity files are merged and then played back in the sequencer, the direct-built matrix plays fine but the 150x15 does not. To check this, I loaded into 4.3.30, several different working 150x16 SUP visualization files created in 4.3.26 and then exported the data for each, overwriting the 4.3.26 versions of the ss.lid files. After doing this, the ss.lid files no longer play correctly. When I export and combine data using 4.3.26, everything plays back as it should. The import visualization file was not changed for the new software. I left another recent post mentioning trouble I had with software installation on 2 different computers when upgrading from 4.3.26 to 4.3.30, just in case these 2 issues are related. As a note, I could not get 4.3.26 to play quite right on the 150x16 matrix without selecting "Use My Order rather than SuperStar's" in the Prop Properties SuperStar Button using "Let Superstar Decide" about matrix. (no other check marks entered there) Before I selected this, the playback was shifted around the 16 pixel width by 1 pixel, otherwise, very close to proper playback. Unchecking this parameter made no noticable difference for 4.3.30. Now the export in 4.3.30 seems to be way off when using visualization mode. Brian, I hope I'm not spoiling your day with this. (I'm glad to see the shockwave width change to 200.) Thanks.
  4. Thanks, Brian. It looks like you’ve taken care of the problem. I’ve exported and merged both of my files and both the Visualizer and the LED matrices are playing properly now. Thanks for your quick response.
  5. Thanks, Brian. I also recreated the visualization from scratch in the 4.3.30 visualizer, imported it into SS 4.3.30 and the problem remained. Email sent
  6. Brad Stucky

    LOR 4.3.28 crashes after install

    Might this change in S4 have something to do with the installation problem I had on 2 different computers? Installing 4.3.30 over 4.3.26 on Windows 7-64 pro, I received an error that the program could not locate a resource file in a temp directory somehware. (lightorama.msi I believe) Sorry I didn't get any screen captures. The program got into some kind of loop so I had to task manager abort the process. I then tried a re-install and selected a repair of the installation and everything seemed fine after that. This same event happened on 2 different computers.
  7. I'm adding a 16x150 matrix to our display this year and have run into an issue when scaling effects from a 24x50 matrix. When scaling a shockwave to the wider matrix, the width of the shockwave on a few of my effects is taken above 50 which seems to be the limit that you can enter into that parameter field. I'm only reminded of the situation if I happen to click on the effect. The parameter window will then pop up and state to re-enter a value of 50 or less. If I escape out, which is a little tricky sometimes, the larger scaling width value remains and when I export the data to the sequence editor, it plays back properly as intended on the 150x16 matrix, so the "incorrect" value seems to be accepted properly for playback. Am I just getting lucky that the SuperStar editor is allowing this without a problem? Since these particular shockwave effects require covering the full width of the larger matrix, I was hoping that this limiting width value can be increased without creating some other issue? I'm using version 4.3.26 with 80CCR license and sending the data through a PixCon16 via dmx E1.31 using 16 universes, one for each row. Thank you for any help.
  8. Brad Stucky

    Issue with shockwave width when scaling up

    Thanks for your quick response, Brian. Glad to hear this is just a temporary arbitrary limit.
  9. Brad Stucky

    4.3.22 has all the new SuperStar features!

    The new features are fantastic, particularly the layer priority features! I did find out that enabling this on an existing sequence can cause some strange things to show up if you have overlapping events without respect to row location. Some of them turn out to be really cool but it can also mess a few things up. With more variables to mess with, I'm looking forward to applying some changes to sequences that I thought were pretty much done for Christmas this year. I am glad, too, that this is a per-sequence preference so that I can update sequences as I find time. Thanks Brian, for adding more great stuff to an already great program. Last year, with a 24x50 matrix added to our display, I spent 99% of my time programming in SuperStar and I probably had more fun than any of the 12+ years prior. There just appears to be so many more things a person can create, particularly with respect to the timing of the music, than what can be done with the pixel editor.
  10. Brad Stucky

    Image Rotation

    Thanks for the quick response, Brian. I get what your saying about the vertical related to horizontal. I think I now understand why you did it that way. When I was talking about creativity, I was actually referring to your Superstar software itself and how much can be done within it. I particularly like the morphing tool, but I will sometimes make changes in the sequence editor following an export from SuperStar. I did order the CCBs from top to bottom and re-arranged the pixel order from bottom to top in the sequence editor. In the visualization screen I have the pixel order from top to bottom. I've fiddled a bit more with the visualization program and now have it set up so I can copy and paste in the sequence editor and have it showing correctly. I also managed to do the same in the animation screen in the sequence editor but that was quite a bit more tedious moving all those pixels as opposed to just swinging around a fixture in the visualization screen. I think I'm now set to go, although after reading though your comments a couple of times, I'm understanding that there may be more than one way to arrange either the channels in the sequence editor or the actual pixels themselves. Re-arranging the pixels may be less work. I may have to explore that some more. Thanks again for your help and for a great program!. I'm looking forward to sequencing again this year with most of my work happening in SuperStar.
  11. Brad Stucky

    Image Rotation

    Last year when using CCBs in a horizontal SuperStar matrix of 8x50, I remember having trouble with events (text) being upside down when exporting into the sequenceeditor. By manipulating the prop in the visualizer software and rearranging controllers I managed to get things looking right. This year, with a 24x50 horizontal arraythis is getting more difficult to address. I created a simple sequence using a 30 second scene of a small 4x5 pixel box in the upperlefthand corner of a SuperStar 24x50 horizontal array with layout in CCR mode and controllers on the left. When I export to the sequence editor, the events show up in thefirst 5 pixels on the last four CCBs 21,22,23, and 24. Shouldn't these events show up in CCBs 1,2,3, and 4? When I change the Superstar layout to right hand controllers,the exported events show up in the last 5 pixels but again in the last four CCBs, 21,22,23,24. I think I can probably manipulate stuff again, but is this normal or am Imissing something? I looked at the cool added rotation feature in version 4.1.2, but if you're scrolling text you may also need to mess with the scrolling direction. Irealize I can probably accommodate this by re-arranging the channel layout in the sequencing editor before I paste stuff from the imported file, but since the LOR sequencerautomatically adds and assigns devices/channels from the top down, it sure would make it easier to observe event programming in both programs if right-side-up in Superstar matched right-side-up in the sequence editor. Is there some option to assign the location of the first channel of the first controller in addition to which end the controllers are located? I really like the SuperStar software so I hope am I completely missing something simple here. Real creativity lies with software that allows you to manipulate any given pixel at any time and at this point I just can't see going to the pixel editor for any major stuff, yet. Thank you for any assistance.​
  12. I'm planning on having 4 CCBs in my display for this year. They will be arranged in an 8x50 horizontal matrix. While working on text in my sequences, I decided to edit the custom 8x8 slim font, but upon upgrading trom version 3.6 to 3.7, I seem to have lost my editing of this font. Would I be so fortunate to be able to recover this font without editing the whole thing again? Is this something that will occur again upon software update, or can this be changed so that custom fonts can be saved through an upgrade? Perhaps I didn't save something correctly. Brad
  13. Thanks, Brian, for responding so quickly. I didn't figure anyone but me would be up this late at night. I have started restoring my font. (It's not anywhere near as serious a thing as it would be to loose all the sequence editing I've been doing recently. ) I've located the font directory and sort of figured out what to do to copy the custom font file, edit the internal font name, rename the file and save it as another file to show up in the list of fonts. It's not a bit deal. I'll like to add that this is some amazing software, and I'm having all kinds of fun with it. I really like the looks of the accelerated chases that can be generated. It would be nice if that could be easily done in the LOR sequence editor. Thanks again, Brian.
  14. Brad Stucky

    Closing Multiple Sequences That Are Open

    jimswinder wrote: I, too, have had some trouble closing the second sequence after closing the one before it, but only when they have been opened in separate windows. (not in the tabs form) I do this quite often in order to cut and paste from older sequences to newer ones with different configurations. I've experienced this problem going back to early versions of LOR 2. When it happens, I get around this by placing the mouse cursor in the region of the window title bar of the sequence that won't close or save and then move the window slightly. After this, I've been able to then close, save or resize the window. I hope this helps.
  15. Brad Stucky

    WANTED: Hallelujah Chorus sequence

    Hey Bryan, Lightoramasequences.com has one. It's not a full chorus but rather a starting or ending piece. http://lightoramasequences.com/component/option,com_remository/Itemid,42/func,fileinfo/id,470/
  16. csf wrote: I've downloaded and installed FRAPS. Although I've heard of the program, I'm new to it. I've been able to get a reading for each of the monitors but it doesn't seem to register what the animation screen is doing. It will register on both monitors what my mouse movement is, which maxes to 60. (monitor refresh rate?) On playback of a sequence, the editor screen reading seems to be related to the timing grid. The reading on the other monitor disappears with the animation screen playing. Maybe I'm doing something wrong. I will play a little more with that and see what I get. Thanks for the great suggestion. The quad-core processor show considerable more on one core but a second core is showing usage as well. One core is running about 40% and another is about 20% while the other two are down around 5%. There is some mention in the display settings referring to OpenGL, but only some adjustment for proper display of the screen. I'll have to play a bit more with this tomorrow since it's way past my bedtime.
  17. stanward wrote: I've had trouble with the animation screen keeping up without being jerky and the best solution I've had to smooth out the animation acreen is to turn off "move grid with play." That's a big one! Also turn off " vary color with channel buttons". I have 2 CCRs with all 300 channels programmed into the animation screen and when I do continuous fast color change/sweeps on both CCRs, the animation is jerky even with these 2 items turned off. I then turned off "control lights" and that almost eliminated the problem. I'm using a 2-year old AMD quad-core 9550 with cpu usage rarely exceeding 15% and I am using a NVidia GTS250 card with 1 gig of ram. I am using 2 monitors. I also have one CCR connected to observe color during programming and I've noticed that when I have the channel grid moving along with the animation screen playing, that sweeps on the CCR will not move smoothly. It appears that the commands are bunch together and sent in bursts, for lack of a better description. As soon as I turn off all screen animation, the CCR then begins to operate much more smoothly. If I play the sequence through the show program, the operation is smooth. I'm convinced there is a bottleneck someplace in the sequence editor when it is trying to control devices, the animation screen, and the editor grid movement at the same time and I don't think it's CPU usage, but then I'm not a programmer (software) so I could be all wet. Could someone much smarter than me shed some light on where this bottleneck might be and what could be done to help the situation? (Would dual video cards, SLI, or something else help?) I'm only using 2 CCRs. I'm guessing there are others using even more of these and must be having similar problems with their animation screens.
  18. Brad Stucky

    Multi-Track out of step with v2.8.12

    LightORamaDan wrote: Thanks, Dan. I am so pleased to here this is on the list for change. Although I did finally make the change from 1 track to 10 tracks this year, the main reason I held off the change was due to the tracks not lining up on the sequence screen during play back. This year, the advantages of multiple tracks finally outweighed this disadvantage. If it's a scroll bar issue, I would rather have a "dummy" scroll bar on a fully shown track and have all the tracks line up. It would also be handy to have a little button to the left of the track bar to open and close the track in a manner similar to the RBG channels. I'm sure not complaining, though. The updates in the software that have taken place over the years have really made things easier to do, particularly, this years fantastic updates.
  19. There is one thing I've noticed about converting existing channels to RGB. Last year I had programmed 3 (actually 4 with white) colors for the windows on our house. This year, I converted these channels to RGB with the separate white channels underneath the RGB channels. The visualization screen still shows these RGB channels as separate red, green, and blue pixels and everything shows properly on the screen during playback. If you decide to move these converted RGB channels to another track, the links for the separate red, green, and blue pixels become lost. I moved just one converted RGB channel, and all 5 RGB channel groups became broken. Fortunately, you can undo the move and it will come back. I decided to continue anyway since I was wanting to use more tracks. I drew the animation back selecting the channel as a group which showed white instead of the individual colors. A minor problem I did have was that I had my white channels mixed in with the original red, green and blue channels so it was a little more tedious to draw the"white" (combined) RGB channels mixed in with the separately designated white channels. (That was sort of tough to explain, too.) :? Anyhow, this is just an observation for those considering converting existing red, green and blue channels to RGB and later deciding to move them to another track.
  20. Brad Stucky

    Careful when converting channels to RGB

    bob wrote: Whoops, didn't catch that until today. It's also sent now to you as well. Thanks, Bob.
  21. Brad Stucky

    Careful when converting channels to RGB

    bob wrote: Bob, that is basically what I did. The sequence I started with contains 4 tracks. One main track with 224 channels which contain 24 channels converted to RGB channels. I have 1 track each for 2 color ribbons and 1 track for VU meter affects. If I move one of the converted RGB tracks to any of the other tracks, the colored pixels for all 24 converted channels vanish from the animator screen. I've tested several of my other sequences and found that I have others that don't do this, but at least half of them do. (about a dozen or so) One other thing I noticed for the affected sequences is that when the RGB channel is moved, the computer hesitates for a while like it's trying to figure something out before the visualization drops the affected pixels. (redraw calculations?). Another thing I tried is that I exported the channel configuration from a sequence that is unaffected and imported it into a sequence that is affected. The affected sequence remains affected. I just can't figure out what possible difference there is between the 2 sequences that would cause one to do this and another not. I will email an affected and an unaffected sequence to support@lightorama.com. I really love the new tools and features so this little glitch hasn't slowed me down.
  22. Brad Stucky

    odd quirk when drawing in visualizations

    mcorbo wrote: I need to correct my earlier statement as it doesn't quite reflect what I meant when I said I noticed the same thing. I haven't noticed the channel popping back when zooming in or out. For me, it only pops back to the first channel when I undo (ctrl -z). It will do that even after I've moved either of the scroll bars. Whether or not I use the scroll bars or the zoom function doesn't seem to affect whether or not the channel pops back to the top. It unconditionally pops back for me when I undo. Additional details of my setup are that I'm using 2 monitors and my animation screen is set to 352 by 934 so I have to be zoomed in to the max in order to draw. I also don't have my selected image in the background resulting in the missing image warning everytime I open the animation screen. This is not a problem for me. I simply chose to do this since the picture would sometimes interfere with being able to see the editing.
  23. Brad Stucky

    odd quirk when drawing in visualizations

    Philip wrote: I've noticed this too. It also does the same thing if you undo any drawing. (ctrl+Z) If you aren't careful, you will then be drawing for the top channel instead of the one you had intended.
  24. Brad Stucky

    Spacebar stopping problem

    Is anyone else having trouble with the spacebar stopping the sequence editor at the proper place? With last years software, I noticed an infrequent glitch while stopping and starting the sequence editor. About 1 in 100-200 times or so, the spacebar would cause the select point to hop back to the starting point instead of stopping and remaining at the correct place. A 2 month-ago change in the video card has had no effect on this behaviour. With the recent update plus the addition of 2 color ribbons (another 300 channels) this little glitch has gotten quite a bit worse. It seems to be much more prominent when the screen is scrolled down to the lower tracks. It happens more than 50% of the time in this case. I have the play range set to full sequence. I am using 4 tracks with 250+ channels on the first track and 1 track each for the color ribbons and another small 16 channel track. Yeah, I should probably split up that 1st track into more but I don't think this should be an issue here if a color ribbon is 150 channels. My animation screen resolution is set to 352 x 934 with all channels programmed to the screen. (Yes, it was tedious to do, but well worth the effort in appearance) My hardware is an Nvidia GTS250 on 2 monitors, AMD Phemon 9550 Quad-core with 6 gig memory. And by the way, Thanks Dan and crew! The updates to the software are fantastic! Multiple clipboards, chase tool and other stuff, oh my!!
  25. Brad Stucky

    Spacebar stopping problem

    Brad Stucky wrote: Fantastic!! Version 2.8.10 fixes this little glitch. Many thanks to Team LightORama!! I'm really really enjoying the new commands and features!