After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 774351 - parsebin: does not insert tsparse to parse additional tables in MP2TS
parsebin: does not insert tsparse to parse additional tables in MP2TS
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal enhancement
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-11-13 09:19 UTC by Arjen Veenhuizen
Modified: 2016-11-17 09:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Arjen Veenhuizen 2016-11-13 09:19:42 UTC
When parsing an MP2TS, parsebin is doing a great job at parsing the elementary streams. It seems to forget, however, about the transport stream itself. We need the tsparse element for that (e.g. to extract table information) but it is not inserted in parsebin after the typefind element. Is there any particular reason not to include the tsparse element or is this a bug?
Comment 1 Jan Schmidt 2016-11-15 09:26:59 UTC
That's not a regression. tsparse isn't plugged by anything by default - it has no rank.

Shouldn't you be getting the info you're after from the tsdemux element?
Comment 2 Arjen Veenhuizen 2016-11-17 06:29:35 UTC
It turns out to be a misunderstanding on my side. I was under the impression that I need the tsparse element to parse more "special" TS tables, but tsdemux is doing an equally good job as well. 

Is it true that functionality of the tsdemux and tsparse are more or less equal except that tsdemux is actually demuxing the TS while tsparse is just parsing the bitstream leaving the original bitstream as-is? Why is tsparse not listed as a child of tsdemux then?

Anyway, this can probably be closed as NOTABUG
Comment 3 Tim-Philipp Müller 2016-11-17 09:32:57 UTC
It's not a "child" of tsdemux in the GstBin child sense.

Both elements derive from MpegTsBase which you can see in the object hierarchy.

Not really sure what to do here. Please feel free to improve the tsdemux plugin docs (or add if missing) :)