bitfocus / companion-module-zoom-osc-iso

MIT License
7 stars 9 forks source link

Companion crashes with Zoom Iso 2.2.0 #175

Closed mixmexmax closed 5 months ago

mixmexmax commented 6 months ago

We are experiencing crashes of Companion together with the new version of Zoom Iso. Sometimes also Zoom Iso crashes and ends along with Companion. What we do is select a participant by index and then do an iso-output and iso-audio to one of 4 outputs. Selecting works fine, also with feedback, but when we assign the selected to the output it does the command correctly (so the selected Participant populöates the output in Zoom Iso), but then no other function works in Companion relation to the Zoom-Iso/OSC-module. We get this in the log over and over again:

Instance/Wrapper/OSC_ISO1 debug Child is not running, unable to send message: {"direction":"call","name":"variablesChanged","payload":"{\"variablesIds\":[\"internal:time_hms\",\"internal:time_s\",\"internal:time_unix\",\"internal:time_hms_12\"]}"} 02.05.2024 08:49 Instance/OSC__ISO1 verbose "stdout: Starting up module class: u " 02.05.2024 08:49 Instance/OSCISO1 verbose "stdout: Sentry disabled " 02.05.2024 08:49 Instance/OSCISO1 verbose "stderr: Module registration failed Error: Call timed out at t.IpcWrapper.sendWithCb (C:\Program Files\Companion\resources\bundled-modules\zoom-osc-iso\main.js:2:911136) at C:\Program Files\Companion\resources\bundled-modules\zoom-osc-iso\main.js:2:904217 " 02.05.2024 08:49 Instance/Wrapper/OSCISO1 debug Child is not running, unable to send message: {"direction":"call","name":"variablesChanged","payload":"{\"variablesIds\":[\"internal:time_hms\",\"internal:time_s\",\"internal:time_unix\",

Any suggestions?

Using the latest beta as of 1.5.2024 with the 3.12 module of ZoomOSC. Also tried the current stable version that has the 3.11 module, same results. Tried different computers, Companion locally and from another machine etc etc....

digitaldrummerj commented 6 months ago

The provided logs looks to be the Companion log. Can you see if the module log has any errors in it? One of the icons next to the connection on the connections tab will open up the module log.

mixmexmax commented 6 months ago

Yes, this comes out of the module log: module-log-2.5.2024-11_48_35.csv

digitaldrummerj commented 6 months ago

@mixmexmax unfortunately the logs did not provide any useful data as to the cause of the crash. I have a version of the module for you to try out in Pull Request #176 that hopefully will not crash the module but will instead output to the module log the data that it is trying to process when it is erroring. Please give the updated module a try and send me the module log of the error message.

mixmexmax commented 6 months ago

Will do that and give feedback on sunday.

mixmexmax commented 6 months ago

Here is the log I made with the forked version module-log-4.5.2024-21_28_45.csv

digitaldrummerj commented 6 months ago

@mixmexmax can you try clearing the cache in ZoomOSC and see if that fixes it. Can you also upload pictures of the output, audio, and settings tabs in ZoomISO?

mixmexmax commented 6 months ago

Clearing the cache did not change the error in the module log. Yesterday I forgot to mention that with the 3.13 version of the module there are no crashes of the companion-module any more. The selection as well as the switching of video and audio-output seems to work multiple times without failing. What I also tried is use another Audio-device, that did not change anything either. I wanted to rule out that there is a problem with the special character in the name of the audio-device ("SSL2+"). But same thing with audio-device "Monitor" . Here are the requested screenshots:

Bildschirmfoto 2024-05-05 um 14 59 43 Bildschirmfoto 2024-05-05 um 15 00 11 Bildschirmfoto 2024-05-05 um 15 00 28
digitaldrummerj commented 5 months ago

closing at latest version is not having this issue