search

bitfocus / companion-module-studiocoast-vmix

Studiocoast vMix module for Bitfocus Companion
MIT License
32 stars 10 forks source link

Module crashing to "Unknown Stopped" state after some period of time. #214

Closed DanielWilliamsMSC closed 1 year ago

DanielWilliamsMSC commented 1 year ago

Describe the bug Module crashing to "Unknown Stopped" state after some period of time.

To Reproduce Leave vMix and companion idle for >4 hrs (at least, unsure on timeframe)

Expected behaviour Stays connected

Screenshots image

System (please complete the following information):

Additional context Seems to be when leaving unattended, vmix and companion run on the same machine. Other companion modules are staying connected. vMix is still running and works correctly. Disabling and re-enabling the vMix module immediately reconnects.

Have tried creating a trigger like this to fix, however whatever is happening, doesn't fire the trigger.

image

thedist commented 1 year ago

If vMix is idle then it could simply be the TCP connections are being dropped for inactivity by the system.

Please try the latest Beta build as we already have a change in place to help alleviate issues from systems/networks from dropping inactive connections.

Julusian commented 1 year ago

Stopped looks like Companion stopped the module for some reason and didnt restart it. I don't know why it would be doing that though

thedist commented 1 year ago

@DanielWilliamsMSC Can you please try the latest Companion Beta build and let me know if you continue to experience these issues.

thedist commented 1 year ago

If you're still having issues with the Beta version, check your log for the instance (the >_ icon on the Connections tab) and see if anything shows there.

Also, while running vMix go to its API page of the web interface, http://localhost:8088/api (replacing localhost with the IP of where you're running vMix, and 8088 with the Web Interface port) and then copy/paste the data into a text file so that I can try see if I can replicate the issue you're experiencing as right now I can't replicate it.

Also, one option to try to improve performance is to go to the instance config and toggle off the options Input Variables by Name/Number/GUID, and toggle on the Limit input Variable Types option under those. This will reduce the input variables that are available within Companion, but this can improve performance.

thedist commented 1 year ago

No further info so closing for now.