[BUG] v3.5.2 is horrendously laggy taking 5 seconds to complete tasks

[BlakesHeaven]

Is this a bug in companion itself or a module?

• I believe this to be a bug in companion

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Since upgrading to Build 3.5.2+7764-stable-fe36af46 everything is taking a long time, to the point that it is practically unusable. When on v3.4.x all button presses were sharpe and immediate.

I beleive it is down to the changes introduced to Custom variables and possibly some knock-on effect in how it interacts with vMix.

I can provide a companion backup and a vMix preset if you PM me, but we make use of the following actions:
vmix: Transition - Transition Mix >>> takes 5-6 seconds to complete

vmix: General - Set Dynamic Inputs and Values

internal: Custom Variable: Set with expression

One button just updates variables. I used to have it set to change $(custom:Set_Cam_To_Move) on button down, and $(custom:Movable_CamA) on button up, which were immediate. Now I have had to introduce a wait of 1.5 seconds minimum, just to wait for the variable change to take effect, else the designed functionallty is broken.

Steps To Reproduce

No response

Expected Behavior

Actions to be quick with no lagg
Variable value changes to be immediate.
Interaction with vMix to be immediate.

Environment (please complete the following information)

- OS: Windows 11
- Browser:Google Chrome
- Companion Version: Build 3.5.2+7764-stable-fe36af46

Additional context

No response

[heisjolly]

I can agree with this experience. I also use vMix and find this version inconsistent. Almost like it 'queues' actions unnecessarily. Having this issue on steroids talking to PTZOptics VISCA endpoints as well.

[BlakesHeaven]

Any chance of getting initial thoughts, please.

Depending on the response and time scales to fix, I may need to downgrade it from the current v3.5.2 back to v3.4.4.

Thankfully I took a backup before the upgrade to 3.5.x took place. I doubt v3.4.4 would be compatible with the later config.

[thedist]

In regards to lag when using vMix, one thing that can be done to reduce the overhead is to go to the connections config in Companion and ensure you only have the variables enabled that you wish to use (For example if you refer to inputs by name, and not number or GUID, make sure number and GUID are disabled). also ensure Limit Input Variable Types is toggled on. This should help reduce the variable set used by the vMix module which has one of the largest performance impact.

As for improving the performance as a whole in both Companion and the modules such as vMix, that is something being looked in to. Personally I'm having difficulty testing myself as even when using an excessively large vMix setup my servers that run Companion don't run in to these sorts of performance issues, as it does seem to just be a subset of users and not everyone experiencing performance issues, but hopefully the improvements being made will help reduce the impact for those who do experience these issues. As for timeline I don't have anything to announce.

[BlakesHeaven]

@thedist , Jeff, Many thanks for the tips. I'll look into limiting variables as you suggested as that make good sense. It still remains the case that it only became an issue after upgrading to 3.5.x

I'll report back after investing tomorrow.

If I can help by suppling my companion config and vMix Preset, please let me know how I can get them to you.

[BlakesHeaven]

I had a look at changing the variables, but found that only the Behringer X32 Soundesk module's would open. Neither vMix nor the three PTZOptics VISCA modules' variables would open. VMix only came up with an application waiting message repeatedly before eventually re-syncing as though F5 had been pressed.

Before I down grade, is there a way of hacking a file to turn unused variables off and also ensure Limit Input Variable Types is toggled on?

[BlakesHeaven]

I managed to open the vMix variables list by not opening vMix and looked though the long list. I realised I was looking in the wrong place for Limit Input Variable Types, but found it and set it to true. I also turned off variables by GUID and by Number.

To be honest, I don't think it was much faster. I Could still press a simple button that only updated a few variables, count "1, 2, 3, 4, 5", and only then see the results on other buttons showing the new variable value used in the titles.

I restored the backup config and then installed v3.4.4. Immediately, all the buttons became responsive. For the example above, I now don't even get to count "1" before seeing the other button titles change as a result. Also a simple vMix transition button is immediately actioned.