DaVinci Revival Features We Want In Resolve

Hi,

Cinematek Belgium here. We still use DaVinci Revival Pro in our restoration workflow. Recently we got some next generation software, but Revival still remains essential.

We would appreciate it if BMD considers adding these features to Resolve, as it is uncertain how long we can still run Revival. We have managed to get Revival running in a Virtual Machine, but due to the old age of CentOS 6, there are a lot of issues regarding graphics speed and network speed to access our fast SAN environment.

Features we absolutely miss:
-Splice Damage repair
-Vertical Streak removal

Features to improve:
-Automatic Dust Busting: the current implementation does not work well at all. It either completely misses a lot of dir/dust, or when applying it more agressively it completely removes the grain. As an archive, we are not a fan of grain removal. I know some institutions add back some grain after, but that's not the way we like it. Further more, when a moving arm/hand is mistakenly detected as dirt, it's very cumbersome to exclude it using a mask (power window). It would be much, much faster if you could just draw masks with a pen directly on the image like with the Manual Dust Buster fx.
-Manual Dust Busting: since resolve 17, it has greatly improved, many thanks for that. If we could have an "auto detect" feature, that resembles the functionality of the automatic dust removal in Revival, then we could simply click the "bad" detections to remove them, or drag them around or change the algorithm for a better repair.

Features we need:
-Gate Weave Stabilisation: with multiple modes: sprocket holes, frame edge, ...

Kind regards,
Nick

There is a separate forum for Feature Requests.

viewforum.php?f=33

Best practice is to search first, to see if someone already asked. If not, post one idea per thread with a very brief description of the idea in the thread's title.

We would appreciate it if BMD considers adding these features to Resolve, as it is uncertain how long we can still run Revival. We have managed to get Revival running in a Virtual Machine, but due to the old age of CentOS 6, there are a lot of issues regarding graphics speed and network speed to access our fast SAN environment.

I think these are good ideas, but Revival has been gone for a long time -- 9 years? 10 years? My suspicion is that this isn't a business Blackmagic wants to be in.

I would really like to see all these features added as OFX plug-ins, but I think the Resolve engineers have their hands full just getting 17 finished as-is. If I had to be in this business today, I'd just buy MTI DRS Nova (which I think is about US$10,000) and use that as a fully-featured film-restoration tool.

I think these are good ideas, but Revival has been gone for a long time -- 9 years? 10 years? My suspicion is that this isn't a business Blackmagic wants to be in.

Well, I would agree with you, but they made the manual Dust Buster OFX plugin, and greatly improve it in version 17. It seems to me like they haven't given up on that segment of the market yet. I guess these things are only used by a small fraction of Resolve users. But it still seems like a good idea to transfer some IP they still have and works well, like the splice damage repair.

I would really like to see all these features added as OFX plug-ins, but I think the Resolve engineers have their hands full just getting 17 finished as-is. If I had to be in this business today, I'd just buy MTI DRS Nova (which I think is about US$10,000) and use that as a fully-featured film-restoration tool.

Absolutely agree. And respect to the Resolve team. We tested DRS Nova, and I thought it was very good.

I'm using Davinci Resolve for a 'second pass' cleanup after a first pass with restoration software known as VIVA PRO. I'm really happy DR17 improved the tools for their manual clean-up.

I am having one issue where the cursor is a 'plus' sign and does not draw a box at the cross-hairs of the plus sign (cursor). The box gets drawn outside and to the right of the cursor. Is anyone else experiencing that? It could be a minor bug I'm going to report it.

Thanks, Bart