WMV9 PowerToy 1.2.5.0

[ajp]

In the Motion Search Level box I only get three choices, Luma only/Fixed Integer Chroma/Fixed True Chroma. The adaptive modes seem missing, any ideas?

[benwaggoner]

In the Motion Search Level box I only get three choices, Luma only/Fixed Integer Chroma/Fixed True Chroma. The adaptive modes seem missing, any ideas?
The Adaptive Chroma modes were discovered to not be working properly in FSDK11.

[ajp]

So Zambelli's presets in wmcmd.vbs which use adaptive modes are no good? :eek:

[benwaggoner]

So Zambelli's presets in wmcmd.vbs which use adaptive modes are no good? :eek:
We just found out about this problem. I imagine he'll fix this in the next update of the script. But in the meantime just using the "Fixed" options will be just fine.

[ajp]

Thanks, I'll use the "fixed" options in the meantime... which I guess will result in a bit slower encodes than usual. No plans on releasing a new WME based on the new SDK eh? :p

[zambelli]

Thanks, I'll use the "fixed" options in the meantime... which I guess will result in a bit slower encodes than usual. No plans on releasing a new WME based on the new SDK eh? :p
No, Microsoft has no plans to release a new free encoder application at this moment. You might see VC-1 SDK incorporated into future commercial encoder products from MS though.

[zambelli]

Let me elaborate about the UI changes in PowerToy 1.2.5.0:

Motion Search Level options have been reduced to just "Luma", "Fixed Integer Chroma" and "Fixed True Chroma" due to a bug found in the v11 encoder DMO that doesn't correctly activate the adaptive chroma search modes when the registry key is set to values 3 and 4. This is very unfortunate, but I'd rather have people be aware of it instead of continuing to use a feature that doesn't actually work.

Perceptual Option now has just a dropdown list of "Adaptive Dead-Zone xx" values where xx ranges from 1 to 15. The default "Adaptive Dead Zone" (unnumbered) option has been removed because it's functionally equivalent to "Adaptive Dead-Zone 1" and therefore redundant. If you import any .reg files that were defined using the old "Perceptual Option = 2 or 3" mapping, those settings will now map to "Perceptual Option = 4" (Adaptive Dead-Zone 1) and everything should still continue to work the same. I'm sorry if that all seems complicated, but I made the change exactly for that reason - to simplify the UI representation of an otherwise messy registry setting.

Furthermore, because there've been several partner releases of the v11 encoder DMO to companies like Tarari, Inlet and Anystream, the PowerToy will now detect those versions of the DMO and dynamically expose options such as adaptive chroma search that were fixed in those releases.

[zambelli]

We just found out about this problem. I imagine he'll fix this in the next update of the script. But in the meantime just using the "Fixed" options will be just fine.
Yes, this will probably be reflected in the next update to WMCmd.vbs. Presets will also be redefined to accomodate this change, but I promise they will continue to be just as useful as they've been so far.