Resolve 15 VFX?
- Thread starter Tamerlin
- Start date
hscully
Veteran
Cool. I’m a big Resolve fan and have been using it exclusively. I’m also catching up with Fusion. There’s a lot to know but it is really capable. Maybe an integration would include some simpler tools such as a Delta keyer right on the edit timeline. Right now Fusion Connect works really well.
I am going to download their free version and start learning it. Got to comfortable with Premiere Pro. Resolve benchmarks seems to show twice the speed in rendering, with many seem to be very happy working with Resolve. Soon BM will buy a photography software and integrate it with resolve. Adobe, you better watch out.
filmguy123
Veteran
Not interested in learning a new software tool at this time but very happy to see the continual progress here. There needs to be serious pressure on Apple and adobe in this space, and BMD is delivering.
Batutta
Major Contributor
Going from FCP7 to resolve was much easier for me than going from 7 to X. Just downloaded 15, and for the free version they are still crippling h.264 playback. 4k h.264 GH4 files are choppy during playback, while FCPX on my system handles them just great. You have to pay for the studio version to get better h.264 playback apparently.
Thomas Smet
Veteran
As cool as merging the two applications together is it really wasn't that big of a deal to have them as two programs. Its cool and it has certain advantages but it is not as earth shattering amazing as some of the reactions have been. Its more of a convenience feature.
The reality is not a lot of people use Fusion. Its kind of like programming for video. I think this was a solution for BMD to leverage Fusion as a means to sell more Resolve copies and keep Fusion funded for future development. Even Grant himself said he isn't sure what will come from this merging of the two applications. Perhaps more people will now use Fusion but considering it was free and pretty easy to launch and get started and people ignored it before might mean it still doesn't gain a huge user base.
The reality is not a lot of people use Fusion. Its kind of like programming for video. I think this was a solution for BMD to leverage Fusion as a means to sell more Resolve copies and keep Fusion funded for future development. Even Grant himself said he isn't sure what will come from this merging of the two applications. Perhaps more people will now use Fusion but considering it was free and pretty easy to launch and get started and people ignored it before might mean it still doesn't gain a huge user base.
Thomas Smet
Veteran
I'm not saying it isn't nice to have them together but that there was nothing wrong with them in the past. Fusion was always there and had a free version with the same capabilities as it has now. Nothing really changed other than the fact that users now only have to download one application for free and click on the tab and actually learn how to use it. Getting clips back and forth was not that complicated.
What stopped people from using Fusion before?
I used Shake before Apple killed it and have a background and degree in VFX so I don't think I am underestimating the user base of Fusion. Fusion is a complex program and not one that a ton of people had a huge interest in. Even with the free version a lot of people ignored it. I believe thats why it was rolled into Resolve. It just never yielded the kind of sales BMD was hoping for. Its really the nature of the target market for such a tool. There are only X number of VFX compositors that use a program like Shake, Nuke or Fusion. No matter how much I love a program like Fusion it just will never reach the market share of a tool like Resolve.
Anyway I'm glad to have the update. I just find it odd that Fusion was there and free and now all of a sudden people are excited about it like they never had access to it before.
Yes, there was a free version, but like its free Resolve counterpart its feature set was limited. But unless I'm mistaken, Resolve Studio 15 contains the full version of Fusion, essentially for free.
Last edited:
Thomas Smet
Veteran
It was not that limited at all. Not any more limited than the free version of Resolve. Fusion could do 2D and 3D comps, load 3D models and use almost all fo the nodes including the Delta Keyer and only some of the advanced stuff like noise reduction was deactivated. In fact Fusion may now be even more limited by the free version. For example Fusion 9 didn't have a resolution limit. I could load DCI 4k or 4.6k content no problem. The free version of Resolve 15 however is limited to UHD or lower resolution. Since you can't load in any content larger that means the Fusion built in is now also limited to UHD.
There may be other new limitations I haven't run into yet but basically now if the free version has a limit then so will Fusion. Another example is loading 10bit material from the GH5. Resolve 14 could load it with the paid version but not the free version. Fusion on the other hand could make use of ffmpeg as an alternative loader to load the 10bit files from the GH5. Unless Resolve 15 suddenly supports the GH5 for free that means Fusion will now also have this limitation.
My point was that the new version of Resolve will have the full version of Fusion effectively for free. At least that may happen eventually. Buried in the press release, which I didn't see until today, is the following: "Adding Fusion to DaVinci Resolve has been a massive project that will be completed over the next 12-18 months." The separate, standalone versions of Fusion 9 will continue to be available for those who need them. As to the limits of the free Resolve 15's Fusion component once it's fully integrated, who knows what BMD will do? For example, by then, the UHD output limitation may have given way to "8K" UHD (7,680 x 4,320). The collaboration features, however, will likely always be a premium.
Even doing the most basic animations (not even getting into particles or ray tracing) I would run out of memory on my loaded 2017 MacBook Pro with Radeon 460 when using the full version of Fusion. Resolve, on the other hand, runs great. Hoping the new integrated version uses memory better on the Fusion side.
Jim Feeley
Veteran
I **think** the issue here is licensing fees for h.264. I have some familiarity with the issues, but perhaps BMD thinks it's just easier to pay MPEG LA (et al) than to pay lawyers to ensure/get/win clarity. Kind of a bummer, but considering the astoundingly low cost of great post tools these days, it's pretty easy to accept.
As for Fusion, sure it may not have a huge potential market. But a friend who's motion design company has a dozen or so Nuke licenses is intrigued. And ya, they're a design company, not a VFX company. So that's something. More significantly, I think, Steve Roberts, the former CEO (and original developer of Fusion) is happily still working at BMD. We've been acquainted for 20ish years, back when Fusion was REALLY fast but had an arguably overly-clever interface, and when we chatted at NAB he said he's really happy to not have to deal with the business side of software and to be concentrating on R&D.
I also met a few other Resolve programmers who worked at DaVinci before the BMD acquisition and are still there. They too seem really engaged in what they're doing. Same with Fairlight. That's all good news, but a common theme was that the teams working in the different apps/panels/sections of Resolve can share some common code (when it makes sense), metadata, etc. But, and I'm guessing here, the different teams all have enough high-end experience in their fields to not settle for common code at the cost of compromised performance. BMD didn't just acquire intellectual property, they hired the programmers who came up with that IP...
I'm not trying to be a Resolve pollyanna, like we're all saying here making all those post tasks live together in one app has got to be difficult. But jeepers is Resolve getting interesting.
Also: BMD said they expect the Resolve 15 beta cycle to run a couple of months and emphasized that they consider it a "real" beta cycle to find and squash bugs and not an endless grind.
I've installed the Beta version of Resolve 15 on 2 different 2012 12 core mac pro's and each time i click on the Fusion tab Resolve crashes.
each computer has 64 gb RAM and one has a 12gb GTX Titan X and the other a GTX 780 3gb both flashed from macvidcards.
I've never had a problem with earlier versions of Resolve on either of these machines.
is this just the nature of a Beta release?
anyone else had this problem?
david
each computer has 64 gb RAM and one has a 12gb GTX Titan X and the other a GTX 780 3gb both flashed from macvidcards.
I've never had a problem with earlier versions of Resolve on either of these machines.
is this just the nature of a Beta release?
anyone else had this problem?
david
Jim Feeley
Veteran
Did you dig through this?
DaVinci Resolve 15 Configuration Guide
http://documents.blackmagicdesign.c...07/DaVinci_Resolve_15_Configuration_Guide.pdf
"Systems using NVIDIA GPUs and also not using DaVinci Resolve from the Apple App Store will need to have the correct NVIDIA and CUDA driver to operate the GPUs. While Resolve will check the CUDA version on your system you may have to update it after any OS updates."
Perhaps the macvidcards driver version you have isn't quite right for the just-released Resolve 15 beta?
At NAB, BMD was showing Resolve running on iMac Pros. At least, they had a bunch of those; perhaps there were a couple other configs that I didn't see. So perhaps cheese-grater & nVidia compatibility is on the to-do list?
DaVinci Resolve 15 Configuration Guide
http://documents.blackmagicdesign.c...07/DaVinci_Resolve_15_Configuration_Guide.pdf
"Systems using NVIDIA GPUs and also not using DaVinci Resolve from the Apple App Store will need to have the correct NVIDIA and CUDA driver to operate the GPUs. While Resolve will check the CUDA version on your system you may have to update it after any OS updates."
Perhaps the macvidcards driver version you have isn't quite right for the just-released Resolve 15 beta?
At NAB, BMD was showing Resolve running on iMac Pros. At least, they had a bunch of those; perhaps there were a couple other configs that I didn't see. So perhaps cheese-grater & nVidia compatibility is on the to-do list?
Yes, it typically is. The purpose of a beta is to get a wider array of testers to test the software before release. Alphas are internal and usually have a small audience of testers (i.e. the developers and the QA team), so the betas invariably expose problems that they didn't encounter. Open beta are actually pretty uncommon; they're basically saying, "We know it isn't ready, but we're letting you kick the tires early in exchange for providing us feedback that helps us find bugs and improve the software."
Expect bugs, missing features, strange quirks... and when you find them, report them to BMD.