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
Cue list / Play list #116
Comments
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 |
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. |
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. |
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 ***@***.***> 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 <#116?email_source=notifications&email_token=AOT5BL6UK47S73RJKPBFCBLRFY34LA5CNFSM4FGT5JW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENXOD4A#issuecomment-594469360>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOT5BL4VQA765AALNVO2MOLRFY34LANCNFSM4FGT5JWQ>.
|
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. |
v3's "step actions" will give you some of this functionality. They're amazing. |
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
The text was updated successfully, but these errors were encountered: