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

Feature Request: Play Variations - Feedback #48

Open
ColinMulcahy opened this issue Apr 3, 2021 · 1 comment
Open

Feature Request: Play Variations - Feedback #48

ColinMulcahy opened this issue Apr 3, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@ColinMulcahy
Copy link

Hi,

Is it possible to implement the following features:

FEEDBACK

Although feedback already exists for "Loop Back" and "Single Clip Playback", it's difficult to implement a useful button set.

For example if you had four buttons to define basic play back:

1). Play All - play↵
2). Play All (Loop) - play: loop: {“true”, “false”}↵
3). Play Single - play: single clip: {“true”, “false”}↵
4). Play Single (Loop) - play: loop: {“true”, “false”}↵

It would be great then if you could provide feedback to the button on the status of the playback.

So along side the two feedbacks of showing loop and single as enabled or disabled individually, could you add a third feedback with the four states:

1). Playing All
2). Playing All (Looped)
3). Playing Single
4). Playing Single (Looped)

Therefor taking the two existing feedback actions and combining them with the other two states which would cover the four states.

The “play” command instructs the deck to start playing:

play↵

The play command accepts a number of parameters which may be used together in most combinations. By default, the deck will play all remaining clips on the timeline then stop.

The “single clip” parameter may be used to override this behaviour:

play: single clip: {“true”, “false”}↵

By default, the deck will play at normal (100%) speed. An alternate speed may be specified in percentage between -1600 and 1600:

play: speed: {% normal speed}↵

By default, the deck will stop playing when it reaches to the end of the timeline. The “loop” parameter may be used to override this behaviour:

play: loop: {“true”, “false”}↵

The “playrange” command instructs the deck to play all the clips. To override this behaviour and select a particular clip:

playrange set: clip id: {Clip ID}↵

To only play a certain timecode range:

playrange set: in: {in timecode} out: {out timecode}↵

To clear a set playrange and return to the default value:

playrange clear↵

The “play on startup command” instructs the deck on what action to take on startup. By default, the deck will not play. Use the “enable” command to start playback after each power up.

play on startup: enable {“true”, “false”}↵

By default, the unit will play back all clips on startup. Use the “single clip” command to override.

play on startup: single clip: {“true”, “false”}↵

@ColinMulcahy ColinMulcahy changed the title Feature Request: Play - Feedback Feature Request: Play Variations - Feedback Apr 3, 2021
@sphlabs sphlabs added the enhancement New feature or request label Apr 4, 2021
@LikeThisReview
Copy link

To summarize this request. The play command should allow variables / following parameters:
play: single clip: $(internal:custom_PLAY_SINGLE_CLIP) speed: $(internal:custom_PLAY_SPEED) loop: $(internal:custom_PLAY_LOOP)

In addition to existing Feedback please add hyperdeck variables for single clip {true/false} and loop {true/false}
This way we can use Feedback Boolean Expression on the Buttons.

JaaHann added a commit to JaaHann/companion-module-bmd-hyperdeck that referenced this issue Jun 21, 2024
Added variable support via toggle on following actions:
- Go forward (n) clips
- Go backward (n) clips
- Shuttle with speed (resolving bitfocus#96)
- Play (resolving bitfocus#48)

Added direct variable support on following actions:
- GOTO (TC) (resolving bitfocus#82)
- Jog backward (TC) duration
- Jog forward (TC) duration

Added variable support on following feedbacks:
- Active clip
- Active slot
- Slot/disk status

Added "parseOptNumber" function to "actions.ts" to parse a number from textinput with variables from options object.
Added "parseOptString" function to "actions.ts" to parse a string from textinput with variables from options object.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants