View Full Version : LedTriks and Vixen V2.0.0.14
biffklg
06-02-2007, 01:25 PM
I just ran and updated Vixen and also deleted the 2 files mentioned in the notes. I didnt see that at first and it caused a windows error without deleting them and the program shut down after the microsoft error reporting thingy. I am just testing the LedTriks with it at this time and noticed the loop checkbox, NICE. I have a question about the looping though. Is it my computer (not super slow, but not superfast either) that is causing the slight hang at the beginning of the 2nd and furthur loops? I have a homebuilt AMD Sempron 2600+ running at 1.6GHz with 1.5GB of memory. I made a quick video clip on my YouTube account to show you what I mean.
http://www.youtube.com/watch?v=icb_8lsAu70
There shouldn't have been any sort of significant error like you experienced. I knew there was potential for trouble with this update because there were big LedTriks changes behind the scenes to allow for LedTriks scripting.
Your computer greatly exceeds mine, so its a problem on my end. It's difficult for me to diagnose at this point as I run my LedTriks sequences through a 595 for the time being, but I will try to duplicate it.
biffklg
06-02-2007, 10:29 PM
Ok, here is what I was doing. I made a routine and saved it with the organize frames screen. (I love that screen) I then loaded it into all 4 of the clipboards. I then went to the 1st clipboard and drug it up to the beginning of an empty ledtriks sequence. I then grabbed #2 clipboard and added that to the end of the 1st. Then I grabbed the 3rd one and drug it up behind the 2nd and when I dropped it into place I got this error:
************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeExceptio n(ExceptionArgument argument, ExceptionResource resource)
at System.ThrowHelper.ThrowArgumentOutOfRangeExceptio n()
at System.Collections.Generic.List`1.get_Item(Int32 index)
at LedTriks.FrameOrganizationDialog.GetFrameEndTime(I nt32 index, List`1 frames)
at LedTriks.FrameOrganizationDialog.CalcSelectionSpan ()
at LedTriks.FrameOrganizationDialog.FrameOrganization Dialog_MouseUp(Object sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseUp(MouseEventA rgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
at System.Windows.Forms.ContainerControl.WndProc(Mess age& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************************************************** ***
I hit continue and then tried the 3rd clipboard thing again and it worked as well as dragging the 4th clipboard up there.
I have no clue what that means, maybe I did something wrong... Just thought I would let you know...
If you were able to do something wrong (which you didn't), it was only because I allowed you to do so. Thank you for the stack trace.
biffklg
06-03-2007, 10:13 AM
This is how I came about to find this error. This is repeatable. Go to a new ledtriks event sequence. Type in something in the test bar and click create. click the start from the 1st frame button and before it gets done click on the remove all button and click yes. If the ledtriks is set up as preview with no plug-ins assigned it will have a windows crash and error reporting thing and vixen will be closed.
That would explain it! Easy enough to fix.
Powered by vBulletin® Version 4.1.10 Copyright © 2012 vBulletin Solutions, Inc. All rights reserved.