Replies: 1 comment
|
REVISED: This is an observation regarding VidCoder's post-encode "Sleep" action on modern hardware using S0 Modern Standby rather than traditional ACPI S3 Sleep that may help avoid user frustration and problem reports. OverviewOn modern hardware where traditional S3 sleep is unsupported or disabled in firmware, initiating VidCoder's post-encode "Sleep" action appears to either do nothing or force the machine into Hibernate (S4), depending on whether system hibernation is enabled. Trigger Conditions & System BehaviorThis behavior appears to stem from how Windows 11 handles legacy Win32 suspension calls (such as
Because Microsoft does not allow legacy suspension APIs to initiate an S0 Modern Standby state, there is no apparent workaround for desktop apps calling standard sleep functions on S0-only hardware. Possibilities to Consider
I'm passing this along in case others report unexpected post-encode power behavior on modern laptops or S0 desktop platforms. Test Environment:
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
DELETED
All reactions