Download x264 10 bit ..rename X264.exe in X264-10bit.exe

put in C:\Soft\Video\Windmotion\x64\

Sorry for my poor English..

Hello Gh2 hack Flow 2.02-Windmotion 0.4.0.Alpha7-Summilux 25 dg

Original (Extract to TIFF) http://www.mediafire.com/view/?drl1wfbbcnr4t8c

Utvideo 444 (Extract to TIFF) http://www.mediafire.com/view/?4uyscbcq3hfvz4f

Download the files..

Make avi utvideo ds silent rgb.bat

:)

@kurt10

In both examples you posted we can clearly see that more details have been extracted from the original clip when we zoom in to the converted image. However, I am not finding any increase in detail when I examine the files I've upsampled.

Are you applying sharpening to your files? If not, would you mind explaining the steps you are taking from stock file > final output. I must be doing something wrong and have no clue how to proceed outside the limited instructions in the read me file.

TIA

@RRRR Strange. Prores 4:4:4 is implemented with two export versions: over ffmpeg or ffmbc. Also there is a mkv and avi export with utcodec - currently the fastest possible free lossless codec for Windows.

Cineform export probably may be implemented, but in 8 bit over avi, if there is a free DirectShow encoder available. 10 bit or more is not possible, because it requires c++ coding but I don't want to code it. I have no time and finances for this. Use H.264 if you really need in 10 bit.

You can also manually create any export you like over DirectShow (8 bit only) or ffmpeg (up to 16bit) using existing export scripts as an example. Also you can change a resulted container for any other, not only avi, mkv or mov.

@zsero, Yes, but it is not avs2avi that can use system API to encode video. Avs2yuv passes raw console output to unix-like command line tools. Has cineform command-line tools those understand this method?

Oops. I have bad news, guys.

I made ​​a mistake on a development stage, thinking that using 4:4:4 instead of 4:2:0 will not take too much space and will increase the processing time quite a bit. But in reality it turned out it's different. I have usage results on a real big video project (one hour of 50p video 1920x1080).

The current script set is too slow for one hour video (two weeks of processing) and it eats around 3-4 TiB memory space. It is too big and slow for regular use (I have smaller HDD size and cannot render this project).

I have also big problems in stability of Avisynth for these big files. These problems can be fixed, but in cost of processing time. Also a realtime processing will not be possible in this case.

So we need to cut most of features, i.e. disable 4:4:4 processing or decrease the resulted quality and usability. Also a release time will be shifted to the far future.

Sorry for all who wait for a release.

Windmotion is back... I found a way to get it faster, easier and more stable with only a very small quality loss. Also I use this version in a real commercial video project now. So, a final version (with a documentation) will be ready soon.

Version 0.6.0.Alpha9, 2013-06-18

This is a fully rewritten version.
Support of 4:2:0 and 4:2:2 is added for fast processing.
Support of multiple project resolution and color mode profiles.
Script architecture is changed for speed and usability.
Memory use optimizations: new 4:4:4 file format, less temp file usage.
Speed optimizations: fast algorithms, Y8 code, file format changes.
Simple Windmotion directory structure.
Export optimizations (H.264 by default with ffmpeg, params).
Better 8-16-8 bit conversion.
Better 601/709 color conversion.
Better lossless H.264 files support (fastdecode, keyint 4).
Better multichannel audio support (L,R channels in PlayEdit).
Better NEX-7 color shift profiles (Pro).
Film and audio project support is improved (Pro).
Fast preview avi (720p 4:2:0) for film scripts (Pro).
Full set of film functions is added (Pro).
Audio compression (mp3 and flac) is added (Pro).
Sony HX20 optimized profile is added.
Support of different camera models are temporary disabled.
Internal 16-bit masktools functions. Dither.avsi is removed.
Most components are updated to the latest version.
Some components are removed, new components are added.
Bugfix: dehalo and sharp code is corrected.
Bugfix: Crash on long files is fixed on i7 (2 or 4 threads).
Bugfix: avs2yuv is used instead of avs2avi because crashes with Avisynth MT.
Many other small improvements.

Can someone please provide some more video samples? I don't know why this isn't generating a lot more buzz. This stuff is great.

Probably this is the latest alpha. Beta versions are coming soon.

Version 0.7.0.Alpha10, 2013-06-25

EncodeFilm360.bat is added.
EncodeFilm H.264 presets are speed+quality optimized now.
Denoise functions quality optimizations.
A possibility to change fps after denoise.
Sharp quality optimizations (Pro).
New denoise functions, including GPU-based (Pro).
Encode film in mp4, aac, flac is added (Pro).
Optimized film encode presets (Pro).
Automatic film clip names generation (Pro).
New function MotionBlur8 (Pro).
Optimized Sony HX20 Avsi (Pro).
x264, ffmpeg, flac, LAVFilters, MatroskaSplitter are updated to the latest versions.
Bugfix: Stability of Edit scripts improved (crash on denoise).
Bugfix: PlayEdit clipboard paste command Ctrl-V works correctly now.
Scripts refactoring and optimizations.
Range of camera support added.
TODO: Documentation in progress.

Windmotion 4K Technology Preview Sample.

This is a ProRes video sample in 4K (4096x1714, 4:2:2, 406 Mbps). It is created from a Panasonic GH2 footage (1920x1080, 4:2:0, 140 Mbps) using Windmotion 0.8.0 Beta 1 Pro Edition. Processing: crop, YUV denoising, upsacale, special detail sharp, film grain noise and dithering. All processing made in Windmotion only.

Video is updated, see page 7 for examples

Footage copyrighted by Space Ludwig.

The beta version will be available to download soon. This version will be final development version before version 1.0. This version is currently tested on real Full HD video projects.

@virgilr, there are 4 denoise types available now to use (but one in a community edition). Any processing is per channel independent. Probably it may help in keying, but I have no test results yet. GH2 has poor U and V channels even on 140 Mbps. Also any other H.264-based encoding cameras have the same thing.