Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
31st July 2016, 07:46 | #43 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
guess there's quality gain more or less, but mainly for being free of clamping (more mathematically correct) in floating point format rather than higher precision
Last edited by feisty2; 31st July 2016 at 07:48. |
31st July 2016, 20:10 | #45 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
you might not see any "real" difference between int8 and int16 most of the time, not to even mention int16 and float32
I started this for my OCD about placebo precision, wanted it to be as mathematically correct as possible, but the actual reason that makes this useful is there're HDR videos out there, HDR videos contain colors even brighter than white or even darker than black, and integers couldn't handle stuff like that, and floats could. |
3rd August 2016, 16:18 | #47 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
r5
Bug Fixes 1. truemotion was corrupted(bug inherited from jackoneill's branch), fixed. 2. the SATD implementation was completely incorrect, did some research and rewrote that from the beginning, SATD works correctly now |
4th August 2016, 00:13 | #49 | Link |
Registered User
Join Date: Feb 2010
Location: Saint-Petersburg, Russia
Posts: 38
|
I've made some stupid compatibility layer for mv and mvsf (mvmulti, 8..32 bit support, incomplete function set). Maybe it would be useful for someone.
Last edited by ~SimpleX~; 4th August 2016 at 00:17. |
4th August 2016, 00:40 | #50 | Link | |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,548
|
Quote:
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
|
4th August 2016, 08:41 | #52 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
theoretically you cannot expand DegrainN to the partial sum of a series like ∑[x=1, y](DegrainRadius[x] * P[x]) (∑[x=1, y]Radius[x] = N, ∑[x=1, y]P[x]=1), it works but the result is very different from DegrainN
Code:
mv123 = core.mv.Degrain3(clip, super, *v[:6], **kwargs) mv456 = core.mv.Degrain3(clip, super, *v[6:], **kwargs) sm = core.std.Merge(mv123, mv456, 0.4615) edit: made the statement more rigorous Last edited by feisty2; 4th August 2016 at 09:41. |
4th August 2016, 11:23 | #53 | Link | |
Registered User
Join Date: Feb 2010
Location: Saint-Petersburg, Russia
Posts: 38
|
Quote:
|
|
7th November 2016, 22:07 | #56 | Link |
Registered User
Join Date: Apr 2016
Posts: 85
|
Hi feisty2,
I'm using BlockFPS to get to a lower FPS (29.97i to 59.94p via QTGMC then to 23.976p) using this code : Code:
clp = core.fmtc.bitdepth(clip,bits=32,fulls=False,fulld=True) super = core.mvsf.Super(clp,pel=4,hpad=16,vpad=16,rfilter=4) bw_1 = core.mvsf.Analyze(super,isb=True,blksize = 16,overlap=0,search=3,badrange =-24) fw_1 = core.mvsf.Analyze(super,isb=False,blksize = 16,overlap=0,search=3,badrange =-24) clp = core.mvsf.BlockFPS(clp, super, bw_1, fw_1, num=24000, den=1001, blend=False) clp.set_output() |
19th December 2016, 11:30 | #57 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
r7
Bug Fix fixed a clip length calculation bug in BlockFPS, reported by groucho86 New Feature extended SATD to 64x64 128x128 and 256x256 blocks Uncategorized replaced Hadamard ordered SATD with the Sequency ordered variant, levels faster.. |
Thread Tools | Search this Thread |
Display Modes | |
|
|