OSC get channel value

No - it's only possible to get the current value.

However you can iterate through cues in blind, and get values that way. Just know that this method can be time consuming.

If you are able to, I'd recommend using one of the export file methods instead. File>Export>CSV, for example will include the information you're looking for.

Thank you for your answer. Can you tell me why it isn't possible? I think that it is basic request. Is it possible to export CSV data by OSC?

MrTom said:

Can you tell me why it isn't possible?

Uh - the methods just don't exist? I can't say why the methods don't exist as I simply don't know! If this is something you think would be a valuable addition you can submit a feature request.

No, it is not possible to export that via OSC. It's a command that needs to be run from the console itself, and the CSV gets saved to a thumbdrive.

Sorry again. How can i get value (intesity and color) from blind if I interate cue and chanel?

by listening to the OSC output of the console.

upon selecting a channel it will send:
/eos/out/active/chan, 2 (and some more details about the type)
/eos/out/active/wheel/1, Intens ...
/eos/out/active/wheel/2, Red ...
/eos/out/active/wheel/3, Green ...
/eos/out/active/wheel/4, Blue ...
/eos/out/active/wheel/5, Hue ...
/eos/out/active/wheel/6, Saturation ...
/eos/out/color/hs, ...

Thank you, but this always back me only data from actual live cue, not from blind interate cue.

ah, sorry. didn't read carefully

i just tried it and i get the blind values...

This is weird. I have same value from live cue (from every blind cue). What I am doing wrong?

/eos/key/blind

/eos/cue/1/<cue>

/eos/chan/<chan>

ah, i think i found my confusion. i have been looking at /eos/out/color/hs, and this seems to change from blind cue to cue, but the wheel parameters don't...

sorry for the confusion.

sktusing is partly correct.  In Blind, the implicit outputs for /hs and /pantilt and /xyz match their Blind values.  However, all the others will be the current live values.  So, you can only iterate through cues in Blind to get PanTilt, HueSat, and XYZ values, but not, say, the Gobo assignment.

We will considering implementing a Blind option in the future. 

This would be useful, especially for other target types like presets.