summaryrefslogtreecommitdiffstats
path: root/gst/amrparse
AgeCommit message (Collapse)AuthorFilesLines
2009-02-27baseparse: revert last change and properly fixStefan Kost1-4/+6
Baseparse internaly breaks the semantics of a _chain function by calling it with buffer==NULL. The reson I belived it was okay to remove it was that there is also an unchecked access to buffer later in _chain. Actually that code is wrong, as it most probably wants to set discont on the outgoing buffer.
2009-02-26baseparse: remove checks for buffer==NULLStefan Kost1-9/+5
Accordifn to docs for GstPadChainFunction buffer cannot be NULL. If we would leave the check, we would also need more such check below.
2009-01-30Fix the return value of the default parse_frame function.Jan Schmidt1-3/+3
Fix the return value of the default parse_frame function in both copies of GstBaseParse
2008-11-13gst/: Fix baseparse type name.Stefan Kost1-1/+1
Original commit message from CVS: * gst/aacparse/gstbaseparse.c: * gst/amrparse/gstbaseparse.c: Fix baseparse type name.
2008-11-13Add two new baseparse based parsers (aac and amr) from Bug #518857.Stefan Kost5-0/+2672
Original commit message from CVS: * configure.ac: * gst/aacparse/Makefile.am: * gst/aacparse/gstaacparse.c: * gst/aacparse/gstaacparse.h: * gst/aacparse/gstbaseparse.c: * gst/aacparse/gstbaseparse.h: * gst/amrparse/Makefile.am: * gst/amrparse/gstamrparse.c: * gst/amrparse/gstamrparse.h: * gst/amrparse/gstbaseparse.c: * gst/amrparse/gstbaseparse.h: Add two new baseparse based parsers (aac and amr) from Bug #518857.