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:
* 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:
* 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_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:
fixed pipeline for vob files so we get sound (bad sound but still), Wim claims we only need 50 more rewrites to get it working well
Original commit message from CVS:
Use stereo2mono plugin for scopes which require mono input.
It would be better if esdmon and osssrc were able to give mono output:
they need caps negotiation.
Original commit message from CVS:
* get up-to-date with the gst_caps_debug api
* improved capsnego in mad
* improved capsnego in adder
* improved capsnego in intfloat plugins
* unbroke capsnego in stereomono plugins
* fix cothread stack allocation within the main thread in new cothreads
Original commit message from CVS:
* get up-to-date with the gst_caps_debug api
* improved capsnego in mad
* improved capsnego in adder
* improved capsnego in intfloat plugins
* unbroke capsnego in stereomono plugins
* fix cothread stack allocation within the main thread in new cothreads
Original commit message from CVS:
adding videosink
is there any good reason why the videosink plugin didn't just go in the xvideo
dir ? It's not like we *need* to have the most dirs we can get ;)
if no one objects then I guess I'll move it to the sensible place
Original commit message from CVS:
let's not update here, it's not necessary; ie, if you run cvs update in gst-plugins,
it will update common automatically, and we don't support half-updated trees
Original commit message from CVS:
adding 'videosink' element
It's basically a rewritten xvideosink, but is more modular and allows 'hooks'.
It is needed by GstVideoWidget in gst-player
Original commit message from CVS:
Fix up esdmon timestamps, so that they don't go completely wrong if
someone changes the frequency, depth or mono/stereo parameters.
Original commit message from CVS:
Added esdmon plugin.
Monitors output from the esd sound daemon.
Particularly useful for displaying a visualisation of the audio being
played on your system. eg:
gst-launch esdmon ! goom ! { queue leaky=yes ! colorspace ! sdlvideosink }
You can even have several of them going at once. :)
