mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-12-22 00:06:36 +00:00
Code Issues 1 Projects Releases Wiki Activity
15196 commits 44 branches 1510 tags 505 MiB
Commit graph

15196 commits

This branch
This branch
All branches
Author SHA1 Message Date
Tim-Philipp Müller
ee6f526404 Automatic update of common submodule 
From 865aa20 to dbedaa0
 2013-11-05 11:17:25 +00:00
Reynaldo H. Verdejo Pinochet
afe174d38d gst-inspect: Remove some dead code 2013-11-04 13:56:37 -08:00
Alessandro Decina
2b84b4bd97 memory: explicitly cast to GstLockFlags to avoid compiler warnings 2013-11-04 11:53:56 +01:00
Mark Nauwelaerts
ebca6aa84f segment: resurrect sanitizing start and stop for seeking 2013-11-02 16:13:27 +01:00
Mark Nauwelaerts
e10af7c409 basesrc: mind boggling wrap when comparing offsets 2013-11-02 16:13:27 +01:00
Mark Nauwelaerts
8da78d1595 baseparse: try first frame pts and dts for a valid start timestamp 2013-11-02 16:13:27 +01:00
Mark Nauwelaerts
3aaa3fcf92 baseparse: print proper variable in debug statement 2013-11-02 16:13:27 +01:00
Olivier Crête
789eda5a37 parse: Make the FATAL_ERRORS flag also work without a GError 
Also add a unit tests
 2013-11-01 17:02:25 +00:00
Matthieu Bouron
a0e2eb6169 gst-launch: fix potential uninitialized variable warning 
https://bugzilla.gnome.org/show_bug.cgi?id=710758
 2013-11-01 15:15:29 +01:00
Reynaldo H. Verdejo Pinochet
a3431f5d8b docs: fix common typos emited/eachother/... 2013-10-31 16:28:06 -07:00
Sebastian Dröge
7e5dc030f5 utils: Add some attributes and reorganize code to fix compiler warnings 
gstutils.c:3659:41: error: format string is not a string literal
[-Werror,-Wformat-nonliteral]
    gchar *expanded = g_strdup_vprintf (stream_id, var_args);

https://bugzilla.gnome.org/show_bug.cgi?id=710621
 2013-10-30 21:53:36 +01:00
Antonio Ospite
c76aaaaa1d pwg: rename the "samplerate" variable to make example code compilable 
In one of the examples about gst_my_filter_setcaps() there is a variable
declared as "rate", but then the name "samplerate" is used when setting
the caps.

Use the name "rate" everywhere in gst_my_filter_setcaps().

https://bugzilla.gnome.org/show_bug.cgi?id=710876
 2013-10-30 18:46:37 +01:00
Fabian Kirsch
4ceeee9ff8 doc: fix forward reference about ghost pads 
https://bugzilla.gnome.org/show_bug.cgi?id=711089
 2013-10-29 22:06:31 +00:00
Tim-Philipp Müller
40872f26ae docs: design: fix some fixes 2013-10-28 12:55:19 +00:00
Tim-Philipp Müller
20c2008ef8 docs: flesh out gst-uninstalled entry in faq some more 
https://bugzilla.gnome.org/show_bug.cgi?id=709916
 2013-10-26 09:48:06 +01:00
Fabian Kirsch
d0dd23cf9f docs: FAQ update to mention create-uninstalled-setup.sh 
https://bugzilla.gnome.org/show_bug.cgi?id=709916
 2013-10-26 09:41:26 +01:00
Stefan Sauer
a6f60fcf2e registry: small cleanups and use object log variants more 2013-10-25 21:29:01 +02:00
Stefan Sauer
1e58699376 private: remove left-over comment 
The caps are saved in the registry.
 2013-10-25 21:28:30 +02:00
Stefan Sauer
ecbe3d4f2e registry: use g_slice_free for slice memory 
Avoid memory list corruption, but g_free'ing slice memory.
 2013-10-25 20:05:03 +02:00
Stefan Sauer
0089bcd3e2 design: flesh out the tracing design a little more 2013-10-25 20:05:03 +02:00
Luis de Bethencourt
bbc26fffc2 docs: fix typos in gstobject 2013-10-25 11:02:19 -04:00
Reynaldo H. Verdejo Pinochet
941cfd14d5 docs: Gram and nit fixes for part-meta.txt 2013-10-24 12:06:01 -07:00
Reynaldo H. Verdejo Pinochet
8a7ad85b23 docs: Gram and nit fixes for part-element-source.txt 2013-10-24 12:06:01 -07:00
Reynaldo H. Verdejo Pinochet
4d3b1d1558 docs: Gram and nit fixes for part-sink.txt 2013-10-24 12:06:01 -07:00
Reynaldo H. Verdejo Pinochet
a6b018a3bc docs: Gram and nit fixes for part-conventions.txt 2013-10-24 12:06:01 -07:00
Reynaldo H. Verdejo Pinochet
3abad71867 docs: Gram and nit fixes for part-controller.txt 2013-10-24 12:06:01 -07:00
Reynaldo H. Verdejo Pinochet
e6dda14148 docs: Gram and nit fixes for part-context.txt 2013-10-24 12:06:01 -07:00
Reynaldo H. Verdejo Pinochet
11503e4b3f docs: Gram and nit fixes for part-clocks.txt 2013-10-24 12:06:01 -07:00
Reynaldo H. Verdejo Pinochet
3d693f387f docs: Gram and nit fixes for part-caps.txt 2013-10-24 12:06:01 -07:00
Reynaldo H. Verdejo Pinochet
72edc18465 docs: Gram and nit fixes for part-buffer.txt 2013-10-24 12:06:01 -07:00
Reynaldo H. Verdejo Pinochet
20c32ffbdf docs: Gram and nit fixes for part-bufferpool.txt 2013-10-24 12:06:01 -07:00
Reynaldo H. Verdejo Pinochet
06a79347f3 docs: Gram and nit fixes for part-buffering.txt 2013-10-24 12:06:01 -07:00
Reynaldo H. Verdejo Pinochet
52810aa6ee docs: Gram and nit fixes for part-messages.txt 2013-10-24 12:06:01 -07:00
Reynaldo H. Verdejo Pinochet
eb57390198 docs: Gram and nit fixes for part-memory.txt 2013-10-24 12:06:01 -07:00
Philip Withnall
3c8424d9ae net: Constify a parameter to gst_net_client_clock_new() 
Even though this parameter is not used, it should be const to fit in with the
coding standards for other similar parameters. Client code already passes in
const strings under the expectation that they won’t be modified.

https://bugzilla.gnome.org/show_bug.cgi?id=710442
 2013-10-18 09:59:25 +01:00
Sebastian Dröge
2231721ddd datetime: Make sure to include gst_private.h before glib-compat-private.h 
We need to define the GLib log domain before including glib.h, which is
included by glib-compat-private.h.
 2013-10-15 11:44:48 +02:00
Thibault Saunier
8a5adf9c68 docs: Add gst_pad_store_sticky_event to sections.txt 
So it appears in the generated documentation
 2013-10-14 18:08:55 -03:00
Sebastian Rasmussen
1479aba1cf tests/filesrc: Set location in wrong state 
Also remove incorrect comment about code possibly not being reachable
that is now exercised by the filesrc unit test.

https://bugzilla.gnome.org/show_bug.cgi?id=709831
 2013-10-13 12:18:57 -04:00
Jan Schmidt
75b7387f8b parse: Fix transfer annotations for parse_launch functions. 
gst_parse_launchv, gst_parse_launchv_full and gst_parse_launch_full
all return floating refs, the same as gst_parse_launch, which just
calls gst_parse_launch_full internally anyway.

Add a unit test assertion to check it's true.

Spotted by nemequ on IRC.
 2013-10-12 16:20:50 +11:00
Reynaldo H. Verdejo Pinochet
94a3394edf core: Fix max DEBUG_LEVEL incongruence on 5 vs 9 
In the docs and the autocompletion logic the maximum
value jumped incongruently between 5 and 9.
 2013-10-10 13:06:14 -07:00
Sebastian Dröge
4429ea53c4 caps: Skip test_subset_duplication until the bug is fixed 
https://bugzilla.gnome.org/show_bug.cgi?id=709253
 2013-10-10 13:19:09 +02:00
Fabian Kirsch
0db5ae7962 docs: Fix some reference URIs 
https://bugzilla.gnome.org/show_bug.cgi?id=709804
 2013-10-10 13:15:45 +02:00
Sebastian Dröge
eb0d978e1e caps: Add a testcase for subset checks on lists with duplicated items 
https://bugzilla.gnome.org/show_bug.cgi?id=709253
 2013-10-10 12:42:52 +02:00
Thibault Saunier
0564c1c2b8 collectpads: Call the collected function while it returns FLOW_OK 
This allows us to make sure the elements is EOS and does not have
remaining buffers to be drained.

https://bugzilla.gnome.org/show_bug.cgi?id=709637
 2013-10-09 20:29:02 -03:00
Tim-Philipp Müller
89ae3c2a82 docs: fix function name in qos design docs 2013-10-05 10:09:00 +01:00
Tim-Philipp Müller
10981f781c tests: use tcase_skip_broken_test() to skip broken multiqueue test 
So that we get a warning in the output that reminds us that
something needs to be fixed.
 2013-10-02 12:30:54 +01:00
Edward Hervey
3537ad8ae1 check: Disable multiqueue test_output_order check 
The check itself is racy.

 (CK_FORK=no GST_CHECK=test_output_order make elements/multiqueue.forever).

The problem is indeed the test and not the actual element behaviour.

The objects to push are being pulled out of the single internal queues in the
right order and at the right time...

But between:
* the moment the global multiqueue lock is released (which was used to detect
if we should pop and push downstream the next buffer)
* and the moment it is received by the source pad (which does the check)

=> another single queue (like the unlinked pad) might pop and push a buffer
downstream

What should we do ? Putting a bigger margin of error (say 5 buffers) doesn't
help, it'll eventually fail.

I can't see how we can detect this reliably.

https://bugzilla.gnome.org/show_bug.cgi?id=708661
 2013-10-02 11:26:09 +02:00
Thiago Santos
007c0e5fe1 value: fix caps serialization when there are caps inside caps 
Wrap caps strings so that it can handle serialization and deserialization
of caps inside caps. Otherwise the values from the internal caps are parsed
as if they were from the upper one

https://bugzilla.gnome.org/show_bug.cgi?id=708772
 2013-09-30 16:20:48 -03:00
Edward Hervey
3892e4dd61 pluginloader: Check errors on the proper fd 
Most likely a copy-paste error from the block before.

If we're going to check for error/closed on the write fd... do it
on the write fd
 2013-09-28 08:42:44 +02:00
Brendan Long
a89d53dd32 docs: fix spelling of "generic" in GstBaseSrc's documentation. 
https://bugzilla.gnome.org/show_bug.cgi?id=708870
 2013-09-26 21:15:27 +01:00