ChangeLog 3.22 MB
Newer Older
Sebastian Dröge's avatar
Sebastian Dröge committed
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
=== release 1.1.2 ===

2013-07-11  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* configure.ac:
	  releasing 1.1.2

2013-07-10 15:52:10 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* gst/gstbin.c:
	  bin: Always forward clock-lost message if we're not a top-level bin
	  This makes sure that no bin misses the clock-lost messages, independent
	  of the state, and could return an old, non-working clock from
	  gst_bin_provide_clock_func().
	  https://bugzilla.gnome.org/show_bug.cgi?id=701997

2013-07-10 14:30:31 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* plugins/elements/gstinputselector.c:
	  inputselector: Keep previous active sinkpad around until we're done with it
	  Otherwise we'll send a new segment event downstream for each buffer.

2013-07-08 15:26:38 +0100  Tim-Philipp Müller <tim.muller@collabora.co.uk>

	* gst/gstallocator.c:
	  allocator: fix type of gst_memory_alignment to match declaration
	  Fixes compiler warnings such as
	  gstallocator.c:61:8: error: conflicting types for 'gst_memory_alignment'
	  ../gst/gstallocator.h:52:18: note: previous declaration of 'gst_memory_alignment' was here

2013-07-05 21:36:27 +0200  Piotr Drąg <piotrdrag@gmail.com>

	* po/POTFILES.in:
	  po: update POTFILES.in
	  https://bugzilla.gnome.org/show_bug.cgi?id=703682

2013-07-04 20:39:26 -0400  Thibault Saunier <thibault.saunier@collabora.com>

	* libs/gst/base/gstbasesrc.c:
	  basesrc: Do not lock a mutex that does not exist
	  The GST_LIVE_LOCK is on GstBaseSrc, not on its source pad.

2013-07-03 21:23:44 +0200  Wim Taymans <wim.taymans@collabora.co.uk>

	* libs/gst/base/gstbaseparse.c:
	  baseparse: reset PTS after seek
	  Fixes https://bugzilla.gnome.org/show_bug.cgi?id=702778

2013-07-03 13:03:49 -0400  Nicolas Dufresne <nicolas.dufresne@collabora.co.uk>

	* gst/gstallocator.c:
	* gst/gstevent.c:
	* gst/gstghostpad.c:
	* gst/gstinfo.h:
	* gst/gstmessage.c:
	* gst/gstminiobject.c:
	* gst/gstpad.c:
	* gst/gstplugin.c:
	* gst/gsttaglist.c:
	* gst/gsttypefind.c:
	* gst/gstutils.c:
	* libs/gst/base/gstcollectpads.c:
	* libs/gst/base/gsttypefindhelper.c:
	* libs/gst/base/gsttypefindhelper.h:
	  Add few missing allow-none annotation

2013-07-03 09:27:13 +0100  Tim-Philipp Müller <tim@centricular.net>

	* scripts/gst-uninstalled:
	  gst-uninstalled: add new -bad mpegts lib
	  And remove signalprocessor/video libs from -bad which have gone
	  away or were merged into -base.

2013-07-01 20:35:21 -0400  Olivier Crête <olivier.crete@collabora.com>

	* plugins/elements/gstfunnel.c:
	* plugins/elements/gstfunnel.h:
	* tests/check/elements/funnel.c:
	  funnel: Re-push all sticky events when buffers come from a different pad
	  Don't special case segment/caps, just push all sticky events when they are
	  received on the currently active pad or when the active pad changes.

2013-07-01 20:21:10 -0400  Olivier Crête <olivier.crete@collabora.com>

	* plugins/elements/gstfunnel.c:
	  funnel: Use default pad function for upstream event/queries
	  The default functions in 1.x already do the right thing

2013-07-01 20:18:58 -0400  Olivier Crête <olivier.crete@collabora.com>

	* tests/check/elements/funnel.c:
	  tests: Remove funnel pad_alloc test

2013-07-01 20:07:03 -0400  Olivier Crête <olivier.crete@collabora.com>

	* libs/gst/check/gstcheck.h:
	  check: Change stream_id parameter name to match GtkDoc

2013-07-01 11:10:00 +0200  Jonas Holmberg <jonashg@axis.com>

	* docs/libs/gstreamer-libs-sections.txt:
	* libs/gst/check/Makefile.am:
	* libs/gst/check/gstcheck.c:
	* libs/gst/check/gstcheck.h:
	* tests/check/elements/funnel.c:
	  check: Added gst_check_setup_events_with_stream_id()
	  Added a new function gst_check_setup_events_with_stream_id(), since
	  gst_check_setup_events() does not work with multiple pads.
	  https://bugzilla.gnome.org/show_bug.cgi?id=703377

2013-06-30 18:39:03 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* gst/gstpad.c:
	  pad: Don't consider flushing pads as needing reconfiguration
	  Renegotiation and reconfiguration will fail because all queries
	  and events won't be accepted by the pad if it's flushing. In the
	  best case this just causes unneeded work and spurious warnings in
	  the debug logs, in the worst case it causes elements to fail completely.

2013-06-24 23:25:51 +0200  Wim Taymans <wim.taymans@collabora.co.uk>

	* plugins/elements/gstqueue2.c:
	  queue2: only block serialized query when it's safe
	  We must be certain that we don't cause a deadlock when blocking the serialized
	  queries. One such deadlock can happen when we are buffering and downstream is
	  blocked in preroll and a serialized query arrives. Downstream will not unblock
	  (and allow our query to execute) until we complete buffering and buffering will
	  not complete until we can answer the query..
	  Fixes https://bugzilla.gnome.org/show_bug.cgi?id=702840

2013-06-19 12:30:47 +0200  Sjoerd Simons <sjoerd.simons@collabora.co.uk>

	* gst/gstpad.c:
	  pad: Add a filter to the caps_query done by acceptcaps
	  Use the caps that the pad is asked to accept as filter for the query
	  https://bugzilla.gnome.org/show_bug.cgi?id=702632

2013-06-19 12:19:02 +0200  Sjoerd Simons <sjoerd.simons@collabora.co.uk>

	* libs/gst/base/gstbasetransform.c:
	  basetransform: optimize default acceptcaps implementation
	  Pass the fixed caps we're asked to accept as a filter for the caps
	  query, so we don't get a fully-expanded set of caps back (which we don't
	  need and can take a lot of time for intersection).
	  This reduces the time for camerabin to produce a second frame on a
	  logitech C910 camera from around 52 seconds to a bit less then 16
	  seconds on my system.
	  https://bugzilla.gnome.org/show_bug.cgi?id=702632

2013-06-19 09:19:53 +0200  Edward Hervey <edward@collabora.com>

	* gst/gsttaglist.c:
	  taglist: Avoid combinatorial explosion when merging tags
	  When appending/prepending tags, avoid re-creating (and copying) lists if we already
	  have one and instead just append/prepend the GValue to the list.
	  https://bugzilla.gnome.org/show_bug.cgi?id=702545

2013-06-19 10:53:21 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* plugins/elements/gstqueue.c:
	  queue: Don't hold the queue mutex while doing serialized queries downstream
	  https://bugzilla.gnome.org/show_bug.cgi?id=702520

2013-06-19 10:45:45 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* tests/check/gst/gstbuffer.c:
	  buffer: Add unit test for map_range()
	  https://bugzilla.gnome.org/show_bug.cgi?id=702617

2013-06-19 08:36:22 +0200  Paul HENRYS <visechelle@gmail.com>

	* gst/gstbuffer.c:
	  buffer: Fix wrong size/index handling when merging memory
	  https://bugzilla.gnome.org/show_bug.cgi?id=702617

2013-06-18 11:39:55 +0200  Stefan Sauer <ensonic@users.sf.net>

	* docs/list-ulink.xsl:
	  docs: add missing file for doc-link check

2013-06-17 11:12:51 +0200  Wim Taymans <wim.taymans@collabora.co.uk>

	* tests/benchmarks/Makefile.am:
	* tests/benchmarks/gstpoolstress.c:
	  tests: add stress test for buffers and pools

2013-06-17 10:25:20 +0200  Wim Taymans <wim.taymans@collabora.co.uk>

	* libs/gst/base/gstbasesink.c:
	  basesink: call state change in all cases
	  When we asynchronously go from READY to PLAYING, also call the
	  state change function so that subclasses can update their state for PLAYING.
	  Because the PREROLL lock is not recursive, we can't make this without
	  races and we must assume for now that the subclass can handle concurrent calls
	  to PAUSED->PLAYING and PLAYING->PAUSED. We can make this assumption because not
	  many elements actually do something in those state changes and the ones that
	  did would be broken even more without this change.
	  https://bugzilla.gnome.org/show_bug.cgi?id=702282

2013-06-16 15:07:35 +0200  Stefan Sauer <ensonic@users.sf.net>

	* docs/faq/dependencies.xml:
	* docs/manual/appendix-integration.xml:
	* docs/manual/basics-pads.xml:
	* docs/manual/intro-motivation.xml:
	  docs: fix some external links

2013-06-16 14:45:08 +0200  Stefan Sauer <ensonic@users.sf.net>

	* docs/manuals.mak:
	  docs: check for broken links in docs
	  The check is done using curl (if available). It lists the curl exit code + http
	  status code (for those > 399) together with the use of the url in the code. The
	  check is not fatal.

2013-06-16 13:05:21 +0200  Stefan Sauer <ensonic@users.sf.net>

	* docs/manual/basics-elements.xml:
	* docs/pwg/intro-preface.xml:
	  docs: change https to http urls
	  Thank you browser for needlessly changing to https for static doc pages.

2013-06-16 11:41:52 +0200  Stefan Sauer <ensonic@users.sf.net>

	* docs/faq/developing.xml:
	* docs/manual/basics-elements.xml:
	* docs/manual/basics-init.xml:
	* docs/pwg/intro-preface.xml:
	  docs: update links to developer.gnome.org
	  The URL layout has changed. Fix the links and comment out one paragraph where
	  the doc is gone.
	  Fixes #702135

2013-06-14 13:05:38 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* docs/gst/gstreamer-sections.txt:
	* gst/gststructure.c:
	* gst/gststructure.h:
	* win32/common/libgstreamer.def:
	  structure: Add gst_structure_new_from_string()
	  Convenience API for bindings, gst_structure_from_string() returns
	  a tuple (structure, end_ptr) in bindings and is unintuitive to use
	  because of that.

2013-06-13 08:36:23 +0200  Hans de Goede <hdegoede@redhat.com>

	* gst/gst.c:
	  gst: Don't intercept --help in gst_init()
	  Before this patch gst_init would intercept --help, causing for example
	  cheese's --help to look like this:
	  [hans@shalem cheese]$ cheese --help
	  Usage:
	  cheese [OPTION...] - GStreamer initialization
	  Help Options:
	  -h, --help                        Show help options
	  --help-all                        Show all help options
	  --help-gst                        Show GStreamer Options
	  gst_init is the only gfoo_init function which does this.
	  https://bugzilla.gnome.org/show_bug.cgi?id=702089

2013-06-12 09:45:56 +0100  Tim-Philipp Müller <tim@centricular.net>

	* scripts/gst-uninstalled:
	  gst-uninstalled: add uridownloader lib in -bad to search paths
	  Even if it might not be around for long.

2013-06-11 10:25:02 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* tools/gst-launch.c:
	  gst-launch: Remove unref that should not be there
	  We keep a reference to the context around all the time.
	  https://bugzilla.gnome.org/show_bug.cgi?id=701985

2013-06-09 17:20:22 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* tools/gst-launch.c:
	  gst-launch: Improve GstContext handling
	  https://bugzilla.gnome.org/show_bug.cgi?id=700967

2013-06-07 13:07:37 +0200  Kim Lam <kim@redgiantsoftware.com>

	* win32/vs10/base/base.vcxproj:
	  win32: Don't include gstcollectpads.c twice
	  https://bugzilla.gnome.org/show_bug.cgi?id=701603

2013-05-31 09:39:55 -0600  Brendan Long <b.long@cablelabs.com>

	* plugins/elements/gstinputselector.c:
	  input-selector: send notify::active signal for input-selector pads.
	  https://bugzilla.gnome.org/show_bug.cgi?id=701319

2013-06-06 16:46:12 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* libs/gst/base/gstbasesrc.c:
	  basesrc: Only force-update the duration for dynamic sources when doing the DURATION query
	  Doing it after every single create() is not very efficient and not necessary.
	  Especially on network file systems fstat() is not cached and causes network
	  traffic, making the source possibly unusable slow.
	  https://bugzilla.gnome.org/show_bug.cgi?id=652037

2013-06-05 18:36:40 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* configure.ac:
	  Back to development

Sebastian Dröge's avatar
Sebastian Dröge committed
306
307
=== release 1.1.1 ===

Sebastian Dröge's avatar
Sebastian Dröge committed
308
2013-06-05 17:58:51 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>
Sebastian Dröge's avatar
Sebastian Dröge committed
309

Sebastian Dröge's avatar
Sebastian Dröge committed
310
311
312
313
	* ChangeLog:
	* NEWS:
	* RELEASE:
	* common:
Sebastian Dröge's avatar
Sebastian Dröge committed
314
	* configure.ac:
Sebastian Dröge's avatar
Sebastian Dröge committed
315
316
317
318
319
320
321
322
323
	* docs/plugins/gstreamer-plugins.args:
	* docs/plugins/gstreamer-plugins.hierarchy:
	* docs/plugins/inspect/plugin-coreelements.xml:
	* gstreamer.doap:
	* win32/common/config.h:
	* win32/common/gstenumtypes.c:
	* win32/common/gstenumtypes.h:
	* win32/common/gstversion.h:
	  Release 1.1.1
Sebastian Dröge's avatar
Sebastian Dröge committed
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000

2013-06-05 16:06:35 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* po/af.po:
	* po/az.po:
	* po/be.po:
	* po/bg.po:
	* po/ca.po:
	* po/cs.po:
	* po/da.po:
	* po/de.po:
	* po/el.po:
	* po/en_GB.po:
	* po/eo.po:
	* po/es.po:
	* po/eu.po:
	* po/fi.po:
	* po/fr.po:
	* po/gl.po:
	* po/hu.po:
	* po/id.po:
	* po/it.po:
	* po/ja.po:
	* po/lt.po:
	* po/nb.po:
	* po/nl.po:
	* po/pl.po:
	* po/pt_BR.po:
	* po/ro.po:
	* po/ru.po:
	* po/rw.po:
	* po/sk.po:
	* po/sl.po:
	* po/sq.po:
	* po/sr.po:
	* po/sv.po:
	* po/tr.po:
	* po/uk.po:
	* po/vi.po:
	* po/zh_CN.po:
	* po/zh_TW.po:
	  Update .po files

2013-06-05 15:14:14 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* common:
	  Automatic update of common submodule
	  From 098c0d7 to 01a7a46

2013-06-05 11:02:50 +0200  Edward Hervey <edward@collabora.com>

	* gst/gstbufferpool.c:
	* gst/gstvalue.c:
	* gst/gstvalue.h:
	* win32/common/libgstreamer.def:
	  gstvalue: Add _append_and_take_value() public variants
	  API: gst_value_array_append_and_take_value
	  API: gst_value_list_append_and_take_value
	  We were already using this internally, this makes it public for code
	  which frequently appends values which are expensive to copy (like
	  structures, arrays, caps, ...).
	  Avoids copies of the values for users. The passed GValue will also
	  be 0-memset'ed for re-use.
	  New users can replace this kind of code:
	  gst_value_*_append_value(mycontainer, &myvalue);
	  g_value_unset(&myvalue);
	  by:
	  gst_value_*_append_and_take_value(mycontainer, &myvalue);
	  https://bugzilla.gnome.org/show_bug.cgi?id=701632

2013-05-29 17:20:34 +0200  Edward Hervey <edward@collabora.com>

	* gst/gstbuffer.c:
	  gstbuffer: Use internal function for buffer_new_wrapped
	  Shaves ~10% instruction calls from the total cost
	  https://bugzilla.gnome.org/show_bug.cgi?id=701633

2013-05-30 22:57:49 -0600  Brendan Long <self@brendanlong.com>

	* plugins/elements/gstinputselector.c:
	  input-selector: return FALSE for "active" property if selector is NULL
	  https://bugzilla.gnome.org/show_bug.cgi?id=701323

2013-06-01 14:00:22 +0100  Andrzej Bieniek <andyhelp@gmail.com>

	* docs/manual/advanced-threads.xml:
	  manual: update elements to match the rest of "Boost priority of a thread" section

2013-06-01 13:55:50 +0100  Andrzej Bieniek <andyhelp@gmail.com>

	* docs/manual/advanced-dataaccess.xml:
	  manual: fix comment in effectswitch example

2013-06-01 13:49:18 +0100  Andrzej Bieniek <andyhelp@gmail.com>

	* docs/manual/advanced-dataaccess.xml:
	  manual: fix a typo in "Inserting data with appsrc" section

2013-06-01 13:22:22 +0100  Andrzej Bieniek <andyhelp@gmail.com>

	* docs/pwg/advanced-dparams.xml:
	* docs/pwg/advanced-qos.xml:
	* docs/pwg/appendix-checklist.xml:
	  pwg: fix a few typos

2013-05-31 23:37:07 +0100  Andrzej Bieniek <andyhelp@gmail.com>

	* docs/pwg/advanced-allocation.xml:
	* docs/pwg/building-boiler.xml:
	* docs/random/porting-to-1.0.txt:
	  docs: remove double "the"

2013-05-28 23:34:54 +0100  Krzysztof Konopko <krzysztof.konopko@gmail.com>

	* scripts/git-update.sh:
	  scripts: improve git-update.sh status message
	  By default when the script is about to exit (normally or due to an error),
	  it checks whether $ERROR_LOG file exists.  If the log file exists, the
	  script prints a "Failures: " message prefix and dumps the log file to the
	  output.
	  Apparently the log file is always created and if the update/build is
	  successful, the script finishes with a bit misleading "Failures: " message.
	  An improvement provided with this change lets the log file to be created as
	  needed, i.e. if there's an error message to be printed.  If the file
	  doesn't exists, the script prints a "Update done" message which clearly
	  indicates success.
	  https://bugzilla.gnome.org/show_bug.cgi?id=701177

2013-05-30 07:03:40 +0200  Wim Taymans <wim.taymans@collabora.co.uk>

	* tests/check/generic/sinks.c:
	  check: fix position unit test

2013-05-30 06:51:24 +0200  Wim Taymans <wim.taymans@collabora.co.uk>

	* libs/gst/base/gstbasesink.c:
	  basesink: improve position reporting without clock
	  When no base time or when sync is disabled, use the same logic as
	  in paused to report position. The logic in PLAYING assumes we use the
	  clock.

2013-05-29 11:36:38 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* tests/check/gst/gstpad.c:
	  pad: Fix memory leak in the unit test

2013-05-28 12:44:19 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* gst/gstelementfactory.c:
	  elementfactory: Add support for checking subtitle/metadata factory types

2013-05-28 12:41:27 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* gst/gstelementfactory.c:
	  elementfactory: Add support for checking only the media type of a factory
	  And while at it also add Metadata and Subtitle media types.

2013-05-27 16:38:18 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gstmultiqueue.c:
	* plugins/elements/gstqueue.c:
	  (multi)queue: Don't access query items during flushing

2013-05-27 16:22:00 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gstmultiqueue.c:
	  multiqueue: Don't do serialized queries when we're flushing
	  Just immediately fail the query, otherwise we would wait forever
	  for the query to be answered.

2013-05-27 16:08:39 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gstqueue2.c:
	  queue2: First set query result, then signal GCond

2013-05-27 15:59:07 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gstqueue.c:
	* plugins/elements/gstqueue.h:
	  queue: Fix handling of serialized queries
	  During FLUSH_START the query needs to be unblocked already, otherwise
	  it can lead to deadlocks if the FLUSH_START is the result of something
	  done from the streaming thread of the srcpad (the queue will never be
	  emptied!).

2013-05-27 15:41:14 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gstqueue2.c:
	  queue2: Unblock any waiting serialize queries on FLUSH_START
	  Fixes some deadlocks during flushing.
	  And store queue items differently to not accidentially read
	  already unreffed queries when flushing. Queries are owned by
	  upstream and not us.

2013-05-27 13:01:43 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* plugins/elements/gstmultiqueue.c:
	* plugins/elements/gstqueue.c:
	* plugins/elements/gstqueue2.c:
	  queue/queue2/multiqueue: When flushing, make sure to not lose any sticky events
	  https://bugzilla.gnome.org/show_bug.cgi?id=688824

2013-05-27 12:40:50 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* gst/gstpad.c:
	  pad: Store sticky events even if the pad is flushing
	  But do this only for events that are not dropped by flushing,
	  i.e. do it only for everything except SEGMENT and EOS.
	  Without this we might drop a CAPS event if flushing happens
	  at an unfortunate time and nobody is resending the CAPS event.
	  https://bugzilla.gnome.org/show_bug.cgi?id=700806

2013-05-25 22:03:53 -0400  Nicolas Dufresne <nicolas.dufresne@collabora.co.uk>

	* plugins/elements/gstvalve.c:
	  valve: Don't read sticky flag from unrefed event

2013-05-24 23:28:04 +0100  Tim-Philipp Müller <tim@centricular.net>

	* plugins/elements/gsttee.c:
	  tee: fix property description for now-unused "alloc-pad" property
	  Should probably proxy ALLOCATION queries on that though, if set.
	  But what else? CAPS and ACCEPT_CAPS too?

2013-05-24 23:01:09 +0100  Tim-Philipp Müller <tim@centricular.net>

	* libs/gst/base/gstbasetransform.c:
	  basetransform: remove 0.10-ism from docs
	  gst_buffer_pad_alloc() never existed, and gst_pad_alloc_buffer()
	  doesn't exist any more either, so don't mention it in the docs.
	  https://bugzilla.gnome.org/show_bug.cgi?id=694714

2013-05-24 19:22:22 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* plugins/elements/gstqueue2.c:
	* plugins/elements/gstqueue2.h:
	  queue2: Add support for serialized queries if using a memory queue

2013-05-24 18:47:24 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* plugins/elements/gstqueue.c:
	  queue: Set the last serialized query result to FALSE when flushing

2013-05-24 18:42:55 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* plugins/elements/gstmultiqueue.c:
	  multiqueue: Initialize all GstMultiQueueItem fields in both code paths

2013-05-24 18:38:40 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* plugins/elements/gstmultiqueue.c:
	  multiqueue: Don't access the query after signalling the waiting thread
	  It might've free'd the query already.

2013-05-24 18:30:44 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* plugins/elements/gstmultiqueue.c:
	  multiqueue: Make sure to always signal any possible pending serialized queries
	  And don't unref them when flushing the queue, they're owned by the caller!
	  https://bugzilla.gnome.org/show_bug.cgi?id=700342

2013-05-24 14:37:19 +0200  Sebastian Dröge <slomo@circular-chaos.org>

	* libs/gst/base/gstbasetransform.c:
	  basetransform: Return GST_FLOW_ERROR if the allocator did not allow to allocate a buffer

2013-05-24 16:24:10 +0900  Olivier Crête <olivier.crete@collabora.com>

	* docs/manual/appendix-integration.xml:
	  docs: Remove mention of gconf* elements
	  Instead recommend pulsesrc/sink for audio, there is nothing GNOME
	  specific for video.

2013-05-15 13:22:04 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gsttypefindelement.c:
	  typefind: Handle the force-caps property more similar to all typefinding code flow
	  This makes sure that events happen in order and simplifies the code a bit.

2013-05-15 11:21:46 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* libs/gst/check/gstcheck.c:
	  check: Fix event handling in gst_check_element_push_buffer_list()

2013-05-15 10:51:01 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* common:
	  Automatic update of common submodule
	  From 5edcd85 to 098c0d7

2013-05-10 16:03:34 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* gst/gstpad.c:
	  pad: Only check if we get buffers before stream-start/segment if compiling without G_DISABLE_ASSERT
	  In releases this is set usually.

2013-05-09 17:17:14 -0400  Nicolas Dufresne <nicolas.dufresne@collabora.com>

	* docs/libs/gstreamer-libs-sections.txt:
	* libs/gst/check/Makefile.am:
	* libs/gst/check/gstcheck.c:
	* libs/gst/check/gstcheck.h:
	  check: Add helper that sends initial events
	  https://bugzilla.gnome.org/show_bug.cgi?id=700033

2013-05-09 17:22:16 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* gst/gstpad.c:
	  pad: Fix uninitialized variable compiler warning

2013-05-09 17:21:13 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* gst/gstpad.c:
	  pad: Make sure pending, older sticky events are sent downstream in dynamic linking scenarios
	  If a pad block was triggered from sending a sticky event downstream, it
	  could happen that the pad block is relinking pads, which then requires
	  to resend previous sticky events.

2013-05-09 13:32:07 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* tests/check/elements/fakesink.c:
	* tests/check/elements/filesink.c:
	* tests/check/elements/funnel.c:
	* tests/check/elements/identity.c:
	* tests/check/elements/multiqueue.c:
	* tests/check/elements/queue.c:
	* tests/check/elements/queue2.c:
	* tests/check/elements/selector.c:
	* tests/check/elements/tee.c:
	* tests/check/generic/sinks.c:
	* tests/check/gst/gstghostpad.c:
	* tests/check/gst/gstpad.c:
	* tests/check/libs/collectpads.c:
	  tests: Fix event order warnings and dataflow before stream-start/segment event

2013-05-09 13:31:38 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* tests/check/libs/test_transform.c:
	* tests/check/libs/transform1.c:
	  basetransform: Properly port unit test to actually use caps and check results

2013-05-09 12:50:20 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gstqueue.c:
	  queue: Store sticky events on the srcpad if we're dropping them because of leaking

2013-05-09 12:27:12 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gstoutputselector.c:
	  outputselector: Always forward sticky events to all pads

2013-05-09 12:15:48 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gstinputselector.c:
	  inputselector: Forward all sticky events, including stream-start

2013-05-09 11:05:50 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* gst/gstpad.c:
	  pad: Warn if data flow happens before stream-start or segment event

2013-05-09 10:59:41 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* gst/gstpad.c:
	  pad: Only let gst_pad_sticky_events_foreach() iterate over existing events

2013-05-09 10:29:11 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* gst/gstpad.c:
	  pad: If we push sticky events because of another sticky event, only push those that come before the new event
	  https://bugzilla.gnome.org/show_bug.cgi?id=699937

2013-05-09 09:50:41 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gstcapsfilter.c:
	  capsfilter: Add more debug output and forward caps events immediately too

2013-05-09 09:42:33 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* gst/gstpad.c:
	  pad: No sticky events must arrive after EOS

2013-05-09 09:38:35 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gstcapsfilter.c:
	  capsfilter: Fix typo in last commit

2013-05-08 19:44:09 -0400  Nicolas Dufresne <nicolas.dufresne@collabora.co.uk>

	* gst/gstpad.c:
	  pad: Improve warning message naming events type name
	  With this patch, message should look like ¨Sticky event misordering, got
	  'caps' before 'stream-start'¨ making it faster to debug.
	  https://bugzilla.gnome.org/show_bug.cgi?id=688188

2013-05-08 18:19:48 -0400  Nicolas Dufresne <nicolas.dufresne@collabora.co.uk>

	* gst/gstpad.c:
	  pad: Only inforce STREAM_START, CAPS and SEGMENT ordering
	  Previous patch was inforcing a complete ordering of the sticky events, while
	  in fact, only STREAM_START, CAPS and SEGMENT events need proper ordering.
	  See: https://bugzilla.gnome.org/show_bug.cgi?id=688188

2013-05-09 09:32:49 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gstcapsfilter.c:
	* plugins/elements/gstcapsfilter.h:
	  capsfilter: Send all events that should happen after CAPS after the CAPS event

2013-05-08 21:45:08 -0400  Nicolas Dufresne <nicolas.dufresne@collabora.co.uk>

	* plugins/elements/gstcapsfilter.c:
	* plugins/elements/gstcapsfilter.h:
	  capsfilter: Send caps before segment
	  In the case the source has no caps, caps must be sent before segment. This
	  fixes few unit tests that where failing due to the new misordering warning.
	  https://bugzilla.gnome.org/show_bug.cgi?id=699968

2013-05-07 21:53:37 -0400  Nicolas Dufresne <nicolas.dufresne@collabora.co.uk>

	* gst/gstpad.c:
	  pad: Detect, fix and warn when sticky events are in wrong order
	  We can prevent buggy element from causing other elements to fail or crash
	  by sorting sticky event at insertion. In this case, we also warn as this
	  is not supposed to happen.
	  See: https://bugzilla.gnome.org/show_bug.cgi?id=688188

2013-05-08 10:26:15 +0100  Tim-Philipp Müller <tim@centricular.net>

	* tests/check/gst/gstbuffer.c:
	  tests: add some basic checks for gst_buffer_fill()

2013-05-08 10:25:36 +0100  Tim-Philipp Müller <tim@centricular.net>

	* gst/gstbuffer.c:
	  buffer: allow calling _fill() with a NULL data pointer if size is 0 bytes

2013-05-07 16:46:32 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* libs/gst/base/gstbasesrc.c:
	  basesrc: Add FIXME comment for unused assignment results

2013-05-07 15:18:06 +0100  Tim-Philipp Müller <tim@centricular.net>

	* docs/manual/advanced-metadata.xml:
	  docs: fix typo in metadata section in app dev manual
	  There's no g_tag_list_get_xyz().

2013-05-07 14:47:09 +0300  Sreerenj Balachandran <sreerenj.balachandran@intel.com>

	* libs/gst/controller/gsttimedvaluecontrolsource.c:
	  controller: Fix the function signature and a minor typo fix
	  https://bugzilla.gnome.org/show_bug.cgi?id=699827

2013-05-06 18:47:44 -0400  Nicolas Dufresne <nicolas.dufresne@collabora.com>

	* plugins/elements/gsttypefindelement.c:
	  typefind: Send stream-start before anything else
	  To do so, send stream-start when the streaming thread goes up for the first
	  time.
	  https://bugzilla.gnome.org/show_bug.cgi?id=699767

2012-12-26 11:54:51 +0000  David Rothlisberger <david@rothlis.net>

	* tools/gstreamer-completion:
	  tools/gstreamer-completion: Allow 1.0 and 0.10 scripts installed simultaneously
	  As long as the scripts' filenames are different, and the _gst_inspect
	  and _gst_launch functions are named differently, the completion scripts
	  for GStreamer 1.0 and 0.10 can be installed side-by-side in
	  /etc/bash_completion.d.
	  On my 0.10 branch† the completion script is renamed to
	  "gstreamer-completion-0.10" and the functions are renamed to
	  "_gst_inspect_0_10" and "_gst_launch_0_10". The remaining helper
	  functions should remain identical (the command-line interface to
	  gst-inspect hasn't changed, nor has the format of the gst-launch
	  pipeline), so it doesn't matter if the 1.0 script overrides the 0.10
	  script's definitions.
	  Note that I don't expect there to be another GStreamer 0.10 release, so
	  the 0.10 completion script will probably never be officially released;
	  but it is still worthwhile allowing both scripts to be installed
	  alongside each other, for those who install the 0.10 completion script
	  manually.
	  Fixes: #690515
	  † https://github.com/drothlis/gstreamer/blob/bash-completion-0.10/tools/gstreamer-completion-0.10

2012-12-21 18:13:53 +0000  David Rothlisberger <david@rothlis.net>

	* tests/misc/test-gstreamer-completion.sh:
	* tools/gstreamer-completion:
	  tools/gstreamer-completion: Complete option & property values on bash 3.2
	  Bash 3's completion doesn't split words by characters in
	  COMP_WORDBREAKS. In particular it doesn't split at "=" signs. Now
	  _gst_launch_parse handles both bash 3 and 4 format of COMP_WORDS.
	  Note that "${cur%%=*}" means cur's value with the longest possible match
	  of "=*" deleted from the end; "${cur#*=}" means cur's value with the
	  shortest possible match of "*=" deleted from the beginning. See
	  http://www.gnu.org/software/bash/manual/html_node/Shell-Parameter-Expansion.html
	  Regardless of the version of bash running the unit tests, I can test for
	  both behaviours because the unit test populates COMP_WORDS manually. So
	  this tests the bash 3 behaviour:
	  test_gst_inspect_completion --gst-debug-level=4
	  and this tests the bash 4 behaviour:
	  test_gst_inspect_completion --gst-debug-level = 4

2012-12-21 08:56:26 +0000  David Rothlisberger <david@rothlis.net>

	* tests/misc/test-gstreamer-completion.sh:
	* tools/gstreamer-completion:
	  tools/gstreamer-completion: Bash 3.2 compatibility fixes
	  Compatible with bash 3.2; doesn't require the bash-completion package at
	  all (though the easiest way to install this script is still to install
	  bash-completion, and then drop this script into /etc/bash_completion.d).
	  Note that bash 3 doesn't break COMP_WORDS according to characters in
	  COMP_WORDBREAKS, so "property=val" looks like a single word, so this
	  won't complete property values (on bash 3). Similarly,
	  "--gst-debug-level=<TAB>" won't complete properly (on bash 3), but
	  "--gst-debug-level <TAB>" will.
	  For that reason, I now offer "--gst-debug-level" etc as completions
	  instead of "--gst-debug-level=".
	  Functions "_init_completion" and "_parse_help" were provided by the
	  bash-completion package >= 2.0; now I roll my own equivalent of
	  "_parse_help", and instead of "_init_completion" I use
	  "_get_comp_words_by_ref" which is available from bash-completion 1.2
	  onwards. If the bash-completion package isn't available at all I use
	  bash's raw facilities, at the expense of not completing properly when
	  the cursor is in the middle of a word.
	  The builtin "compopt" doesn't exist in bash 3; those users will just
	  have to live with the inconvenience of "property=" completing to
	  "property= " with a trailing space. Property values aren't completed
	  properly anyway on bash 3 (see above).
	  "[[ -v var ]]" to test whether a variable is set, also doesn't exist in
	  bash 3. Neither does ";;&" to fall through in a "case" statement.
	  In the unit tests:
	  * On my system (OS X), "#!/bin/bash" is bash 3.2, whereas
	  "#!/usr/bin/env bash" is the 4.2 version I built myself.
	  * I have to initialise array variables like "expected=()", or bash 3
	  treats "+=" as appending to an array already populated with one empty
	  string.

2012-12-19 10:46:50 +0000  David Rothlisberger <david@rothlis.net>

	  tools/gstreamer-completion: Support gst-inspect, and gst-launch element properties
	  Completes options like "--gst-debug-level" and the values of some of
	  those options; completes gst-launch pipeline element names, property
	  names, and even property values (for enum or boolean properties only).
	  Doesn't complete all caps specifications, nor element names specified
	  earlier in the pipeline with "name=...".
	  The GStreamer version number is hard-coded into the completion script:
	  This patch is off the master branch and has the version hard-coded as
	  "1.0"; it needs to be updated if backported to the 0.10 branch. You
	  could always create a "gstreamer-completion.in" that has the appropriate
	  version inserted by "configure", but I'd rather not do that. The
	  hard-coded version is consistent with the previous implementation of
	  gstreamer-completion, which had the registry path hard-coded as
	  ~/.gstreamer-1.0/registry.xml.
	  Note that GStreamer 0.10 installs "gst-inspect" and "gst-inspect-0.10".
	  "gst-inspect --help" only prints 4 flags (--help, --print, --gst-mm,
	  gst-list-mm) whereas "gst-inspect-0.10 --help-all" prints the full list
	  of flags. The same applies to "gst-launch" and "gst-launch-0.10".
	  GStreamer 1.0 only installs "gst-inspect-1.0", not "gst-inspect".
	  Requires bash 4; only tested with bash 4.2. Requires "bash-completion"
	  (which you install with your system's package manager).
	  Put this in /etc/bash_completion.d/ or in `pkg-config
	  --variable=compatdir bash-completion`, where it will be loaded at the
	  beginning of every new terminal session;
	  or in `pgk-config --variable=completionsdir bash-completion`, renamed to
	  match the name of the command it completes (e.g. "gst-launch-1.0", with
	  an additional symlink named "gst-inspect-1.0"), where it will be
	  autoloaded when needed.
	  test-gstreamer-completion.sh is (for now) in tests/misc -- it might be
	  worth creating "tests/check/tools", with all the necessary automake
	  boilerplate, and moving test-gstreamer-completion.sh there, and have it
	  run automatically with "make check".
	  IF YOU'RE NEW TO BASH COMPLETION SCRIPTS
	  ----------------------------------------
	  "complete -F _gst_launch gst-launch-1.0" means that bash will run the
	  function "_gst_launch" to generate possible completions for the command
	  "gst-launch-1.0".
	  "_gst_launch" must return the possible completions in the array variable
	  COMPREPLY. (Note on bash syntax: "V=(a b c)" assigns three elements to
	  the array "V").
	  "compgen" prints a list of possible completions to standard output. Try
	  it:
	  compgen -W "abc1 abc2 def" -- "a"
	  compgen -f -- "/"
	  The last argument is the word currently being completed; compgen uses it
	  to filter out the non-matching completions. We put "--" first, in case
	  the word currently being completed starts with "-" or "--", so that it
	  isn't treated as a flag to compgen.
	  For the documentation of COMP_WORDS, COMP_CWORD, etc see
	  http://www.gnu.org/software/bash/manual/html_node/Bash-Variables.html#index-COMP_005fCWORD-180
	  See also:
	  * http://www.gnu.org/software/bash/manual/html_node/Programmable-Completion.html
	  * http://www.gnu.org/software/bash/manual/html_node/Programmable-Completion-Builtins.html
	  The bash-completion package provides the helper function
	  "_init_completion" which populates variables "cur", "prev", and "words".
	  See
	  http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git;a=blob;f=bash_completion;h=870811b4;hb=HEAD#l634
	  Note that by default, bash appends a space to the completed word. When
	  the completion is "property=" we don't want a trailing space; calling
	  "compopt -o nospace" modifies the currently-executing completion
	  accordingly. See
	  http://www.gnu.org/software/bash/manual/html_node/Programmable-Completion-Builtins.html#index-compopt

2012-11-13 16:36:46 +0000  David Rothlisberger <david@rothlis.net>

	* tools/gstreamer-completion:
	  tools/gstreamer-completion: Updated to work with the binary registry
	  The original registry was in xml format (~/.gstreamer-*/registry.xml). A
	  binary registry format was added in 2007 (commit ebf0c9d3) and made the
	  default in 2008 (commit 3f39fd7e). In 0.10 you could still choose at
	  "configure" time to use the xml registry instead; in 1.0 the binary
	  registry is your only choice.
	  This change to gstreamer-completion should work with either format
	  because it parses the output of "gst-inspect" instead of reading the
	  registry file directly.
	  Note that _gst_launch no longer needs an explicit "return 0" because,
	  unlike the previous grep command, compgen always returns 0 (unless a
	  genuine error occurs).
	  Just like the previous implementation by David Schleef, this "only
	  completes names of features, but that's 90% of what I want it for."

2013-04-29 21:11:36 +0200  Stefan Sauer <ensonic@users.sf.net>

	* docs/random/porting-to-1.0.txt:
	  porting-to-1.0.txt: nit clarification
	  It is the process context that matters.

2013-04-29 13:20:11 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gsttypefindelement.c:
	  typefind: Always leave TYPEFIND mode when we're stopping typefinding

2013-04-29 13:03:24 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gsttypefindelement.c:
	  typefind: Simplify code
	  This is only called when in TYPEFIND mode.

2013-04-29 12:58:07 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gsttypefindelement.c:
	  typefind: Push pending events independent of the existence of a downstream chain function and peer
	  Downstream might create a peer only as result of the events in theory.

2013-04-29 12:56:54 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gsttypefindelement.c:
	  typefind: Only push CAPS event once if we get one from upstream
	  https://bugzilla.gnome.org/show_bug.cgi?id=692784

2013-04-29 12:54:27 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gsttypefindelement.c:
	  typefind: Stop typefinding if we get a CAPS event from upstream

2013-04-29 12:52:46 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gsttypefindelement.c:
	  typefind: Improve handling of GAP events
	  There's still room for improvement though.

2013-04-29 12:48:29 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gsttypefindelement.c:
	  typefind: Forward events that should happen before the caps event directly
	  There's no point in storing them and sending them later, and doing so would
	  later require to distinguish between events that should come before caps and
	  after.
	  https://bugzilla.gnome.org/show_bug.cgi?id=692784

2013-04-29 12:48:13 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>

	* plugins/elements/gsttypefindelement.c:
	  typefind: Only push pending buffers and events if we have caps

2013-04-29 12:39:20 +0200  Sebastian Dröge <sebastian.droege@collabora.co.uk>