• State Suggested Answer
  • Date
    liamcorley
  • Date
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 85 subscribers
  • Views 687 views
  • Users 0 members are here

Is it possible to access Scene Labels via OSC?

I am attempting to access scene labels via OSC, with the goal being to end up with a list of all scene labels in my show (ideally with each scene label including a reference to its scene start cue). I have not been able to find any information on scene labels in the OSC documentation, but I tried accessing scene labels like I would with other targets, for example trying:

"/eos/get/scene/count"

This did not work. Am I missing something here, or are Scene Labels not accessible via OSC?

Parents
  • 0

    Scene labels are an attribute of a Cue, so you access them by getting information about cues.

    In my example, CueList 2, Cue 4 is the start of a Scene called "hello"

    /eos/get/cue/2/4

    gives lots of information, including that name toward the end

    [ 15:00:38 ] [15:00:38] TCPOUT [10.101.2.99:3032] [OSC Packet] /eos/get/cue/2/4
    [ 15:00:38 ] [15:00:38] TCPIN [10.101.2.99:3032] [OSC Packet] /eos/out/get/cue/2/4/0/list/0/31, -1(i), AF419B8D-2591-4305-BCC4-A5593B3E2E80(s), (s), 5000(i), 0(i), -1(i), -1(i), -1(i), -1(i), -1(i), -1(i), -1(i), -1(i), False(F), 0(s), 100(i), (s), (s), (s), 0(i), -1(i), -1(i), False(F), -1(i), False(F), (s), 0(i), (s), hello(s), False(F), -1(i)
    [ 15:00:38 ] [15:00:38] TCPIN [10.101.2.99:3032] [OSC Packet] /eos/out/get/cue/2/4/0/fx/list/0/2, -1(i), AF419B8D-2591-4305-BCC4-A5593B3E2E80(s)
    [ 15:00:38 ] [15:00:38] TCPIN [10.101.2.99:3032] [OSC Packet] /eos/out/get/cue/2/4/0/links/list/0/2, -1(i), AF419B8D-2591-4305-BCC4-A5593B3E2E80(s)
    [ 15:00:38 ] [15:00:38] TCPIN [10.101.2.99:3032] [OSC Packet] /eos/out/get/cue/2/4/0/actions/list/0/2, -1(i), AF419B8D-2591-4305-BCC4-A5593B3E2E80(s)

    I can then set that value using the syntax eos/set/cue/2/4/scene=good_bye:

    [ 15:01:55 ] [15:01:55] TCPOUT [10.101.2.99:3032] [OSC Packet] /eos/set/cue/2/4/scene, good_bye(s)


    [ 15:01:59 ] [15:01:59] TCPOUT [10.101.2.99:3032] [OSC Packet] /eos/get/cue/2/4
    [ 15:01:59 ] [15:01:59] TCPIN [10.101.2.99:3032] [OSC Packet] /eos/out/get/cue/2/4/0/list/0/31, -1(i), AF419B8D-2591-4305-BCC4-A5593B3E2E80(s), (s), 5000(i), 0(i), -1(i), -1(i), -1(i), -1(i), -1(i), -1(i), -1(i), -1(i), False(F), 0(s), 100(i), (s), (s), (s), 0(i), -1(i), -1(i), False(F), -1(i), False(F), (s), 0(i), (s), good_bye(s), False(F), -1(i)

    The output of that "get" command is detailed here: Detailed Information Packet Contents

    I agree that the documentation is not explicit about how to get and set Scene names - I will add a request that it be updated.

Reply
  • 0

    Scene labels are an attribute of a Cue, so you access them by getting information about cues.

    In my example, CueList 2, Cue 4 is the start of a Scene called "hello"

    /eos/get/cue/2/4

    gives lots of information, including that name toward the end

    [ 15:00:38 ] [15:00:38] TCPOUT [10.101.2.99:3032] [OSC Packet] /eos/get/cue/2/4
    [ 15:00:38 ] [15:00:38] TCPIN [10.101.2.99:3032] [OSC Packet] /eos/out/get/cue/2/4/0/list/0/31, -1(i), AF419B8D-2591-4305-BCC4-A5593B3E2E80(s), (s), 5000(i), 0(i), -1(i), -1(i), -1(i), -1(i), -1(i), -1(i), -1(i), -1(i), False(F), 0(s), 100(i), (s), (s), (s), 0(i), -1(i), -1(i), False(F), -1(i), False(F), (s), 0(i), (s), hello(s), False(F), -1(i)
    [ 15:00:38 ] [15:00:38] TCPIN [10.101.2.99:3032] [OSC Packet] /eos/out/get/cue/2/4/0/fx/list/0/2, -1(i), AF419B8D-2591-4305-BCC4-A5593B3E2E80(s)
    [ 15:00:38 ] [15:00:38] TCPIN [10.101.2.99:3032] [OSC Packet] /eos/out/get/cue/2/4/0/links/list/0/2, -1(i), AF419B8D-2591-4305-BCC4-A5593B3E2E80(s)
    [ 15:00:38 ] [15:00:38] TCPIN [10.101.2.99:3032] [OSC Packet] /eos/out/get/cue/2/4/0/actions/list/0/2, -1(i), AF419B8D-2591-4305-BCC4-A5593B3E2E80(s)

    I can then set that value using the syntax eos/set/cue/2/4/scene=good_bye:

    [ 15:01:55 ] [15:01:55] TCPOUT [10.101.2.99:3032] [OSC Packet] /eos/set/cue/2/4/scene, good_bye(s)


    [ 15:01:59 ] [15:01:59] TCPOUT [10.101.2.99:3032] [OSC Packet] /eos/get/cue/2/4
    [ 15:01:59 ] [15:01:59] TCPIN [10.101.2.99:3032] [OSC Packet] /eos/out/get/cue/2/4/0/list/0/31, -1(i), AF419B8D-2591-4305-BCC4-A5593B3E2E80(s), (s), 5000(i), 0(i), -1(i), -1(i), -1(i), -1(i), -1(i), -1(i), -1(i), -1(i), False(F), 0(s), 100(i), (s), (s), (s), 0(i), -1(i), -1(i), False(F), -1(i), False(F), (s), 0(i), (s), good_bye(s), False(F), -1(i)

    The output of that "get" command is detailed here: Detailed Information Packet Contents

    I agree that the documentation is not explicit about how to get and set Scene names - I will add a request that it be updated.

Children
No Data
Related

www.etcconnect.com