A (buggy) glib g_slice_dup macro may cause compiler warnings on e.g. x86_64.

'type' is never used until line 1847 where it's overwritten.

The return value of gst_element_change_state isn't used after that call.

If that block is entered, then start_time becomes GST_CLOCK_TIME_NONE.
Since start_time is invalid, the code will enter the block at line 434 and
new_base_time will be set there.

that variable isn't used anywhere else within that block.

Also wake up the async thread when it is doing an async wait for an entry.

Check all reads against the end of the data region. Roll back registration of
partial reads.

Move the checks for using an unscheduled entry from the unsafe GstClock to the
SystemClock object so that we can perform the correct locking.
fix a leak and potential deadlock then the async thread fails to start.
Sprinkle some G_LIKELY around because we can.

Remove a pending async wakeup before we check if the next entry is UNSCHEDULED
because we might leave the control socket busy.

Keep a counter for the amount of outstanding wakeups that we produce and only
perform a write/read to the control socket when 1 or 0 respectively.
don't poll when waiting for the entries to be unblocked and clear their wakeup
counts, just act on the signal when the wakeup count is 0.
unscheduled entries will clear their wakeup count themselves.
Keep track of when we wakeup the async thread because the list of entries has
changed.
don't try to see if the list changed because we can't really know when one entry
is added multiple times.
Only wake up the async thread when we add an async entry to the head of the list
and the old entry was BUSY.

Note the changed behaviour of gst_poll_wait for timer GstPoll's, and
fix a couple of spelling errors.

when an entry being waited on in the async thread is unscheduled, clear the
wakeup queue so we can continue waiting on other entries.
When an entry being waited on in the async thread is unlocked because an earlier
entry was added to the list, set the entry to OK again. This makes sure that
only the entries being waited on have the BUSY flag set and wake up the timer
poll when they are unscheduled.

Saves some cycles/pandas for those of us who run uninstalled setups.

This helps prevent filesystem/data inconsistencies in certain
circumstances on certain filesystems (like ext4, xfs, ubifs).
Also see bug #562976.

Convenience API, mostly for image tags, so people don't have to
figure out the whole GValue/GstValue thing just for this.

Yes, 'codec' isn't exactly the best word, but let's be consistent with AUDIO_CODEC
and VIDEO_CODEC (which may be 'raw' formats as well after all). Prerequisite for
bug  #576552.

Use string deserialisation instead of custom parsing code to allow for all
supported ways of specifying property values.
fixes #576582.

Running configure with e.g. --disable-dst-debug was compiling out the debug
system (ABI break). Now stubs are added and only if one does e.g.
make CFLAGS="-DGST_REMOVE_DISABLED" the symbols are ommitted.

because we can, and for consistency.

We were converting the GstPadLinkReturn to a gboolean, which is not what we want
to do.

Fixes #517231.

Refactor the debug line code to use as much code as possible for the win32 and
other color codings.
Update docs with new symbol.

Move the gst_pad_can_link() implementation from gstutils to gstpad and use
gst_pad_link_prepare() to make it work correctly and also check the caps.

Make the broken implementation in gstutils static.

Small cleanups in the _get_fixed_caps() function.

Fixes #575682.

Fixes build with -Werror caused by '_FILE_OFFSET_BITS redefined' warning on
OpenSolaris where _FILE_OFFSET_BITS may be defined both in our config.h
and via stdio.h (#575695).

Bin collects segment-start messages and segent-done messages. it posts a
segment-done message to its parent, once it has received a segment-done for
each segment-start. Imho it should also send a segment-start if it receives the
first segment start and if parent is !=NULL. This is needed for bins in bins,
so that also higher order bins can group segment-starts and segment-dones.
Right now higher order bins will post a segment-done for each segment-done
received.