3.7 Output Controllers

dononeil said:
I've tested this on 3 machines, 2 of the 3 had older versions of Vixen installed and stopped working, the 3rd had a fresh install. All 3 are Windows 10 machines with all the latest windows patches, same security software (avast/defender), and the same network config.

I've tried un-installing on one of the machines that wasn't working. I cleaned up the Vixen3 folder, re-installed and re-configured the display and it works again.... So something must be amiss with the core code too to make it stop working, or something that MS 'patched' and then patched again.
Click to expand...

Now, when I copy the /My Documents/Vixen 3 folder from the non-working machine to the working machine, to copy all the sequences and fixtures and base config, because it's identical between the 2 machines, it doesn't work. The output controller has a red dot next to it. But when I then remove the controller and re-add it (same element, just patch to new controller ) and then try to open the original test sequence Vixen says Error Trying to open Sequence. But, I can re-create the sequence with this new controller and it works again. The DMX controller doesn't have this problem (DMX Pro on both machines with same port setting)

So it seems like either I'm doing something I'm not supposed to be that is breaking things (copying the Vixen 3 folder from machine to machine), or there is a bug in the core code that stops it from working when this is done.
 
Ok, if you still have one of the older machines that is not working, look in the install folder and see if the ElexolEther dll is a different date than the rest of the files. They should all be the essentially the same date time. After cleaning and reinstalling it works, along with the new machine suggests there is an old or weird version it is picking up on the existing installs.

Post the logs from the new machine with the error opening sequence. I would like to see what error it is complaining about. The sequence has no knowledge of the controller or the patching. All it knows is the effect to element mapping so something odd is going on there.

Here is a test build with some better error handling in the Elexol controller to prevent crashes if something goes wrong and at least produce better error messages. I didn't change any happy path logic, just added better error handling. The cancel button is also fixed. On my machine without hardware this stopped the crashing and provided better messages in the log. If you can test that out, I can update the builds with that better code.

Vixen Test Elexol
 
Yes, I do still have a non-functioning machine. On that machine the .dll date is 10/7/24, version 3.11.1260.1, which matches the same on the working machine.

There is nothing added to the application error log when the file can't be opened, it's like it doesn't see the file any more, even if you go browse to it and open it. Maybe the file got locked somehow?

I'll test out the controller on the non-functioning machine and report back.
 
So I installed the test version over the top of the non-working version. No change, still doesn't work, and there isn't anything showing up in the logs except the info log (I cleared them all first):

12/18/2024 19:58:38.643 [VixenApplication.Program] Vixen app starting.
12/18/2024 19:58:39.557 [VixenApplication.VixenApplication] Starting JIT Profiler
12/18/2024 19:58:39.557 [VixenApplication.VixenApplication] Completed JIT Profiler
12/18/2024 19:58:39.557 [VixenApplication.VixenApplication] Processing Profiles
12/18/2024 19:58:39.569 [VixenApplication.VixenApplication] Finished Processing Profiles
12/18/2024 19:58:39.569 [VixenApplication.VixenApplication] Process info: 8072@PHENOM-MEDIA
12/18/2024 19:58:39.578 [VixenApplication.VixenApplication] Release 3.11u1 - Build #1260
12/18/2024 19:58:39.677 [VixenApplication.VixenApplication] .NET Runtime is: 8.0.6+3b8b000a0e115700b18265d8ec8c6307056dc94d
12/18/2024 19:58:39.709 [Vixen.Sys.VixenSystem] Vixen System starting up...
12/18/2024 19:58:41.281 [VixenModules.App.WebServer.Startup] Webserver started.
12/18/2024 19:58:41.281 [Vixen.Sys.State.Execution.OpeningState] Vixen execution engine entering the open state...
12/18/2024 19:58:41.340 [Vixen.Sys.State.Execution.OpenState] Vixen execution engine entered the open state.
12/18/2024 19:58:41.340 [Vixen.Sys.VixenSystem] Vixen System successfully started.
12/18/2024 19:58:43.370 [VixenApplication.NLogListener] Application.MainWindow is null, cannot subscribe to keyboard events, subscribed to Application.Activated event

Going into the display setup still shows the controller with a red dot beside it, even though you can configure and test it successfully. Also, when you bring up the config/test dialog, the cancel button doesn't work, only the X or OK.

If I remove the controller, then re-add, re-patch and re-configure then the red dot goes away and it starts working, but a ton of these log entries are recorded in the warn log:

12/18/2024 20:02:00.609 [VixenModules.Output.ElexolEtherIO.ElexolEtherIOModule] Elexol Ether I/O: failed to connect to device, not updating the current state.

But it's still working.
 
dononeil said:
So I installed the test version over the top of the non-working version. No change, still doesn't work, and there isn't anything showing up in the logs except the info log (I cleared them all first):

12/18/2024 19:58:38.643 [VixenApplication.Program] Vixen app starting.
12/18/2024 19:58:39.557 [VixenApplication.VixenApplication] Starting JIT Profiler
12/18/2024 19:58:39.557 [VixenApplication.VixenApplication] Completed JIT Profiler
12/18/2024 19:58:39.557 [VixenApplication.VixenApplication] Processing Profiles
12/18/2024 19:58:39.569 [VixenApplication.VixenApplication] Finished Processing Profiles
12/18/2024 19:58:39.569 [VixenApplication.VixenApplication] Process info: 8072@PHENOM-MEDIA
12/18/2024 19:58:39.578 [VixenApplication.VixenApplication] Release 3.11u1 - Build #1260
12/18/2024 19:58:39.677 [VixenApplication.VixenApplication] .NET Runtime is: 8.0.6+3b8b000a0e115700b18265d8ec8c6307056dc94d
12/18/2024 19:58:39.709 [Vixen.Sys.VixenSystem] Vixen System starting up...
12/18/2024 19:58:41.281 [VixenModules.App.WebServer.Startup] Webserver started.
12/18/2024 19:58:41.281 [Vixen.Sys.State.Execution.OpeningState] Vixen execution engine entering the open state...
12/18/2024 19:58:41.340 [Vixen.Sys.State.Execution.OpenState] Vixen execution engine entered the open state.
12/18/2024 19:58:41.340 [Vixen.Sys.VixenSystem] Vixen System successfully started.
12/18/2024 19:58:43.370 [VixenApplication.NLogListener] Application.MainWindow is null, cannot subscribe to keyboard events, subscribed to Application.Activated event

Going into the display setup still shows the controller with a red dot beside it, even though you can configure and test it successfully. Also, when you bring up the config/test dialog, the cancel button doesn't work, only the X or OK.

If I remove the controller, then re-add, re-patch and re-configure then the red dot goes away and it starts working, but a ton of these log entries are recorded in the warn log:

12/18/2024 20:02:00.609 [VixenModules.Output.ElexolEtherIO.ElexolEtherIOModule] Elexol Ether I/O: failed to connect to device, not updating the current state.

But it's still working.
Click to expand...
That info log suggests you were not running the new test build since it shows Release 3.11u1 - Build #1260. The test build installs to a separate path in program files and should have its own shortcut. The release and test build will live side by side so you can have both installed.
 
I thought it showed the test version, but it obviously didn't. I cleared the logs and ran it again, and here's what shows up in the info log:

12/19/2024 08:33:05.911 [VixenApplication.Program] Vixen app starting.
12/19/2024 08:33:06.816 [VixenApplication.VixenApplication] Starting JIT Profiler
12/19/2024 08:33:06.816 [VixenApplication.VixenApplication] Completed JIT Profiler
12/19/2024 08:33:06.816 [VixenApplication.VixenApplication] Processing Profiles
12/19/2024 08:33:06.826 [VixenApplication.VixenApplication] Finished Processing Profiles
12/19/2024 08:33:06.826 [VixenApplication.VixenApplication] Process info: 9240@PHENOM-MEDIA
12/19/2024 08:33:06.826 [VixenApplication.VixenApplication] Test Build
12/19/2024 08:33:06.826 [VixenApplication.VixenApplication] .NET Runtime is: 8.0.6+3b8b000a0e115700b18265d8ec8c6307056dc94d
12/19/2024 08:33:06.868 [Vixen.Sys.VixenSystem] Vixen System starting up...
12/19/2024 08:33:08.471 [VixenModules.App.WebServer.Startup] Webserver started.
12/19/2024 08:33:08.471 [Vixen.Sys.State.Execution.OpeningState] Vixen execution engine entering the open state...
12/19/2024 08:33:08.522 [Vixen.Sys.State.Execution.OpenState] Vixen execution engine entered the open state.
12/19/2024 08:33:08.522 [Vixen.Sys.VixenSystem] Vixen System successfully started.
12/19/2024 08:33:10.848 [VixenApplication.NLogListener] Application.MainWindow is null, cannot subscribe to keyboard events, subscribed to Application.Activated event
12/19/2024 08:34:01.852 [Vixen.Sys.VixenSystem] Vixen System stopping...
12/19/2024 08:34:01.852 [Vixen.Sys.State.Execution.ClosingState] Vixen execution engine entering the closing state...
12/19/2024 08:34:01.998 [Vixen.Sys.State.Execution.ClosedState] Vixen execution engine entered the closed state.
12/19/2024 08:34:02.023 [VixenModules.App.WebServer.Startup] Webaerver is stopping...
12/19/2024 08:34:02.031 [Vixen.Sys.VixenSystem] Vixen System successfully stopped.
12/19/2024 08:34:02.031 [VixenModules.App.WebServer.Startup] Webserver stopped.

No other logs had anything. The testing was successful.
 
Ok, if everything works, I would not expect to see anything in the other logs. Does the Cancel and Test button work?
 
Yes, both the test and cancel buttons work now.

Keep in mind in order to get it to work I had to remove and re-add the controller.... That's an OK work around if it happens again.
 
Can you zip up and provide the SystemData folder files from before and after you remove and add the controller back. I would like to see what the real differences are. There should a ModuleStore.xml and SystemConfig.xml file.
 
Unfortunately I don't have a non-working one to get the before from anymore... However, if the problem pops up again I will post them here.
 
You must log in or register to reply here.
Back
Top