Software Version 3.0 problem

[DaveP]

Jumps in the memory stack

Only tested on Phantom Frog X so far, but will go and update the board to V3 tomorrow and see what happens.

 

Created a stack of 10 entry's

 

1. Fader 1 to 100% everything else at 0%

2. Fader 2 to 100% everything else at 0%

3. Fader 3 to 100% everything else at 0%

4. Fader 4 to 100% everything else at 0%

5. Fader 5 to 100% everything else at 0%

 

And so on through to 10.

 

Running the above via the 'go' button, behaves exactly as expected... and all is well

 

An issue arises when jumps are put into the stack

 

1 Normal

2 Normal

3 Next 7

4 Normal

5 Normal

6 Next 8

7 Next 4

8 Normal

9 Normal

10 Normal

 

The outputs are as follows

 

1 @ 100% everything else at 0%

2 @ 100% everything else at 0%

3 @ 100% everything else at 0%

7 @ 100% + 3 @ 100%

4 @ 100% + 7 @ 100%

5 @ 100% + 7 @ 100%

6 @ 100% + 7 @ 100%

8 @ 100% + 6 @ 100%

9 @ 100% + 6 @ 100%

10 @ 100% + 6 @ 100%

1 @ 100% everything else at 0%

 

It seems that on a jump, if the last memory was not numerically proceeding the memory jumped to.. then its not cross fading

[Kirkup_xp]

Hi Dave

 

Thanks for the bug report, however I think this is the designed functionality on the Next Memory.

 

Each memory on the cue stack only outputs the *changes* made by the relevant memory, rather than the state as it was outputting. The instructions in Memory 7, for example, tell channel 6 to go off and channel 7 to go on. Because the stack was recorded using Smart Tags, Memory 7 doesn't contain any information about channels 1-5 and 8-10. Therefore, when you run into memory 7 from any memory other than 6, only the changes made in 7 are applied.

 

If you wanted it to output ONLY the channel required, you'd need to record instructions for the other channels to go off. To do this, turn off Smart Tags and manually tag each dimmer at 0. The quickest way to do this is to select them (either using command line or set the flash buttons to Off/Select mode) and 'nudge' the intensity wheel.

 

I will add an issue to our reports system for an easier mechanism to get the 'outputting' state rather than the 'changes'.

 

 

Peter

[DaveP]

Thank you for your very prompt reply Kirkup_xp

 

designed functionality

 

If I hadn't gone to the pub for a liquid lunch, then maybe I would of understood it...

 

I will add an issue to our reports system for an easier mechanism to get the 'outputting' state rather than the 'changes'.

 

Now that bit I do understand ..

 

Yes please, as as a quick / simple method of adding 'jumps' due to last min changes (like on Friday night when Roy Orbison decided 30mins before the doors opened and the tabs were closed that he would sing the songs in a different order, cos he just found out that he had the wrong backing cd.. ) would be great.

 

David