search

bitfocus / companion-module-figure53-qlab-advance

MIT License
3 stars 7 forks source link

Feature Wish List #103

Open istnv opened 8 months ago

istnv commented 8 months ago 
          Thanks,  I hadn't noticed the workspace option on the setup page.

A lot of the features that would be good to have added aren't even Qlab5 specific. They could be added to the regular Qlab module as they don't need feedback, it's just that that module doesn't allow for passcode either. `This is why I suggest adding the ability to write our own OSC messages, with option to send string, integer, or float arguments, much like standard companion OSC module.

The features that need OSC feedback that would be great to have options for are things like, being able to get output names from Qlab. I know it's possible to get the names, if these could be stored in a variable, so they could be displayed on a button, you could easily see which output fader you were going to bump the level of, PA L, PA R, Sub, Surround etc etc, rather than just 1, 2, 3, 4, etc.

Toggles for things that don't have a control to toggle, where it is possible to query the state. Such as loop last slice, or integrated fade on off.

Similar to output fader names mentioned above it would be good to be able to get output patch names for things like network, MIDI and anything with an audio output.

A variable for unique cue ID. Then the ability to make new cues. When you do this Qlab returns the unique cue ID of the new cue, this could be saved in that variable and then used.. For example, for moving cues into a recently created group. Or for retargeting cues to the new cue.

Command to save the unique cue ID of the selected cue. It could go in the same previously mentioned variable, but we could then access that variable in other commands.

Really most of the commands that Qlab can receive via OSC it would be good to be able to access, there are an awful lot of them, so if we could just write them ourself it would surely simplify your coding. but to have some more variables, as mentioned above that could be integrated into user messages would help hugely.

Sorry, this was a long response. There is more I'm sure, but this was what came to the top of my head.

Originally posted by @Limitedheadroom in https://github.com/bitfocus/companion-module-figure53-qlab-advance/issues/82#issuecomment-1493320953

dherlein commented 1 month ago

It would be helpful to have a variable/feedback for the flagged status of the playhead cue

dherlein commented 1 month ago

Would also be nice to have a variable for a specific cue name/notes (not just playhead cue or running cue) This way buttons could be dynamically updated for hotkeys (play specific cue) without having to open Companion

istnv commented 1 month ago

@dherlein Cue name variable is already available. From the Help document:

$(INSTANCENAME:q_{num}_name)    Name of the QLab cue number {num}. See below for certain restrictions.
$(INSTANCENAME:id_{ID}_name)    Name of the QLab cue ID {ID}. See below for certain restrictions.

It is not usually listed since there can be hundreds or more. There is an option on the configuration tab to expose these.

dherlein commented 1 month ago

Sorry I missed that. Thanks! Works Great!