You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
completed an upgrade to Companion 3.5.2 on Windows 11. Now experiencing continuous connection failure error messages on all 4 installed connections and connection configuration details become inaccessible. The application becomes so busy from connection failures, processing incoming MIDI commands and related triggers can take several minutes. A cold start of the Windows machine will result in normal performance temporarily. The application will eventually exhibit the failure. Launching the GUI generally triggers immediate failure.
Steps To Reproduce
Cold restart of the machine will temporarily clear the error condition
Problem will eventually return
Launching GUI will almost immediately trigger the issue.
Web button interface typically (but not always) continues function normally during the failure
Expected Behavior
Connection configurations should be accessible from the GUI
Incoming MIDI messages and related triggers process immediately
Environment (please complete the following information)
- OS: Windows 11
- Browser: Google Chrome and MS IE
- Companion Version:3.52 (and 3.4.2)
Additional context
The 3.4.2 client was functioning normally before the upgrade. Did a clean install of 3.5.2 after removing all related data configuration folders and uninstalling Companion
Rolling back to 3.4.2 does not resolve the issue. Have a second installation of 3.5.2 on identical windows 11 machine without issue.
The text was updated successfully, but these errors were encountered:
Is this a bug in companion itself or a module?
Is there an existing issue for this?
Describe the bug
completed an upgrade to Companion 3.5.2 on Windows 11. Now experiencing continuous connection failure error messages on all 4 installed connections and connection configuration details become inaccessible. The application becomes so busy from connection failures, processing incoming MIDI commands and related triggers can take several minutes. A cold start of the Windows machine will result in normal performance temporarily. The application will eventually exhibit the failure. Launching the GUI generally triggers immediate failure.
Steps To Reproduce
Cold restart of the machine will temporarily clear the error condition
Problem will eventually return
Launching GUI will almost immediately trigger the issue.
Web button interface typically (but not always) continues function normally during the failure
Expected Behavior
Connection configurations should be accessible from the GUI
Incoming MIDI messages and related triggers process immediately
Environment (please complete the following information)
Additional context
The 3.4.2 client was functioning normally before the upgrade. Did a clean install of 3.5.2 after removing all related data configuration folders and uninstalling Companion
Rolling back to 3.4.2 does not resolve the issue. Have a second installation of 3.5.2 on identical windows 11 machine without issue.
The text was updated successfully, but these errors were encountered: