Help on defining fixture

[apl4]

How would you go about defining a fixture where the values actions set by different values on channel 2 where dependant on which value was set on channel 1? As per the attached mode table.

[boxy]

Here's a definition with a similar issue:

<Channel Name="Strobe/Speed/Sound Sensivity">
<Group Byte="0">Effect</Group>
<Capability Min="0" Max="10">No function/Slow to fast/Off</Capability>
<Capability Min="11" Max="15">No function/Slow to fast/Control the sound sensitivity level</Capability>
<Capability Min="16" Max="255">Slow to fast/Slow to fast/Control the sound sensitivity level</Capability>

Ignore the xml data - just look at the bold text. Each function is seperated by '/'s.

If the descriptions are too long they should be shortened so QLC+ can show them in the Simple Desk tab correctly.

Note how 'No function' for the 'Strobe' overlaps 'Off' and 'Control the sound...' between 0 and 15. This way a whole mess can be sorted out.

[apl4]

Here's a definition with a similar issue:

<Channel Name="Strobe/Speed/Sound Sensivity">
<Group Byte="0">Effect</Group>
<Capability Min="0" Max="10">No function/Slow to fast/Off</Capability>
<Capability Min="11" Max="15">No function/Slow to fast/Control the sound sensitivity level</Capability>
<Capability Min="16" Max="255">Slow to fast/Slow to fast/Control the sound sensitivity level</Capability>

Ignore the xml data - just look at the bold text. Each function is seperated by '/'s.

If the descriptions are too long they should be shortened so QLC+ can show them in the Simple Desk tab correctly.

Note how 'No function' for the 'Strobe' overlaps 'Off' and 'Control the sound...' between 0 and 15. This way a whole mess can be sorted out.

Thanks boxy.

Does that mean that you have to write the xml manually, as the fixture editor can't handle overlaps?

[boxy]

No. It was the easiest way of me demonstrating how to do it.

To keep the amount of text used down, put repeated information in the title eg: Mode, Effect, Speed etc.

Have a go and post it. Then we'll see.