Jump to content
Light-O-Rama Forums

JamesWright

Members
  • Content count

    133
  • Joined

  • Last visited

Everything posted by JamesWright

  1. Report Number: JMW-S5_009Module: SESoftware Version: 5.0.18 PRO (Beta)OS Version: Windows 10 x 64Description: In SE, 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.Repeatability: Happens every time and in all of my sequences.Hardware Used: N/A (I think).
  2. Motion Effect Fills

    Thanks Matt. It sure would be nice to have a simple fill effect. Jim
  3. Motion Effect Fills

    Does anyone know how to do a simple fill in a motion effect row? I have a custom prop, a wreath with 5 concentric rings and progressively fewer nodes on each ring. I want to be able to a simple fill (which would look like a spiral out or in), running from node 1 to node 128 or node 128 to node 1. I would also like to be able to use any of the other effects to "color" this fill. I know how to do this on a linear prop, such as an arch, but I can't figure out how to do it on a circular object. Jim
  4. Thanks for the reference. I agree. I am using 5.0.16 and, as you do, I use it year-around for landscape purposes. I guess that we will just have to go dark for a couple of days. Of course that means that we can't work on sequencing either. Jim
  5. Jim: Where did you see that announcement from Mike? I can't find it. Jim
  6. In the past we were able to add a flood prop to the preview. In S5, I do not see that capability. Either I am missing something or it is gone. If it is gone, then we need to get it back. I need to be able to define a RGBW flood, yes a red, green, blue, white flood. Jim
  7. CCR Question

    Matt: Thanks for the reply. No. I haven't got my CCRs working yet. I will send you a sequence later today. Jim
  8. CCR Question

    I know that the LOR developers are working on fixing the visualizer so that it will interpret the CCR macro commands. This is not about that, at least directly. My CCR set up has been working since 2009 - the days of the animator. Through all of the software conversions they have become a mess; and the conversion to S5 (which I really like) left the channel makeup in a worse mess. Therefore, I decided to remake my 10 CCR arches from scratch. Using a new version of my preview design, I made a new CCR arch to replace the old one. However, when I appended the prop to a view and added channel level to it there was something that I need missing - the macro channels. So, my question is - how do I make a new CCR prop with macro channels attached to the prop? Jim
  9. CCR Question

    I am and control lights is on. Everything else works fine, except the 1 converted CCR. LOR: Do you have any suggestions/comments?
  10. CCR Question

    I can do CCR sequencing, in S5, using my old props with no problem. I wish to continue that and have the problem discussed above.
  11. CCR Question

    Yesterday when I wrote the above, I got distracted and didn't finish. In addition to the question about the macro channels, I have another more sever problems. The main problem is that the new CCR arch will not light. The system will not control these CCRs at all. Everything works when I use an older version of the sequence, but the new one will not control the lights. It shows on the visualizer just fine, but no lights. What might the problem be and how do I fix it. Jim
  12. Using 5.0.14 Pro (beta). When the verifier issues a Warning 28 (Channel is completely off), the details column lists a channel number such as "[CHANNEL]: c171". How do you find out what actual or physical channel this refers to? I would like to be able to track down the actual issue, but I can't figure out how to convert this number to an actual prop. Thanks. Jim
  13. Verifier Channel Numbers

    I am just interested in where those current channel numbers come from and to see what props they are attached to. Also, if they are not needed, I would like to be able to delete the channels. I want to be able to clean up all of the unneeded stuff in the sequences. Jim
  14. My show is running using 5.0.14! However, I have a problem that I can't figure out. My mega tree is turned 180 degrees. The back is in the front and the front is in the back. I have everything connected exactly like I did using S4, last year. I have double checked the string and controller setups. I have also double checked my prop definition. The starting location is "Bottom Back CW" which is the way that I have it wired. The tree displays properly in the playback window. However, the actual lights display with string 1 in the front instead of the back. Text reads and scrolls properly, but starts over in the from instead of the back. Does anyone one have any idea why this might be happening or how to resolve it? Jim
  15. Mega Tree Turned 180 Degrees

    All of my sequences act the same way. All of the other props seem to display properly, but the sequencing for them is not as elaborate. I know that my sign (matrix) is working just fine. Some of my sequences are new with S5 and some have been brought forward from as far back as 2009 (through each generation of software). These sequences and particularly the tree worked correctly last year. This sequencing was made using S4-S5. I don't use Superstar. BTW, the tree uses RGB nodes via E1.31, not CCRs. Jim
  16. Show Player Problem

    I tested my full show tonight and ran into a major problem that I can't figure out how to resolve. I am getting HUGH delays between sequences on the first time through the show. I am experiencing black (no lights) for a minimum of 7 seconds to over 20 seconds, using 5.0.14. I assume that the player is loading each sequence as it needs it because CPU and disk access go up noticeably during the "no show" run. I have not had this problem with LOR software for a long time. The problem does not happen during subsequent runs through the show, just the first time. Is there a way to correct this issue in 5.0.14 or do I need to move this comment to the bugs section? Jim
  17. Show Player Problem

    Thanks to the Phil and Default for the great information. Unless my mind is failing me, in previous releases, such as S4, I think all we had to do was select an option to save as a compressed file and that was the end of it. Now we have to: 1. Save the sequence, 2. Generate the .play file, then, 3. In a completely different place, remember to generate the compressed file. I would like to suggest an enhancement to S5. I suggest an option to generate and save the .play as a compressed file automatically, instead of having to go thru 2 separate steps. I realize that this will take awhile longer in the process, but then there is no more that needs to be done. After all, as far as I know, the only reason to generate a .play file is to run it in a show. Having this feature added would avoid a lot of possible confusion and extra work on the user's part. Now, if I want to make a change in a sequence, after I have set up the show, I need to remember to generate a new .play file and then, in another section of the program, compress that new .play file so that there will be no interruption in the playing of a show. Just a thought Happy Thanksgiving All. Jim
  18. When I open Preview Design and then select one of the arches, the prop definition starts to display and then gives the following error;" Error while drawing shape diagram, Parameter is not valid."This appears 3 times, I click OK on each one and then the Prop Definition displays. Here is an excerpt from the log file that I think is relevant - LORSequencer.exe Information: 0 : System.ArgumentException: Parameter is not valid. at System.Drawing.Graphics.CheckErrorStatus(Int32 status) at System.Drawing.Graphics.DrawArc(Pen pen, Single x, Single y, Single width, Single height, Single startAngle, Single sweepAngle) at LightORama.Preview.ShapeArch.PaintShapeDiagram(Graphics g) at Ku`7<-:I)~\.554\.n%4\&1Gygm!.‌‮‎‎‏‏‍‪‪‫‫‌‮‪‌‫‏‎‮‭‏‬‍‌‪‫‬‏‌‮(Object , PaintEventArgs ) DateTime=2017-11-18T04:02:15.8042796Z LORSequencer.exe Information: 0 : System.ArgumentException: Parameter is not valid. at System.Drawing.Graphics.CheckErrorStatus(Int32 status) at System.Drawing.Graphics.DrawArc(Pen pen, Single x, Single y, Single width, Single height, Single startAngle, Single sweepAngle) at LightORama.Preview.ShapeArch.PaintShapeDiagram(Graphics g) at Ku`7<-:I)~\.554\.n%4\&1Gygm!.‌‮‎‎‏‏‍‪‪‫‫‌‮‪‌‫‏‎‮‭‏‬‍‌‪‫‬‏‌‮(Object , PaintEventArgs ) DateTime=2017-11-18T04:02:18.8689383Z LORSequencer.exe Information: 0 : System.ArgumentException: Parameter is not valid. at System.Drawing.Graphics.CheckErrorStatus(Int32 status) at System.Drawing.Graphics.DrawArc(Pen pen, Single x, Single y, Single width, Single height, Single startAngle, Single sweepAngle) at LightORama.Preview.ShapeArch.PaintShapeDiagram(Graphics g) at Ku`7<-:I)~\.554\.n%4\&1Gygm!.‌‮‎‎‏‏‍‪‪‫‫‌‮‪‌‫‏‎‮‭‏‬‍‌‪‫‬‏‌‮(Object , PaintEventArgs ) DateTime=2017-11-18T04:02:20.4531267Z Anyone have any idea what the problem with the arch might be? Jim
  19. Parameter is not valid error

    Matt: Here is the requested screen shot. The link is https://1drv.ms/i/s!Aor4cHE_ElMqqiVXz-yVA4TnSl_o . BTW this forum board will never allow me to upload files. Just thought that I would mention it. Jim
  20. What effect (S) were you using and how did you set it up? Jim
  21. Dimming Curve Question

    Matt: Thanks. I did have a problem with both files. I fixed them and everything works great. Jim
  22. I am using 5.0.14. I just built a new dimming curve. It is in the same directory as all of the others (Light-O-Rama > Plugins > Dimming Curves). When I go into preview design, select a prop and try to add the dimming curve that I just made, it is not listed. What am I doing wrong? Jim
  23. Dimming Curve Question

    Matt: I am glad that you mentioned the trace file. Here is part of the file that deals with the problem: LORSequencer.exe Information: 0 : DimmingCurveCollection.ReadCurve: C:\Users\JMW\Documents\Light-O-Rama\Plugins\DimmingCurves\Linear_20pct.xml DateTime=2017-11-16T23:31:31.2487567Z LORSequencer.exe Error: 0 : DimmingCurveCollection.ReadCurve: System.Xml.XmlException: '<', hexadecimal value 0x3C, is an invalid attribute character. Line 19, position 3. at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr) at System.Xml.XmlTextReaderImpl.ParseAttributes() at System.Xml.XmlTextReaderImpl.ParseElement() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlReader.MoveToContent() at System.Xml.XmlReader.IsStartElement() at ‪‫‫‭‍‍‌‬‎‭‎‏‫‪‭‎‬‍‏‎‬‮.‏‭‎‍‪‏‪‮‏‎‭‏‮‎‍‭‮(String ) DateTime=2017-11-16T23:31:31.2517579Z LORSequencer.exe Information: 0 : DimmingCurveCollection.ReadCurve: C:\Users\JMW\Documents\Light-O-Rama\Plugins\DimmingCurves\Linear_20pct_For_Sign.xml DateTime=2017-11-16T23:31:31.2517579Z LORSequencer.exe Error: 0 : DimmingCurveCollection.ReadCurve: System.Xml.XmlException: '<', hexadecimal value 0x3C, is an invalid attribute character. Line 19, position 3. at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr) at System.Xml.XmlTextReaderImpl.ParseAttributes() at System.Xml.XmlTextReaderImpl.ParseElement() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlReader.MoveToContent() at System.Xml.XmlReader.IsStartElement() at ‪‫‫‭‍‍‌‬‎‭‎‏‫‪‭‎‬‍‏‎‬‮.‏‭‎‍‪‏‪‮‏‎‭‏‮‎‍‭‮(String )
  24. Dimming Curve Question

    Matt: I have tried that. I have even rebooted the computer. I still do not see my dimming curve. Is there a required file name or will it list anything in that directory? Jim
  25. Conversion Issue

    I have just converted a file that I used in 2012 (whatever sequencer version was in use at that time). All of the sequencing information is there from all of the channels. However, many of the channels are listed in red in the "view" or left side of the sequencing window. These channels will not play in the Design Preview window. These channels are in the same relative position now that they were in the original 2012 file. Why would they be in red? I assume that this means there is no match between the two for some reason. I also realize that they have been archived for some reason. What makes this even stranger is that some channels/controllers further on down in the file show in black and do work in the Design Preview window. I think that it might have something to do with the fact that the channels/controllers that don't work are now in a different network than they were in 2012, but that is just a guess. If, so why would that matter? I also note that none of the channels, whether or not they work in the preview window, are listed as a part of their prop groups; they are all listed as individual channels only. I have also noted that the sequencing associated with the archived channels cannot be copied. Anyone have any ideas? What would be a relatively easy way to fix this? We need an easy way to convert archived channels to active current prop channels. Also, why can't the sequencing for these channels be copied to another set of active prop channels? I finally figured out how to restore the channels to active service using "Sequence Manage Archived Props". Now at least I can copy the sequencing to an active prop. However, I have another question. How do I force one of these channels to become a part of an existing prop? With the conversion problem described above, I hope that there is a way to tell these channels, once they are activated, that they are part of a prop. Otherwise, do we have to manually add the current prop to the view and then copy the sequencing to it, then remove the old channels? That is a lot of extra work. Jim
×