[Bug 733819] New: Port teletextdec to 1.0

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=733819
  GStreamer | gst-plugins-bad | git

           Summary: Port teletextdec to 1.0
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: dkk089 at gmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Created an attachment (id=281814)
 View: https://bugzilla.gnome.org/attachment.cgi?id=281814
 Review: https://bugzilla.gnome.org/review?bug=733819&attachment=281814

Patch porting teletextdec to 1.0

The attachment contains a patch with a 1.0 port of the teletextdec plugin. I've
been able to successfully build and run this plugin with the latest GStreamer
from master.

Other changes include :
 * The element no longer sends a "dummy buffer for preroll", as it relied on
the src_setcaps function being called before pushing the first buffer. This is
now fixed.
 * teletext.c has been deleted, as it did not serve any particular purpose.
 * GQueue and GMutex has been replaced with GstAtomicQueue.
 * The output function is now selected via a pointer-to-function instead of an
enum.
 * Fix some warnings related to unused arguments and/or signed-unsigned
comparison.
 * VBI structures (PES demuxer and HTML export module) are allocated only when
needed, instead of always (in case of demuxer) or on every push (in case of
exporter).

This element can also accept VBI teletext data packed inside MPEG PES packets.
This capability is exposed as "video/mpeg,mpegversion=2,systemstream=TRUE",
which is obviously wrong, but I was not sure how to say "teletext packed inside
a PES" in caps-speak. Suggestions welcome.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.