- Posts: 627
- Joined: Sat Nov 19, 2016 6:21 am
Kays Alatrakchi wrote:
I really don't understand why the everything-under-one-app is a bad thing. If you don't like the other components, simply ignore them and treat Resolve 15 the same way that you would treat Fusion — go in, get what you need done, and get out. There is a general sense that more functionality = code bloat, but that is not necessarily true. For instance, color grading in Resolve was not negatively impacted the moment that the other modules were added.
Fusion in Resolve has a much larger memory footprint, considerably slower and worst of all has much stricter hardware requirements than Fusion standalone. I cannot run Resolve on hardware I CAN run fusion on. This includes render nodes.
Also, I cannot do all the things I can do in Fusion, please see my lengthy response in the previous page.
This has severely impacted the usefulness of Fusion in Resolve. This is bloat from a Fusion user POV.
Kays Alatrakchi wrote:I find far too many veterans in the industry to be very rigid in their ways, and looking at change always in a negative light. This is true for the hardcore users in many apps out there. I really don't understand the resistance to change, or the reluctance to realize that the industry and workflow are in constant state of evolution.
Theres no reluctance to change from the industry, in fact a lot of the tools you use today came from r&d and production tools. This includes Nuke and Fusion, Naiad, Mudbox etc etc. However, since you stated that you're not a compositor I can understand how it may seem like it.
Major feature films employ literally hundreds of VFX artists to solve the work, it all has to be coordinated, planned, produced and be tailored to the specific needs of the film. This requires specialists (roto
artists, compers, coordinators, supervisors, pipeline TDs etc) and specialists tools (like Nuke, Fusion, Houdini etc) to solve very bespoke problems. There isn't such a thing as "all under one roof". Hence the need for surgical tools, and a stable and predictable environment to work in. (Tools can be beta, but they have to be predictable in their usage)
Film VFX is a custom build pr show, sequence and even shot. It requires flexibility and special-purpose tools, some of which can be abstracted to fit a bigger picture sure. But in general its not just about just the features, its about how flexible a tool is to fit this special and fluid workflow. Lets say a new Renderer comes along thats super fast, does almost everything we need and reduces our rendering time from 20min pr frame to 1 second, but it doesn't support any pipelining/scripting/or some other hook that VFX REQUIRE, then the tool is practically useless. Not because its not a good tool, but because it doesn't fit the needs at a fundamental level.
This is Resolve (right now) due to be reasons I mentioned in the previous page.
I hope this sheds some light on the subject for you. Happy to give more production examples if you need.