Reply to thread

Message

<blockquote data-quote="Sebastiii" data-source="post: 1191839" data-attributes="member: 60104">Great <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Could be nice to see the log to see if we have the D3D device set to NULL and see if it's handled correctly (or at least better than before).About 3D trick, i think it was done too earlier now because it is activated right after OSD call back.I was able to reproduce some madVR crash and it was related to timing issue when releasing OSD, i need to try something on this side.About those blank thingy, it seems to be related when cleanup directshow graph between codec and renderer and i fear that i can't do nothing <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" /> (i have seen this too and try different manipulation but with no luck for now lol).</blockquote>

[QUOTE="Sebastiii, post: 1191839, member: 60104"] Great :) Could be nice to see the log to see if we have the D3D device set to NULL and see if it's handled correctly (or at least better than before). About 3D trick, i think it was done too earlier now because it is activated right after OSD call back. I was able to reproduce some madVR crash and it was related to timing issue when releasing OSD, i need to try something on this side. About those blank thingy, it seems to be related when cleanup directshow graph between codec and renderer and i fear that i can't do nothing :( (i have seen this too and try different manipulation but with no luck for now lol). [/QUOTE]

Verification