[Bug 785531] appsink: forward the Protection Event to the application

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Wed Oct 4 07:37:42 UTC 2017


https://bugzilla.gnome.org/show_bug.cgi?id=785531

--- Comment #8 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
Why do you split it up into two different pipelines?

There's nothing technically wrong with posting messages from the demuxer, and
it would also be required probably (see the qtdemux patch about selecting
between multiple DRM systems). Overall this nonetheless looks like you have a
misunderstanding about how the protection API is supposed to be used.


Basically, everything should be handled by the decryptor element. The demuxer
and parser before that extracts the "common" knowledge from the streams and
provides it downstream via the buffers/events/metas/caps. It might have to ask
the application to do some kind of decision (see above), but that's about it.
The decryptor then makes use of this information and does everything that is
needed for actually decrypting the stream. This might include asking the
application for further information and blocking any processing until that
information is available. Such information could involve asking the application
to do its stuff to contact any DRM/license servers for example so that
decryption can happen, or it sounds like in your case the application is
actually responsible for doing decryption ("buffer manager"?) so it would pass
the buffers to the application (CDM?), get buffers back from the application
and pass them onwards.

There should be no reason to split the pipeline for this, and it could all be
relatively self-contained in the decryptor element (which then does the
communication with the app).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list