MSC command for scene ?

Hi.
I'm sorry, I can't understand the User Manual for the MSC Tips for scene:" To work round this, you can send an MSC command with a CUE_PATH value of 5. Wholehog OS will treat the cue number as a scene number instead.".
I don't know how to use the CUE_PATH value of 5. Could you for example with a MSC command to control the "Scene 20" play?
Thanks.
I'm sorry, I can't understand the User Manual for the MSC Tips for scene:" To work round this, you can send an MSC command with a CUE_PATH value of 5. Wholehog OS will treat the cue number as a scene number instead.".
I don't know how to use the CUE_PATH value of 5. Could you for example with a MSC command to control the "Scene 20" play?
Thanks.
Comments
That's a good idea, I'll try it if the condition is accepted. Could i please you post the fix answer here if you get.
I've another question. how can i set the cuelist number or cue number to 22 , 333 or 4444 etc with the msc command. I just know to set the number from 1 to 9, when the number is bigger, I don't know how to set it ?
F07F01020101310031
Cue 15, list 10
F07F010201013135003130
Basicaly a number 3 is added between each digit of the cue or list.
F0 7F - Begin Command
01 - Device ID
02 - Constant Value
01 - Lighting Command Format
01 - GO
31 - Cue Number 1
00 - Separator
31 - Cuelist Number 1
00 - Separator
F7 - Complete Command
thanks
Cue #
List #
Device ID
I would re-record them as cues and do it that way.
SCENE X COPY ENTER, will copy the contents of Scene X to the Programmer.
You can then Record it as a single cue cuelist and do that way.
to give scene 1 a go: F0 7F 01 02 01 01 00 31 00 05 F7 (31 in this string is the scene1)
to release scene 1: F0 7F 01 02 01 0B 00 31 00 05 F7 (0B is the release command, 31 is still scene1)
to give scene 17 a go: F0 7F 01 02 01 01 00 31 37 00 05 F7 (31 is the first digit, 37 is the second digit).
i hope this will explain the question enough,
with regards,
sander
The answer is very clear. That's the answer I want. Thanks. Thanks everyone.
the ID can be between 0 and 111. i do not know why it cannot go up to 127 like it usually should go, this is maybe a hogIII thing.
I assign two different Device ID in the MSC and the Console, but the console also received the MSC normally and execute.(MSC Device ID must be 1, the console's Device ID set to other number).
by the way, I try it in a same console.
and in this configuration both IDs have to be the same, else hogPC will not listen to the generated MSC of midiox.
Yes. in your example, the both IDs have to be the same.
May be, The Note Number and Device ID in MS macro command are ignored in a same console when a midi cable connected MIDI In and MIDI Out on itself.