[Leif Heidenreich]

works fine now

thanks for the fix, ben

[Leif Heidenreich]

Exactly, that works very well render wise.

I get a sideeffect though, maybe not due to your last alteration.

When the value stayed above the threshold and than falls below it, in some occasions the value flips from 0% to 100% for 1 Frame, and falls back to 0% then.
(or the other way around)

I havent found a clue yet, accept that the triggertime seems to be involved…

Could u explain the triggertime aspects to me… I am still confused about its value…

thanks for your enhancements…

[Leif Heidenreich]

I liked to keep things dynamic to a certain level.

Wouldnt it be possible to just check back the last so and so many seconds to gateher the necessary information?

Isnt there anyway to bypass the recalculation of the whole framedruation?

But certainly this expression made me read a lot about javascript, since I still seem not to be able to comprehend the big picture…

I thought it would be enough, to have the expression check the valueAtTime and than trigger the ease in/out…

Like:
If the value is >= 5 ease in over 1 second from 0 to 100 and stay
unless
the value is <= 5 than ease out over 1 second form 100 to 0 and stay thanks leif

[Leif Heidenreich]

sl=thisComp.layer("Work_Radar_Ring Control").effect("Sector 1")("Slider");
threshold=5;

fd=thisComp.frameDuration;

t=0;
triggerTime=-100;
crossed=null;

// look at all previous frames to find out the last time sl crossed the threshold;
while(time>t) {
if (sl.valueAtTime(t)<=threshold && sl.valueAtTime(t-fd)>threshold) { triggerTime=t; crossed="up"; }
if (sl.valueAtTime(t)>=threshold && sl.valueAtTime(t-fd)
Hi Filip, salut everyone,
Is it possible, that due to the script rendering times increase allmost exponential.
0:00:00:00 (1): 3 Seconds

0:00:01:00 (31): 2 Seconds

0:00:02:00 (61): 3 Seconds

0:00:03:00 (91): 3 Seconds

0:00:04:00 (121): 4 Seconds

0:00:05:00 (151): 5 Seconds

0:00:06:00 (181): 5 Seconds

0:00:07:00 (211): 6 Seconds

0:00:08:00 (241): 8 Seconds

0:00:09:00 (271): 7 Seconds

0:00:10:00 (301): 9 Seconds

0:00:11:00 (331): 9 Seconds

0:00:12:00 (361): 9 Seconds

0:00:13:00 (391): 10 Seconds

0:00:14:00 (421): 11 Seconds

0:00:15:00 (451): 11 Seconds

0:00:16:00 (481): 12 Seconds

0:00:17:00 (511): 12 Seconds

0:00:18:00 (541): 13 Seconds

0:00:19:00 (571): 14 Seconds

0:00:20:00 (601): 15 Seconds

0:00:21:00 (631): 16 Seconds

0:00:22:00 (661): 16 Seconds

0:00:23:00 (691): 17 Seconds

0:00:24:00 (721): 18 Seconds

0:00:25:00 (751): 18 Seconds

0:00:26:00 (781): 19 Seconds

0:00:27:00 (811): 19 Seconds

0:00:28:00 (841): 20 Seconds

0:00:29:00 (871): 21 Seconds

0:00:30:00 (901): 21 Seconds

0:00:31:00 (931): 22 Seconds

0:00:32:00 (961): 23 Seconds

0:00:33:00 (991): 26 Seconds

0:00:34:00 (1021): 23 Seconds

0:00:35:00 (1051): 28 Seconds

0:00:36:00 (1081): 25 Seconds

0:00:37:00 (1111): 30 Seconds

0:00:38:00 (1141): 31 Seconds

0:00:39:00 (1171): 28 Seconds

0:00:40:00 (1201): 34 Seconds

0:00:41:00 (1231): 57 Seconds

0:00:42:00 (1261): 1 Min, 14 Sec

0:00:43:00 (1291): 1 Min, 13 Sec

0:00:44:00 (1321): 1 Min, 27 Sec

0:00:45:00 (1351): 1 Min, 19 Sec

0:00:46:00 (1381): 1 Min, 24 Sec

0:00:47:00 (1411): 1 Min, 55 Sec

0:00:48:00 (1441): 1 Min, 29 Sec

0:00:49:00 (1471): 1 Min, 27 Sec

0:00:50:00 (1501): 4 Min, 24 Sec
The Script is used on 40 Sectors, which fade in and out, triggered by the script.
I assume that over time the script seems to recalculate previous processes.
Any Idea where this problem could evolve from?
Regards

Leif 

		

    

[Leif Heidenreich]

you pinpointed my problem.
The relative time aspect is the key.

works flawless.

Thank you very much…