has someone managed to use wm via wine or anything alike? i don't have a virtual machine set up, so that's not an option for me.

cheers, htf

I purchased the pro edition a couple weeks back, but never received any or of confirmation or download link. Was it just a pre-order for the eventual release of this beta version, or is there another step I need to go through?

Short Windmotion denoise "howto" (before I publish a full manual).

Usage: MotionDegrain8(clip c, clip m, int "bs", int "frames", int "th", int "limit")

Here are: c - original clip in the current channel (Y,U,V)

m - motion clip, used to restore details. These two parameters are default used for best quality. So, no any changes are required. Pro edition has a feature to tweak this motion clip to get better results in some cases.

bs - block size, used for motion calculation. Use 4 or 8 for detailed clip, 16 or 32 for very noise or less detailed clip.

frames - number of sequenced frames used to calculate motion and to denoise. Use values from 2 to 6. No any common requirements to choose, because it is a source kind-related. I use 2 to 4 in most cases. Bigger values creates motion artifacts (see below).

th - threshold to denoise. Use values from 1 to 10000. Bigger values enable more aggressive denoise, also you will get temporal artifacts (like a slow motion of fast movement objects). So better usage of this filter - to convert 50p(60p) to 25p(30p) or to denoise static scenes. Change a framerate after this filter. As a result you will get less strobe effect. I use 800 in my projects (50p->25p). You should keep this value minimal, for your source, to get less artifacts.

limit - frame change threshold limit in a brightness value range. In most case use 255(no limit). If you have artifacts, try to decrease it to 2 or 3.

Pro edition has another denoise filters, those create no temporal artifacts, or can better denoise of some clips.

My workflow for my current project was DSLR footage -> Cineform and then edit within FCP7. How is the workflow with windmotion ? Do I need to denoise using Neat Video and then use windmotion ? So the workflow will be DSLR -> Cineform -> Neat Video -> Windmotion ?

Can you offer an output option to Cineform ? Or even to Prores ? I would be very keen on an output from 1080p or 720p to 2K 16:9 footage - with the 4:4:4 scaling applied.

Hi @rean,

Thanks for your beta version. I've already downloaded your beta and since you didn't release any tutorial, I would appreciate if you could confirm I'm doing everything right.

I'm on Win7 64bit. I use GH2 files. My goal: to get a video file transcoded to 4:4:4 16bit.

1. In order to get 4:4:4 I in "\wm 0.8.0 beta1 free\inc\" in settings.bat I changed "set wm_chroma_subsampling=422" to "set wm_chroma_subsampling=444".
2. Execute "\1. Src\Panasonic\Panasonic GH2.bat".
3. Execute "\2. Extract\Edit 01. Import.bat" (I didn't do anything here and closed the window).
4. Execute "\2. Extract\Edit All.bat" (I didn't do anything here and closed the window).
5. Execute "\2. Extract\Make.bat".
6. Execute "3. Edit\Avsi.bat".
7. Execute "3.Edit All.bat" (I didn't do anything here and closed the window).
8. Execute "\4. Make\Make h264 mov.bat"

According to these steps I got my file transcoded to Chroma Subsampling 4:4:4 and Bit depth: 8 bit!!! The new file is visually better than the original MTS and its size is much larger than the original. Why is it 8 bit and not 16 bit?

I also tried another export formats (Make DNxHD-10bit mov.bat, Make DNxHD-10bit mov.bat) and these transcoded files became: Chroma Subsampling 4:2:2 and Bit depth: 10 bit!!! The new file is visually the same as the original MTS and its size is almost the same as well. Why is it 10 bit and not 16 bit, and not 4:4:4?

I didn't use ProRes because I'm on a PC.

Am I doing something wrong?

Thank you in advance.

@rean Thanx a lot for your comments. I'll wait for your beta version. As you can see, your software is not that easy for a general user to understand, so a good manual is needed in any case.

@tosvus I have a wide internet connection, so I can download any file size. You can use a file store services: Google Drive, Dropbox, etc. to share it. They are fast.

@spacewig a help will be published online, because also big examples will be published there to demonstrate "how-to". I have no plan to include it to a distribution. Currently no help available yet. I am focusing now to a program stability. Also I am testing it currently on a real project before publish.

@MikhailK. Wrong way at all...

"In x64 directory I renamed x264 to x264-10bit.exe" - the program will not work with a renamed 8-bit x264. Only a real 10-bit version should be used. Also x264 10 bit is already included to the coming beta (and latest alpha, as I remember). No any download and rename required to make 10 bit results.

Your steps are correct in generally, but you forgot to execute "Make.bat" files in every step (or if you use a very old alpha - "Apply"). They are necessary. This trick is a speed optimization to control every step with a comfort fps, because a lot of CPU needed to whole processing chain.

This may look complicated, but if you have a lot of long files, you get the fastest and comfort way to process them. The program is optimized for very long batch processing with many processing hours in every step.

Some important knowledge things:

An Avsi file is a project file. It contains a list of all step parameters and filters used in every step. So when click to "Add to/Make Avsi" you include these steps to that file. Also you had no any tuning steps, as I see, so your result will contain an unknown "default" set of filters. So you will get an unknown processing and an unknown result. Because no any video file extracted and created in every step (no Make.bat had executed), you had only a short black windows. These scripts execute only if any source video is available.

The correct behavior is "Add to avsi" → change processing parameters → "Make" → Go to a next step. In a coming beta version these steps are now simplier.

Also please wait the beta version. There are a lot of important bugs fixed. I.e. an incorrect color profiles used in import and export to H.264; a color shift in ut codec in RGB mode.

@rean I'm interested in the personal paid version. Is there a help file included with this version?

@tosvus I have already a GH3 example, but in a perfect lighting. More interesting things are about bad lighting, noise, compression artifacts, etc.

@Ian_T the program comes with two editions: free and pro. A different set of filters used. Pro edition gives an additional result transparency and restoration possibility. For example, the free edition has no film grain noise generator. Import and export possibility is the same - no restriction.

Purchase? That's new.

@CTheEsrevinu, you will use all 1.x.x versions.

@rean As I wrote before, I previously tried some older version of Windmotion many months ago. I still haven't installed the new version of Windmotion. So, if you say it already has a GUI, then I'm sorry :-) I will try it as soon as I can. Thanx.

Windmotion already has a GUI. See latest posted screenshot. It is more usable and precise than most video editors I used before. Of course, some training steps are required.

If you want to get a GUI you know in a different software... it will take many years of development. I do not have any time for these things, and I do not see any relevance in this. Use Adobe or any other software.