Forum Replies Created

  • Allen Ellis

    June 30, 2009 at 3:18 am in reply to: Is the hmc 150 really better than the hpx 170?

    170 has more versatility in terms of over cranking and under cranking. The 150 does not let you shoot either. This is a big deal if you plan on doing slow motion or time lapse.

    Just want to say you can shoot 720/60p on the HMC-150, so if your delivery is 24p then yes, you can overcrank.

    It doesn’t do timelapse. But with a 16 or 32GB card you can record for, what is it, 5-8 hours?.

  • Allen Ellis

    May 22, 2008 at 9:08 pm in reply to: creating a 60 minute countdown clock?

    That will work, but for future reference there is a ‘value’ parameter that you can just keyframe with the numbers you want.

    Also, I usually just apply the Numbers effect to a standard layer, so then I can move it up and down properly. I don’t see why you would do an adjustment layer.

    Glad you have it working though. 🙂

  • Allen Ellis

    May 22, 2008 at 9:04 pm in reply to: Premiere to After Effects Multi Camera workflow

    David, manually separating them into layers doesn’t help. You’ll just end up with each ‘clip’ on it’s own layer with no lead-room or end-room. For any transition you need some extra time for the transition to take place, but Premiere is exporting it without any leadroom.

    Just moving the clips earlier is no good because the audio will be out of sync.

    I’d love to know an answer, as well.

  • Allen Ellis

    May 22, 2008 at 9:00 pm in reply to: Slow down randomly generated value

    Also consider using wiggle() instead. If you want it to blur between 6 and 8, then set the blur value to 7, and then add this expression:

    wiggle(1,1)

    The first argument is the speed of the change, in this case: 1 time per second. The second argument is the amount of change, in this case: 1. So it will randomly raise or decrease up to 1 amount (maximum 8, minimum 6).

  • Allen Ellis

    February 14, 2008 at 4:34 am in reply to: Limitations with Math.pow?

    Thanks so much – that’s exactly what I needed.

    I’m running into other similar issues now but they’re more minor and I think I’ll know how to deal with them now. Thanks again :).

  • Allen Ellis

    February 14, 2008 at 1:48 am in reply to: Limitations with Math.pow?

    Well that project opens fine for me, too – I get the error when I change layer 3’s expression to be

    y = Math.pow(x,2.5);

    Or some other decimal/fraction number.

    Sorry that I forgot to mention that. I didn’t want to submit a project with errors because I assumed it wouldn’t show the error that way.

  • Allen Ellis

    February 14, 2008 at 1:10 am in reply to: Limitations with Math.pow?

    You’re right – it does.

    The expression is applied to a point control. Here is the code:

    x = this_comp.layer(“X”).effect(“X”).param(“Slider”);
    y = Math.pow(x,3); // y = x^3

    [x,y]

    It complains about the error on the last line, not line 2.

    Here is the project file:
    https://www.allenellis.com/public/Graph.aep

    Look at layer 3: “Point Control”.

    Thanks in advance.

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