Forum Replies Created

Page 2 of 3
  • Micheel Leavitt

    September 5, 2009 at 7:28 pm in reply to: break in source text

    Alright alright, I was still using the forward slash piece from earlier, but I changed all the slashes and it works perfectly! Thanks a lot Dan, this really will help make what I’m doing much easier. I got an audio spectrum that has a line of nulls reading the spectrum layer, and it displays a percentage for how much of the spectrum layer fills the null. Seeing all of the nulls values in realtime makes it easy to see what ranges are the most reactive. Thanks so much again!

  • Micheel Leavitt

    September 5, 2009 at 7:24 pm in reply to: break in source text

    Alright, the problem was the lack of “value” before the toFixed, and it now works, it just doesn’t make a line break Dx and it also shows the /r in the source text, but hey, at least no code errors!

  • Micheel Leavitt

    September 5, 2009 at 7:13 pm in reply to: break in source text

    That also gave a toFixed undefined error. Is it because I have toFixed(2) stored as a variable?

  • Micheel Leavitt

    September 5, 2009 at 7:12 pm in reply to: break in source text

    Okay, so I changed the slashes to backslashes, but then it gave a syntax error, then I made it look more like this:

    “a \r b \r c \r d”

    but then function toFixed is undefined. So it wasn’t just the forward slashes that had me.

  • Micheel Leavitt

    September 5, 2009 at 7:00 pm in reply to: break in source text

    Gah, for some reason it is having an error on the last line, it wants a “;” somewhere, I added one to the end but that didn’t work. Heres the code so far (about half of the values)

    z = toFixed(2);
    a = thisComp.layer(“a”).effect(“Final Range Value”)(“Slider”).z;
    b = thisComp.layer(“b”).effect(“Final Range Value”)(“Slider”).z;
    c = thisComp.layer(“c”).effect(“Final Range Value”)(“Slider”).z;
    d = thisComp.layer(“d”).effect(“Final Range Value”)(“Slider”).z;
    e = thisComp.layer(“e”).effect(“Final Range Value”)(“Slider”).z;
    f = thisComp.layer(“f”).effect(“Final Range Value”)(“Slider”).z;
    g = thisComp.layer(“g”).effect(“Final Range Value”)(“Slider”).z;
    h = thisComp.layer(“h”).effect(“Final Range Value”)(“Slider”).z;
    i = thisComp.layer(“i”).effect(“Final Range Value”)(“Slider”).z;
    J = thisComp.layer(“a”).effect(“Final Range Value”)(“Slider”).z;
    “a” /r “b” /r “c” /r “d” /r “e” /r “f” /r “g” /r “h” /r “i”

    So what am I doing wrong? Thanks for any help!

  • Micheel Leavitt

    September 5, 2009 at 6:50 pm in reply to: break in source text

    Sweet, thanks a lot Dan, that helps a lot. Its a shame that you can’t read the data from multiple properties while doing a Ram preview. (Or is there?) Either way this makes it easier, even if it’s going to slow down preview speed. :} Thanks again

  • Micheel Leavitt

    September 2, 2009 at 5:15 pm in reply to: formula of linear interpolation

    Ah, I see the connection now. When you calculate this in AE, it will continue on without stopping because time is not constrained. Thank you for the help, I was having trouble grasping that for some reason. I’m doing most of this on paper and proving it in After Effects. I was talking to my teacher about it and she couldn’t understand what I was asking, so now I can explain what my babbling was about on Monday 🙂 Thanks for the help Dan and Filip!

  • Micheel Leavitt

    September 2, 2009 at 6:37 am in reply to: formula of linear interpolation

    Thank you for the conversion formula, but it was in the book already 🙂
    However, the formula you provided earlier:

    result = value1 + ((t – t_min)/(t_max – t_min))*(value2 – value1);

    was exactly what I was looking for, but I am still a little lost as to what exactly the need for clamp is. If result would always be between value1 and value2, then why would you have to clamp it? So there must be certain situations where this formula would generate numbers slightly higher or lower than value1 and value2, right? Thats what I meant by it not being exact. This code looks very similar to the formula at

    https://en.wikipedia.org/wiki/Linear_interpolation

    and it also talked about an error margin, but I don’t think they were the same. But thank you Dan for your insight so far, and if you have another way to explain the need for clamp that would be great!

  • Micheel Leavitt

    September 1, 2009 at 6:03 pm in reply to: formula of linear interpolation

    I suppose I should have made it clear that I was looking to explain this on paper, rather than in code. However, I think what you showed is what I am looking for, and I noticed while doing some research that linear interpolation is not exact, so that must be why you said to use clamp() to constrain the values. If it helps people understand what I’m asking, I was working on farenheit/celcius conversions and I was curious as to how they came across the formula for conversion, and if there was a function that would take any set of values and “remap” it to another set of values. I know this is basically what interpolation methods do, so like I said I think you answered my question. Thanks a lot Dan!

  • If you are not animating scale, and doing it with a camera, you should probably look for a script that will take all of those pieces made with the grid script and then have it save each one as a .psd or high res JPEG, and then maybe find a way to quickly replace each original piece with the new .psd/.jpeg images. Theres a keyboard shortcut to do one at a time, but if you could find a script that would be handy. Good luck!

Page 2 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy