First: I assume your encrypted format has some sort of header that
will allow you to identify it as something using your format. If
that's not true, then you'll want to change the format (if you cannot
for some reason, then you have a terrible file format, and you won't
be able to use decodebin2).
Then, you should write a typefind function for gstreamer to use, which
will identify your file format.
Then you'll be able to manually plug whatever you want using the
autoplug-* signals.
Mike
On Fri, Oct 21, 2011 at 8:58 AM, Jayanth K.P <
[hidden email]> wrote:
> Hi ,
> We are trying to build a pipeline using encrypted stream using
> decodebin2. For the encrypted stream, decodebin2 is generating a bus error
> "Could not determine type of stream".
>
> Issue is we depend on the "autoplug-continue" signal coming from the
> decodebin2 to continue auto-plugging or manually build the pipeline. In
> this case of encrypted stream,we were expecting the decodebin2 to give a
> "autoplug-continue" with cap string as 'application/octet-stream' or some
> thing similar. Based on this we would make the decision to continue
> auto-plugging or manually build the pipeline.
>
> Is it possible for the decodebin2 to generate "autoplug-continue" signal
> with an appropriate cap string( ex. application/octet-stream)?
>
> Your help on this issue will be appreciated..
>
> Regards,
> Jayanth
>
>
> _______________________________________________
> gstreamer-devel mailing list
>
[hidden email]
>
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel>
>
_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Locked
