Page 1 of 1

Resizing imported titles - Terrible quality!

PostPosted: Mon Jun 04, 2018 10:28 am
by Johan Fleetwood
Hi,

Right now I'm working on a 1080p project where all titles are 2160p png's, and already the input scaling produces jagged edges and 'stray pixels'.

Setting the input scaling to 'crop' or setting the timeline to 2160p prevents the input scaling from doing its dirty deeds, but NO means of resizing in resolve (except Fusion) manages to produce an even acceptable quality.

The easiest way I've found so far (in this project) to get good quality resized graphics is to set 'crop' mode, use Fusion Transform with appropriate filtering for the resizing, and then use 'Input scaling' in the Color tab to conveniently position the titles.

This issue seems to have nothing to do with straight/premultiplied alpha or which file format you use.
With PSD, TIF, PNG etc you pretty much get UNUSABLE resizing in Resolve, and you really shouldn't have to use Fusion for such a common task.

As much as I like the development we've seen the last couple of years, this is just AWFUL and really should be a top priority of things to fix in Resolve.


Resolve 15B4, Win 10 current, I7 6700K, 32GB RAM, GTX 1080

Re: Resizing imported titles - Terrible quality!

PostPosted: Mon Jun 04, 2018 10:38 am
by Gabriele Gelfo
I found the same issue scaling high resolutions png logos with transparent background.
It seems that Resolve and Fusion programmers don’t talk together because Fusion does the job very well.
Few lines of code and it is done.

regards

Re: Resizing imported titles - Terrible quality!

PostPosted: Tue Jun 05, 2018 8:51 am
by Tom Early
Johan Hansson wrote:Hi,

Right now I'm working on a 1080p project where all titles are 2160p png's, and already the input scaling produces jagged edges and 'stray pixels'.

Setting the input scaling to 'crop' or setting the timeline to 2160p prevents the input scaling from doing its dirty deeds, but NO means of resizing in resolve (except Fusion) manages to produce an even acceptable quality.

The easiest way I've found so far (in this project) to get good quality resized graphics is to set 'crop' mode, use Fusion Transform with appropriate filtering for the resizing, and then use 'Input scaling' in the Color tab to conveniently position the titles.

This issue seems to have nothing to do with straight/premultiplied alpha or which file format you use.
With PSD, TIF, PNG etc you pretty much get UNUSABLE resizing in Resolve, and you really shouldn't have to use Fusion for such a common task.

As much as I like the development we've seen the last couple of years, this is just AWFUL and really should be a top priority of things to fix in Resolve.


Resolve 15B4, Win 10 current, I7 6700K, 32GB RAM, GTX 1080


do these have alpha channels or are results bad either way?

Re: Resizing imported titles - Terrible quality!

PostPosted: Tue Jun 05, 2018 10:52 am
by Johan Fleetwood
Tom Early wrote:do these have alpha channels or are results bad either way?


They have alpha channels.

When disabling the alpha, I can clearly see that the resize erodes the fill and at least the alpha seems to suffer from a simple resize algorithm with little or no filtering.

Also, changing the Inspector/Resize Filter it seems there's no difference between Sharper and Smoother.
The same goes for Bicubic and Bilinear, but they look even worse.

From what I can tell, the fill/image resizing seems the same with or without alpha (besides the eroding), and it would be great if the edit resize filterering could be the same as in Fusion.

Re: Resizing imported titles - Terrible quality!

PostPosted: Tue Jun 05, 2018 2:24 pm
by roger.magnusson
If Performance Mode is activated it can affect which resizing algorithm is used for preview, depending on how the Performance Mode settings are set in Preferences > User > Playback Settings.

It shouldn't affect renders though, but you're seeing this in rendered files as well so this is a different issue?

Re: Resizing imported titles - Terrible quality!

PostPosted: Tue Jun 05, 2018 3:14 pm
by Johan Fleetwood
roger.magnusson wrote:...you're seeing this in rendered files as well so this is a different issue?


Yes, the problem unfortunately is still there in rendered/exported media.