Funnily enough, using in remoteFX machines (which was the first known obvious way to to use WMC remotely, before DVBlink and patched WMC were things). The behavior of "DisableRemoteSessionSupport" is reversed (stock wmc works out of the box, setting it to 1 introduces the black screen problem), more interestingly the original patch from Raznok doesn't affect it. I know, I'm the king of corner cases
Well, it's really the expected behavior: given I reverted Raznok's mod to make it conditional, WMC mini-mods should behave like WMC stock: you need to set DisableRemoteSessionSupport to 1 for the black screen issue to reappear It's still a mystery why you were seeing a different behavior with "normal RDP".
Ok, I see. minimod files and NO registry settings at all = same as stock. I noticed the behavior because I installed the patches and imported the registry. Now makes sense. Well I tested in a physical Server 2025, and it worked as you expected, I didn't investigate further on the first two OSes used in the first tests...
It's still a preview, but since the build 26040 it has the official branding "2025". (in theory) It expires in sept 2024, so espect the official release (assuming it means something) a month or two before that date. https://forums.mydigitallife.net/threads/server-ip-ltsc-builds.84158/page-31
Hi, please help me with nextpvr, I can't export the m3u list, I also purchased dvbviewer but I can't... Thank you
Perhaps, npvr4 should be more than enough for the purpose, npvr5 has a way better WEB UI and is multiplatform, but if the only purpose is to serve dvblink (or tvheadend) npvr4 should do the job decently.
@Kévin Chalet I noticed another side effect of minimod. I don't use the disabled windowed mode, given I have a rule to maximize the WMC window since the stone age (using Eventghost), so my WMC starts in full screen but I can still windowize it. But seem that the /widescreen switch is ignored. WMC always starts using a 4/3 aspect ratio windows. Not a huge problem obviously, but maybe keep it in mind if/when you take a further look to the code.
Weird, I'm not seeing this behavior on any of my machines. What's the list of mods you've enabled? (don't forget that everything in mini-mods is opt-in so if you don't enable anything, it's unlikely caused by WMC mini-mods).
Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\MiniMods] "AlbumPlaylistSortAttribute"="SourceURL" "DisableFullscreenOptimizations"=dword:00000001 "DisableInvalidRecordingsDeletion"=dword:00000001 "DisableQuickLinkImageFilters"=dword:00000001 "DisableRemoteSessionSupport"=dword:00000001 "DisableVideoOverscan"=dword:00000001 "DisableWindowedMode"=dword:00000000 "SpacebarShortcutCommandCode"="PlayPause" "WriteAdditionalRecordingMetadata"=dword:00000001 Remember I use a 16/10 monitor, and often with the taskbar on the side, so I have my shortcut with the /widescreen switch to avoid any "misunderstanding" with WMC Try this... Set the resolution to say 1024x768 or another 4/3 or 5/4 resolution (a remote connection using those resolutions should do the job s well) Launch wmc w/o any switch. It will start in 4/3, because it's the standard behavior Now add the widescreen switch and it should start in 16/9, no matter the aspect ratio of the monitor, this is the stock behavior as well Now try using minimod with the above settings, and WMC starts in 4/3 no matter the switch. (at least this is what I'm seeing, no extensive test done). I Yes and no, as you wrote on TGB "DisableFullscreenOptimizations" has a side effect that lead to the "DisableWindowedMode" option. So not 100% opt out, I just think the side effects are two not just one, then I repeat I didn't test extensively on various builds (yet).
It's very likely related to the fact you're using DisableFullscreenOptimizations = 1 (the other ones should have no impact on this). Yep, it definitely has side effects and what you're describing is undoubtedly one of them (another one is that tweaking LogicalWidth has no effect when disabling the exclusive fullscreen mode so you can't get rid of the infamous blinking vertical pixels line that appears the right side of 4K+ screens). That said, this mini-mod was added as a last resort for those who are using recent platforms where using WMC with the default fullscreen mode is completely impossible, it's not really meant to be a perfect option. I'll take a look when I have a moment but the rendering part is extremely complex, so don't expect any improvement in the near future (fun fact: despite what many people think, WMC doesn't use WPF and has its own rendering GDI/DirectX engine that was reused in Zune and Windows Phone - and called Iris Framework - but we know very little about this beauty as it's never been mentioned publicly).
I'm not really taking you as the customer support of a paid SW, just mentioning small glitches to help, in an eventually improved version. After all I did already most of what minimod does using a different approach, given I'm not a coder, so a fix isn't really a requirement for me, just a nice to have. I realized that WMC was something different when, many years ago, I tested the RemoteFX path for the first time. While it solves the forbidden remote connection and the black screen, it doesn't seem to take advantage of RFX in the same way WMP does. On a not so powerful machine WMP, videos are hugely improved over the standard RDP connection, but WMC ones does not. If you have a choppy rendering using the standard RDP it will be choppy as well using RemoteFX.
Sure, no worries I've never tried RemoteFX personally but I've seen it in action a few times and it was pretty cool. Too bad MSFT officially killed it...
It was (it is) I shared here my latest findings about its "replacement" and how RFX and GPU-P compare https://forums.mydigitallife.net/th...r-april-2021-solved.83764/page-3#post-1821546