Reply to thread

Message

<blockquote data-quote="Sebastiii" data-source="post: 1196394" data-attributes="member: 60104">Ok <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> i didn't explain fully what i have in mind.I think that madVR restore display too soon with MP while MPC-HC is faster because of pure C++.It means that something is sent but not handled properly or avoid when MP in use in conjunction with crimson drivers.For example, we can see that when closing MPC-HC player, windows react fast to goes back to 2D.MP when closing/stopping a video take a little higher time and i think that in this window of few sec the crimson driver didn't handle the restoredisplaynow.Can i try to delay it or try to start restore earlier, we can try <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="Sebastiii, post: 1196394, member: 60104"] Ok :) i didn't explain fully what i have in mind. I think that madVR restore display too soon with MP while MPC-HC is faster because of pure C++. It means that something is sent but not handled properly or avoid when MP in use in conjunction with crimson drivers. For example, we can see that when closing MPC-HC player, windows react fast to goes back to 2D. MP when closing/stopping a video take a little higher time and i think that in this window of few sec the crimson driver didn't handle the restoredisplaynow. Can i try to delay it or try to start restore earlier, we can try :) [/QUOTE]

Verification