Issue: MC26 GUI issue with MadVR adjusting image resolution and or aspect ratio

Devices > Video Cards, Monitors, Televisions, and Projectors

<< < (3/5) > >>

wer:
That's something new you've added in. You didn't say previously it was a physical disc.

Zone Switch works best for items in the library, as they have fields. For things not in the library, you can have rules based on the physical path, or other properties of the file that can be detected.

Or you could rip to an ISO if you want menus, or to MKV if you just want the movie. If you don't rip, there are limitations.

Also, by the way, you CAN have hotkeys, or remote commands, for controlling the zoom function.
You should research Media Center Core Commands (MCC) and pay attention to 22025 and 22026.

Good luck.

Movieman:

--- Quote ---Also, by the way, you CAN have hotkeys, or remote commands, for controlling the zoom function.
You should research Media Center Core Commands (MCC) and pay attention to 22025 and 22026.
--- End quote ---

I have researched them, and they are non functional for my purpose and environment. As far as I can determine, 22025 doesn't take effect at initial launch unlike, for example VLC

"D:\Apps\VLC 3.10\vlc\vlc.exe" --monitor-par 23:16 --zoom 1.35 --fullscreen

and since MC occupies the entire screen when playing video, it's hard to run a command line window without a second monitor, which isn't going to fly in an Home Theater environment.

MPC:

[HKEY_CURRENT_USER\Software\MPC-HC\MPC-HC\Settings\PnSPresets]
"Preset0"="1.77,0.500,0.500,0.700,1.000"
"Preset1"="1.85,0.500,0.500,0.720,1.037"
"Preset2"="2.00,0.500,0.500,0.780,1.126"
"Preset3"="2.20,0.500,0.500,0.860,1.243"
"Preset4"="2.40,0.500,0.500,0.925,1.349"
"Preset5"="2.55,0.500,0.500,0.970,1.430"
"Preset6"="2.76,0.500,0.500,1.070,1.550"

Zoom Player

[HKEY_CURRENT_USER\Software\VirtuaMedia\ZoomPlayer]
"Preset2"="2: XOfs[268] YOfs[-20] Width[1384] Height[1120]"
"PresetCustomAR2"="2: Width[1.77] Height[1]"
"Preset3"="3: XOfs[228] YOfs[-70] Width[1460] Height[1230]"
"PresetCustomAR3"="3: Width[1.85] Height[1]"
"Preset4"="4: XOfs[140] YOfs[-130] Width[1640] Height[1340]"
"Preset5"="5: XOfs[60] YOfs[-188] Width[1800] Height[1460]"
"PresetCustomAR5"="5: Width[2.20] Height[1]"
"Preset6"="6: XOfs[30] YOfs[-237] Width[1860] Height[1550]"
"PresetCustomAR6"="6: Width[2.40] Height[1]"
"Preset7"="7: XOfs[-27] YOfs[-300] Width[1980] Height[1680]"
"PresetCustomAR7"="7: Width[2.55] Height[1]"
"Preset8"="8: XOfs[-72] YOfs[-330] Width[2060] Height[1720]"
"PresetCustomAR8"="8: Width[2.76] Height[1]"
"Preset9"="9: XOfs[-92] YOfs[-340] Width[2100] Height[1740]"
"PresetCustomAR9"="9: Width[2.85] Height[1]"

wer:
I'm beginning to wonder why you came here asking for help when you are so sure of your own counsel.

And your continual movement of the goalposts is wearing me out. You asked about hotkeys. Do you know what that word means? I wonder, because now you're switching it to launch-time parameters. If you only wanted launch time parameters, don't waste our time asking about hotkeys.

Hotkeys activate when pressed. The conclusions you reached from your research are wrong. The MCC commands I referred you to can be activated at ANY time when MC is running, without accessing the command line, by using a HOTKEY or by using a remote control. I assumed you knew what a hotkey was since you were asking for it, but evidently you need to be educated about hotkeys with MC as well. You could have found this by googling "jriver hotkeys" but doubtless you saw no need to do that.
Go look at this link:
https://wiki.jriver.com/index.php/User_Defined_Global_Keyboard_Shortcuts

Now combine that knowledge with the MCC info you "researched" and realize that you can assign ANY mcc command with its parameters to a hotkey. Also realize that you can assign ANY mcc command to a remote control input by using the dialog found at Options->Remote Control-Commands.

I use hotkeys and remote commands, in a home theater environment, without accessing the command line, and have been for years, as have many others here. It happens instantly in the background without disrupting playback. I use it to control zooming. I use it to control cropping. So it does fly. You're just wrong.

I'm not going to invest my time in typing out the exact config file lines you need to map specific zoom and crop actions to specific hotkeys, because you would probably just move the goalposts again.

Good luck achieving what you want.

Movieman:

--- Quote ---I'm not going to invest my time in typing out the exact config file lines you need to map specific zoom and crop actions to specific hotkeys, because you would probably just move the goalposts again.

Good luck achieving what you want.
--- End quote ---

Your comments were rather inappropriate IMHO. I have been an I.T. professional for 45+ years and have 55+ years of experience in the AV field.

If you had invested any time, you would possibly have found out that the feature added in this change appears to be broken.

--- Code: ---21.0.38 (1/18/2016)
9. NEW: Added MCC_PLAYBACK_ENGINE_VIDEO_ZOOM (28038) to set the zoom for a playing video.
28038 MCC_PLAYBACK_ENGINE_VIDEO_ZOOM int nZoomAmount (100 is 1.0)
--- End code ---

My custom resources file:

--- Code: ---<ACCELERATORS>

<Entry TranslateFlags="32" Param="100" Command="28038" Key="Alt;F1"/>
<Entry TranslateFlags="32" Param="130" Command="28038" Key="Alt;F2"/>
<Entry TranslateFlags="32" Param="150" Command="28038" Key="Alt;F3"/>
</ACCELERATORS>
--- End code ---

When that failed to work, I modified the default resources file which also failed to work. Then, to make sure that it wasn't an issue with a existing key conflict I commented out two existing entries for the + and - keys and substituted my additions for them):

--- Code: --- 
<Entry Key="Ctrl;Shift;F12" Command="25015" Param="1" Global="1" />



<Entry Key="+" Command="28038" Param="150" TranslateFlags="32" />
<Entry Key="-" Command="28038" Param="250" TranslateFlags="32" />



<Entry Key="I" Command="28000" TranslateFlags="32" />

<Entry Key="O" Command="28001" TranslateFlags="32" />
--- End code ---

Still no success with setting a specific zoom.

So, could we please get a developer to see if there was a possible regression or other issue that has disabled or broken the 28038 MCC code function?

Environment:
MC 26
Windows 8.1
NVidia GT 1030 Driver 425.31
DirectX 11

Thanks

tij:

--- Quote from: Movieman on April 29, 2020, 01:30:52 pm ---I am seeing issues with the top control bar (see attachment for the issue) in two specific environments;

1: Using a 3840x2160 desktop resolution and using the MadVR display mode switching to select either 1920x1080 23Hz or 1920x1080 29Hz resolutions on an LCD display.

2: Using MadVR anamorphic lens corrections on a JVC LCOS projector.

It appears to me that the position and size of the top bar are predetermined based on the display resolution and aspect ratio in effect before MadVR makes it's modifications.

Once MadVR switches the display to a different resolution, or changes the aspect ratio to accommodate an anamorphic lens, the bar is no longer usable as both the size of the bar and the location of the clickable areas are no longer correct.

The attachment shows the problem after MadVR has changed the desktop resolution from 3840x2160 to 1920x1080.

I'm not sure how difficult the coding would be, but it seems that the on screen GUI would need to be dynamically verified and modified after any MadVR changes to the image.

Also, on a different (but related) topic, we front projection constant height users are still waiting for the implementation of user defined presets assignable to hotkeys for the zoom function. It's pretty ugly to have to hold down the "i" key for a period of time, only to overshoot the desired zoom and have to correct, instead of having a set of user defined hot keys to handle the various aspect ratios. We certainly appreciate the tools that MadVR brings, but they fall short of other players support (examples being MPC, Zoom Player, VLC).

Thanks again for a great product.

--- End quote ---

That behavior is related to DPI setting of Windows (just tested myself) ... if you set your Windows Display properties you scale 100% ... this will not happen BUT your windows text will be puny and unreadable at 4K resolution.

Only reason I am aware of this problem is cause I output 3D in 1080p frame pack. If you don’t watch 3D, the easiest way to avoid that is not to switch to 1080p and just leave everything running at 4K (let MadVR do upscaling from HD to UHD ... I highly doubt anything come close to scaling quality of MadVR)

If you REALLY want to switch resolution and avoid that problem ... there is a way, but for the purpose of not confusing less advance users I won’t post it on forum ... PM me if you are still interested

EDIT: that bar at the top is not really needed for HTPC as mouse is often not use for HTPC ... whatever that bar can do can be achieved with MC OSD navigation that uses up/down/left/right arrows and Enter, which are easily mapped to remote control buttons

Though ... if you use MadVR ... that DPI setting can be problematic as MadVR will scale video by DPI percentage then something else scale it back to desired resolution (check MadVR OSD to see it)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version