Forum Replies Created

Viewing 1 - 10 of 10,333 posts
  • Craig Seeman

    July 25, 2022 at 9:35 pm

    Accusonus is out of the audio plugin business.

    https://accusonus.com

    Dylan John has this tutorial on making your voice sound deeper.

    https://www.youtube.com/watch?v=DvTCySB24wI

    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

    July 20, 2022 at 4:34 pm

    Many of the better gyro stabilization videos I’ve seen suggest using 90° or even 75° shutter angle to avoid issues with motion blur.

    It would seem the best use of it is when you’re working with a prime lens without its own OIS when going handheld so one would have the forethought to use a much higher shutter speed. Its purpose is basically just to get rid of the micro jitter one would get otherwise. On BMD this might be a common need. I’d imagine this would be less important on Sony cameras given their IBIS.

    From what I understand BMD Gyro isn’t an option in Resolve if you have a lens with OIS and it’s enabled. So they put the kibosh on that (so far… Resolve 18 is beta after all).

  • Craig Seeman

    July 20, 2022 at 12:24 pm

    BMD cleverly and inexplicably made it so you have to shoot BRAW with certain resolutions/settings. Which is clearly just a ploy. In which case, big whoop. I can run everything through Resolve in minutes or use the aforementioned plugin

    That may well be the issue/game that BMD plays. Really for most work, even broadcast work Apple ProRes HQ may be all that’s needed. Only in the most demanding feature film or high-end advertising would RAW (and BRAW isn’t quite raw) have notable advantages.

    Alas BMD cameras have a growing base given their low point of entry. It’s as if BMD uses BRAW specifically to frustrate FCP users by slowing down the workflow with transcodes and adding to storage costs. Now they’ve thrown in gyro stabilization which is only supported in Resolve.

    All this does seem to make Sony “cinema” cameras more attractive with their 422 10-bit I with flexible autofocus and IBIS (and ProRes RAW with Atmos if you really need it).

    BTW I hate track-based editing and I say that with experience going back to the earliest Avid around 1990 or so. You can throw in all the bells and whistles in an NLE but nothing beats the magnetic timeline and organizing tools in FCP for speed, efficiency, and flexibility.

    Now if only there were a way more cameras could record ProRes RAW internally (I suspect the RED patents stand in the way).

  • Craig Seeman

    July 19, 2022 at 9:02 pm

    There’s also a plugin for FCP from the Color Finale developers that transcodes from BRAW to ProRes. The problem is that takes time and means creating another large file. Also one can import into Resolve (which is free after all) and then export to ProRes. All this is a lot of extra work.

  • Craig Seeman

    July 19, 2022 at 3:14 pm

    I’ve heard similar analysis to Robin’s elsewhere as well.

    The problem is the end user still has to make a difficult workflow decision.

    As far as the post production market is concerned one might has how many Blackmagic BRAW users are there vs ATMOS with ProResRAW users. Few people have the choice between both codecs so hardware (BMD Cameras vs other camera with ATMOS) is going to dictate the choice.

    While it’s only anecdotal I hear more about FCP users moving to Resolve than the other way around. I don’t doubt that’s added by BMD including the full version of Resolve free with the camera. That may mean BMD will win this war by attrition.

  • Craig Seeman

    June 28, 2022 at 9:55 pm

    This COW post mentions that FCP7 can run on High Sierra.

    https://creativecow.net/forums/thread/final-cut-pro-7-now-works-in-mojave-and-high-sierr/

    I’ve heard that “Retroactive” mentioned in that post allows it to also work on Mojave.

    That’s also mentioned in this article

    https://appleinsider.com/articles/20/10/27/how-to-run-aperture-iphoto-and-older-versions-of-itunes-on-macos-big-sur

    If you have access to a Mac running either macOS Mojave or macOS High Sierra, you can get more. Macs running those systems can also install Final Cut Pro 7, Logic Pro 9, and iWork ’09.

    Final Cut Pro 7 now works in Mojave and High Sierra using Retroactive

  • Craig Seeman

    June 23, 2022 at 11:59 am

    And today there’s more salt in the wound of FCP.

    Blackmagic added Gyro stabilization date to the Pocket Camera’s BRAW in today’s camera firmware update. Major important for a camera that has no IBIS.

    Of course, Resolve 18 Beta will be getting this update very shortly.

    I love FCP but us Pocket 4K (recording to ProRes) but this update adds a very good reason to move to Resolve. FCP just can’t handle Pocket Cameras to their best advantage and it costs 0$ to move to Resolve (only the time to relearn the older more widely established non-magnetic track-based timeline which I have 20 plus experience in before FCPX’s introduction).

  • Craig Seeman

    June 23, 2022 at 12:01 am

    There’s lots of speculation back and forth as to which company is blocking.

    Some believe it’s Blackmagic because they’d prefer their camera uses to use Resolve and buy their additional hardware (edit controller, color controller). Note that Resolve does not support ProRes Raw.

    But if Blackmagic were the culprit they’d be preventing Premiere Pro from using it as they’re a much bigger threat.

  • Craig Seeman

    June 14, 2022 at 11:44 am

    Use software that has a good deinterlacer.

    Sorry, but without further details, we can only give general information. Either you’re not using software with deinterlacing or your not setting it correctly for your source.

  • Craig Seeman

    May 20, 2022 at 2:40 pm

    Features are only one area at issue.

    In some cases there are editors who already prefer FCP but are being told no by others in the chain of command. There’s also the lack of integrators who can support the end-to-end workflow chains and concern about the talent pool should hired post people pull out during a project. All these are training and support rather than feature issues.

Viewing 1 - 10 of 10,333 posts

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