Forum Replies Created

Page 8 of 66
  • I just realized I never thanked you for this, so thank you very much, it was a huge help.

    Best,
    David.

  • David Cabestany

    September 24, 2019 at 6:22 pm in reply to: R20 won’t open old files

    Thanks, Allan,
    It was made on R11.5 I think. I ended up using a different file of a similar object.

    I appreciate your help, anyway.

    Best,
    D.

  • David Cabestany

    September 19, 2019 at 10:53 pm in reply to: Are there internal index numbers inside shape layers?

    Hey Dan, two more questions and I promise I’ll get off your hair.

    1. How do you determine that Ellipse # is the propertyGroup(2)? I tried adding extra objects on the shape layer and it only works with 2, every other number breaks the expression so I haven’t been able to determine which one is propertyGroup(1), (3), etc.

    2. I think the 10 after the [1] array determines which character to read from the 2nd word, in this case the number of the Ellipse, but why 10? I tried other numbers such as 8 and the expression still works but I don’t get where the result is coming from, the numbers are unrelated.

    Sorry for all the asking, I’m trying to understand what is going on so I don’t keep bothering with lame questions in the future.

  • David Cabestany

    September 19, 2019 at 10:23 pm in reply to: Are there internal index numbers inside shape layers?

    Thanks Dan.

    Yes, they are stacked with the highest on top and the lowest at the bottom, when I duplicated them the newer ones were created above the previous ones.

    It partially works, the expression is not broken, but the values are all haywire. I’ll try tweaking it to see if I can make it work.

    Thanks again,
    D.

  • David Cabestany

    September 19, 2019 at 8:37 pm in reply to: Are there internal index numbers inside shape layers?

    I’m trying to push position 100 pixels further than the previous ellipse. Right now it looks like this:

    And I’d like to replace (“Ellipse #”) with the index of the object. It’s a shape layer with multiple ellipses in it. I manually replaced the number (“Ellipse 4,5,6 etc) but if I can do it with index numbers would be better.

    Thanks

    y=thisComp.layer("xp").effect("y")("Slider");
    content("Ellipse 4").transform.position+[0,y]

  • I think this expression (sourceReactAtTime) is either broken or not quite ready to be included with AE.
    I’m getting all sorts of unwanted jumps and resizes even after I compensated for the in point of the layer. It’s been more of a hindrance than a helper.

    Reporting a bug to adobe, once an easy task, it’s now useless with their new “forum” format.

  • Really? Maybe I had it wrong this whole time. I use alt-drag to replace clips and have them keep the scale to fit feature activated, but I always thought that to also maintain the in point the shift keed was required.

    I’ll check as soon as I have a minute, I’m on a deadline with my current project.

    Thanks for your help.
    D.

  • David Cabestany

    August 20, 2019 at 5:58 pm in reply to: What happened to the knife tool in R20?

    Oh, ok. Thanks.

  • I think is that too, but can’t understand why the frames since the layer begins several more frames after.

    Can I send you the file? I have your email already.

  • I managed to solve it by adding .1 to the inPoint, but I can’t understand why.
    If you can explain why is happening it’s be greatly appreciated.

    t = thisComp.layer("xp").effect("Layer Control")("Layer");
    margin = thisComp.layer("xp").effect("margin")("Slider");
    r = t.sourceRectAtTime(time-(t.inPoint+.1),false);
    w = r.width*t.scale[0]/100 + margin;
    h = r.height*t.scale[1]/100 + margin/2;
    [w/width,h/height]*100

Page 8 of 66

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