[Royce Jacobs]

You’re a legend Dan, thanks so much!! I knew something was awry…
As far as having multiple styles, what approach would you recommend? Once I call more than just one variable it gets angry about objects, which is doesn’t do if the variables are only strings..

first = text.sourceText.style.setFontSize(25).setText("This is text");
second = text.sourceText.style.setFontSize(72).setText("This is bigger text");
first+'\r'+second

[Royce Jacobs]

Wow thank you Walter for the very thorough response! Excellent resources and info here, I know what I’ll be doing the rest of the day… I highly appreciate you putting this together, cheers! 😀

[Royce Jacobs]

Jeez I’m realizing I’ve missed this reply; I think I need to look at my notification settings. This is great. Thanks Dan, you’re a legend whose thinking and coding are always at the peak of efficiency… much respect and thanks! 😀

[Royce Jacobs]

Oleg,

Thank you so much for this in depth solution and explanation, I’ve learned a lot this afternoon from what you’ve provided! And yes, it works immaculately! I didn’t know about Math.max, that’s a great little tool for niche applications like this…

So the last thing I’m trying to accomplish is a slider that takes and holds the Boom value upon delta until the next delta. I have it working except for the hold; it doesn’t seem to want to reference it’s own value from (-1) frames ago. I have this on a slider called CurrentBoom:

boom = effect(“Boom”)(“Slider”);
dcBoom = effect(“DC Boom”)(“Slider”);
thisSlider = effect(“CurrentBoom”)(“Slider”);//Self-referential.

if(dcBoom.valueAtTime(time) > dcBoom.valueAtTime(time-framesToTime(1))){//Check to see if dcBoom just went up to 1.
boom//Make this slider the boom value.
}else{//Otherwise…
thisSlider.valueAtTime(time-framesToTime(1))//Make this slider the value it was last frame.
};

So I get the boom value on delta, but then then it goes to zero the next frame until the next delta. Are these types of self-referential calls possible?

Thanks again so much for your help! Already you’ve gotten my head spinning with nerdy options I didn’t know I had….. :O

boom = effect("Boom")("Slider");
dcBoom = effect("DC Boom")("Slider");
thisSlider = effect("CurrentBoom")("Slider");//Self-referential.

if(dcBoom.valueAtTime(time) > dcBoom.valueAtTime(time-framesToTime(1))){//Check to see if dcBoom just went up to 1.
boom//Make this slider the boom value.
}else{//Otherwise...
thisSlider.valueAtTime(time-framesToTime(1))//Make this slider the value it was last frame.
};

[Royce Jacobs]

So, quick update, I actually made a slider on the text layer and copy/pasta’d the opacity code onto it, and the slider changed from 0 & 100 at the correct times. Then I simply erased the code on the opacity, and pickwhipped it to the slider on the text layer and it works great!

What a bizarre work-around.. and honestly I still want to figure out why the same exact code wouldn’t work on the opacity parameter. Anyone have any thoughts?

[Royce Jacobs]

You deserve a medal, Mr. Taras. ಠ_ರೃ

[Royce Jacobs]

I just found this issue too and it’s driving me crazy! =O I use the mouse wheel scrub frequently, and for Adobe to change the way it works without the option to choose between linear and accelerated in prefs is pretty baffling. PLEASE ADOBE REVERT OR ADD OPTION IN GEN PREFS!

[Royce Jacobs]

Thanks, Dan!! Appreciate the tips! I’ll keep plugging away…

[Royce Jacobs]

Greg,

I appreciate the suggestions! Unfortunately, the part I really needed the help in was the missing part (position in your example). I need a way to “play” a layer and freeze on the last frame.

I have re-posted this in the expression forum per your suggestion.

[Royce Jacobs]

Perfect, thanks so much! I am running it in a script; I think I’ll use the setValue(0).