Commit graph

114587 commits

Author SHA1 Message Date
Erik Walthinsen
da03fde054 WARNING: Don't grab this updated unless you're really, REALLY sure.
Original commit message from CVS:
WARNING: Don't grab this updated unless you're really, REALLY sure.
WARNING: Wait for the next one.

Whole lotta changes here, including a few random bits:

examples/*/Makefile: updated to use `libtool gcc`, not just `gcc`
gst/
gstbuffer.h: updated to new flag style
gst.c, gstdebug.h: added new debugging for function ptrs
gstpipeline.c: set type of parent_class to the class, not the object
gstthread.c: ditto
plugins/
cdparanoia/cdparanoia.c: added an argument type, updated some defaults
cobin/spindentity.c: updated to new do/while loopfunction style
mp3encode/lame/gstlame.c: argument types, whole lotta lame options
tests/: various changes

Now, for the big changes:  Once again, the scheduling system has changed.
And once again, it broke a whole bunch of things.  The gist of the change
is that there is now a function pointer for gst_pad_push and gst_pad_pull,
instead of a hard-wired function.  Well, currently they are functions, but
that's for debugging purposes only, they just call the function pointer
after spewing lots of DEBUG().

This changed the GstPad structure a bit, and the GstPad API as well.
Where elements used to provide chain() and pull() functions, they provide
chain() and get() functions. gst_pad_set_pull[region]_function has been
changed to get_pad_set_get[region]_function.  This means all the elements
out there that used to have pull functions need to be updated.  The calls
to that function have been changed in the normal elements, but the names
of the functions passed is still _pull[region](), which is an aesthetic
issue more than anything.

As for what doesn't work yet, just about anything dealing with Connections
is hosed, meaning threaded stuff won't work.  This will be fixed about 12
hours from now, after I've slept, etc.  The simplefake.c test works in
both cothreaded and chained cases, but not much else will work due to the
Connection problem.  Needless to say, don't grab this unless you *need*
these features *now*, else wait to update this stuff until tomorrow.

I'm going to sleep now.
2000-12-16 10:18:09 +00:00
Wim Taymans
64a740ad9b Move a step closer to autoplugging. The element selection in the pipeline works.
Original commit message from CVS:
Move a step closer to autoplugging. The element selection in the
pipeline works.
Slight modification to the typefind function handling.
removed the stupid mime types in the mpeg decoders.
Adjust videosink for the new caps handling.
Modified the queue example to show an error in plan creation; Erik can you
solve this? This is the type of pipelines autoplugging uses.
2000-12-15 16:43:26 +00:00
Wim Taymans
a63780a377 Header cleanup: try to include as little as possible; this will probably speed up compilation a bit.
Original commit message from CVS:
Header cleanup: try to include as little as possible; this will probably
speed up compilation a bit.
changed the .c files to use #include "..."
Fix for the 'plugins are loaded twice' bug.
Fix 22186: GstObject flags are now used everywhere. Added *_FLAG_LAST so
elements do not use the same flags. Added some padding in the flag enum
for future expansion.
2000-12-15 01:57:34 +00:00
Wim Taymans
f8386fbaa0 Some plugins are adjusted to the new pad template mechanisms.
Original commit message from CVS:
Some plugins are adjusted to the new pad template mechanisms.
2000-12-14 17:21:29 +00:00
Erik Walthinsen
1ba6c1b526 First few TODO items to be done after 0.1.0 (i.e. in 2001)
Original commit message from CVS:
First few TODO items to be done after 0.1.0 (i.e. in 2001)
2000-12-13 21:42:19 +00:00
Wim Taymans
196c67d7ff Changed the GstPadFactory and added the GstPadTemplate.
Original commit message from CVS:
Changed the GstPadFactory and added the GstPadTemplate.

The GstPadFactory is an easy way to define a pad with capabilities.
The GstPadFactory is converted into a GstPadTemplate. The template is
used to create new pads and to expose the possible pads used in an
element to the plugin system.

updated mp3parse, mpg123, cdparanoia to the new API.
Rerun gstreamer-register because the XML definition has changed.
2000-12-13 19:29:35 +00:00
Wim Taymans
97fc2e9f07 Added a document about how we handle plugins and dynamic loading.
Original commit message from CVS:
Added a document about how we handle plugins and dynamic loading.
2000-12-12 19:31:00 +00:00
Wim Taymans
d78215be9d More Caps changes, this change introduces the padfactory. the GstPadFactory will be used to describe the pads that an...
Original commit message from CVS:
More Caps changes, this change introduces the padfactory. the GstPadFactory
will be used to describe the pads that an element will contain during
its lifetime.
mpg123 and mp3parse serve as an example.
More XML changes to incorporate the padfactories.
2000-12-12 19:29:43 +00:00
Erik Walthinsen
5f7a20ff6f Added LAME encoder. Wow.
Original commit message from CVS:
Added LAME encoder.  Wow.
2000-12-12 09:40:25 +00:00
Erik Walthinsen
ffbc7201a7 Brand new source, the cdparanoia source. Reads audio data from a CD, writes out raw audio. The tests/paranoia.c pro...
Original commit message from CVS:
Brand new source, the cdparanoia source.  Reads audio data from a CD,
writes out raw audio.  The tests/paranoia.c program will simply hook this
up to a sound card.  It works perfectly.

Next step is to flesh out the rest of the element, including pad caps,
better seek and playout control, signals, and whatever else comes up.

A minor patch to the editor is included here, the GstElementFactory details
struct has a name change from 'class' to 'klass' that wasn't reflected
in the elementselect widget.  Fixd.
2000-12-12 06:49:26 +00:00
Erik Walthinsen
c28633b01d Updated to latest code for testing scheduling.
Original commit message from CVS:
Updated to latest code for testing scheduling.
2000-12-11 00:25:06 +00:00
Erik Walthinsen
b063cb96f1 Implemented the hybrid scheduling system for sources and connections outside the current Bin. Is a bit hackish in on...
Original commit message from CVS:
Implemented the hybrid scheduling system for sources and connections
outside the current Bin.  Is a bit hackish in one place, but I'll work out
a way to make that cleaner soon.  queue.c in tests now works nicely in all
cases.  More to come later.
2000-12-11 00:24:32 +00:00
Wim Taymans
ec1548618e Test program to check the registry handling
Original commit message from CVS:
Test program to check the registry handling
2000-12-11 00:06:16 +00:00
Wim Taymans
6fa6cd8ce4 First attempt at rebuilding the type/plugin system
Original commit message from CVS:
First attempt at rebuilding the type/plugin system
- make sure caps/props are saved in the registry
autoplugging is completely broken.
removed the typefactories and typeids from all the pads in the plugins
XML load/save is ok (be sure to rerun gstreamer-register)
2000-12-11 00:04:25 +00:00
Erik Walthinsen
6ba0668cd8 Snapshot of work-in-progress do deal with out-of-bin elements. Current system is very likely going to be ditched due...
Original commit message from CVS:
Snapshot of work-in-progress do deal with out-of-bin elements.  Current
system is very likely going to be ditched due to its complexity and the
fact that it doesn't work right now.  More than that, it's generating some
really odd results in my test program, which aren't readily explainable.

If you want to keep a working copy of your working copy (heh), don't update
until this is replaced with a hybrid approach.  This approach will be the
beginning of a plan generator that can construct full hybrid schedules
given hints from various places.

Hybrid means that cothreads are used, but there are chunks of the pipeline
that are actually dealt with by chaining. This can improve speed by
reducing cothread switches (which are much cheaper than thread switches,
but still far from free, about 570 cycles on my PIII), but does carry a
complexity burden.  Luckily, the structure of GStreamer allows that burden
to live entirely in create_plan.  Luck?  I think not ;-)
2000-12-09 09:13:09 +00:00
Erik Walthinsen
0f9d972b3d Mostly debugging changes. What's in CVS seems to work rather well, actually.
Original commit message from CVS:
Mostly debugging changes.  What's in CVS seems to work rather well, actually.

Next is the work on task 23098...
2000-12-08 23:38:12 +00:00
Erik Walthinsen
1aed13ae6b Test program for simple queue operations. Good for testing thread/cothread interations.
Original commit message from CVS:
Test program for simple queue operations.  Good for testing thread/cothread
interations.
2000-12-08 20:31:40 +00:00
Wim Taymans
cd24b35b70 Added pullregion in again, it got removed with the previous commit.
Original commit message from CVS:
Added pullregion in again, it got removed with the previous commit.
2000-12-08 18:24:16 +00:00
Erik Walthinsen
990baba8e3 Another big set of changes. Connections are now also pullfunc based. gstqueue has been updated, I don't know of any ...
Original commit message from CVS:
Another big set of changes.  Connections are now also pullfunc based.
gstqueue has been updated, I don't know of any other connections offhand.

There are still a few things that need doing, specifically the concept
of a source or connection with connections to multiple thread contexts is
not dealt with.  This may force us to move the threadstate from the
element to the pad, maybe keeping the element's copy for simple cases.
Then the Bin would create a structure to pass to the cothreaded _wrappers
of any such elements, which would detail the pads that are to be dealt with
by this particular cothread context.

That will speed things up to, since we don't have to look through the list
of all pads for every Src or Connection element for every iteration, we can
simply step through the list provided by the plan.  Special case might even
have a single pad pointer sitting there to trump the list, if there's only
one (the common case anyway).

Task 23098 is tracking these changes.  The main task 22588 depends on that
subtask, as well as 22240, which is a consistency check on PAD_DISABLED.
2000-12-08 10:33:01 +00:00
Wim Taymans
d29ff12b69 Updated the test program
Original commit message from CVS:
Updated the test program
2000-12-07 18:38:54 +00:00
Wim Taymans
eaa6e55855 separated the properties from the capabilities as we might use the properties for metadata too.
Original commit message from CVS:
separated the properties from the capabilities as we might use the properties
for metadata too.
2000-12-07 18:37:56 +00:00
Wim Taymans
1af7640685 Added pulregion handling.
Original commit message from CVS:
Added pulregion handling.
Added GstCapsListFactory in headers
2000-12-06 23:04:12 +00:00
Wim Taymans
855b6877e9 Fixed autoplugging.
Original commit message from CVS:
Fixed autoplugging.
2000-12-05 18:08:59 +00:00
Wim Taymans
06913f27c3 Added some capability options
Original commit message from CVS:
Added some capability options
2000-12-04 19:24:25 +00:00
Erik Walthinsen
04c360e39f Changed the way things are scheduled, especially sources. A Src used to have a push() function, and optionally a pus...
Original commit message from CVS:
Changed the way things are scheduled, especially sources.  A Src used to
have a push() function, and optionally a pushregion() to deal with async
reads, etc.  That whole thing has gone away, in favor of providing a
pull() function for the output (Src) pad instead, ala chain functions.
This makes constructing cothreaded schedules out of non-loop elements
somewhat easier.  Basically there was always a question as to which pad
was being dealt with.  In the pullregion case, cothread-specific data was
used to try to pass the region struct to the right place, which is a slow
hack.  And in general, the push function severely limited the kind of
tricks that could be played when there's more than one output pad, such as
a multi-out file reader with async capabilities on each pad independently.

This changes the way cothread scheduling occurs.  Instead of the hack to
deal with Src's by calling their push() function (or optionally the
pushregion(), in certain cases), we now are working towards a general
mechanism where pads are the only thing that are dealt with directly.

An optimization was made in the process of doing this: the loopfunction
actually run as the outer [stack] frame of the cothread is now set more
intelligently in create_plan() based on what kind of element it is.  We
now have:

loopfunc_wrapper: used for loop-based elements, it simply calls the
loopfunc in a loop, paying attention to COTHREAD_STOPPING (see
below).  It currently does other, soon to be depracated, stuff.

pullsrc_wrapper: wraps a Src that's not loop-based (since your options
are now loop- or pull-based)

There will be a couple more to deal with other cases, such as Connections
and chain-based elements.  The general idea is that it's a lot more
efficient to make the decisions once in create_plan than to keep doing
this huge if/else chain in the wrapper.  Just choose the right wrapper up
front.  It'll be most apparent performance-wise in the case of whichever
element context is switched to first for each iteration, since the whole
wrapper setup is done for every iteration.

The tricky part is that there is now a bit of overloading of the function
pointers in a pad.  The current meanings (possibly to change a bit more
soon) are:

chainfunc: as always, chainfunc pointer is mirrored between peer pads
(this may change, and the chain func may end up in pushfunc)
pushfunc: SrcPad: gst_pad_pushfunc_proxy, cothread_switch to peer
SinkPad: none (may take over chainfunc, see below) pullfunc:
SrcPad: Src or Connection's function to construct buffers
SinkPad: gst_pad_pullfunc_proxy, cothread_switch to peer

There are a number of issues remaining with the scheduling, not the least
of which is the fact that Connections are still dealt with the old way,
with _push() functions and such.  I'm trying to figure out a way to unify
the system so it makes sense.  Following the scheduling system is hard
enough, trying to change it is murder.


Another useful scheduling addition, mentioned above, is COTHREAD_STOPPING.
It's an element flag that's used to signal whatever code is running in
cothread context that it should be finishing up and exiting soon.  An
example of this is in plugins/cobin/spindentity.c.  All the loops should
now be composed of do/while loops, rather than while(1) loops:

do {
buf = gst_pad_pull(spindentity->sinkpad);
gst_pad_push(spindentity->srcpad,buf);
} while (!GST_ELEMENT_IS_COTHREAD_STOPPING(element));

The reason for this is that COTHREAD_STOPPING may be set before the above
loop ever gets started.  It wouldn't do for the body of the loop to never
once get called, that would simply stall the pipeline. Note that only the
core library code is ever responsible for setting and unsetting this flag.
All elements have to do is respond to it by cleanly exiting the loop and
the function holding it.

This is needed primarily to allow iterations to occur properly.
Basically, there's a single entry point in the cothread scheduling loop,
gst_bin_iterate_func() simply switches to this cothread.  If the element
in this context is allowed to loop infinitely, nothing would even switch
back to the context from which the iterate() was originally called.  This
is a bit of a problem.  The solution is for there to be an implicit switch
back to the originating context.  Now, even I'm not sure exactly how this
works, but if the cothread that's switched to actually returns, execution
returns back to the calling context, i.e. iterate_func().

COTHREAD_STOPPING is therefore set just before switching into this
(currently randomly chosen) context, on the assumption that it will return
promptly after finishing its duties.  The burden of clearing the flag
falls to the various wrapper functions provided by the Bin code, thus
element writers don't have to worry about doing that at all (and simply
shouldn't).


Related changes:
All the sources in elements/ have been changed to reflect the new system.


FIXMEs:
1) gstpipeline.c calls gst_src_push at some point, dunno why, it's
commented out now.
2) any other sources, including vcdsrc, dvdsrc, and v4lsrc will break
badly and need to be modified to work as pull-based sources.
2000-12-04 10:52:30 +00:00
Erik Walthinsen
29d567ba23 Changes made to the DEBUG system. New header file gstdebug.h holds the stuff to keep it out of gst.h's hair. DEBUG ...
Original commit message from CVS:
Changes made to the DEBUG system.  New header file gstdebug.h holds the
stuff to keep it out of gst.h's hair.  DEBUG prints out the process id,
cothread id, source filename and line number.  Two new macros DEBUG_ENTER
and DEBUG_LEAVE are used to show the entry and exit of a given function.
This eventually might be used to construct call trace graphs, even taking
cothreads into account.  This would be quite useful in visualizing the
scheduling mechanism.

Minor changes to various debug messages.

Also sitting in gstdebug.h is a prototypical DEBUG_ENTER that's capable of
performing DEBUG_LEAVE automatically.  It does this by utilizing a
little-known GCC extension that allows one to call a function with the
same parameters as the current function.  The macro uses this to basically
call itself.  A boolean is used to ensure that when it calls itself it
actually runs the body of the function.  In the meantime it prints stuff
out before and after the real function, as well as constructing a
debugging string.  This can be used eventually to provide call-wide data
on the DEBUG lines, instead of having to replicate data on each call to
DEBUG.  More research is needed into how this would most cleanly be fit
into some other chunk of code, like GStreamer (I think of this DEBUG trick
as a separate project, sorta).

Unfortunately, the aforementioned DEBUG trick interacts quite poorly with
cothreads.  Almost any time it's used in a function that has anything
remotely to do with a cothread context (as in, it runs in one), a segfault
results from the __builtin_apply call, which is the heart of the whole
thing.  If someone who really knows assembly could analyze the resulting
code to see what's really going on, we might find a way to fix either the
macro or the cothreads (I'm thinking that there's something we missed in
constructing the cothreads themselves) so this works in all cases.

In the meantime, please insert both DEBUG_ENTER and DEBUG_LEAVE in your
functions.  Be sure to put DEBUG_ENTER after your variable declarations
and before any functional code, not to put the function name in any DEBUG
strings (it's already there, trust me), and put a DEBUG_LEAVE if you care
enough.

Changes are going to happen in the way DEBUGs and other printouts occur,
so stay tuned.
2000-12-04 09:35:08 +00:00
Erik Walthinsen
47bd1b0545 Added a check to see if the plugin actually exists before even bothering to try to load it. Saves a fair amount of d...
Original commit message from CVS:
Added a check to see if the plugin actually exists before even bothering
to try to load it.  Saves a fair amount of debugging spew with
_gst_plugin_spew enabled.
2000-12-04 09:32:43 +00:00
Wim Taymans
61ed3b06ee More test cases.
Original commit message from CVS:
More test cases.
2000-12-03 20:15:24 +00:00
Wim Taymans
0c40e4b819 Implemented real Caps checking.
Original commit message from CVS:
Implemented real Caps checking.
2000-12-03 20:15:15 +00:00
Wim Taymans
9652a3aef9 Added a test program for the capabilities
Original commit message from CVS:
Added a test program for the capabilities
2000-12-03 17:52:14 +00:00
Wim Taymans
4f55ae4ded Added multiple types to the pads.
Original commit message from CVS:
Added multiple types to the pads.
Added first preview of the capabilities system.
Autoplugging is seriously broken with these (and other) changes.
2000-12-03 17:51:29 +00:00
Richard Boulton
ed8dac9fa8 Remove cothreads.[ch] from tests/cothreads/ and replace then with a rule in the Makefile.am to generate symlinks to t...
Original commit message from CVS:
Remove cothreads.[ch] from tests/cothreads/ and replace then with a rule
in the Makefile.am to generate symlinks to the live versions of the code
in gst/ : fixes a compile error, and should keep things cleaner.
2000-12-03 15:02:24 +00:00
Erik Walthinsen
34811a366d Enhanced debugging by making DEBUG() print out the cothread ID as well as the process ID. cothread_getcurrent return...
Original commit message from CVS:
Enhanced debugging by making DEBUG() print out the cothread ID as well as
the process ID.  cothread_getcurrent returns the current cothread ID, or
-1 if cothreads aren't set up in this process context.
2000-12-03 00:17:52 +00:00
Erik Walthinsen
16834308e7 First pass at an outline for the Filter Writer's Guide. Mostly complete, though the structure needs some work. Just...
Original commit message from CVS:
First pass at an outline for the Filter Writer's Guide.  Mostly complete,
though the structure needs some work.  Just need someone to write it ;-)
2000-12-02 10:07:50 +00:00
Wim Taymans
f2128112c3 Another type system proposal.
Original commit message from CVS:
Another type system proposal.
2000-11-30 20:30:45 +00:00
Erik Walthinsen
64b4ac5cdf Rearranged cothread_switch a bit to move all the code for error conditions to the end, using goto's to get there. Th...
Original commit message from CVS:
Rearranged cothread_switch a bit to move all the code for error conditions
to the end, using goto's to get there.  This has the presumed advantage of
consolidating all the normally run code into one chunk, reducing jumps
(and the associated penalties in any modern processor) and limiting cache-
line usage.  It may be instructive to look at the generated assembly for
this revision and the previous, to see if gcc is smart enough to do this
for us anyway.

If you want to turn off some of the checks (they are all checks for NULL
pointers, if you're curious) for a speed gain, disable the #define of
COTHREAD_PARANOID at the top.
2000-11-29 10:05:47 +00:00
Wim Taymans
1eb3884bc6 Added the type system design.
Original commit message from CVS:
Added the type system design.
2000-11-26 19:11:00 +00:00
Wim Taymans
933bf32b3f More ramblings..
Original commit message from CVS:
More ramblings..
2000-11-25 18:13:26 +00:00
Wim Taymans
a588e5748b Another alternative to the src. Please correct.
Original commit message from CVS:
Another alternative to the src. Please correct.
2000-11-25 16:45:16 +00:00
Wim Taymans
d8e23920eb Added asci art control flow diagrams
Original commit message from CVS:
Added asci art control flow diagrams
2000-11-25 16:00:39 +00:00
Wim Taymans
26a69ef7f8 Code Cleanups
Original commit message from CVS:
Code Cleanups
Added use cases for the source elements.
2000-11-25 14:18:47 +00:00
Erik Walthinsen
a075cbda18 Added code to force the gsttypes plugin to load before gstelements, by simply having gstelements.c request the plugin...
Original commit message from CVS:
Added code to force the gsttypes plugin to load before gstelements, by
simply having gstelements.c request the plugin.  Solves some dependency
problems.  This is the correct method of doing this for now, though I had
a thought:

Have a static list of hard dependencies that the plugin system is responsible
for satisfying before even trying to load the plugin.  Makes plugin design
easier.
2000-11-25 07:43:57 +00:00
Erik Walthinsen
726f7d36dc added the ability to disable pads, not quite complete but sufficient for now
Original commit message from CVS:
added the ability to disable pads, not quite complete but sufficient for now
2000-11-25 07:02:55 +00:00
Erik Walthinsen
ab45f4c930 Fixed a dumb mistake: in gst_element_set_loop_function, it was forcing the cothread's entry function to change. This ...
Original commit message from CVS:
Fixed a dumb mistake: in gst_element_set_loop_function, it was forcing
the cothread's entry function to change. This is totally wrong, the
create_plan function in GstBin is responsible for setting that to its
own internal helper function.  Code removed outright...
2000-11-24 22:28:19 +00:00
Erik Walthinsen
9120d1bd43 Closed 22145 - gstelement.c: support hotswapping of loopfunc
Original commit message from CVS:
Closed 22145 - gstelement.c: support hotswapping of loopfunc

Added a flag GST_ELEMENT_NEW_LOOPFUNC that's set when a new loopfunc is set,
which needs to be obeyed by the loopfuncs themselves.  The assumption is
that only a loopfunc or an element that knows what it's doing will ever
change the loopfunc pointer, so they can be responsible for exitting
the loopfunc itself appropriately.

The loopfunc_wrapper function has been changed to call the loopfunc
pointer itself in a loop.  If the loopfunc changes, the current loop is
supposed to exit, which causes the loopfunc_wrapper to start up the new
loopfunc.
2000-11-23 21:49:09 +00:00
Erik Walthinsen
c758337d5a Closed task 22143 - gstelemnt.c: complete gst_element_connect
Original commit message from CVS:
Closed task 22143 - gstelemnt.c: complete gst_element_connect

SImple matter of cleaning up the conflicting checks and actually
connecting the pads in question.
2000-11-23 20:39:54 +00:00
Erik Walthinsen
4638451539 gstbin.c: modified so create_plan occurs after the state change of all the child elements.
Original commit message from CVS:
gstbin.c: modified so create_plan occurs after the state change of all the
child elements.
gstelement.c: set_state now loops such that each element only deals with
one state change at a time, i.e. NULL->READY,READY->PLAYING,
instead of a single NULL->PLAYING.
2000-11-23 08:13:43 +00:00
Wim Taymans
587051a384 Something was wrong with SSE initialisation in mpeg2dec
Original commit message from CVS:
Something was wrong with SSE initialisation in mpeg2dec
Added little performance test (compile with gprof)
2000-11-20 22:05:30 +00:00
Wim Taymans
92c447c536 Reworked AC3 decoder. No seeking yet but at least we do not need ac3parse anymore.
Original commit message from CVS:
Reworked AC3 decoder. No seeking yet but at least we do not need ac3parse
anymore.
Reworked dvdsrc to read scrambled data (DeCSS not included). I have
modified DeCSS a bit to work in GStreamer. Can I release the code or is
there some lawyer that's going to sue me?
MPEG2 SSE motion compensation.
Tried to add PTS to the MPEG decoder but failed.
2000-11-20 19:04:32 +00:00
Wim Taymans
01eb2caf72 The bonobo component now works on audio only (mp3/vorbis). Video is broken because bonobo does not handle multithread...
Original commit message from CVS:
The bonobo component now works on audio only (mp3/vorbis). Video
is broken because bonobo does not handle multithreading yet.
Added Bonobo toolbar and menu.
2000-11-12 20:34:29 +00:00