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.
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.
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, ...
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...
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.
