Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Action triggers from end if clip playback #53

Closed
pscphil opened this issue Jul 7, 2021 · 3 comments
Closed

Action triggers from end if clip playback #53

pscphil opened this issue Jul 7, 2021 · 3 comments

Comments

@pscphil
Copy link

pscphil commented Jul 7, 2021

I am trying to create an action that will let a whole single clip play and end on a camera once the clip has played. Do I have to set the Ms to the duration of the clip or should it be able to cut at the end of the clip?

@pscphil pscphil changed the title Cin Single Clip Playback Jul 7, 2021
@sphlabs
Copy link
Collaborator

sphlabs commented Nov 2, 2021

Since you are talking about cutting and cameras, I assume your setup includes a Hyperdeck and a switcher of some sort (ATEM perhaps?). So I think you are asking if an event on a Hyperdeck could trigger an action in Companion?

This might be possible with the Triggers section in Companion. You could try building a trigger with Feedback conditions, that check for a certain clipID and then the status, or timecode value.

@sphlabs sphlabs changed the title Single Clip Playback Action triggers from end if clip playback Nov 2, 2021
@AndyHuska
Copy link

AndyHuska commented Dec 15, 2021

(Copied this from one of my recent Slack posts)

I’ve modified my fork of bmd-hyperdeck to allow the storing of timecode variables (in this case just two specific ones, for now, In Point and Out Point). I’ve also added the ability for the module to programmatically press a button when the timecode hits the Out Point. My usage is to mark In and Out, be able jump to them quickly to verify, then start playback with a button action that also arms a button press (user selectable in the action) at Out to tell my ATEM to crossfade to a different input (since it can push any button you can have anything happen). It also does timecode math to store the segment duration as a variable for use, such as sending that time to ProPresenter for a countdown timer.

I imagine this could be made more generic as a timecode trigger. I thought about using the global triggers and storing state variables, but it seemed to spread logic across too many places and possibly introduce some race conditions.

If there's enough interest and some synergy in the design I'd be happy to clean it up and make a pull request.

@sphlabs
Copy link
Collaborator

sphlabs commented Jan 16, 2023

I believe it is now possible to achieve what you describe with the current module.

You can use the status of a hyperdeck as part of a trigger (playing, stopped, etc). Combined with custom variables, you could create an action that triggers when it is 'armed' (with a custom variable) and when the status changes to stopped. You could even add a condition for a specific clip by name, with the clipName variable.

@sphlabs sphlabs closed this as completed Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants