Forum Replies Created

Page 62 of 699
  • Bret Williams

    March 12, 2016 at 12:02 am in reply to: Compressor aspect ratio dysfunction

    Your source is 16:9, right? If so it should fill the frame at 720×486 anamorphic. Display shouldn’t be 640×486 in either case it doesn’t seem. If you have bars on the side of a 720×486 4×3 video displaying at 640×480 then something is screwy. That’d be 4:3, but with an extremely squished video in the middle.

  • Bret Williams

    March 11, 2016 at 11:07 pm in reply to: Compressor aspect ratio dysfunction

    Shouldn’t it display at 864×486 if it’s anamorphic SD? Not 640×486. That’s 4:3 display.

  • Bret Williams

    March 11, 2016 at 9:17 pm in reply to: roto options?

    Good idea. But we’ve moved on. Reshoot tomorrow.

  • Bret Williams

    March 11, 2016 at 8:32 pm in reply to: roto options?

    Yeah. Flesh tone is same as mulch tone.

  • Bret Williams

    March 11, 2016 at 7:35 pm in reply to: roto options?

    Thanks for the suggestions. All good ideas. Unfortunately tried ’em. Apparently there’s a real good reason Hollywood hasn’t accepted brown screen chroma keying as a standard practice. Just not enough luma or chroma to deviate from skin, clothing, shadows and so on. We are editing around the issue. Or reshoot.

  • Bret Williams

    March 11, 2016 at 7:31 pm in reply to: How do you reconnect Motion-made generators?

    In my experience, they have to be in the exact same file path as they were when you used them. Now maybe you can put some sort of symlink in there but that’s beyond my expertise.

  • Bret Williams

    March 10, 2016 at 7:32 pm in reply to: Resolve 12 collaborative workflow thoughts?

    [Michael Gissing] “This is a feature that might sway more big facilities to using Resolve for the edit.”

    It’s great to have a free option out there like Resolve, but I can’t see why anyone would be choosing it as their edit system of choice. It really is like they married the common ground between Adobe CC and FCP X. They completely left out the stuff that makes either one of those powerful. They don’t have keywording, roles, skimming or magnetic timeline from X. They don’t have the advanced audio, key framing or pancaking ability of CC. And they don’t have the many plugins and effects and integration you get with X or CC. It’s kinda like they took the lesser of the two apps and put them together.

    Good for cuts/dissolves and color correction though!

  • Bret Williams

    March 8, 2016 at 6:31 pm in reply to: Black magic driver(s) crash FCP X constantly

    I’m looking at the Ttap as well. 10.6.1 driver didn’t solve any issues for me either. I can play back, as long as that’s all I’m doing. No scrubbing, trimming or anything. But I always forget to turn the monitoring back off.

    Having an external is extremely helpful for motion graphics. You can see the 100% view on the external, while you’re zoomed in to 500% on the screen to create a mask or whatnot. I miss having that capability, plus the crashing is making me nuts.

    I blame El Cap.

  • Bret Williams

    March 8, 2016 at 5:43 pm in reply to: Rename file on disk?

    I don’t necessarily recommend it, but if you reveal a clip in the finder while FCP X is running, you can rename it right there and X will still have it’s hooks into it. You can also move the file as well and X will keep track of it as long as the app is running. FCP legacy was the same way. If you trashed a bunch of files in the finder while the app was running, it would simply follow them to the trash and link to them there. It doesn’t knock them offline.

    But renaming original camera files just seems like a bad idea. It’s breaking a connection to the original card backups isn’t it?

  • Bret Williams

    March 5, 2016 at 11:51 pm in reply to: FCPX rookie question

    Component signals should be 0 too I believe.

Page 62 of 699

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