bitfocus / companion

Bitfocus Companion enables the reasonably priced Elgato Stream Deck and other controllers to be a professional shotbox surface for an increasing amount of different presentation switchers, video playback software and broadcast equipment.
http://bitfocus.io/companion
Other
1.63k stars 505 forks source link

Cue list / Play list #116

Open PerRoine opened 6 years ago

PerRoine commented 6 years ago

Describe the feature A Cuelist or Playlist to stack up actions which then can be assigned to buttons like Go Fwd, Go Back, Jump Fwd, Jump Back and reset if we added auto-follow option to each Cue in the list as well we would have a Huge Workflow improvement

Usecases Stack up Powerpoints and have listeners open and close them in the right order with the push of a button, stack up a series of actions to perform complex transitions, either because the devices are not capable them self or because it's a drag to program complex things involving other equipment

haakonnessjoen commented 6 years ago

I'm not sure how we would do this the best way, but I think CasparCG would need this to be very useful. Ref: #105

M4TSON commented 4 years ago

I have no idea has this thing gone any further, but I have an idea how this could be possible. Except I really don't know how to program it.

But I will try to explain it with pictures... companionqlist This is an example how this cuelist could look like. Basically the cues are like buttons but the button actions are just arranged to a certain order. Also the cues might need a wait time, because there might be situations that we need to wait for fades or something like that. Also follow could be quite handy.

companionqlist2 Cuelist tool could be in the menu on the left. Same place with the web buttons and the emulator.

companionqlist3 We need to be able to control this cuelist somehow. So I would say that we need to be able to set and assign few buttons for the cuelist. As mentioned earlier (Go Fwd, Go Back, etc...). It would be quite handy if there is some sort of option to choose which buttons are controlling the cuelist. Also we need to be able to choose what those buttons are doing, that might easier to do it from the dropdown menu as usually.

Is this the dummest idea ever or is it doable??

jwnremt commented 4 years ago

As a simple temporary solution could you just make it possible to copy the buttons via OSC then you could build all of your buttons on say page 99 then as you need them you have commands sent that "bring them forward" into the order you need them for your show. i.e. /copy/bank/99/1/to/1/1 then you could automate this process using cues in a software program like QLab or using another button.

I could see this useful if you have a show that has a set order but needs the flexibility of having multiple options. Rather than having to scroll through every option you could just have the few options needed for that "scene" brought to your fingertips. Technically this can already be done by creating new pages and recalling the Page by OSC, however, if you need most of your buttons to stay the same and only need to change a few then this would make for a lot of very similar pages that could lead to clutter and confusion quite quickly.

M4TSON commented 4 years ago

Actually if Companion can receive OSC commands from other softwares and use it for button commands, then this discussion is kind of pointless. Because for example qlab is already quite good cue based program for osc commands.

My suggestion was more or less for that somebody who might have taken this to his ToDo list. And if this cuelist thing is coming as addition for Companion.

jwnremt commented 4 years ago

Yes, any button can be fired via OSC or http commands. (OSC Port 12321)

/press/bank/1/1

All the way through

/press/bank/99/32

As it comes, you have 2,871 available buttons that can be brought all the way up to 3,168 if you were to remove your navigation buttons.

On Mar 4, 2020, at 4:32 AM, M4TSON notifications@github.com wrote:

Actually if Companion can receive OSC commands from other softwares and use it for button commands, then this discussion is kind of pointless. Because for example qlab is already quite good cue based program for osc commands.

My suggestion was more or less for that somebody who might have taken this to his ToDo list. And if this cuelist thing is coming as addition for Companion.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion/issues/116?email_source=notifications&email_token=AOT5BL6UK47S73RJKPBFCBLRFY34LA5CNFSM4FGT5JW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENXOD4A#issuecomment-594469360, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOT5BL4VQA765AALNVO2MOLRFY34LANCNFSM4FGT5JWQ.

krocheck commented 2 years ago

1630

JEK58 commented 2 years ago

I came here by searching if what I have in my mind is already listed:

A cue list from buttons.

For example:

Press buttons (or multiple) in your preferred order and then fire this button presses with a next/prev buttons on a separate page. Complex openings or transitions in vMix for example would be a use case for this.

MeestorX commented 2 years ago

v3's "step actions" will give you some of this functionality. They're amazing.