Feature Request: Labeling Multipart Cues

I use a lot of multipart cues, and use label a ton for notes for dance.

In a standard cue, pressing [label] once in the cue brings up the cue label for that cue.  Additionally, clicking the label section of the playback list for a cue brings up the label for that cue for modification.

If a cue is a multipart cue, when pressing [label] once the in the cue, EOS defaults to labeling part 1.  This is particularly annoying when I've split a cue into a multipart after labeling the cue.

I'm requesting:

1) Pressing [label] when in a cue with multiple parts would default to labeling the base cue

2) Clicking the part in a multipart cue would bring up the label function

Thanks



  • CUE [100] PART [1] LABEL
    give what you ask for



  • That are all option i find for label Cues:

    Timecode:
    CUE [1]/ {EXECUTE} {TIMECODE} [X] ENTER
    (you will get in the TC Colume the Timecode times from ShowControl, you can make only one TC per Cuelist visible) 

    Ext Links:
    CUE [1] {EXECUTE} {MORE SOFTKEYS} {STRING} (insert a "free" text) ENTER
    ( i think/hope this free text will have no effect for any other operations)

    Name:
    CUE [100] LABEL
    (label the complete Cue)

    Cue-Part Name:
    CUE [100] PART [X] LABEL
    (give every Cue Part his own label, this is the only option i know for label every Cue-Part separate)

    Notes:
    CUE [100] SHIFT LABEL
    (give a note for the complet Cue, Part Notes not possible)

    Scene:
    CUE [100] {ATTRIBUTE} {SCENE} (insert the text you wanna add) ENTER
    (give the green line with grey text in, above the Cue you wanna discribe)

    Scene End:
    CUE [100] {ATTRIBUTE} {MORE SOFTKEYS} [SCENE END} ENTER
    (give a green line under the Cue, you can`t add any text here)

    ---------------------------------------------------------------------------

    In my workflow i use Cue Parts for slower-faster-delayed Fixtures/Parameters and discribe in the Cue Part what will happen slower-faster-delayed.
    Notes i use for discribe the action for GO.

  • I am fully aware of how to label the cue parts, I am asking that the system be changed so that when only pushing [label] it defaults to the base cue.

    I write cue timing notes for dance pieces in labels, and it's a lot faster to type [LABEL] :34 [ENTER] than [CUE] 3415 [LABEL] :45 [ENTER].  

  • Do i missunderstand now?
    If you do
    [LABEL] [:45] [ENTER]
    you will ever label the base Cue.
    Depends which cue have the golden border.

    If you want label a Cue Part -or label a cue that is not shown in command line- you must press some knobs more

  • Maybe just for inspiration.
    I have create a Magic Sheet for see what will when and why happen in the show...
    Of corse, the notes i must give all manual, also the Timecode times.
    Also if a Cue is a Autofolow Cue.

    In a Drama-Show i will write down as note, Side in textbook, if it is a keyword given by Actor or is it an action the Actor do, or, or, or,....

  • If we are in Cue 100 from your example above, and just hit [LABEL] [:45] [ENTER], that label will apply to Part 1 of Cue 100, not the base cue of 100. 

  • Ah,.... now i see what you mean.
    I think this is a bug.
    Because EOS highlight the Cue-Part 1 and not the Base Cue

  • If this is a bug, it's been the case since at least 2.4.  I've been frustrated with this minor thing for years.



  • Hope you can see it.
    You see in Cue 79 the Highlight for the Cue is visible.
    Then i press GO, the Highlight change to Cue 100 Part 1.
    I also expect the Highlight will go to Cue 100 base
    If i hide Cue Parts the Highlight is not longer visible.

    I am shure it is a bug.

    I am not shure about.
    But if i remember right it is "new" you can record a Cue Part 1.
    In older Versions if you want record Cue Part 1 it was not possible.
    You have can only ever record Cue Part 2
    (or i have ever type a wrong syntax)
    Maybe because the Base Cue was ever Cue Part 1?
    But about this i am not shure...

  •  Eos Family Feature Requests
    We have a forum for feature requests with a +1 feature that is pretty handy!

  • But,...... first we must know...
    Is it a Bug or a Feature?
    GrinGrinGrin

Related