fmtconv: resize, bitdepth and colorspace conversions

[asarian]

Originally Posted by videoh

I like to remind people to look at the CPU utilization too, because savings can be applied to CPU things, especially encoding.

Consider my following script:

import vapoursynth as vs

core = vs.get_core ()
core.max_cache_size = 8192

core.avs.LoadPlugin ("C:/Program Files (x86)/dgdecnv/x64 Binaries/DGDecodeNV.dll")

vid = core.avs.DGSource (r'i:\jobs\inter.dgi', resize_w=1920, resize_h=1080, fulldepth=True)
vid = core.dghdrtosdr.DGHDRtoSDR (clip=vid, fulldepth=False)
vid = core.avs.DGDenoise (vid, strength=0.12, searchw=9)

vid.set_output ()

The typical CPU-utilization for a job like this is 99% CPU (for the x264 process), and about 0.3% for vspipe (YAY GPU!)

On a non-GPU accelerated jon, CPU saturation for the vspipe process is around 50% (with haf.QTGMC). So, yeah, whatever can be done in GPU, I'll take it!

[videoh]

Originally Posted by asarian

So, yeah, whatever can be done in GPU, I'll take it!

Have a look at DGBob() and PVBob() instead of QTGMC for deinterlacing if you are after blazing speed. Decomb is also implemented for GPU (DGTelecide and DGDecimate).

Maybe getting OT for this thread.

[asarian]

Originally Posted by videoh

You may like this one as it is GPU accelerated. Apply it after resizing on the GPU (if needed) for maximum performance.

I'm loving it!

I noticed, however, that sometimes DGHDRtoSDR still leaves things too washed out, as it were. See: https://1drv.ms/u/s!AhSxhQ9g_mrMlEJQ6vC4Z8ExAKlg

Those are stills from the movie Divergent. The overlapped image (on the right, with the black bars) is from the original blu-ray; the underlying, big image is what DGHDRtoSDR produced (with default values).

In Photoshop, I needed +48 contrast to have it look kinda like the blu-ray. Sadly, I found no contrast parameter for DGHDRtoSDR (brightness didn't seem to affect much of anything). Is there a way to achieve this?

Thanks.

EDIT: 'what DGHDRtoSDR produced' from the UHD source, of course.

[videoh]

Originally Posted by asarian

Sadly, I found no contrast parameter for DGHDRtoSDR (brightness didn't seem to affect much of anything). Is there a way to achieve this?

Use Tweak() in your Avisynth script.

[asarian]

Originally Posted by videoh

Use Tweak() in your Avisynth script.

Thanks. I see it's part of havsfunc itself.

[RainyDog]

Is it possible to use fmtconv to resize and crop together?

For example, in avisynth you can the below script when the exact crop is a row of 21 black pixels at both the top and bottom to avoid either overcropping or undercropping by 2 pixels.

Spline36Resize(1920, 1038, 0, 21, -0, -21)

Thanks.

[sneaker_ger]

See documentation about "resample" "sx", "sy", "sw", "sh" parameters.

sx, sy

Coordinate of the top-left corner of the picture sub-area used as source for the resizing. They can be fractional. If negative, the picture is extended by replicating the left pixel column.

These parameters are arrays, so it’s possible to specify a different value for each plane. The last value is used for the unspecified planes. The coordinates are always related to the pixel dimensions, you don’t need to scale them with the chroma subsampling.

sw, sh

Size in pixels of the sub-area to resize. They can be fractional. If 0, the area has the same size as the source clip. If negative, they define coordinates relative to the bottom-right corner, in a Crop-like manner. These parameters are arrays like sx and sy.

[zorr]

Originally Posted by Wolfberry

If you are using the dll from the official release, I will recommend to use the one from ChaosKing's FATPACK or the one in my signature as it is compiled with a newer compiler and might save you from random crashes.

I'm using the FATPACK version but fmtconv.dll is dated March 2016 and has the exact same date as the official version. Is the more recent (and hopefully less buggy) version still available somewhere?

[asarian]

Originally Posted by zorr

I'm using the FATPACK version but fmtconv.dll is dated March 2016 and has the exact same date as the official version. Is the more recent (and hopefully less buggy) version still available somewhere?

I'm using the one Wolfberry linked to (his own version), but the link doesn't seem valid any more. Sad, because that one is very stable.

[zorr]

Originally Posted by asarian

I'm using the one Wolfberry linked to (his own version), but the link doesn't seem valid any more. Sad, because that one is very stable.

Could you share the file? It could be included in the next FATPACK.

[asarian]

Originally Posted by zorr

Could you share the file? It could be included in the next FATPACK.

Here it is: fmtconv.dll

It's for 64-bit, btw.

[poisondeathray]

wolfberry has 3 public shared fmtconv versions, which one are you linking to? or is it a different one ?
https://drive.google.com/drive/folde...mHKYLzO3elemlC

[asarian]

Originally Posted by poisondeathray

wolfberry has 3 public shared fmtconv versions, which one are you linking to? or is it a different one ?
https://drive.google.com/drive/folde...mHKYLzO3elemlC

If I recall correctly, he had a separate vapoursynth directory there (which I couldn't find any more earlier either). The fmtconv version I took was dated 8 Dec 2018 (which I don't see any more either). Said directory had things like a new libdfttest too.

[wonkey_monkey]

A warning, as people still seem to be posting directly to threads and may not be aware:

It appears that the forum may have been hacked. There is a suspicious "test" announcement, apparently from tebasuna51 (but probably not), parts of the forum are not working, and there appear to be some malicious javascript files.

I'm not speaking in any official capacity here, but I would recommend, at the very least, NOT entering your password anywhere on Doom9 for the time being.

Please refer to this post: https://forum.doom9.org/showthread.p...wpost&t=176128

[asarian]

Originally Posted by wonkey_monkey

A warning, as people still seem to be posting directly to threads and may not be aware:

It appears that the forum may have been hacked. There is a suspicious "test" announcement, apparently from tebasuna51 (but probably not), parts of the forum are not working, and there appear to be some malicious javascript files.

I'm not speaking in any official capacity here, but I would recommend, at the very least, NOT entering your password anywhere on Doom9 for the time being.

Please refer to this post: https://forum.doom9.org/showthread.p...wpost&t=176128

The guy that did speak in an official capacity ('Swede'), is he legit?! He has locked his announcement, so I can't react, but suggests ppl change their password... which would be an ideal hack (as you need to enter your old password on the form there too) if it's illegit.

[videoh]

Swede is legit.

[asarian]

Originally Posted by videoh

Swede is legit.

Puts my mind at ease. Thanks.

[groucho86]

Hi everyone,
Just opened up an issue on fmtconv's github, wondering if anyone had any insight here.

I have a SGamut3.Cine Linear EXR. It seems like the Linear to Slog3 conversion is clipping in the highlights.

import vapoursynth as vs
import muvsfunc
core = vs.get_core()

input_path = 'source_sgamut

c = core.imwri.Read(input_path,float_output=True)
c = core.fmtc.transfer (clip=c, transs='linear', transd='slog3')
c.set_output()

Test material is here:
https://github.com/EleonoreMizo/fmtc...o_slog3_tb.zip

Includes:
source_sgamut3cine_linear.exr <-- source file
resolve_delinearized.tif <-- expected result
vs_delinearized.png <-- fmtconv result

[age]

Yes it looks so

import vapoursynth as vs
import muvsfunc
core = vs.get_core()

input_path = 'source_sgamut

c = core.imwri.Read(input_path,float_output=True)
#c = core.std.Expr(clips=[c], expr="  x 0.9 *")
c = core.std.Expr(clips=[c], expr="  x  0.01125000 >= x 0.01 +  0.19 / log 10 log / 261.5 * 420 + 1023 / 171.2102946929  95 -   x *   0.01125000  95 + /  1023 / ?")
c.set_output()

Not sure if the resolve result is right either, maybe there is need to scaling from linear to reflection multiply by 0.9

https://github.com/videovillage/Latt...sues/issues/17

https://pro.sony/s3/cms-static-conte...7494271406.pdf

[groucho86]

Thanks age! Your expr matches well to the DCTL I am using in Resolve. The 0.9 does not seem relevant in this case.

Any idea why fmtconv would be clipping? I looked at TransOpSLog3.cpp and nothing's jumping out at me. Maybe I'm not looking in the right place.