Doom read me v1.0 release full#

Also do a bit of testing about StripeMask as to whether it includes too much. If you find that occlusions aren't being detected enough, yet show on the raw mask, let me know and we can tweak either maskOcc or the merge opacity. VapourSynth occlusion mask is a lot narrower than in Avisynth where it marks large areas.

Pay particular attention to the occlusion mask. This now gives seriously good results!! Please test it and post your reports.

I created a thread for RIFE problems here. Run the same clip twice (with preset='normal') and you'll get slightly different masks. Using diff mode with RIFE is counter-productive, so preset 'rife' uses preset 'slow'. 4ДЄvisynth version now has FullRange parameter If doubling framerate, rife is set to 1-pass.Д¬hanged maskOcc from 105 to 125, and blending with. Preset 'rife' sets rife=2 and maskThr=80. It does have a few bugs that need to be rounded up. Also, VirtualDub process doesn't terminate correctly. The random junk that sometimes appear when running multiple instances does make it harder to test. I confirm that model=1 gives better results. Why does Vpy MvTools have this 'random' factor? I run twice with output='raw' debug=true in VapourSynth, and although the raw mask visually looks the same, the raw value varies randomly. If there remains specific situations causing trouble, the only way would be to have a specific plugin to scan for that problem, just like StripeMask is doing.Д«TW can someone explain this. Full-frame blending or skipping is done based on the raw masks from MvTools. That's pretty much what I'm doing except that RIFE doesn't provide any info as to what artefacts it produces. But if that doesn't work, replace that frame with RIFE 2.4, and if that doesn't work replace with xyz etc. MVTools2 is much faster still, and if it works - great.

Doom read me v1.0 release full#

It would be pure awesomeness if an automatic tiered choice algorithm could choose what works based on least artifacts, then fallback on some of the masking, or full blending if none work.

Scene changes are not handled well either - probably the same underlying issue with those flashing lightsДЄlso, often you can get a 'clean solve' on some frames by pre manipulations such as turnleft, or flipping (then reverting the change post rife) so I asked zorr about zopti maybe figuring combinations out on a per frame basis I'm finding 2.3 seems the best model overall on varied content (but it's not included in vapoursynth version - But YMMV as usual. I've been doing quite a bit of testing and there are frames where 2.4 does better job than 3.1 or 3.8. Yes, RIFE can sometimes produce worse results on seemingly 'simple' content that mvtools2 breezes through without issues