Skip to content
This repository has been archived by the owner on Jan 7, 2023. It is now read-only.

[WINDOWS] Overlay window not handled correctly by mfxsink #150

Open
boxerab opened this issue Jan 11, 2019 · 5 comments
Open

[WINDOWS] Overlay window not handled correctly by mfxsink #150

boxerab opened this issue Jan 11, 2019 · 5 comments

Comments

@boxerab
Copy link

boxerab commented Jan 11, 2019

see ishmael1985#31 for details.

@boxerab boxerab changed the title Overlay window not handled on windows [WINDOWS] Overlay window not handled correctly Jan 11, 2019
@boxerab boxerab changed the title [WINDOWS] Overlay window not handled correctly [WINDOWS] Overlay window not handled correctly by mfxsink Jan 14, 2019
@boxerab
Copy link
Author

boxerab commented Feb 1, 2019

A polite ping on this issue - seems like a major flaw in mfxsink.

@ishmael1985
Copy link
Contributor

@boxerab maybe, but it doesn't make practical sense to implement such a feature, since memory copies will be involved when painting with the overlay window. If that is the case, you might just as well use d3dvideosink.
A better solutiion would be to use glimagesink with zero-copy, but it is more technically involved from an application developer's perspective. You could take this as your coding challenge, @boxerab .

@boxerab
Copy link
Author

boxerab commented Feb 1, 2019

Thanks @ishmael1985 . So, the mfx decoder can interoperate with glimagesink ?

@ishmael1985
Copy link
Contributor

@boxerab
Copy link
Author

boxerab commented Feb 2, 2019

Thanks. I don't want to draw an overlay onto the rendered frame, I am looking for an implementation of

GstVideoOverlay

GstVideoOverlay — Interface for setting/getting a window system resource on elements supporting it to configure a window into which to render a video.

On master mfxsink, there seems to have been work on supporting this on LInux, but not windows.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants