[BUG] Companion if statement - Hyperdeck clip (name)

[Carl-Drogo]

Make sure you're on the latest stable or beta build

• I have tested this on the latest stable or beta release

Is this a bug in companion itself or a module?

• I believe this to be a bug in companion and not a specific module

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I believe the Internal: Logic: If Statement, When true: Hyperdeck active clip name to be bugged.

I'm creating a button that has the Hyperdeck go to a specified clip, then look to see if it's actually on that clip, and if true, play the clip. This way if a clip does exist on the SD card it will play, if that clip does not exist nothing will happen.

Steps To Reproduce

"Playback" is the name of the Hyperdeck

Action 1 - Playback: Goto Clip (name) "x" (this works)
Action 2 - internal: Logic: If statement
When True - Playback: Active Clip (name) "x" (Invert is not selected. Slot ID = Any)
Then - Playback: Play

Expected Behavior

Clip "x" should start to play. Currently, nothing happens.

Environment (please complete the following information)

- OS:MacOS 15.6.1
- Browser: Chrome 139.0.7258.157
- Companion Version: Latest Stable 4.0.3

Additional context

[Julusian]

While I can understand the frustration/confusion of this not working as you expect, I dont think this is a bug, or at least is not something that we can really fix.

The key thing to note here is that by default we run all the actions in parallel; so at the same moment we send to the command to the hyperdeck you are checking what clip is loaded, so the hyperdeck wont have had an opportunity to respond.

But even if you put this inside a group set to sequential, I am not sure it would work.
What I believe would happen is that when we tell the hyperdeck to load the clip it does so and acknowledges our command. A few ms later it will then report its new status which includes that clip being loaded.
Because of the very small delay in this status, we will be receiving that status after the if condition has been checked, resulting in those actions not running as you expect.
So to me, this is expected behaviour.

Maybe we could do better and do some optimistic updates, but that introduces risk of mistakes if an action fails. And might require updating every module to handle that if we want the experience to be consistent.

So I suggest try putting them in a group set to sequential which might or might not work, or add a short wait between them (you will need to try different durations until you find something reliable), to allow the hyperdeck to report its new state before you check if the clip loaded

[LikeThisReview]

I also believe it is not working as expected. When I select the file name of the active clip it the feedback in When True does not recognize it. Same result if I type in the file name manually. Also, adding " hyperdeck: Active Clip (name)" under Feedback (and not under actions) does not recognize it. So I think this bug needs to be transferred to the hyperdeck module.

In the mean time Carl-Drogo can use workaround "internal: Variable: Check boolean expression" with expression $(hyperdeck:clipName) == file-name without extension.

Note. Condition "hyperdeck: Active Clip" work just fine.

[LikeThisReview]

Weird, did another test on condition "hyperdeck:Active Clip (name") with copy-paste of the value from the Variables View and that actually worked. But manually typing the same value does not work. It show that it is adding the file extension (.mov in my case) for a moment and then reverts back to displaying the data entry without the file extension

[G8YTZ]

When I look at the status from the Hyperdeck the clip names are thus:
ClipName":"BBC Test Card HD GB3JT 2025.png","ThumbName":"BBC Test Card HD GB3JT 2025.png"

But if I log using Companion the clip names returned on the log are:
info: Clip " BBC Test Card HD GB3JT 2025.png" does not exist
info: Clip " GB3JT PM Funk.mp4" does not exist

Where did the space in front of the clip name come from? I have exactly the same arrangement working on an older version of Companion without issue, and no spaces.

I've found a work-round.
The issue is the time between selecting a video clip and the action of playing the video from the "Triggers". If yo put in a 200ms delay the problem is solved. It seems that the later version of Companion is much quicker at sending commands to the media player and the media player needs more time to "cue up" and load the clip. When I back-revved the Hyperdeck module there was an improvement, likely because the older code introduced its own delay.

[Carl-Drogo]

When I look at the status from the Hyperdeck the clip names are thus: ClipName":"BBC Test Card HD GB3JT 2025.png","ThumbName":"BBC Test Card HD GB3JT 2025.png"

But if I log using Companion the clip names returned on the log are: info: Clip " BBC Test Card HD GB3JT 2025.png" does not exist info: Clip " GB3JT PM Funk.mp4" does not exist

Where did the space in front of the clip name come from? I have exactly the same arrangement working on an older version of Companion without issue, and no spaces.

I've found a work-round. The issue is the time between selecting a video clip and the action of playing the video from the "Triggers". If yo put in a 200ms delay the problem is solved. It seems that the later version of Companion is much quicker at sending commands to the media player and the media player needs more time to "cue up" and load the clip. When I back-revved the Hyperdeck module there was an improvement, likely because the older code introduced its own delay.

I believe I'm doing your work-around suggestion properly, but to no success. I put a 200ms delay both before and after the When True check. I've also attempted to do this within a Sequential Internal: Action Group as was suggested by Julusian with no success.

[G8YTZ]

Here is my version. The delay is between the "goto clip" and "play" sections. It works for me. I think the return that the clip does not exist should say "does not yet exists" in other words it has not loaded yet.

[LikeThisReview]

That’s because you use a different pla action

…

On Mon, 15 Sep 2025 at 21:34, G8YTZ ***@***.***> wrote: *G8YTZ* left a comment (bitfocus/companion-module-bmd-hyperdeck#140) <#140> Here is my version. The delay is between the "goto clip" and "play" sections. It works for me. Screenshot.2025-09-15.at.20.30.35.png (view on web) <https://github.com/user-attachments/assets/05572936-47eb-4ad9-b823-dd8bb5f1aa05> — Reply to this email directly, view it on GitHub <#140>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A25NECCUWDGWVQCQPNQJWXT3S4IDNAVCNFSM6AAAAACGNZ63R2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEOJTGY2DKNZVGM> . You are receiving this because you commented.Message ID: ***@***.***>

[G8YTZ]

There is definitely a bug in Companion. It has stopped working for me again. STICK WITH v2.04 of the module.

If you select a clip to load and look carefully at the selection, you'll find that Companion puts a space in front of the filename. If you remove the space you get a prompt, but it still does not work.

If you modify the trigger it will be ok, until the next change. I was using the 2.04 module version for Hyperfeck, when I went back to 2.5 everything stopped working, going back to 2.04 did not fix that without a reboot.

It's seems that it's all down to that mystery space before the filename.

[Julusian]

I have done a quick test and am not seeing the extra space, but am seeing some inconsistentncy on whether the file extension should be included. It appears that the feedback options include it (but dont show that clearly), but the value it is comparing against does not.

This seems to be consistent back to 2.0.4 for me