Reply to thread

Message

<blockquote data-quote="ziphnor" data-source="post: 94165" data-attributes="member: 14215">Thanks, while it was a bit of a downer to have to give up on the filter approach, this will result in much less code that is also much easier to maintain(and i did learn alot). I do need a slight amount of C++ code though, cant escape the native part completely, but its only:Anyway, the idea is that when the video surface is passed to managed MP in PlaneScene.PresentSurface as a native pointer, i can create a managed ARGB surface, pass both to the above method, and get my managed ARGB surface filled with the video. This is then easily translated into a Bitmap object which can be used by the cropper for determining bounds. Now that i can do this its only a matter of tying loose ends together, such that the frame is only grabbed when needed (it would have a nasty impact on performance otherwise <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />, something i hope to have time for in the weekend.Something which came as a positive surprise is that the video surface given by VMR is actually not upscaled yet(the application is responsible for that in VMR9 Renderless), so i am in fact working just on the deinterlaced frame exactly like in my filter!As for potential problems, i can only imagine that some drivers might not support the necessary color space conversion in StretchRect, but i dont think that this would occur with any DX9 cards (have no idea though). See <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/directx9_c/IDirect3DDevice9__StretchRect.asp" target="_blank">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/directx9_c/IDirect3DDevice9__StretchRect.asp</a> for reference.</blockquote>

[QUOTE="ziphnor, post: 94165, member: 14215"] Thanks, while it was a bit of a downer to have to give up on the filter approach, this will result in much less code that is also much easier to maintain(and i did learn alot). I do need a slight amount of C++ code though, cant escape the native part completely, but its only: Anyway, the idea is that when the video surface is passed to managed MP in PlaneScene.PresentSurface as a native pointer, i can create a managed ARGB surface, pass both to the above method, and get my managed ARGB surface filled with the video. This is then easily translated into a Bitmap object which can be used by the cropper for determining bounds. Now that i can do this its only a matter of tying loose ends together, such that the frame is only grabbed when needed (it would have a nasty impact on performance otherwise ;), something i hope to have time for in the weekend. Something which came as a positive surprise is that the video surface given by VMR is actually not upscaled yet(the application is responsible for that in VMR9 Renderless), so i am in fact working just on the deinterlaced frame exactly like in my filter! As for potential problems, i can only imagine that some drivers might not support the necessary color space conversion in StretchRect, but i dont think that this would occur with any DX9 cards (have no idea though). See [url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/directx9_c/IDirect3DDevice9__StretchRect.asp[/url] for reference. [/QUOTE]

Verification