SmoothAdjust [v3.20 - Update 2015/11/15]

[Dogway]

Sorry sorry, seems that the last example did work. I don't understand still why but its ok.

If I use ditherpost (mandatory) after smoothcurve16 or at the end of the 16b chain for dithering, there's no point on having the "dither" parameter in smoothcurve16, just wondering

[LaTo]

Originally Posted by Dogway

Sorry sorry, seems that the last example did work. I don't understand still why but its ok.

No problem, it's great that everything works

Originally Posted by Dogway

If I use ditherpost (mandatory) after smoothcurve16, there's no point on having the "dither" parameter in smoothcurve16, just wondering

Yes, you can disable it (unless you have a full 16bits chain with a 16bits display ^^)

[LaTo]

v2.00 beta6:
added SmoothCustom

Todo-list:
- improve debug view
- fix all bugs

Download here: > SmoothAdjust v2.00 beta6 <


SmoothCustom is considered "alpha", I can't test everything alone.
So if some people are motivated, here is what to do:
- find expressions that crash
- find expressions that produce a syntax error
- find expressions that output a false result
- find expressions that work but which should not



PS: All informations about SmoothCustom are in the readme.

[LaTo]

v2.00 beta7:
improved debug view
tweaked smoothing

Todo-list:
- fix all bugs

Download here: > SmoothAdjust v2.00 beta7 <

[leeperry]

for the new build!

[Dogway]

Thanks LaTo!
Is it possible to implement lsb_in, for reading stacked 16b?
I normally put color correction at the end of the chain, that's why

[LaTo]

Originally Posted by Dogway

Thanks LaTo!
Is it possible to implement lsb_in, for reading stacked 16b?
I normally put color correction at the end of the chain, that's why

Yes it's already implemented...
Simply use SmoothLevels16(), SmoothTweak16(), SmoothCurve16() and SmoothCustom16().

[Dogway]

Yay! Thanks you \(^o^)/

[jmac698]

Hey, this is great, I'll have to test it. Can you add avg and std and atan2 to the functions in smoothcustom?
Even better, correlation

[Dogway]

LaTo, since long Ive struggling trying to convert PC values to TV values. Normally this is a workflow:

SmoothLevels(preset="pc2tv",smooth=10,limiter=0)

sat=0.0
Cb=0.0
Cr=-0.0
SmoothCurve(\
ycurve="0-0;16-16;30-32;60-50;116-95;190-150;228-208;236-236;255-255",\
ucurve="0-"+string(128*(-sat))+";"+string(int(128-(128*Cb)))+"-"+string(128+(128*Cb))+";255-"+string(255-128*(-sat))+" ",\
vcurve="0-"+string(128*(-sat))+";"+string(int(128-(128*Cr)))+"-"+string(128+(128*Cr))+";255-"+string(255-128*(-sat))+" ",\
smooth=10,show=true,limiter=false)

Is it possible to do everything in one step inside smoothcurve? What operations should I do to convert the ycurve values to PClevels?

I also observed that the first value must be an integer in order to work...

Another issue is the graphs in the debug view, they change position depending on input values length. It makes it hard to compare 2 different graphs to check the changes.

Thanks for all the hard work.

[atra dies]

Is it wrong to use smoothlevels16 on linear y values?

Blacks wash out much earlier on than in ylevelsg, even before gamma=2 whilst ylevels can go up to 9 with this dark movie. I am trying to replicate ylevels with chroma=0.

smoothlevels16(input_low=0,gamma=1.2,input_high=65535,output_low=0,output_high=65535,chroma=0,lmode=0 or 3,ecurve=1,dither=-1,smooth=0,limiter=0)

[LaTo]

Originally Posted by jmac698

Hey, this is great, I'll have to test it. Can you add avg and std and atan2 to the functions in smoothcustom?
Even better, correlation

Yes I will add some functions in the next version.
No problem/bug/crash in SmoothCustom?

Originally Posted by Dogway

I also observed that the first value must be an integer in order to work...

ex: SmoothCurve("a-b;c-d;e-f")
In this expression "a", "c" and "e" must be an integer.

Originally Posted by Dogway

Another issue is the graphs in the debug view, they change position depending on input values length. It makes it hard to compare 2 different graphs to check the changes.

I will add a parameter "to fix" the graph position.

Originally Posted by atra dies

Is it wrong to use smoothlevels16 on linear y values?

Blacks wash out much earlier on than in ylevelsg, even before gamma=2 whilst ylevels can go up to 9 with this dark movie. I am trying to replicate ylevels with chroma=0.

It's because ylevelsS or ylevelsG doesn't follow a linear conversion.
Simply use Lmode=1 or 2 in SmoothLevels for the same behaviour.
On top of that you can add protect=16 (or protect=4096 for 16bits) which protects the black parts.

[Dogway]

Thanks LaTo, by chance wouldn't you know what operations requires converting one value from PC levels to TV levels?

for example in PC levels I want to convert the value of 30 to 50 ("30-50"), what is the equivalent in TV levels?

SmoothCurve(\
ycurve="0-0;30-50;255-255",\
smooth=10,show=true,limiter=false)


SmoothCurve(\
ycurve="0-16;30-x;255-235",\
smooth=10,show=true,limiter=false)

[atra dies]

Originally Posted by LaTo

It's because ylevelsS or ylevelsG doesn't follow a linear conversion.
Simply use Lmode=1 or 2 in SmoothLevels for the same behaviour.
On top of that you can add protect=16 (or protect=4096 for 16bits) which protects the black parts.

Well I tried to replicate that with version beta 5, lmode3 (3 = limit conversion on bright areas (apply conversion @100% at luma=0 & @0% at luma=255)), ecurve 1, and chroma=0 which is why I found the result surprising. Should they have behaved similarly? I didn't want to protect anything cause I added borders later to avoid brightening them. Or is ylevelsg supposed to limit on the dark, not the bright? (going to check it now)

Edit: I think ylevelsg does something similar to lmode 1 with a low ecenter thereby protecting the blacks. Would be nice to know the exact center of the curve.

[leeperry]

hi LaTo, is there anything I'm overlooking here please?



It works fine w/ 1.33 DAR, but w/ 1.5(untouched SAR) I get this error msg

[LaTo]

Originally Posted by leeperry

hi LaTo, is there anything I'm overlooking here please?



It works fine w/ 1.33 DAR, but w/ 1.5(untouched SAR) I get this error msg

Maybe because you use multithreading, height[480]/threads[4] = 120

[leeperry]

Ah, you nailed it! Any chance of allowing 120 as a minimum instead of 128?

[LaTo]

v2.00 beta8:
added "scale" parameter for debug view
relaxed minimum frame size (128 for AVX & 64 for SSE2)
added sinh, cosh & tanh in SmoothCustom

Todo-list:
- fix all bugs

Download here: > SmoothAdjust v2.00 beta8 <

[leeperry]

I was eagerly hoping for a new build w/ more better colors, but this will do

for the new build, and especially the lower minimum frame size requirement.

[jmac698]

added sinh, cosh & tanh in SmoothCustom

Great, but could you add avg, std, atan2 at some point, as per my original request
avg(a,b)=(a+b)/2, std=standard deviation of the pixels, atan2(a,b) like atn