Original commit message from CVS:
Make local copy of lists because they change while walking them. Use name
from GstPluginFeature, since that's a parent class (GstObject isn't). This
should go into the release.
Original commit message from CVS:
- Make the return GList of gst_element_get_pad_list as const
- Pad scheduler refactoring
- Remove gst_pad_set/unset_scheduler as it's not needed
- Reimplement gst_pad_get_scheduler using the parent scheduler
- Remove gst_pad_peek as it cannot work reliably
- Remove the pad bufpen, replace with scheduler private gpointer
- Make queue use the new _get_scheduler implementation
- Remove _pad_unset_scheduler from GstScheduler
- Remove LOOP_SEEK mode from aggregator
- Other fixes for API changes.
Original commit message from CVS:
spill over paths from a registry that couldn't load to the next one to ensure
that a usable registry gets built in the end
Original commit message from CVS:
- Make inspect show the event masks, formats and qupported query types.
- convert enum values to something readable in -launch
Original commit message from CVS:
This looks a lot better when printing out ranges for doubles which are
set at max. Tell me if I can change the other arguments to be printed like
this too and I will change them
Original commit message from CVS:
this seems to be needed when doing a pipeline like -launch { foo ! bar }
Now you can run:
gst-launch --gst-mask=-1 { fakesrc ! fakesink }
to see what seems to be a double locking problem
Original commit message from CVS:
- The clock_wait now returns the difference between requested time and
unlock time.
- Misc defines like GST_SECOND in gstclock.h
- remove pre/post in gstelement.c until fixed.
- added release_locks to gstelement so that the element can unlock itself
- added some more predefined events.
- added folowing functions to gstpad:
- convert function: get the relation between formats on this pad
- query function: get stats about the pad (position/total/latency)
- internal connect function: find out how this pad connects to other
pad internally to the element.
- generic pad_dispatcher.
- removed the last bits of pullregion
- use release_locks on the queue.
- added some events to queue
- make gstthread use the new release_locks function
- make the scheduler use the new clock_wait functions
- added events to fakesink
- added query functions to filesrc
- swap type and offset in the bytestream seek API to match fseek
- added some event handling in bytestream.
Original commit message from CVS:
Totally rewritten registry handling.
- move the registry save/load code into a gstregistry subclass, this
will make it possible to use other registries (flat file, web based,
RDBMS type, etc..)
- a simple GMarkup xml registry is implemented
- use standard statically linked plugins for core elements.
- GstPlugin has a very well defined set of functions now
A little bytestream hack..
Added more info to -inspect.
Some more debugging info for clocking.
Small cleanups
I use ./gst-register --gst-plugin-path=/opt/src/sourceforge/gst-plugins/gst-libs:/opt/src/sourceforge/gst-plugins/
to register core and gst-plugins now.
Original commit message from CVS:
- make all _get_list functions return a const reference to original lists and no copy
- redo code accordingly
- fix compile issue in dparam stuff
Original commit message from CVS:
yay, a new option to play with!
added -X / --exclude to exclude output of specific properties. Currently only --exclude will work because we're not on popt 1.6.3 yet (blame it on Debian).
removed the harcoded excluding of the 'offset' property. You need to specify --exclude=offset now if you want your old output back
Original commit message from CVS:
- changed the output so that the names of elements can be parsed by gst-inspect-check
- display the range of the element properties
- display the available dparams, just like the properties
- added int64 to element properties displayed
Original commit message from CVS:
link gst-inspect to libgstcontrol so that -inspect will show what dparams are available. I think it is ok to link helper libraries like libgstcontrol to the apps in tools/.
Original commit message from CVS:
registry handling changes
read up on it in docs/random/thomasvs/registry if interested
net effect should be transparent; ie. it will keep on working, but will
be more flexible than before. Testing with garnome seems to work now.
Should probably be rewritten completely, together with plugin loading, but
only after we spec it out ;) It's a bit messy.
