[BUG]internal: Wait internal: Wait

[tobamiester]

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

I running Companion on a RasperryPie 4b using a Streamdeck XL. I use it to control OBS and an ATEM Extreme. I have a bunch of buttons that play video ads used during my broadcasts (by going to an OBS scene which contains the video source). While the video runs it does an 'Internal' wait before then moving back to a different OBS scene.
On occasion it completely messes up the internal wait and flips back to the target OBS scene, cutting off the video. Any ideas why its doing this ? Bug ?

Steps To Reproduce

Inconstent. Sometimes will work fine, but others it will completely mess up the video length which is a problem for my broadcast/

Expected Behavior

Consistent Wait.

Environment (please complete the following information)

- OS:Mac
- Browser:Chrome
- Companion Version: 3.5.1

Additional context

No response

[Julusian]

This sounds like its going to be a pain to reproduce, which is going to make diagnosing this hard..

What kind of duration are these delays? Is it at all consistent in how long into them they fail?
Is it at all predictable/consistent in how it goes wrong?
Could it be another button press that causes this? Or something not companion?

What does the log show around the time this happens?

[tobamiester]

Sorry for the delay in responding.

On button press, it switches to an OBS scene that contains one source which is a video file. While the video plays , the videos plays around 30 seconds, i set a wait of about 31000ms, and after which it switches back to a different OBS Scene. I'm not sure about consistency in terms of when the Wait fails. usually its pretty quick, like 2-3seconds in.

No other buttons are pressed.
Couldn't find anything in any log files (I was looking on the Raspberry Pi but wasn't sure where the log was. The on-screen one didn't seem to show anything obvious.

I seem to have found a workaround. I'm not sure if it's the new v4.5.1 functionality that is solving the issue. But using an Internal Action (Sequential) , seems to work; consistently so far.

I've attached a couple of screenshots of both scenarios.

The original_failing_button.jpg just shows how I had the button configured (ignore the 10000 timing as this is basically a mock up of the button that I have since changed).

The file new_button_design.jpg shows how I configured it to use the Internal Action.

Let me know your thoughts.

Thankyou.

[Julusian]

both those screenshots look the same to me.

but using a similar same setup, (using an 'internal: custom variable: set with expression' instead of obs actions) I am not able to reproduce an issue here.