Hi! It’s been a long time since I last used Topaz, I’d put my old family videos aside until now.
So I decided to get back into it, and for the moment, I’m using a workflow I didn’t use before.
To put it simply, I use DaVinci Resolve before sending the video to Topaz. But to open it in DaVinci, I have to go through VirtualDub first. At first, I used the “Muksun” deinterlacing filter in VirtualDub and exported the video as an uncompressed AVI to open it directly with Topaz.
Now, if I want to open it with DaVinci (which is rather temperamental), I no longer use Muksun or any filters. I make a direct copy of the video stream, and then I can import it into DaVinci.
The second step involves reusing NeatVideo (sometimes on noisy sequences that Topaz handles rather poorly) with a good profile and a mix around 30%. NeatVideo no longer removes as much detail as it did with version 6. It has improved considerably and, above all, is much faster because it manages CPU resources better. In short, most of the time I don’t even use it.
In DaVinci Resolve’s project settings, I set the deinterlacing to normal (or high, I haven’t noticed a difference between the two). I think Neural Engine should be avoided because it still uses AI, and even if it produces less of a combing effect, I doubt it truly preserves all the original details.
Next, I do some color correction. That’s where DaVinci Resolve is amazing. To send the video to Topaz, I make sure to lower the highlights in the “Color Grading” section to around 50 or 60%.
It seems to me that DaVinci Resolve is the only software that can recover detail in blown-out highlights. It’s quite astonishing.
I use the MotionCam app to film in 4K RAW with my smartphone, and when you record a video, you see the three primary channels on the screen. If a single color is clipped, DaVinci Resolve is able to recover the video information thanks to highlight recovery. It’s the same principle, in my opinion, with our old SD videos, even if the recovered details aren’t as striking as with our current RAW videos.
Here’s an original screenshot/highlight recovery:
I modified three options:
-
Highlight recovery, at -50%.
You can see more detail in Santa’s (my dad’s) basket, a bit more detail on the little boy’s (myself) white sweater, and in general, faces have a better tone. I think you shouldn’t set the recovery to 100% when there’s a blown-out sky, for outdoor videos, otherwise the sky will be too gray and it will look unrealistic.
In a situation like this, it might be a good idea to use Power Windows with tracking to recover highlights everywhere except the sky. I’m not familiar with tracking, but I’m going to learn! It’s worth it when a Topaz model invents details and creates strange lines that shouldn’t be there (Power Windows + tracking with a slightly more aggressive NeatVideo filter in the affected area).
-
The lift is slightly higher (0.2) to boost the blacks (black compression). If it’s set too high, the details in the dark areas are less contrasted, but there’s no noise amplification.
-
The shadows are boosted (16). This works in the opposite way to the highlights to brighten the image. Unlike the lift, the blacks aren’t compressed even though they’re brighter, so the noise is amplified. This can help Topaz better see the details in the shadows.
So I’m trying this setting, even though I’m not a color grading expert, but it seems like a good approach for improving the image with Topaz initially.
Anyway, that was a (small) digression. But you get the idea: to recover a bit more detail 
Next, I usually export as uncompressed AVI, but I think it might be better to import as PNG. I’ve noticed that when I use the 2x upscaling with Topaz in 8-bit PNG, I get visible banding in certain areas. I’ve talked quite a bit with my friend Gemini about how to better manage VirtualDub, DaVinci Resolve, and Topaz, and he advised me to export in 10-bit. When trying YUV2, YCBCr, MagicYUV, in 422 or 444, etc., I recover slightly less detail, which I noticed particularly with the blue or green trash can icon, depending on your perspective.
However, when selecting “422 YCBCbr 10-bit (v210)” in VirtualDub’s color depth settings, I recover the missing detail, but there are lots of black specks in the blown-out areas. So, it’s unusable. I’ve tried many settings, and even with a lot of adjustments to color depth and compression, when saving as AVI, DaVinci Resolve refuses to open them. Only Direct Stream Copy works to recover all the original details.
And so, by exporting as a 16-bit PNG with Topaz, once re-imported into DaVinci Resolve, I no longer have this banding.
Here’s a screenshot of the rendering with “422 ycbcbr 10 bit (v210)” enabled in the color depth settings:
So, I’m going to continue my tests by exporting with Direct Stream Copy using VirtualDub, exporting as a 10-bit PNG with DaVinci Resolve (uncompressed PNG or AVI), and exporting as a 16-bit PNG with Topaz to be sure. Aside from this subtle color correction, I apply Anarchy’s deflicker effect (the best I’ve found, it works very well on my footage) with these values:
For the third step, I simply use the Proteus v4 x2 template (1440 x 1152) in Topaz. With everything set to auto, I might want to adjust the parameters for certain dark sequences or those with a lot of movement, or even use NeatVideo before sending to Topaz.
I then export as a 16-bit PNG to send back to DaVinci Resolve for color correction and noise reduction, in an HD (1280 x 720) timeline.
I follow this workflow, but I think that for the Proteus pass, I’ll crop the video to remove the black bars on either side and use 20% cropping for stabilization.
here : original/upscaling:
I’m still a beginner with color depth and VirtualDub compression. Even DaVinci Resolve isn’t quite up to scratch for me. I’m thinking of doing tracking on certain sections only, using specific filters. It shouldn’t be too complicated, and from what I’ve tried, it allows me to save shots where Proteus creates strange artifacts, like here (on the sort of gray plate behind the girl):
This is the workflow I’m currently developing. Any suggestions or corrections would be greatly appreciated! 