mpegtsmux error: Could not create handler for stream

Marianna Smidth Buschle msb at qtec.com
Fri Oct 22 10:00:17 UTC 2021


I'm getting this error from mpegtsmux:

Oct 22 11:49:53 qt5122 qtec-mediamixer[272641]: 0:00:01.244140161 272641 
0x5556a57b51e0 WARN               basetsmux 
gstbasetsmux.c:811:gst_base_ts_mux_create_pad_stream:<mpegtsmux2> error: 
Could not create handler for stream


But I can't figure out what it is about, what is the problem.


If I look at the .dot file from the ERROR all looks fine. All seems 
linked and all CAPS seem correct.


Also, when I ran a simplification of my program pipeline using 
gst-launch all works:

gst-launch-1.0 udpsrc address=224.1.1.1 port=5000 multicast-iface=eth1 ! 
application/x-rtp,media=video,payload=33,clock-rate=90000,encoding-name=MP2T 
! rtpbin ! queue ! decodebin caps="video/x-h264" ! h264parse ! 
"video/x-h264,stream-format=byte-stream,alignment=au" ! tee name=t ! 
queue ! "video/x-h264,stream-format=byte-stream,alignment=au" ! 
multiqueue name=mq ! mpegtsmux name=mux ! rtpmp2tpay ! fakesink 
audiotestsrc ! 
"audio/x-raw,format=S32LE,layout=interleaved,rate=44100,channels=2,channel-mask=(bitmask)0x3" 
! mq. mq. ! audioconvert ! avenc_aac ! mux. -v --gst-debug=*:3


Best Regards

Marianna


On 22.10.2021 08.35, gstreamer-devel-request at lists.freedesktop.org wrote:
> Send gstreamer-devel mailing list submissions to
> 	gstreamer-devel at lists.freedesktop.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
> or, via email, send a message with subject or body 'help' to
> 	gstreamer-devel-request at lists.freedesktop.org
>
> You can reach the person managing the list at
> 	gstreamer-devel-owner at lists.freedesktop.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gstreamer-devel digest..."
>
>
> Today's Topics:
>
>     1. Re: building gstreamr from mono repo meson issues
>        (Nicolas Dufresne)
>     2. Number of threads in a typical Gstreamer pipeline
>        (Mohammad Sheraj)
>     3. Re: building gstreamr from mono repo meson issues (Belisko Marek)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 21 Oct 2021 08:21:35 -0400
> From: Nicolas Dufresne <nicolas at ndufresne.ca>
> To: Discussion of the development of and with GStreamer
> 	<gstreamer-devel at lists.freedesktop.org>
> Cc: Matthew Waters <ystreet00 at gmail.com>, Belisko Marek
> 	<marek.belisko at gmail.com>
> Subject: Re: building gstreamr from mono repo meson issues
> Message-ID:
> 	<9d2de4e510ea1a867fb884dc9199ac1ae2ac42af.camel at ndufresne.ca>
> Content-Type: text/plain; charset="UTF-8"
>
> Le jeudi 21 octobre 2021 ? 19:53 +1100, Matthew Waters via gstreamer-devel a
> ?crit?:
>> On 21/10/21 17:37, Belisko Marek via gstreamer-devel wrote:
>>> Hello,
>>>
>>> according documentation on webpage :
>>> https://gitlab.freedesktop.org/gstreamer/gstreamer
>>> for building gstreamer it is necessary to run following commands:
>>>
>>> meson builddir
>>> ninja -C builddir
>>>
>>> I'm trying to add support for gstreamer to yocto and I hit some issue
>>> which are not quite clear to me.
>>>
>>> - gstreamer requires meson >= 0.59 (doesn't work with version on
>>> Ubuntu 16.04 or 18.04)
>>> - when added meson 0.59.1 I'm hitting following issue:
>>>
>>>   | DEBUG: Python function extend_recipe_sysroot finished
>>>> DEBUG: Executing shell function do_configure
>>>> NOTE: Executing meson -Dintrospection=true ...
>> You need to update your build scripts (yocto?) to not use
>> -Dintrospection=true and as mentioned below, use "enabled", "disabled",
>> or "auto", probably "enabled".
> p.s. I don't think Yocto will need any update to build from tarballs, as we will
> emit the same tarballs as before. You can maintain the git support by simply
> building form the right direction (e.g. cd subproject/gstreamer) and then
> anything else from upstream Yocto should still work.
>
>>>> The Meson build system
>>>> Version: 0.59.1
>>>> Source dir: /home/builder/build/tmp/work/cortexa53-crypto-poky-linux/gstreamer/1.0+gitAUTOINC+b4ca58df76-r0/git
>>>> Build dir: /home/builder/build/tmp/work/cortexa53-crypto-poky-linux/gstreamer/1.0+gitAUTOINC+b4ca58df76-r0/build
>>>> Build type: cross build
>>>>
>>>> ../git/meson.build:1:0: ERROR: Value "true" (of type "string") for
>>> combo option "Generate gobject-introspection bindings" is not one of
>>> the choices. Possible choices are (as string): "enabled", "disabled",
>>> "auto".
>>>> A full log can be found at
>>> /home/builder/build/tmp/work/cortexa53-crypto-poky-linux/gstreamer/1.0+gitAUTOINC+b4ca58df76-r0/build/meson-logs/meson-log.txt
>>>> ERROR: meson failed
>>> Is meson too new or am I doing something wrong?
>>>
>>> Is there some way to cross-compile gstreamer from mono  repo in some
>>> docker container or so for experimenting with bleeding edge master?
>>>
>>> Thanks and BR,
>>>
>>> marek
>>>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 22 Oct 2021 03:48:11 +0000
> From: Mohammad Sheraj <msheraj at qti.qualcomm.com>
> To: "gstreamer-devel at lists.freedesktop.org"
> 	<gstreamer-devel at lists.freedesktop.org>
> Subject: Number of threads in a typical Gstreamer pipeline
> Message-ID:
> 	<PH0PR02MB71571D1A63D3B4D567050BF998809 at PH0PR02MB7157.namprd02.prod.outlook.com>
> 	
> Content-Type: text/plain; charset="us-ascii"
>
> Hi,
>
> I want to improve my understanding of Gstreamer.
>
> How many threads are there in this GStreamer pipeline?
> gst-launch-1.0 autovideosrc ! queue ! fakesink
>
> I want the total number and function of each thread.
> I searched online and in the documentation (https://gstreamer.freedesktop.org/documentation/application-development/advanced/threads.html?gi-language=c#) but couldn't find a clear answer.
>
> My knowledge is that there is a main loop thread, an event thread (not sure) and two (because of queue element) buffer threads here.
> This gives a total of 4 threads for the mentioned pipeline.
>
> Am I correct? Or is there some other mechanism?
>
> **Experiments:**
>
> Running the first time gives 8 threads initially.
> / # ps -T | grep "gst"
> 3681 root      0:00 gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3702 root      0:00 gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3703 root      0:00 gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3704 root      0:00 gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3716 root      0:00 {queue0:src} gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3717 root      0:00 {fake-auto-video} gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3718 root      0:00 {gmain} gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3719 root      0:00 {pool} gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3729 root      0:00 grep gst
>
> After some time it becomes 7 threads
>
> / # ps -T | grep "gst"
> 3681 root      0:00 gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3702 root      0:00 gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3703 root      0:00 gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3704 root      0:00 gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3716 root      0:00 {queue0:src} gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3717 root      0:02 {fake-auto-video} gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3718 root      0:00 {gmain} gst-launch-1.0 autovideosrc ! queue ! fakesink
> 3731 root      0:00 grep gst
>
> I did `strace -p 3681` and so on and found
>
> 3681:
> ppoll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}], 2, NULL, NULL, 0
> 3702:
> ioctl(11, BINDER_WRITE_READ
> 3703
> ioctl(11, BINDER_WRITE_READ
> 3704:
> ioctl(11, BINDER_WRITE_READ
> 3716:
> ...
> futex(0x5580a842a8, FUTEX_WAIT_PRIVATE, 11083, NULL) = 0
> 3717:
> ...
> ppoll([{fd=6, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 1, {tv_sec=0, tv_nsec=31373754}, NULL, 8) = 0 (Timeout)
> futex(0x5580a842a8, FUTEX_WAKE_PRIVATE, 1) = 1
> futex(0x5580a84290, FUTEX_WAKE_PRIVATE, 1) = 1
> 3718:
> ppoll([{fd=5, events=POLLIN}], 1, NULL, NULL, 0
>
> What does this mean?
>
> Thanks and Regards,
>
> Mohammad Sheraj
> Connected Smart Systems (CSS)
> Qualcomm
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20211022/3eba9bb7/attachment-0001.htm>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 22 Oct 2021 08:35:19 +0200
> From: Belisko Marek <marek.belisko at gmail.com>
> To: Nicolas Dufresne <nicolas at ndufresne.ca>
> Cc: Discussion of the development of and with GStreamer
> 	<gstreamer-devel at lists.freedesktop.org>,  Matthew Waters
> 	<ystreet00 at gmail.com>
> Subject: Re: building gstreamr from mono repo meson issues
> Message-ID:
> 	<CAAfyv36AApxH6-giRAyhoLqe3=467PQi=7oevffCXZiyy6vPKA at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> On Thu, Oct 21, 2021 at 2:21 PM Nicolas Dufresne <nicolas at ndufresne.ca> wrote:
>> Le jeudi 21 octobre 2021 ? 19:53 +1100, Matthew Waters via gstreamer-devel a
>> ?crit :
>>> On 21/10/21 17:37, Belisko Marek via gstreamer-devel wrote:
>>>> Hello,
>>>>
>>>> according documentation on webpage :
>>>> https://gitlab.freedesktop.org/gstreamer/gstreamer
>>>> for building gstreamer it is necessary to run following commands:
>>>>
>>>> meson builddir
>>>> ninja -C builddir
>>>>
>>>> I'm trying to add support for gstreamer to yocto and I hit some issue
>>>> which are not quite clear to me.
>>>>
>>>> - gstreamer requires meson >= 0.59 (doesn't work with version on
>>>> Ubuntu 16.04 or 18.04)
>>>> - when added meson 0.59.1 I'm hitting following issue:
>>>>
>>>>   | DEBUG: Python function extend_recipe_sysroot finished
>>>>> DEBUG: Executing shell function do_configure
>>>>> NOTE: Executing meson -Dintrospection=true ...
>>> You need to update your build scripts (yocto?) to not use
>>> -Dintrospection=true and as mentioned below, use "enabled", "disabled",
>>> or "auto", probably "enabled".
>> p.s. I don't think Yocto will need any update to build from tarballs, as we will
>> emit the same tarballs as before. You can maintain the git support by simply
>> building form the right direction (e.g. cd subproject/gstreamer) and then
>> anything else from upstream Yocto should still work.
> OK I'll give a try. Thanks.
>>>>> The Meson build system
>>>>> Version: 0.59.1
>>>>> Source dir: /home/builder/build/tmp/work/cortexa53-crypto-poky-linux/gstreamer/1.0+gitAUTOINC+b4ca58df76-r0/git
>>>>> Build dir: /home/builder/build/tmp/work/cortexa53-crypto-poky-linux/gstreamer/1.0+gitAUTOINC+b4ca58df76-r0/build
>>>>> Build type: cross build
>>>>>
>>>>> ../git/meson.build:1:0: ERROR: Value "true" (of type "string") for
>>>> combo option "Generate gobject-introspection bindings" is not one of
>>>> the choices. Possible choices are (as string): "enabled", "disabled",
>>>> "auto".
>>>>> A full log can be found at
>>>> /home/builder/build/tmp/work/cortexa53-crypto-poky-linux/gstreamer/1.0+gitAUTOINC+b4ca58df76-r0/build/meson-logs/meson-log.txt
>>>>> ERROR: meson failed
>>>> Is meson too new or am I doing something wrong?
>>>>
>>>> Is there some way to cross-compile gstreamer from mono  repo in some
>>>> docker container or so for experimenting with bleeding edge master?
>>>>
>>>> Thanks and BR,
>>>>
>>>> marek
>>>>
>>
> marek
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
>
> ------------------------------
>
> End of gstreamer-devel Digest, Vol 129, Issue 37
> ************************************************

-- 
Best regards / Med venlig hilsen
“Marianna Smidth Buschle”



More information about the gstreamer-devel mailing list