-
Wiggle exceeding limits? Have you seen anything like that?
* Edit post
* Delete post
* Report this post
* Reply with quoteWiggle exceeding limits? Have you seen anything like that?
Postby imago on 27 May 2010 19:55
OK, so i am working on a new tutorial right now and among other things I need to have a Point Control Effect wiggling about. I know my way around the expressions quite well, but this time I am totally blank on what is happening.Have a look:
https://downloads.qubahq.com/images/WiggleWTF.jpgBasically, I have the value for the effect set at 0,0 and apply independent wiggles to x and y position using the following expression:
[ wiggle(1,512)[0] , wiggle(1,288)[1] ]
The y value seems to work fine, but for some reason on some of the frames x results in values as high as 530.2. How is that possible? Shouldn’t it be limited to the -512 to 512 range?
Have anyone experienced a similar behavior? Any bright ideas?
[ wiggle(1,512)[0] , wiggle(1,288)[1] ]Quba Michalski
qubahq.com -
4 Replies
-
I just checked the project and it behaves identically both in CS3 and CS5. I would like to share the file with you, but I am not too eager to release it before I complete the project…
So far the only workaround I can think of is to clamp the value using the linear function. It will remove the exceeded limits problem, but meanwhile I would like to understand why the hell is this thing happening in the first place.
Quba Michalski
qubahq.com -
This is very weird. I managed to eliminate the buggy behavior by pre-composing the offending layer and all its effects. When it is sitting alone in its own composition the wiggle seems to be working fine.
Still no bloody idea what was causing it to misbehave.
Quba Michalski
qubahq.com -
Yeah, sometimes wiggle()can exceed the amplitude value somewhat. To get a different wiggle result you just need to do something that changes the seed. Adding a null above the layer should do it, or you can set a specific seed using seedRandom();
Dan
-
Thanks Dan,
It is the first time I experienced wiggle going outside of the range – gotta keep an eye on that.
Since the effect is a part of a tutorial/preset I am developing, I don’t want to leave anything to chance. Defining a seed manually could be a good idea, but the whole thing needs to be easily duplicable and I don’t want to force the people who use it to have any headaches.
I think your answer solved the mystery: “It just happens”.
I will stick to keeping the layer in a separate composition. Tested it with many different variables and everything seems to work OK.
Quba Michalski
qubahq.com
Reply to this Discussion! Login or Sign Up