Bringing this up again because I still believe the video engine zoom needs a little bit more TLC from the developers:
Observations after using zoom control, both with the i / o keys and with a custom resource file.
From the i / o zoom control:
The percentage of the zoom value shown in the GUI when zooming seems not to totally be consistent , it can go from 101% to 102% to 103%, then to 105%. (An integer rounding error, maybe?)
From the custom resource file:
1. the Parameter actually decreases in value as the zoom increases and the value seems to have very little relation to actual zoom percentage shown on the GUI when the i / o zoom option is used
2. the parameter is required to be an integer, which does not allow for sufficient granularity in the sizing of the image.
These may be related to using integer math, since the parameter doesn't allow non-integer values.
For now, I am certainly happy to have the capability of presets, but after selecting a preset, I almost always have to use multiple presses of the i / o keys to fine tune the image size to establish the exact zoom amount to completely eliminate the black bars without eliminating any of the image.
For example, the integer value prevents me from setting an exact 2.40:1 zoom when using a test pattern with the appropriate sizes.
My custom resource file:
<!--
Media Center Resource XML (Default / English)
-->
<MJRS version="1.0">
<!--
COMMANDS:
Command: the MCC command index
Text: the string to be used in menus, etc.
Param: the parameter for the MCC command (leave empty if param doesn't matter)
Text Tokens: [Product Name], [Character]
-->
<!--
ACCELERATORS:
Key: semi-colon delimited list of key strokes to be pressed (see list below for special keys)
note that the only valid combinations are: [Key], [Key];Ctrl, [Key];Ctrl;Shift, [Key];Alt
Type: the type of command (defaults to MCC)
MCC: the command is an MC command
Program: the command is a program to run
Command: the MCC command index / name of program
Param: the parameter for the MCC command / program arguments
TranslateFlags: flags that determine when and how an accelerator is translated (binary or'd together)
1: don't translate in edits, comboboxes, and other data entry controls
2: don't translate in fullscreen mode or theater view
4: don't translate in any type of popup window
8: only translate in fullscreen
16: don't translate in IE, VB controls, or other unknown rich controls
32: targets playback engine / display (DVD, image playback, etc.)
64: only translate when Action Window is focused
128: not in Theater View
256: not in report controls
512: not in web browser
1024: not in video player
NoShowAsShortcut: 1 if you don't want MC to show this shortcut in menus, tooltips, etc.
Global: 1 if you want the accelerator to be translated even when MC doesn't have the focus
Special key list: Insert, Delete, -, +, Right, Left, Up, Down,
NumPad0, NumPad1, NumPad2 (etc.), F1, F2, F3 (etc.), Backspace, Enter, Escape,
Apps, Page Up, Page Down, Home, End, Space, Print Screen, Tab, Multiply ('*' on NumPad),
Decimal ('.' on NumPad)
Remember that order is relevant when the same shortcut appears multiple times.
MadVR Anamorphic lens correction = 13/9
-->
<ACCELERATORS>
<!-- Playback engine Zoom custom shortcuts (shared) -->
<Entry Key="Alt;A" Command="28038" Param="100" /> <!-- 1.77:1 -->
<Entry Key="Alt;S" Command="28038" Param="96" /> <!-- 1.85:1 -->
<Entry Key="Alt;D" Command="28038" Param="86" /> <!-- 2.00:1 -->
<Entry Key="Alt;G" Command="28038" Param="79" /> <!-- 2.20:1 -->
<Entry Key="Alt;H" Command="28038" Param="74" /> <!-- 2.40:1 -->
<Entry Key="Alt;J" Command="28038" Param="69" /> <!-- 2.55:1 -->
<Entry Key="Alt;K" Command="28038" Param="64" /> <!-- 2.76:1 -->
<Entry Key="Alt;L" Command="28038" Param="59" /> <!-- 2.85:1 -->
</ACCELERATORS>
</MJRS>
Could you please consider this as a possible enhancement for a future release?
Thanks again for a great product.