Little problem

[alverman]

I have two button in a widget project:
One custom script button, for me is GO, contain:

SeqSetState,1,Play
'Fade up LAYER 1
WDFaderUp,1,6
'LAYER 1 Speed
WDFaderValue,3,35
ClearAllActive

When I Push GO the state of relative layer opacity is 0
Whem I push GO I want fade up in 6 second from 0 to 255 of opacity.
It work but when I press GO button I see a rapid flash of the clip and only after the fade start correctly.

Why ?

Thanks, Alberto

[JustynR]

Have you tried this without the 'ClearAllActive" at the bottom?

Also, what is in fader 1?

I'm guessing you don't actually have the

'Fade up LAYER 1

or

'LAYER 1 Speed

Written in the button?

[Julia Foest]

Hi Alberto,

Justin is right, the ClearActiveAll script at the end lets the opacity jump back to zero for a short time before it starts beeing increased by the fader again.
If you want to remove other active values please place this script before fading up the other faders.

Best regards,
Julia

[alverman]

Without changing the contents of the my custom script the problem does not occur, if the WD project is executed on the machine where is running the manager.
If I run the same project from a PC network projecting start with a flash!

?

Alberto

[JustynR]

Do you mean that it quickly flashes on the screen when you control it over a network computer?

I would assume that it is because there is maybe a small delay in the script that tells it to clear all active.

Have you tried without that line in the script?

[Patrick Verhey]

Hi,

please put a "WDWait,6" right in front of the "ClearAllActive" Command. What happens in your case is that the Fader starts to move but the widget designer is clearing the active value in between. You need to make sure that the fader did move up all the way before you send the clear all active command.

Right know the fader will start moving up, so you start to see the layer, but a few seconds later the value is cleared for a second and then the fader is taking over again. Thats why you see a flash. This is more or less a LTP programming mistake.

I hope that my explanation is understandable. It is not so easy to explain without showing it.

best regards

Patrick

[alverman]

I understand perfectly!

Thanks