Forum Replies Created

  • Philip Neves

    January 18, 2016 at 4:10 pm in reply to: Trigger Layer Position with Layer Marker

    I also needed an expression to offset a null (parent for a set of lyrics) by a specific amount on a marker trigger (so the lyrics automatically rise on triggers, like a typewriter return). This is really helpful! Thank you for putting it online!

    I made a small modification so it’d take frames explicitly:

    offsetAmt = -100;
    easeFrames = 10;
    n = 0;
    if (marker.numKeys > 0){
    n = marker.nearestKey(time).index;
    if (marker.key(n).time > time) n--;
    }
    yOffset = 0;
    if (n > 0){
    t = time - marker.key(n).time;
    yOffset = easeOut(t,0,framesToTime(easeFrames),(n-1)*offsetAmt,n*offsetAmt);
    }
    value + yOffset;

  • Philip Neves

    August 6, 2015 at 7:36 pm in reply to: How do you manage your media archive?

    Thank you, Joseph! Great article. I wish I had seen it earlier.

    We’ll probably wind up in Bridge, but we had some hesitations because it doesn’t play MXFs right now (or the raw XF codec structures from the camera). But we should probably transcode everything to ProRes anyway, right?

    I’m impressed by how you manage projects at the filesystem level with the clients/client-name/project-name structure, too. We just make the client name part of the project folder, but this might be better.

    Question: Would you set up the filesystem organization any differently if you knew going in that one set of footage would be feeding multiple projects? IE make a sort of media pool in a static location that projects can draw from without having to store multiple copies of the footage close to each?

    – philip

  • I noticed it didn’t update a transition and an After Effects comp the other day, too. That’s probably the same thing. Thanks, James!

  • We had the same problem with an XF300 this week — same horizontal glitches burned into footage, card wiped before we spotted them.

    After way too many hours testing the camera and cards, we finally tracked it down to a bad (new!) card reader.

    Which is shaking my whole worldview… if you can’t trust your name-brand card reader, who can you trust?!

    The errors were surprisingly consistent — I’d like to see if a checksum test would even catch a glitchy card reader. Meanwhile, time to check all the other ones. And visually check everything BEFORE wiping cards for a while, which I should have been doing anyway.

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