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

Age	Commit message (Collapse)	Author	Files	Lines
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-03-23	aacparse: Fix busyloop when seeking. Fixes #575388	René Stadler	1	-5/+0
	The problem is that after a discont, set_min_frame_size(1024) is called when detect_stream returns FALSE. However, detect_stream calls check_adts_frame which sets the frame size on its own to something larger than 1024. This is the same situation as in the beginning, so the base class ends up calling check_valid_frame in an endless loop.
2009-03-23	aacparse: Refactor check_valid_frame to expose broken code	René Stadler	1	-8/+20
	Just moving code around and removing an unhelpful/misleading comment.
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-02-11	aacparse: Fix license specified in plugin details.	René Stadler	1	-2/+1

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
2009-01-23	Log aac details found in codec_data.	Stefan Kost	1	-0/+3

2008-11-13	gst/aacparse/gstaacparse.c: Don't autoplug aacparse until it works.	Wim Taymans	1	-1/+1
	Original commit message from CVS: * gst/aacparse/gstaacparse.c: (plugin_init): Don't autoplug aacparse until it works.
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/+2965
	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.