I always found Color’s layer methods to be very fast – faster, in fact, than copy/pasting specific nodes in Resolve. The comment about Color was partially layers and partially quality of the look. I don’t think it did that because of the number of layers, but rather because of the convoluted video pipeline I had created. At that point the 2013 Mac Pro’s GPUs started flaking out. I tried the same thing with one of their presets, which consist of several layers within each preset. So then as an experiment I compounded the clip and added yet another instance on top (last section of the video), which included a Koji film stock LUT. The adjustment layer also had CF2Pro applied and it also had several layers. In this video, I used several layers on each clip and then an adjustment layer on top of that. It’s probably also an issue of where they are placed.
I haven’t stacked layers too terribly deep, but I don’t think there’s a limit, except in what the GPU will handle. So it might simply be a preference issue. I believe the developer’s background involves experience with Filmlight (Baselight) systems, which also don’t use nodes. Naturally every NLE may cause a bad day like that, but things like that can really can you.īut more on-topic and related to your question, from what I can tell, implementing nodes in FCPX might pose some issues with the UI.
#Color finale review fcpx manual
Automatic (the default) wasn’t working right, so switching to manual and turning off one option fixed it. Turned out to be an optimization setting in preferences. For example, I hit a really weird one today, which was that some Alexa clips would get blown up by about 300% or more when I played or scrubbed the source clip or the timeline.
#Color finale review fcpx plus
Plus there are tons of gotchas buried in its complexity.
I work with Resolve on a regular basis and IMHO, it’s still pretty rough around the edges as an NLE.
0 kommentar(er)
