Forum Replies Created

Page 46 of 222
  • Michael Hancock

    April 11, 2013 at 6:21 pm in reply to: 20 minutes of the NAB media composer demo.

    True resolution independence (2K and 4K projects, custom project sizes), better AMA responsiveness (lessening the need to transcode/consolidate, but MC7 may address some of that), better effects handling, more timeline improvements (nudge clip up/down a track, clip enable/disable), improved color correction toolset, scripting/automation ability, ability to export quicktime reference with AMA or long GOP footage, closed captioning encoding, etc…

    There are still a ton of things Media Composer could use to improve the editing experience, but I’m really excited for what MC7 promises. Huge steps forward with LUT application and reframing shots using source media resolution.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    April 8, 2013 at 1:47 am in reply to: Avid announce MC7

    Looks like some form of resolution independence as well. And LUT support maybe. Those are pretty significant in my workflows – very excited to learn more.

    —————-
    Michael Hancock
    Editor

  • [Lance Bachelder] “…the FCPX debate forum”

    The FCPX or Not debate forum. Adobe is obviously part of the or not.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    April 4, 2013 at 2:50 pm in reply to: Adobe NAB Sneak Peeks

    Not as many steps as the Prelude route, but still not as elegant as importing a text file and syncing footage directly to the script. The fact that you have to use Story complicates everything unnecessarily, in my opinion. But I am glad that the option is there – I just hope to see it improved and simplified.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    April 4, 2013 at 2:40 pm in reply to: Adobe NAB Sneak Peeks

    Click here and watch the video called: Adobe Premiere Pro and Prelude: Find clips faster based on a script

    It seems to do what ScriptSync does, but in way more steps and with much less elegance. That said, it’s a start.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    April 2, 2013 at 7:46 pm in reply to: MXF file folder structure

    Avid kind of puts the files where it wants, as far as the numbered folders go. I believe it’s supposed to switch to another numbered folder when the folder it’s capturing/transcoding/consolidating to gets 5,000 files in it. But outside of that, there is no way to really control which number it goes into.

    I wish you could. And I wish there was a dedicated render folder too you could nuke. Would make archiving a lot easier.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    April 2, 2013 at 7:43 pm in reply to: The Cloud is the future! Except…

    I had an instance where SoShareIt was down for a day. Sent a file to the client and the link was dead when they got it. I couldn’t log in and see that the file had uploaded, either. The next morning it was live again. Like anything – have a backup plan waiting. If a file just has to be there I send it through a combination of YouSendIt, SoShareIt, WeTransfer and/or FTP.

    But SoShareIt was great when I had 24GB to send to somebody – took less than a day to upload and deliver.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    March 28, 2013 at 7:52 pm in reply to: FCPX, Premiere Pro and Finishing Echo System

    [Shane Ross] “That seems like a fine solution…QT and EDL.”

    It works, but I still prefer AAF or XML so you can render from Resolve with handles, just in case there are last minute tweaks. Plus it makes working with transitions easier – they aren’t baked in.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    March 28, 2013 at 7:43 pm in reply to: FCPX, Premiere Pro and Finishing Echo System

    Not easily. You can transcode it to a self contained quicktime and use an EDL to notch it in Resolve, but there’s no media manager that transcodes to an intermediate codec. It’s a huge hole in the Premiere workflow.

    —————-
    Michael Hancock
    Editor

  • Select all the clips in your bin (the ones with .new.xx on them), then File–>Import. Click on Options, click the Shot Log tab, and click the box at the bottom that says “Merge events with known clips.” Hit OK. Select the ALE you revised and click Open. It will merge the name from the ALE with the name of your selected clips in the bin, removing the .new.xx.

    I use this trick all the time to preview footage at the finder level and type comments into the ALE while the footage is transcoding in Avid (DSLR footage, primarily). When the transcode is finished I import the ALE and merge it with the clips and my comments field is automatically populated with everything I logged using finder and the preview function. Super useful.

    —————-
    Michael Hancock
    Editor

Page 46 of 222

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