gst-plugins-bad - LV2 for GStreamer (SoC 2009)

Age	Commit message (Collapse)	Author	Files	Lines
2009-08-07	baseparse: prevent infinite loop when draining	Mark Nauwelaerts	1	-0/+8

2009-08-07	baseparse: fix minor memory leak	Mark Nauwelaerts	1	-0/+1

2009-07-14	amrparse: Sync baseparse changes	Sebastian Dröge	2	-29/+63

2009-06-02	aacparse, amrparse: remove bogus gst_pad_fixate_caps() calls	Tim-Philipp Müller	1	-1/+0

2009-06-02	baseparse: propagate return value of GstBaseParse::set_sink_caps()	Tim-Philipp Müller	1	-1/+1
	gst_base_parse_sink_setcaps() presumably should fail if the subclass returns FALSE from its ::set_sink_caps() function.
2009-06-02	baseparse: don't try to GST_LOG an already-freed caps string	Tim-Philipp Müller	1	-6/+2
	The proper way to log caps is via GST_PTR_FORMAT anyway.
2009-05-28	amrparse: consider header size in byte <-> time conversions	Mark Nauwelaerts	2	-4/+7

2009-05-28	baseparse: fix debug category	Mark Nauwelaerts	1	-1/+1

2009-05-03	baseparse: fix (regression in) newsegment handling	Mark Nauwelaerts	1	-16/+8
	(aacparse, amrparse, flacparse). Fixes #580133.
2009-04-07	baseparse: Fix slightly broken buffer-in-segment check (aacparse, amrparse, ↵	René Stadler	1	-1/+1
	flacparse)
2009-04-05	baseparse: Fix push mode seeking (aacparse, amrparse)	René Stadler	1	-5/+12
	Sending the flush-start event forward before taking the stream lock actually works, in contrast to deadlocking in downstream preroll_wait (hunk 1). After that we get the chain function being stuck in a busy loop. This is fixed by updating the minimum frame size inside the synchronization loop because the subclass asks for more data in this way (hunk 2). Finally, this leads to a very probable crash because the subclass can find a valid frame with a size greater than the currently available data in the adapter. This makes the subsequent gst_adapter_take_buffer call return NULL, which is not expected (hunk 3).
2009-03-31	baseparse: Delay newsegment as long as possible.	Mark Nauwelaerts	1	-25/+34
	If newsegment is sent (too) early, caps may not yet be fixed/set, and downstream may not have been linked.
2009-02-27	baseparse: revert last change and properly fix	Stefan Kost	1	-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-26	baseparse: remove checks for buffer==NULL	Stefan Kost	1	-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-30	Fix the return value of the default parse_frame function.	Jan Schmidt	1	-3/+3
	Fix the return value of the default parse_frame function in both copies of GstBaseParse
2008-11-13	gst/: Fix baseparse type name.	Stefan Kost	1	-1/+1
	Original commit message from CVS: * gst/aacparse/gstbaseparse.c: * gst/amrparse/gstbaseparse.c: Fix baseparse type name.
2008-11-13	Add two new baseparse based parsers (aac and amr) from Bug #518857.	Stefan Kost	5	-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.