Original commit message from CVS:
- Changed plugins for new APIs
- modularized audiofile.
- added seeking, query and convert functions for mad, mpeg2dec,
avidemux, mpegdemux, mpegparse
- sync updates to oss. removed the ossclock for now
Original commit message from CVS:
added a typefind function for all supported audiofile types.
the type is called audio/audiofile - I could have split it into seperate types like audio/aiff and audio/wave but there doesn't seem to be a way to have a padtemplate respond to more than one type, hence this umbrella type.
Also, fixed optimisation logic so that aiffs are read through the lib.
Original commit message from CVS:
- when possible, bypass afReadFrames and just access the data directly. this optimisation seems to improve performance by about 20%, whee!
- remove unused funcs
- type finding will go into a seperate file
Original commit message from CVS:
this works for me locally now, however it requires:
- my local fix to implement gst_bytestream_tell (which I won't commit until events are redone)
- an audiofile patch which is already in debian but don't hold your breath for an upstream release
Original commit message from CVS:
afparse will eventually be able to support pipelines like:
gst-launch filesrc location=file.aiff ! afparse ! osssink
However at the moment it doesn't, because the public function afOpenVirtualFile isn't actually implemented yet. I implemented it with the audiofile CVS but it now segfaults the very first time one of the virtual file callbacks is called.
So, I'm committing this for posterity but it is not being built. Hopefully the audiofile lib will be released with working virtual file support soon.
Original commit message from CVS:
* a hack to work around intltool's brokenness
* a current check for mpeg2dec
* details->klass reorganizations
* an element browser that uses details->klass
* separated cdxa parse out from the avi directory
Original commit message from CVS:
* removal of //-style comments
* don't link plugins to core libs -- the versioning is done internally to the plugins with the plugin_info struct,
and symbol resolution is lazy, so we can always know if a plugin can be loaded by the plugin_info data. in theory.
Original commit message from CVS:
s/@GST_PLUGIN_LDFLAGS@/$(GST_PLUGIN_LDFLAGS)/
@-substitued variables variables are defined as make variables automagically,
and this gives the user the freedom to say make GST_PLUGIN_LDFLAGS=-myflag
Original commit message from CVS:
* s/gst_element_install_std_props/gst_element_class_install_std_props/ -- it just makes more sense that way
* added jack element, doesn't quite work right yet but i didn't want to lose the work -- it does build, register,
and attempt to run though
* imposed some restrictions on the naming of request pads to better allow for reverse parsing
* added '%s' to reverse parsing
* added new bin flag to indicate that it is self-iterating, and some lame code in gst-launch to test it out
* fixen on launch-gui
* added pkg-config stuff for the editor's libs
Original commit message from CVS:
Modified passthrough, adder, playondemand, float2int, int2float, and ladspa to
work with the new caps nego changes.
Updated adder to work with float data, now uses bytestreams.
Updated ladspa to work in any M sinkpads by N srcpads configuration, M > -1 and
N > 0. Also updated ladspa to work as a loop-based element using bytestreams for
MxN configurations other than M == N == 1 or M == 0.
