@arum great!

One idea thing: if you have very noised video, do not remove all noise. Motion compensated denoise works not as good as needed in this case, because it produces moving objects those looks noised in a motion phase. Or stationary areas may become static noise that looks horrible. So it is better to get it less aggressive or add another (own) noise on the top of the result.

In the Core edition default denoise filter parameters are:

MotionDenoise420(bs=32, frames=4, th=350, limit=10, pel=2, dct=9, smode=4, ssteps=2, bitdepth=OutBitdepth)

They are good for low noise sources.

For a very noised source, try to decrease a frame count to 2 or even to 1 (frames=2). Try also limit denoise by decreasing limit=10 down to limit=2 or even limit=1. Another way to tweak is to decrease a threshold value th=350 to th=50 or less.

But, for some cases (static camera and no fast object moving) increase th up to 2000 (find a value you like). It will remove totally any noise, but may give additional artifacts for moving areas.

To add noise, uncomment NoiseY(amp=1.0, seed=0, bitdepth=OutBitdepth)

and increase a noise strength value from 1.0 up to 10.0 (see better values in the final video that plays, not in a static preview or low fps drawing, because noise in static is looking very differently as in the video playback). Paid editions allow to use a film grain emulation that looks better that a simple noise.

@rean Please check Cineform, excellent codec

What about google's VP9? It says it's royalty free and can do 444 and is supported in Adobe. But for all other editors you have to use free converter to change codec, so it's a longer workflow for those people but maybe still useful.

The problem is in the distribution of the Core edition. Every binary codec distribution (even free) requires a license fee. It is a cause why Google created VP9. I can create exr or similar cinema output that compatible with all NLE, but it is very slow. Also I can use DirectShow for input, but it is also slow (transcode is required, like in Wm 1.0 where I used utcodec - it is an AviSynth multi-threading incompatibility problem with DirectShow).

Probably I will found a solution, but currently I have no usable idea. Also it is required to many Wm code changes.

update:

@Manicd VP9 is a good idea. I see some internet messages that it supports 10/12-bit. Can you test it? Also a performance report of encoding 4K lossless 10-bit would be fine. If it will be ok, I will try to port the plugin code to be exported from Wm and try to create DirectShow import like Wm 1.0. It will allow to complete remove any FFmpeg code from Windmotion and to continue to develop it.

Is there any way for the program to require a separate installation of ffmpeg? That way it could all ffmpeg when it needs to do encoding, and no binary codec distribution would be required.

What about this?

http://www.openh264.org/faq.html

Hi @rean, maybe following tool could help you to analyse denoise effects due to windmotion. I developed a kind of SCOPE which analyses just a given line z on your screen with given direction (yellow line). If you choose a blurred area then deviation of rgb values shows the noise (top-left) of each channel. To get a better idea the noise of each rgb channel is just normalized and amplified shown (bottom-right). There you can also see a bar graph which shows the deviation of these amplitudes. You can analyse a steady picture as well as a dynamic video as it updates with approx. 10fps. It can be compiled for windows and mac as I used lazarus for cross platform development.