Forum Replies Created

Page 26 of 222
  • I’ve found that trying to remap Zoom In and Zoom Out in FCPX to be unpredictable and buggy.

    You’re seeing that it forgets the shortcut. When I remapped it to Up Arrow and Down Arrow it changed how zoom actually worked. It normally zooms in around the playhead, but my system would zoom in to random points. Here’s a video demonstrating it:

    https://reels.creativecow.net/film/fcpx-zoom-possible-bug

    I think it’s a bug.

    In regards to seeing “Zoom out” listed multiple times – I think that’s just showing you every keyboard shortcut for Zoom Out. Cmd – (twice, because I assume left command and right command), and Shift Down. It’s all the same zoom, just mapped to several places.

    —————-
    Michael Hancock
    Editor

  • Nope. FCPX could use a complete overhaul in how it presents favorites/markers/etc…. The current implementation has tons of wasted space and clutter, as you’ve found. Wait until you start adding markers/keywords and use clips. All of that info will be displayed too when you twirl a clip down.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    July 18, 2016 at 1:47 pm in reply to: Where’s your footage coming from?

    I work at a small production/post production shop as an editor/budding colorist. We do primarily corporate, TV spots, and web videos. No episodic or film work (except for local short films other employees and their friends shoot).

    If we shoot, it’s Arri Amira 95% of the time. The other 5% is C300/C100.

    If an ad agency, outside producer or direct-to-client is bringing us just the post work there’s no telling where the footage will come from. This year we’ve gotten footage from 5D, 7D, C100, C300, GoPro, DJI Phantom, XDCam, Red Epic and Dragon, Alexa, F5 and iPhone. We’ve also gotten footage from miniDV, Beta, HDCam, and Digibeta. No 3/4 or 1″ (yet!).

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    July 15, 2016 at 7:19 pm in reply to: A bridge too far?

    [Jeremy Garchow] “[Bill Davis] “Seems to me the point was for Apple to quietly but definitively put out the message that X is not being ignored, but rather STILL in a robust cycle of constant improvement and we’ve decided to take a big step – not just small incremental stuff – and that’s going to take time.

    And they are saying that to a few hundred people at a trade show? Why?”

    This is what bothers me most about Apple. The unnecessary secrecy, particularly for the ProApps division.

    They decide to tease new features in FCPX, a program purported to be used by millions of people, but they only show it to a room full of people who happen to be in Vegas and happen to be at that hotel/conference room and happen to be there at the right time and are willing to sign an NDA? If Apple wanted to definitively put the message out there that X was not being ignore, this isn’t how you do it.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    July 12, 2016 at 8:11 pm in reply to: TC Burn In App

    You’re welcome, and hope it helps. That’s the preset I use when we send interviews out for transcription. The files are super small with big timecode.

    Another great little feature of Media Encoder is the ability to transcode footage with a custom LUT applied. It’s also under the Effects tab. So if you have Log footage and need to send out low res previews for client/producer review, you can apply a LUT to the footage sand have it stamp timecode all at once, so you aren’t sending out super flat fooage. And it’s super fast.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    July 12, 2016 at 7:49 pm in reply to: TC Burn In App

    You should be able to just drag it into the Preset Browser pane in the “User Presets and Groups” (upper right pane).

    What version of Media Encoder are you running?

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    July 12, 2016 at 6:49 pm in reply to: TC Burn In App

    Adobe Media Encoder will do it. It’s under the Effects tab.

    Here’s a preset to generate a 360p .h264 file, matching your source frame rate, with timecode burn (for Media Encoder CC 2015 v9.2.0.26).

    https://www.dropbox.com/s/1bfpeuu58tjzml8/Timecode%20Preview%20360p.epr?dl=0

    —————-
    Michael Hancock
    Editor

  • [Shane Ross] “I want to know who ducks audio AFTER they edit scenes?”

    Good point, and this new feature doesn’t automatically do it as you edit. But you could just set your audio a little lower than normal for your first pass rather than duck as you go, then run Audio Ducking and it will generate all the keyframes you need. After that you just go through and adjust to taste. I’ve been playing with it a bit today, and it’s a neat little feature.

    —————-
    Michael Hancock
    Editor

  • [Paul Golden] “If I’m trying to run Resolve 12.5, I’m not sure I can roll that far safely back in Desktop Video.

    I’m using FCPX, Premiere, and Resolve 12.5 and running Blackmagic drivers 10.4.3. Works fine.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    June 21, 2016 at 9:44 pm in reply to: Software update available!

    [John Davidson] “don’t torch my workflow with a haphazard update. It’s reckless.”

    There’s a certain irony in this statement being posted in the FCPX forum, no? And I agree – Adobe needs to change the default behavior to leave the old apps alone, or at least make it a user preference in the Adobe cloud app.

    —————-
    Michael Hancock
    Editor

Page 26 of 222

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