DTL2020

>Trying to test idea: do not make copy of MVs data to data of the class FakeBlockData but only save pointer to the 'array' in the class FakePlabeofBlocks and make...

Well - may be simply make copy of MVs array (per each plane if required) with memcpy() to the special allocated buffer in the each PlaneofBlocks class ? And possibly...

Well - the incoming pointer looks were alive but not keeped to the required data and updated somewhere. So the only current version is based on copying to local for...

> If you force push with your fixes, your pull request will be renewed and won't contain fix of a previous wrong commit. And how to 'force push' via github...

In B and C looks you not need to make 2 MSuper if you not modify 'clip' (like pre-filtering for MAnalyse). Your first MSuper already create all levels required for...

> No, the chroma location itself cannot be the issue, because the problem is not consistent. Some patches are being shited other are not shifted. Do disabling of 'truemotion' preset...

"So MAnalyse returns only one set of vectors for all planes. " Yes. But when you process in 4:2:0 the UV planes are twice smaller and the quantization error in...

If this UV for 4:2:0 quantization error is important and need to be reduced - may be add 1 more option to MSuper - to twice enlarge UV planes for...

So we need new special mode of processing - for example multi-pel MSuper for colour clips (if input is not 4:4:4) and keeping track of different MVs to real sizes...

For correct MDegrain you need the same colour formats for 'current' and 'other' frames (also same sub-pel refined planes). It is typically done by MSuper() with calculating of pel-refined planes...