Vixen 3.0 and the *nix

**chilloutdocdoc** · 12-28-2011, 03:38 PM

After a fruitful endeavor of compiling and installing mono from source, downloading Vix 3.0 to my Ubuntu 10.10 x64 machine, and getting the startup screen to run... It crashed :/

Missing method System.Windows.Forms.SplitContainer::BeginInit() in assembly /usr/local/lib/mono/gac/System.Windows.Forms/4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll, referenced in assembly /home/josh/Downloads/Vixen/Common/CommonElements.dll
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.MissingMethodException: Method not found: 'System.Windows.Forms.SplitContainer.BeginInit'.
at CommonElements.Timeline.TimelineControl..ctor () [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) CommonElements.Timeline.TimelineControl:.ctor ()
at VixenModules.Editor.TimedSequenceEditor.TimedSeque nceEditorForm.InitializeComponent () [0x00000] in <filename unknown>:0
at VixenModules.Editor.TimedSequenceEditor.TimedSeque nceEditorForm..ctor () [0x00000] in <filename unknown>:0
at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (System.Reflection.MonoCMethod,object,object[],System.Exception&)
at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
at System.Reflection.MonoCMethod.Invoke (BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
at System.Reflection.ConstructorInfo.Invoke (System.Object[] parameters) [0x00000] in <filename unknown>:0
at System.Activator.CreateInstance (System.Type type, Boolean nonPublic) [0x00000] in <filename unknown>:0
at System.Activator.CreateInstance (System.Type type) [0x00000] in <filename unknown>:0
at Vixen.Module.Editor.EditorModuleManagement._GetEdi torUI (IEditorModuleDescriptor descriptor) [0x00000] in <filename unknown>:0
at Vixen.Module.Editor.EditorModuleManagement.Get (System.String filePath) [0x00000] in <filename unknown>:0
at Vixen.Sys.ApplicationServices.CreateEditor (System.String sequenceFilePath) [0x00000] in <filename unknown>:0
at VixenApplication.VixenApplication.<initializeEdito rTypes>b__2 (System.Object sender, System.EventArgs e) [0x00000] in <filename unknown>:0
at System.Windows.Forms.ToolStripItem.OnClick (System.EventArgs e) [0x00000] in <filename unknown>:0
at System.Windows.Forms.ToolStripMenuItem.OnClick (System.EventArgs e) [0x00000] in <filename unknown>:0
at System.Windows.Forms.ToolStripMenuItem.HandleClick (Int32 mouse_clicks, System.EventArgs e) [0x00000] in <filename unknown>:0
at System.Windows.Forms.ToolStripItem.FireEvent (System.EventArgs e, ToolStripItemEventType met) [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) System.Windows.Forms.ToolStripItem:FireEvent (System.EventArgs,System.Windows.Forms.ToolStripIt emEventType)
at System.Windows.Forms.ToolStrip.OnMouseUp (System.Windows.Forms.MouseEventArgs mea) [0x00000] in <filename unknown>:0
at System.Windows.Forms.ToolStripDropDown.OnMouseUp (System.Windows.Forms.MouseEventArgs mea) [0x00000] in <filename unknown>:0
at System.Windows.Forms.Control.WmLButtonUp (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
at System.Windows.Forms.ScrollableControl.WndProc (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
at System.Windows.Forms.ToolStrip.WndProc (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
at System.Windows.Forms.ToolStripDropDown.WndProc (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
at System.Windows.Forms.Control+ControlWindowTarget.O nMessage (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
at System.Windows.Forms.Control+ControlNativeWindow.W ndProc (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
at System.Windows.Forms.NativeWindow.WndProc (IntPtr hWnd, Msg msg, IntPtr wParam, IntPtr lParam) [0x00000] in <filename unknown>:0

Didn't know if anybody else had tried the effort yet. It would sure be nice to see a semi-cross platform engine available.
Heck. I'd even be happy if just the output modules worked on my *nix machine... Could sequence on my home computer than ssh into my show computer and play from that

**Materdaddy** · 12-28-2011, 04:03 PM

Haven't tried. I would also love to be able to use Vixen in linux.

I was going to write something to parse vixen files to run on linux, but haven't had much time to devote to that. Partially because I haven't made time since most of the things I've read about Vixen 3.0 say that the event data isn't stored, but the high-level "effects" and the engine will need to run to parse that information into event data to be sent to the controllers. With the vixen 2.0 stuff I was writing, I could simply parse the XML files, base64 decode the event data and spit it out. Very simple. Re-implementing the effects and everything else? not so much!

**Jonpro03** · 12-28-2011, 07:20 PM

Try apt-get install libmono-winforms2.0-cli

**steve** · 06-11-2012, 12:31 PM

The Lumos software I wrote does this (runs on *nix and "plays" sequence files exported from Vixen 2.x). At the moment it's still very alpha (I don't have a sequence editor yet for it and some more sophisticated GUI stuff around the core functionality), but if you just want to create sequences in Vixen and play them back on non-Windows hosts, it might get you where you need to be as an alternative to using mono.

I've been experimenting with my own controller design over the last few years, and thinking seriously about releasing the plans and firmware back to the community like the others are, so I've been thinking it's about time I learned to write Vixen plugins for them too, and I'm guessing that leaping in at Vixen 3 makes more sense at this point, so I'm ramping up on the new Vixen code from that point of view... so if you want a Vixen 3 *nix playback option, I'll probably be inclined to update Lumos' player to be able to import from Vixen 3 as well, would that help?

**Materdaddy** · 06-11-2012, 06:29 PM

Originally Posted by steve

The Lumos software I wrote does this (runs on *nix and "plays" sequence files exported from Vixen 2.x). At the moment it's still very alpha (I don't have a sequence editor yet for it and some more sophisticated GUI stuff around the core functionality), but if you just want to create sequences in Vixen and play them back on non-Windows hosts, it might get you where you need to be as an alternative to using mono.

I've been experimenting with my own controller design over the last few years, and thinking seriously about releasing the plans and firmware back to the community like the others are, so I've been thinking it's about time I learned to write Vixen plugins for them too, and I'm guessing that leaping in at Vixen 3 makes more sense at this point, so I'm ramping up on the new Vixen code from that point of view... so if you want a Vixen 3 *nix playback option, I'll probably be inclined to update Lumos' player to be able to import from Vixen 3 as well, would that help?

I too wrote some proof-of-concept code to do this a while back. Do you have a link for this "Lumos"? It sounds like you've gotten farther than me. I didn't want a UI, I wanted to make a CLI app to run on embedded devices.