Forum Replies Created

Page 20 of 1040
  • Remember the days when people complained that Resolve worked best with Nvidia cards. I’ve heard from some quarters Resolve can be quite zippy on Macs (and AMD of course) at least with some functions.

    I wonder if Adobe’s base will be eroded by Resolve over time. Perhaps not there yet but maybe a couple of years down the road.

  • Craig Seeman

    February 14, 2019 at 5:46 pm in reply to: Eye tracking matte in Fcpx

    CoreMelt TrackX/SliceX There’s also FXFactory CrumplePop EasyTracker.
    Otherwise, frame by frame by hand.

  • Craig Seeman

    February 11, 2019 at 9:12 pm in reply to: SXS pro card driver

    Are the drivers Mojave compatible?
    Sony is often far behind in OS compatibility on Mac.

  • Craig Seeman

    February 3, 2019 at 4:52 pm in reply to: Converting Prores RAW without loosing quality

    [Grzegorz Kwiatkowski] “We don’t want to loose any bit of quality.”

    Transcodes generally impact quality. They may not be observable and, with the right one, may have little impact on compositing or grading. That said, the best way to go would probably be to transcode to ProRes 4444. Of course, depending on your workflow, there may little appreciable difference between recording ProRes Raw and recording ProRes HQ which the Atmos Shogun also supports and you’d save the transcode, the time and space involved with that.

    When choosing an acquisition codec you really need to evaluate your entire workflow as sometimes more isn’t better, it’s just more, more time, more money, more storage space.

    Do you really need a ProRes Raw to ProRes 4444 workflow over ProRes HQ?
    Of course, if you were working in FCPX, ProRes RAW could easily make sense over ProRes HQ in many cases.

    If not losing any bit of quality is REALLY your primary concern then you would edit in FCPX on Mac. Again you need to really determine what your priorities are and what is the best workflow for your job from an agnostic position.

  • Craig Seeman

    January 19, 2019 at 7:32 pm in reply to: Burn H.264 to Blu-ray without re-encode

    A meaningful example.

    From this forum about 8 years ago.

  • Craig Seeman

    January 19, 2019 at 7:31 pm in reply to: Burn H.264 to Blu-ray without re-encode

    That’s a very broad question. Theoretically yes if your source falls within Blu Ray specs.

    In order to have any kind of meaningful response you have to describe your workflow and indent.

  • Craig Seeman

    January 15, 2019 at 3:11 pm in reply to: Accumulating compressor mxf files

    Presets couldn’t be much more intuitive and there’s always the Help menu too. That links to the complete User Guide (manual).

  • Craig Seeman

    January 15, 2019 at 3:05 pm in reply to: Accumulating compressor mxf files

    RippleTraining Digital Distribution and Encoding with Compressor costs all of $19.

  • Craig Seeman

    January 4, 2019 at 2:59 pm in reply to: Need advice with VirtualDub Encoding/Saving avi

    It depends on what your intent is with the resultant files. VirtualDub hasn’t been updated in more than five years and doesn’t support some of the “modern” codecs preferred in typical video post production workflows.

    If you can access x264 encoder that might be a workable option but it would be .mp4 extension. Again it’s not clear what your intent is. x264 wouldn’t be my choice for post production work.
    https://www.youtube.com/watch?v=bKgkLAoAEv8

    Some contents or functionalities here are not available due to your cookie preferences!

    This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

  • Craig Seeman

    December 12, 2018 at 10:48 am in reply to: Adobe pro video apps now support ProRes on Windows

    [David Cherniack] “Well BRAW is an acquisition codec like ProresRaw only tied (so far, and probably indefinitely) to BM cameras. Not being a delivery codec like Prores, I don’t see how it might factor in A’s decision to license Prores to Adobe.

    Because, as you see here on this on other forums, there’s a general residence to trust Apple’s proprietary codecs. It may well factor into the business decision a camera manufacturer may make in their decisions to license codecs.
    BRaw is being made freely available. ProRes Raw is not. Industry players (both manufacturers, developers, end users) may make decision on paying an “Apple Tax” (licensing) especially when there are alternatives.

    We’ll never know for sure but I can’t help but think BRaw, announced shortly after Apple’s ProRes Raw, the (short term) ATMOS deal along with implementation by DJI, may have resulted in Apple rethinking its approach to codec license if its goals standardization based on market share.

Page 20 of 1040

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