Shark007

Upon 1st use of my Codecs GUI, everything is set to use LAV Filters. These Filters are not good for winmm.dll usage. When selecting to use [MCI Video Player] from the Misc TAB, My GUI automatically sets splitters and decoders to MPC-BE Filters according to the files extension. So to make it easy, 1st play your MP4 4K file using my GUI/Player. Close my player and then try your player.

my two cents are not worth much since I previously discussed this with you when you 1st began using winmm.dll; your issues are codec related. I personally use winmm.dll (and also WMP Legacy) to playback 4K video including bitstreamed or decoded 7.1 Audio content flawlessly. If you wish to test my claims, MCI Player is found on the Misc TAB of my Application which can be downloaded HERE. Pressing F1 -during playback- will bring up a list of controls for the included MCI Player based solely on winmm.dll. Only to inform, installing LAV Filters will NOT solve the issues presented with the use of winmm.dll

also know that the script would need Admin Privileges to write to anything other than HKCU

setting of 1 setting of 20 setting of 40 @Jos, although not perfect, it certainly gets props for visibility and usability. Please carry some form of this into the next official release. I have not tested 32bit yet. I will post of it only if I encounter anomalies. EDIT: It may be of interest to you, I'd like to explain my use of HiDpi=n I have recently adopted @argumentum solution for DPI Awareness GUI presentation integration in This Thread which is facilitated by @UEZ solution in This Post because the resulting code is so much cleaner than adding a multiplication factor to all of the coordinates and dimensions as I was doing in the past. I hope these projects see the love they deserve.

I will pay attention to this thread and offer my system(s) as a testbed.

Those are interesting results that I cannot reproduce.

It really does seem that there is no one size fits all here. The best we can hope for is to provide the user with easily accessable settings to toy with.

For reference, my screen is 3840x2160 with 150% recommended but I use 225%

after rebooting, I used the SciTEx64.zip and here are pics setting 1 setting 0 (seems no different) Now, interestingly, I used SciTEx86.zip to produce these screenshots setting 1 setting 0

New screenshots follow using 64bit release. setting of 1 setting of 0 It seems to have lost the DPI Awareness. I checked the EXE manifest to be sure I had the original and the manifest does have the correct info. I'm going to reboot my system to see if that makes any difference because turning off and on again is always step one.

Jos, hold on making any determinations from those screenshots . . . I may have screwed up and mixed and matched x86/x64 exe's and dll's

DPI intact with setting of large=1 DPI intaact with setting of large = 0 with no DPI setting 1 with no DPI setting 0 Notice the loss of quality text when no DPI in use

I'll assume you mean with the DPI Aware stuff intact. I'll be back to edit this post shortly.

I keep up with your beta releases so large=1 was a default setting. Only the icons are an issue and since I do use them, seeing them is imperative.

Yes. and the 1st thing I checked was toolbar.large=1 large =1 was the default setting. For giggles, I tried zero and 2 with no improvement.