Personal View site logo
Make sure to join PV on Telegram or Facebook! Perfect to keep up with community on your smartphone.
Please, support PV!
It allows to keep PV going, with more focus towards AI, but keeping be one of the few truly independent places.
Windmotion - upsampling to 4:4:4
  • 263 Replies sorted by
  • @rean Will there be some friendly user interface? Or we better say - GUI? I once installed your software (many months ago) but crashed my head in finding out how this "beast" works... And I still haven't figured it out...

  • @humpman It should import mjpeg .mov files using "Generic File.bat" script. If you have a camera that writes these files, send me in a pm a short video example and a camera model. I will create a special profile for your camera. Currently I have added GH3 and FS100 camera support by user requests.

  • @rean Great job, looking forward to the new beta. I think upsampling to 2k would be great for those wanting the benefits of the process without incurring the huge file and rendering time penalty.

  • Does this work with mjpeg .mov files?

  • @endotoxic a beta version is planned in a next week or two. There are some things those are not ready really to be published. A final release will be available after tests, ~ in a next month, but these are no plans to change anything more, so the coming beta version will be ready for production use and final questions “how to...” or "how do I...". I am testing it currently on my next real video project. Many bugs and issues are already fixed in this testing.

    A documentation will be written after beta publishing. As you see, this year I have created many development versions where you can see a huge amount of cardinal changes in every release to release. It is because I create as great software as I can create and optimize everything. Also I want to keep my time and CPU use time, so it must be as fast as possible with long projects for hours of rendering. I have now a great project of summary video time for hundreds of hours, so I create the program to use in this big project. Key goals are: speed+usability+final quality+color accuracy.

    Previous versions were very slow and have some usability, stability and quality issues.

    About 4K use. This usage requires a special program settings (reduced thread count and memory used), or you can get crashes. Windmotion is a x86 software, so a free memory is a key. Also, be ready to get processing with 0.1-0.5 fps. The published example is rendered in 0.3 fps on i7 3.5Ghz.

    @SuperSet it should work with GH3, but there are no GH3 profile yet. I have not found any original GH3 file on the internet, so I don't know a file format, color matrix and other things to create a valid profile.

    Most of unsupported cameras should be imported correctly (but with wrong color information - manual change is required), using "Generic File.bat" or "Generic File (to mkv).bat". Some cameras require special tricks.

    If you are interesting in a GH3 profile, send me in a private message some short GH3 originals in different file formats, supported by GH3.

    Also I still need in information for GH2 about an exact mts file size, used by camera for spanning. Currently I use this value: 4300,000,000 bytes. Of course, it is incorrect. How to get this value? Create a big ~one hour video and send me exact file sizes for all mts files. Currently only Sony NEX camera profiles can join mts files correctly, because I own these cameras and know span sizes.

    One question: is anyone are interesting in support of upsampling to 2K resolution?

  • Does this work with GH3 MOV or only GH2 MTS?

  • when we will be able to use the final product.

    Im very interested in this upsampling method. Also for 2k blowup no 4k, i find it very interesting. Until now i cant completely work on this software.

    An UI would be grate.

  • @Butt, "for ever"? Are you sure?

    Windmotion restores broken pixels using special motion-compensated algorithms. So your thing is valid if only you use only one frame as a source. In your case you will not have any extra data, just some blur or sharping.

    But in a Windmotion case it is possible - up to 7 frames used to restore frame pixels. Look at the screenshot. You will find there many details (right side) those are not available in a source frame (left side).

  • it is nonsense - 4:2:0 is 4:2:0 remain, for ever

  • I have found some issues with the posted 4K file:

    1. Color Y range is not valid (see a histogram). Just mistake in settings (original range is 16-235, not 16-255).
    2. Temporal noise/surface visibility variations. It may be fixed by adding more film-grain noise to mask these artifacts and less sharping or less noise reduction in Y channel.

    These issues and other examples will be updated with the final Windmotion version.

  • @rean This is impressive! Really looking forward to it. Keep us posted.

  • I have seen the file in 4K, is impressive and surprisingly from a GH2.

  • Ian_T, I tried to open it in Adobe After Effects CC Trial, using Quick Time. Also, it is playable in Windows over PotPlayer (but no 1:1 view). If someone have problem to open it, I can create another lossless copy: utcodec avi or H.264 avi or mov or mkv. Ask me if you really need it. But I found ProRes is more universal to open in most software.

  • I must say that the before and after is like night and day when it comes to detail (also detail in the blown highlights come back to life). I'm still trying to wrap my head around how it does this. In any case it is cool to be able to push the saturation all of the way and see absolutely no artifacts. I'm just having a problem with it in Sony Vegas. It runs fine for about a minute before I see a complete red screen and no video.

  • @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.

  • This is terribly exciting! I'm very interested from a post-production point of view if this tool can help control blue and red channel noise? would make for much better grading and especially chroma-key if one is required to use a blue screen. Obviously it would improve grading as well in terms of trying to get a bit of dynamic range lift in the shadows with some control over noise.

  • 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.

  • I hope you plan to make this a one-click simple solution. If you need help creating a GUI, maybe I can help :) - feel free to send a PM.

  • 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.
    
  • @Ian_T it is because the program is a complicated for understanding now, because there is no documentation yet. So many users do not understand how to work with it. The documentation will be available later, so more buzz is coming soon :)

  • 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.

  • Nice one! Thanks for sharing.

  • 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.
    
  • Anyone who has got this to work could kindly provide a basic work flow? do you just go into every folder in the vm directory and double click every single bat file in there? is there a specific order of execution? some of the files are numbered some don't have numbers. The folder structure is clearly numbered as to where to start. If you make a mistake how do you clear and start a fresh? I am following the instructions in the read me file, they are a bit vague. For example if instructions could say start in folder 1, double click bat files numbered 1 - 10 (do not double click and of the files which do not have numbers?

  • 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.