Forum Replies Created

Page 3 of 51
  • Hi Rob.

    Are you using PNG in your settings to save the frame? I have been exporting frames from a timeline in PNG format, then imported them again in FCP X and put them right behind the original video. And I don’t see any difference between the original video and the exported frame. Even the waveform/scopes don’t show any difference.

    – Ronny

  • Ronny Courtens

    April 16, 2019 at 9:25 am in reply to: ProRes RAW and RED patent

    Jeremy from Atomos officially said they are paying a license fee to RED for capturing to ProRes RAW on their devices. And, as Shawn stated, BRAW is strictly not a RAW format because they do a partial debayer before encoding to BRAW.

    I think the term “RAW” is being used pretty loosely these days. When talking with some colorists at Films@59 (a very high-profile post house in Bristol) a few months ago, they surprised me by saying that they did not even consider REDRAW as a true RAW format. But then again they also don’t consider Resolve as a valid tool for their color workflows. They use Baselight and Flame Premium on Supermicro Linux boxes. I guess it’s all in the eye of the beholder.

    – Ronny

  • Ronny Courtens

    April 14, 2019 at 7:32 pm in reply to: Resolve 16 vs FCPX

    [Michael Gissing] “And jumping ship make perfect sense when your boat is taking on water and may sink your business.”

    You see, Michael, there is where the caveat lies. I honestly don’t see anyone right now who feel that their boat is taking water or that their business is at risk just because of the software they are using. Today, I think most people are quite happy with the tools they use. And these tools are not limited to just one NLE. I can see a good future for Resolve, but just not one that is causing the kind of landslides we have witnessed before.

    – Ronny

  • Ronny Courtens

    April 13, 2019 at 11:58 pm in reply to: Resolve 16 vs FCPX

    As an NLE, Resolve is now getting on par with the three other major editing platforms. Just like with the others, this has required BM pushing out a whole boatload of fast updates in the first years. And just like with the others, this update cadence will slow down once the software gets more complete. Although it looks promising, I’m not really sure if Resolve as an NLE will cause a huge shift in the market. For three reasons:

    1. This is not a one-solution-fits-all market anymore. Today, people tend to use multiple tools at the same time or multiple NLEs within the same company. And this seems to work out well for everyone.

    2. Hardcore professionals and enterprises seem to stick with their choice(s) for a long time unless the company that creates their tools screws up. This has happened with Avid who got much too greedy during the transition to HD, causing them to lose a fair amount of users to Final Cut. Then it happened to Apple who got much too cocky with the launch of FCP X, causing them to lose a fair amount of users to Premiere Pro. And now it also seems to be happening to Adobe (just visit the Premiere Pro forums) and here’s where I see Resolve taking its share of the market in the short term.

    But, eventually, every developer recovers from its mistakes. Avid has evolved and still holds strong in film and television. FCP X has evolved and has become the most widely used NLE in our market. And I am expecting a major overhaul of Premiere Pro in the not-so-distant future. So I don’t doubt that Resolve will eventually get its fair share of the market, just like the others. But I don’t see any major landslides or worldwide ship-jumping happening. People who constantly jump ships tend to fall into the water anyway (-:

    – Ronny

  • I just noticed you said that you also might apply audio changes to the compound clip. You cannot do this with adjustment layers. So Brett’s solution might be better for you.

    – Ronny

  • Dirk is correct.

    Julie, in your particular case it would be better to use adjustment layers.

    Instead of applying your color corrections onto the compound clip, open the CC and put an adjustment layer on top of the clips inside the CC. Then apply your color correction or whatever video effects to the adjustment layer. This way, your changes to the CC will ripple through all your projects where that CC is used.

    – Ronny

  • Ronny Courtens

    April 7, 2019 at 2:42 pm in reply to: Avid Media Composer gets slick overhaul

    Absolutely hate that interface, much too cluttered for me. But great to see Avid MC finally catching up with modern workflows on the performance side. Hopefully, this will keep their small but loyal user base happy for another few years.

    – Ronny

  • Ronny Courtens

    April 7, 2019 at 12:15 pm in reply to: Opening file with extension *.fcpbundle fails

    You need to zip your Libraries before uploading them into the cloud.

    – Ronny

  • Ronny Courtens

    April 3, 2019 at 2:02 am in reply to: Relink

    I am a big fan of NFS because it’s more stable than SMB and it supports hard links. But we do have many clients who use mixed workflows over SMB and I can say that FCP X editing performance over SMB equals that of NFS.

    I did find that file copies over NFS are much faster. These are two screenshots I made recently when remotely testing a large Jellyfish Rack setup with 70 FCP X users at one of our clients in Switzerland (not Swiss national tv). You can see that transfer speeds between NFS shares are much stabler (fewer traffic drops) and that average transfer speeds are higher (370MB/s over SMB and 500 MB/s over NFS).

    The Jellyfish (even the small Mobile) runs FCP X Libraries straight off the server without any issues. I actually don’t know any of our clients who do NOT keep their FCP X Libraries or their Premiere Pro project files and cache on their Jellyfish. We can do this because we use advanced hi-level caching in all of our systems.

    Relinking files on a Jellyfish is exactly the same as relinking files on a direct attached drive, no matter f you use NFS or SMB. If you are at NAB next week, I will be happy to demo this. We are at the Frame io booth on the floor, in our demo suite at the Encore (send me an e-mail if you want to come and visit: ronny@lumaforge.com), and at the Faster Together Stage: https://lumaforge.com/nab

    – Ronny

  • Ronny Courtens

    March 30, 2019 at 6:02 pm in reply to: Library will not open after Final Cut Pro update

    I have never seen FCP X ask me to convert a PNG file to a .mov video file when updating a Library, that even does not make sense.

    To be clear:

    1. You opened the Library, it asked you to update the Library to the newest version and then you got this strange message, is that correct?

    2. You say you converted a PNG file to MOV. Where was that PNG file, and how did you convert it to MOV?

    3. What did you do with the MOV file after the conversion?

    – Ronny

Page 3 of 51

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