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. |
21st January 2016, 15:43 | #23 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
https://github.com/IFeelBloated/vapo...ses/tag/test13
test13 precision boost 1. SAD (float -> double) 2. SATD (int16_t -> double) 3. DCT (uint8_t -> even more precise than float) and also features some cosmetic changes from @ jackoneill |
5th February 2016, 17:24 | #24 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
https://github.com/IFeelBloated/vapo...ses/tag/test14
test14 A. Full Precision Boost 1. DCT (float -> double) 2. Motion Analysis (float -> double) 3. Super (float -> double) 4. Overlap (float -> double) 5. Variance (float -> double) 6. Degrain (float -> double) and more... basically everything works at double precision, rounded to single precision only at the final output stage B. Bug Fixes fixed a bug inherited from the avisynth plugin (bit shift operation on negative values, reported by @Are_ via runtime debugging) |
5th February 2016, 17:38 | #25 | Link | |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,555
|
Quote:
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
|
7th February 2016, 13:04 | #27 | Link |
Registered User
Join Date: Aug 2012
Posts: 203
|
Probably you'll see some speed difference if you enable auto vectorization [on GCC -O3 and -march=corei7-avx]. Right now it isn't any slower because latency between float and double is the same [5 cycles on the latest intel generation], the little speed difference is probably due to memory access, fftw is 2x slower due to loss in vectorization [in a 128bit vector register can fit 4 floats but only 2 doubles].
I'll be more interested to know if this precision boost is really useful |
8th February 2016, 08:30 | #28 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
floats lose precision as the calculation goes on, and giant plugin like mvtools comes with hell lot of calculations, double precision is required to do the intermediate stuff if you want the final output features a real single precision, otherwise it's just low precision data in a single precision format..
|
12th February 2016, 23:43 | #29 | Link | |
Registered User
Join Date: Aug 2012
Posts: 203
|
Quote:
While i understand the using of single precision for this kind of calculation, i think that double is rather overkill. But let make clear that this my statement is not supported by actual facts, i'm willing to change my mind [but please, try to make some better example than the one you did on fmtc thread] |
|
8th April 2016, 17:09 | #30 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
https://github.com/IFeelBloated/vapo...ses/tag/test15
test15 A. Colorspace all floating point colorspaces are supported now, GrayS, RGBS and YUV4xxPS (note that dct 1-4 on YUV clips might be kind of buggy, as chroma features a different range from luma, will be fixed in the next release) B. Degrain the stupid "thsadc" and "limitc" parameters got their asses canceled, "thsad" and "limit" have been made arrays "plane" parameter won't do nothing on RGB and GRAY clips, all planes will be processed C. stuff, here and there.. bug fixes shamelessly copied from @jackoneill Last edited by feisty2; 8th April 2016 at 17:11. |
9th April 2016, 09:40 | #31 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
so I been testing, RGB colorspace has been supported but,
I found motion estimating under RGB is not some kind of nice thing to do, I mean, it works, but the quality sucks comparing to just do it under YUV 4:4:4 convert your RGB input to YUV before applying mvtools on it, or, anyways, mvtools will happily take the RGB input and feed you back with some shitty motion estimation if you give it like some RGB input directly |
16th April 2016, 13:24 | #32 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
https://github.com/IFeelBloated/vapo...eleases/tag/r1
r1 first stable release!!! A. sanity check. will raise an error if the input is not single precision fp or features varying dimensions B. DCT fixed dct stuff on YUV input |
24th June 2016, 14:26 | #35 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
r3
A. BlockFPS 1. added support to overlap (merged from Fizick's master branch) 2. new modes, mode 6-8, occlusion mask weighted on SAD (merged from Fizick's master branch) B. Compensate 1. new parameter "time", use it to do partial time compensation (merged from Fizick's master branch) C. Bug Fixes 1. vector length was clamped to 127/pel on motion flow functions, now it's 2147483647/pel, practically unlimited (Fizick relaxed it to 32767/pel, I decided to do it more thoroughly) D. Precision Boost 1. internal masking for motion flow (uint8_t -> double) 2. simpleresize for masks (uint8_t -> double) floating point precision MMask should be super easy to implement now (all internal stuff are double already), but I didn't do it anyways like, yeah, I'm all fucked up lazy |
30th July 2016, 13:11 | #38 | Link |
Registered User
Join Date: Feb 2010
Location: Saint-Petersburg, Russia
Posts: 38
|
VS Editor crashes on simple
Code:
import vapoursynth as vs core = vs.get_core() src = core.d2v.Source(...) last = core.fmtc.bitdepth(src, bits=32, fulls=False, fulld=True) super = core.mvsf.Super(last) last.set_output() Last edited by ~SimpleX~; 30th July 2016 at 13:35. |
|
|