please please some video instructions in not russian PLEASE!!!!!!!!

FROM FIRST STEP TO FINAL STEP PLEASE!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I have some grate footage from my movie, this is the program i need, but wont pay you 300 bucks for creating scripts downloading apps, and aplying complex prosses to make video output.

@fancydancer finetune with a difference viewer (like in version 1) will be possible on Premium Edition only. Core and Postproduction editions have no such feature.

@zcream, I agree with you. It is the main purpose why upsample is required. I have used a lot of new computer graphics methods to make edges nonaliased. My experience with the version 1 showed its bottlenecks and ways of improvement. The new version uses 5 various antialiasing filters for achievement of this effect. And all camera templates will already contain edge smoothing in all color channels. For my green screen tests, it works perfectly now. I will publish learning videos to demonstrate this later.

Unfortunately aliasing is the main problem of all H.264 cameras. I found that MPEG compression algorithms produce aliasing because edges are the main point where compression makes artifacts. Also many consumer cameras have additional aliasing because modern photo matrices are too slow to reading from them. So many camera engeners read only a part of full matrix scan so we get aliasing. Summing aliasing of MPEG compression we get very ugly edges. It is the main point why modern camera videos are looking blurred - it is a way to masking aliasing.

Great work Rean. How does this new release differ from the 'old' Windmotion? Can users fine tune the denoiser/noise profile as in the old '3.Edit' Folder?

@domenl, to create a profile for a new camera I need different light source files to see: - camera codecs and bitrate - noise level on different light - color balance and color primaries, gamma etc - camera sharpening - compression artifacts, if any: halos, oversharp, blocking, overcompression, aliasing, etc. - for AVCHD source: typical span file size (when camera records next file). For example: SONY NEX cameras write 2026 megabyte spans.

Of course, there are many camera settings. But I assume that is better to make templates on the basis of the files created with the best camera settings for the corresponding lighting, because Windmotion is for advanced users, so we need a maximal possible quality:

Record settings: Use maximal possible frame size and bitrate settings. If camera can record progressive video, record progressive shots. If camera can record 50 or 60 fps - record on these settings (better quality for typical cameras).

ISO: Use minimal possible ISO for these light conditions.

ISO compensation: Use better value to get no cutoff of white areas. Most cameras require -0.3...-1.0. Do not use Manual mode. Aperture priority is better.

Sharpening: Some low cost cameras have hardcoded sharpening or very huge sharpening level by default settings. They produce ugly halos. For hardcoded sharpening I can add dehalo filter to the template by default. If you can setup sharpening, please setup it to a better level (minimal in most cases). It is better to add sharp in software than remove halos (very hard to remove).

Color balance: Use gray card or if it is not possible use manual color balance by a preset.

Make very short shots: 5...20 seconds with nature and peoples. Do not record abstract household things and cats - it is better to record a nature or a city landscape.

Upload these files to any sharing resource: Google Drive, Yandex Drive, Dropbox, etc. Do not edit them in video editor. Do not change file names. I assume to get files directly from the camera. Send me in a private message these download links.

I guarantee these files will not be published from my side. They will be used for Windmotion development only.

So, if I will have many different light sources, I can create more quality templates for a new camera. In most cases 2 templates per camera is a good start point: daylight profile (sunny day= minimal noise) + low light profile (noised).

I have currently some sources from camera review web sites, but most of these sources are for default camera settings.

Andrew

@spacewig, yes. I can try to support this camera Prores files with full dynamic range reading. CinemaDNG files reading is better in Davinci. But if you get noised source, you can export the result in Prores and read it in Windmotion to denoise. Windmotion 2 has 16-bit source file reading now.

Also I can fix Prores compression artifacts of low quality compression (MPEG blocking).

Hello. Great news.

I will release a beta version of Windmotion 2 within a few days. This beta version will have a set of a few of camera model support (Sony and Panasonic).

The final release will have ~50 camera support and it will cost ~ $150 for a standard edition and ~$350 for a premium edition. There will be a free edition for AviSynth lowers with no profiles.

Each camera profile lets you to give the maximal possible image quality, ready for pro usage on TV, reclaim, films.

The coming release lets you to create proxy or final quality files using only a few of mouse clicks. I personally create templates for each camera. As a result you will get the maximal possible quality (anti-aliased sources in 10 bit 4:2:2 or 4:4:4).

For example, default NEX-7 (bitrate 25 Mbps) profile gets final 80 Mbps quality equivalent with minimal MPEG compression artifacts and digital noise.

If you want to get your camera support in this beta release, please share to me some short daylight and low-light source files.

PS. This version is no more multistage and it is now 3-10 times faster for rendering of final quality. Also you will get much better quality.

For my tests:

4K to 4:2:2 4K profile transcode performance is 0.1-1.0 fps on 4 core I7 4Ghz. Typical Full HD 4:2:2 profile camera performance is 2.0-5.0 fps. 4:4:4 is possible, but true 4:4:4 (strong equivalent) is possible for some high quality top consumer cameras with a bitrate >50 mbps.

Full HD proxy generation fps is 20-120. Typical value is 35 fps for most cameras.

Proxy feature is now a core program feature. You can create your film quickly, then render final version files later (or in parallel with NLE/grading).

PS. the premium edition now also has a 32-bit 3D LUT color correction support for quality color grading on a post-production stage. You can create a 3D LUT file using BlackMagicDesign Fusion (free software with a top-quality 32-bit color corrector) or 3D LUT Creator (shareware).

The coming version is much simple for end user. Only a few of mouse clicks. Total development time of this release is ~ 7 months.

Andrew

@froboy88, it was not "just 8bit in a 10bit wrapper in your NEL". You are wrong, but anyway, let it be the way you think. Anyway, the program is no longer available. I have no any cheap 4K cam. But, as I see, the increased pixel count produces noise that kills any information. Also very strong compression also kills any video. Cheap 4 k camera is a marketing ploy for blondes.

True HD cameras very expensive. All existing cheap Full HD cameras have the actual resolution 600-800 lines. Also this is a resolution of Y channel. Real color channel resolution is ~ 100-200 lines. You can check your camera using test images. There is also a moire and other color distortions. The discussion theme author had misunderstood the purpose of the program. I never advertised the program for the purpose of upsampling. It is simply one of the added features, with the side effect of increasing the resolution using restoration algorithms. The program is for restore image from artifacts of modern video compression codecs, e.g. mosquito noise and edge color artifacts.

If you want to reduce the resolution, just do the resize. All resize algorithms working not in 8 bits will add to you missing bits. Because they calculate new values of color on the basis of several pixels, averaging them on special algorithms. In case of multiple reduction of the size (1/2x or 1/4x) you just get a total calculation of an arithmetic average from 4 or 8 pixels. So this feature is in each video editor and there is no sense in any special program.

@rean, I think you should be paid for you efforts. Perhaps finding an affordable price point will create more actual sales, which in the end could make your program more successful. Word from happy customers spreads very fast.

I wish you success in your work and look forward to your upcoming release.

@rean, are you saying that your software will no longer be available for any version free or paid?

@rean ok well thank you for the free license, I appreciate that. My method was definitely easy especially with the framework I used. Let me know if you need any help.

@rean I suppose you are correct, this is more of a launcher. I feel that it would make your application more inviting and a little simpler to use with everything accessible with one click in a single window. Would you like me to continue to look into this, and release it to you if I get it working? Or is this not the style/direction you want to take?

What Avisynth GUI do you mean? Windmotion has own GUI to view and edit, also special tools integrated, like screenshot and fast and usable mouse zoom operations. Also there are some fixes of Avisynth crashes. It is not listed in Avisynth sites, because I created it for Windmotion needs and do not want to provide support service for Avisynth peoples who want use Windmotion editor without Windmotion. But it is possible.

Any external editors are not good for Windmotion. They do not support full screen and have many special requirements. Some programs crash very quickly, like VirtualDub. It is simple incompatible with Avisynth MT and crashes every few script updates. Some editors are not usable and slow and cannot play audio. Also they cannot edit only selected parts. I designed Windmotion editor specially to fast and simple use.

All existing Avisynth IDE and GUI is really simple text editors with very basic frame viewer. I know no IDE that plays video with in sync with audio. Correct trimming with audio monitoring is a most useful feature for me.