ChangeLog 973 KB
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
=== release 1.10.0 ===

2016-11-01  Sebastian Dröge <slomo@coaxion.net>

	* configure.ac:
	  releasing 1.10.0

2016-10-27 17:13:48 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecodebin.c:
	  vaapidecodebin: resurrect disable-vpp property
	  https://bugzilla.gnome.org/show_bug.cgi?id=773589

2016-10-27 16:32:23 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecodebin.c:
	  vaapidecodebin: name the internal queue
	  https://bugzilla.gnome.org/show_bug.cgi?id=773589

2016-10-27 16:27:45 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecodebin.c:
	* gst/vaapi/gstvaapidecodebin.h:
	  vaapidecodebin: remove unused variables
	  Since vaapipostproc is only registered if the driver supports it, all the
	  support for dynamic loading were removed. Though some leftovers remained.
	  https://bugzilla.gnome.org/show_bug.cgi?id=773589

2016-10-27 12:53:54 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* docs/plugins/Makefile.am:
	* docs/plugins/gstreamer-vaapi-plugins-docs.xml.in:
	* docs/plugins/running.xml:
	  docs: document environment variables
	  https://bugzilla.gnome.org/show_bug.cgi?id=773544

2016-10-27 12:31:49 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* docs/plugins/gstreamer-vaapi-plugins-docs.xml.in:
	* docs/plugins/gstreamer-vaapi-plugins-sections.txt:
	* gst/vaapi/Makefile.am:
	* gst/vaapi/gstvaapidecode.c:
	* gst/vaapi/gstvaapidecodebin.c:
	* gst/vaapi/gstvaapidecodedoc.c:
	  docs: replace vaapidecode with each codec
	  In the spirit of the codec split, this patch removes the documentation of
	  vaapidecode and adds a page per each possible decoder.
	  Nonetheless, only those available in the compilation system are going to be
	  instrospected, because the rest are not registered.

2016-10-27 11:06:06 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginutil.c:
	* gst/vaapi/gstvaapivideobuffer.c:
	* gst/vaapi/gstvaapivideometa.c:
	  docs: add missing long descriptions

2016-10-25 14:32:44 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipostproc.c:
	  vaapipostproc: use GST_*_OBJECT when possible
	  Since we can have several vaapipostproc operating in a pipeline, it is useful
	  to know which one is generating the logging message.
	  https://bugzilla.gnome.org/show_bug.cgi?id=773497

2016-07-19 17:00:23 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecode.c:
	* gst/vaapi/gstvaapidecode.h:
	  vaapidecode: rename member to allowed_sinkpad_caps
	  vaapidecode has a member named allowed_caps, but this name is not enough
	  explicit. This patch renames allowed_caps to allowed_sinkpad_caps.
	  No functional changes were included.
	  https://bugzilla.gnome.org/show_bug.cgi?id=773497

2016-10-20 18:12:04 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapiencode_h264.c:
	* gst/vaapi/gstvaapiencode_h265.c:
	* gst/vaapi/gstvaapisink.c:
	* gst/vaapi/gstvaapivideomemory.c:
	* gst/vaapi/gstvaapivideometa.c:
	* gst/vaapi/gstvaapivideometa_texture.c:
	  plugins: fix code style for errors
	  https://bugzilla.gnome.org/show_bug.cgi?id=773497

2016-10-20 17:01:57 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapivideomemory.c:
	  vaapivideomemory: comment style
	  https://bugzilla.gnome.org/show_bug.cgi?id=773497

2016-10-20 11:19:50 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapivideomemory.c:
	* gst/vaapi/gstvaapivideomemory.h:
	  vaapivideomemory: rename input parameter
	  In order to clarify the use of flag as input parameter, it is renamed to
	  surface_alloc_flag, since it is used when creating a VA surface with certain
	  properties.
	  https://bugzilla.gnome.org/show_bug.cgi?id=773497

2016-10-25 19:22:03 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecode.c:
	  vaapidecode: rename element description
	  So encoders and decoders have similar descriptions.
	  https://bugzilla.gnome.org/show_bug.cgi?id=773497

2016-08-02 11:32:19 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapiencode_h264.c:
	* gst/vaapi/gstvaapiencode_h265.c:
	  vaapiencode: h264, h265: rename codec name
	  So encoder and decoders have the same codec name.
	  https://bugzilla.gnome.org/show_bug.cgi?id=773497

2016-07-29 15:17:33 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginbase.c:
	  plugins: simplify code
	  Merge two lines of variable declarations.
	  https://bugzilla.gnome.org/show_bug.cgi?id=773497

2016-10-07 18:46:22 +0900  Hyunjun Ko <zzoon@igalia.com>

	* gst-libs/gst/vaapi/gstvaapidecoder.c:
	* gst-libs/gst/vaapi/gstvaapipixmap_priv.h:
	* gst-libs/gst/vaapi/gstvaapitexture_priv.h:
	* gst-libs/gst/vaapi/gstvaapiwindow_priv.h:
	  libs: minor correction for logical consistency
	  GstVaapiDecode is a descendant of GstVaapiMiniObject, so, thought we should
	  use its methods, even though it doesn't change functionality.
	  GstVaapiPixmap, GstVaapiTexture and GstVaapiWindow are descendant of
	  GstVaapiObject, hence its methods shall be used.
	  https://bugzilla.gnome.org/show_bug.cgi?id=772554

2016-10-19 15:39:54 +0100  Julien Isorce <j.isorce@samsung.com>

	* gst/vaapi/gstvaapivideomemory.c:
	  vaapivideomemory: add explanation about the call 'dup (dmabuf_fd)'
	  In short GstFdMemory is configured to call close when using
	  GstDmabufMemory.
	  https://bugzilla.gnome.org/show_bug.cgi?id=755072

2016-09-02 16:42:45 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* configure.ac:
	* gst-libs/gst/vaapi/Makefile.am:
	  build: clean up the dlopen usage

2016-10-08 14:33:59 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapiencoder_h264.c:
	* gst-libs/gst/vaapi/gstvaapiencoder_h265.c:
	  encoder: h264,h265: fix regression in offset count
	  In commit dc35dafa a bug was introduced because I assumed that
	  GST_CLOCK_TIME_NONE is zero when is -1. This patch fixes that mistake.
	  https://bugzilla.gnome.org/show_bug.cgi?id=772259

2016-10-18 17:02:59 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* README:
	  docs: update README

2016-09-27 17:29:25 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapidisplay_egl.c:
	  libs: display: egl: remove unused header include
	  The header gmodule.h is not used since the library dynamic loading for EGL
	  display was removed.
	  https://bugzilla.gnome.org/show_bug.cgi?id=772599

Sebastian Dröge's avatar
Sebastian Dröge committed
174
175
=== release 1.9.90 ===

Sebastian Dröge's avatar
Sebastian Dröge committed
176
2016-09-30 13:05:20 +0300  Sebastian Dröge <sebastian@centricular.com>
Sebastian Dröge's avatar
Sebastian Dröge committed
177

Sebastian Dröge's avatar
Sebastian Dröge committed
178
179
180
	* ChangeLog:
	* NEWS:
	* common:
Sebastian Dröge's avatar
Sebastian Dröge committed
181
	* configure.ac:
Sebastian Dröge's avatar
Sebastian Dröge committed
182
183
	* gstreamer-vaapi.doap:
	  Release 1.9.90
Sebastian Dröge's avatar
Sebastian Dröge committed
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
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
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

2016-03-04 16:35:11 +0900  Vineeth TM <vineeth.tm@samsung.com>

	* gst/vaapi/gstvaapidecode.c:
	* gst/vaapi/gstvaapidecodebin.c:
	* gst/vaapi/gstvaapiencode_h264.c:
	* gst/vaapi/gstvaapiencode_h265.c:
	* gst/vaapi/gstvaapiencode_jpeg.c:
	* gst/vaapi/gstvaapiencode_mpeg2.c:
	* gst/vaapi/gstvaapiencode_vp8.c:
	* gst/vaapi/gstvaapipostproc.c:
	* gst/vaapi/gstvaapisink.c:
	  vaapi: use new gst_element_class_add_static_pad_template()
	  https://bugzilla.gnome.org/show_bug.cgi?id=763083
	  Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

2016-09-22 16:34:48 +0900  Hyunjun Ko <zzoon@igalia.com>

	* gst/vaapi/gstvaapipluginbase.c:
	  plugins: reset textures at negotiation/shutdown
	  When caps reconfiguration is called, the new downstream frame size might be
	  different. Thus, if the downstream caps change,the display's texture map is
	  reset.
	  In addition, during pipeline shutdown, textures in texture map have to be
	  released, since each one have a reference to the GstVaapiDisplay object, which
	  is a dangerous circular reference.
	  https://bugzilla.gnome.org/show_bug.cgi?id=769293
	  Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

2016-09-22 16:34:38 +0900  Hyunjun Ko <zzoon@igalia.com>

	* gst-libs/gst/vaapi/gstvaapidisplay.c:
	* gst-libs/gst/vaapi/gstvaapidisplay.h:
	* gst-libs/gst/vaapi/gstvaapidisplay_egl.c:
	* gst-libs/gst/vaapi/gstvaapidisplay_egl_priv.h:
	* gst-libs/gst/vaapi/gstvaapidisplay_glx.c:
	* gst-libs/gst/vaapi/gstvaapidisplay_glx_priv.h:
	* gst-libs/gst/vaapi/gstvaapidisplay_priv.h:
	* gst/vaapi/gstvaapivideometa_texture.c:
	  libs: display{egl,glx}: cache GstVaapiTextures
	  instances when created and reuse
	  This patch improves performance when glimagesink uploads a GL texture.
	  It caches the GStVaapiTexture instances in GstVaapiDisplay{GLX,EGL}, using an
	  instance of GstVaapiTextureMap, so our internal texture structure can be found
	  by matching the GL texture id for each frame upload process, avoiding the
	  internal texture structure creation and its following destruction.
	  https://bugzilla.gnome.org/show_bug.cgi?id=769293
	  Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

2016-09-22 16:33:06 +0900  Hyunjun Ko <zzoon@igalia.com>

	* gst-libs/gst/vaapi/Makefile.am:
	* gst-libs/gst/vaapi/gstvaapitexturemap.c:
	* gst-libs/gst/vaapi/gstvaapitexturemap.h:
	  libs: vaapitexturemap: implement GstVaapiTextureMap
	  Implement GstVaapiTextureMap object, which caches VAAPI textures, so them can be
	  reused. Internally it is a hash table.
	  Note that it is GstObject based rather than GstVaapiObject, as part of the future
	  converstion to GstObject of most of the code.
	  https://bugzilla.gnome.org/show_bug.cgi?id=769293
	  Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

2016-09-21 09:55:53 +0300  Sreerenj Balachandran <sreerenj.balachandran@intel.com>

	* gst-libs/gst/vaapi/gstvaapiencoder_vp8.c:
	  encoder: vp8: Increase the allocation size for coded buffer
	  We are not getting enough compression for some streams and
	  encoded frame end up with more size than allocated.
	  Assuming a compression ratio of 4, which should be good enough
	  for holding the frames.
	  https://bugzilla.gnome.org/show_bug.cgi?id=771528

2016-09-21 09:52:21 +0300  Sreerenj Balachandran <sreerenj.balachandran@intel.com>

	* gst-libs/gst/vaapi/gstvaapiencoder_vp9.c:
	  encoder: vp9: Fix refresh frame flag setting
	  While doing the mode-1 referece picture selection,
	  the circular buffer logic was not correctly setting the
	  refresh frame flags as per VP9 spec.
	  Make sure refresh_flag[0] get updated correclty after
	  each cycle of GST_VP9_REF_FRAMES.
	  https://bugzilla.gnome.org/show_bug.cgi?id=771507

2016-09-14 18:42:09 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapidecoder_h264.c:
	  vaapidecode: codec_data minimal size is 7
	  When the format of a H.264 stream is AVC3, the SPS and PPS are inside the
	  stream, not in the codec_data, so the size of codec_data might be 7.
	  This patch reduces the minimal size of the codec_data buffer from 8 to 7.
	  https://bugzilla.gnome.org/show_bug.cgi?id=771441

2016-09-14 16:29:01 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecode.c:
	  vaapidecode: reset decoder hard when set_format()
	  set_format() is called by upstream when the stream capabilites has changed.
	  Before, if the new stream is compatible with the old one the VA decoder was
	  not destroyed. Nonetheless, with this behavoir, the VA decoder ignores
	  when the upstreamer parsers gets more details of the stream, such as the
	  framerate. Hence, when the src caps are negotiates, the further sink caps
	  updates are ignored.
	  This patch forces the VA decoder destroying and recreation when set_format()
	  is called.
	  https://bugzilla.gnome.org/show_bug.cgi?id=770921

2016-09-14 11:31:39 +0200  Sebastian Dröge <sebastian@centricular.com>

	* configure.ac:
	  configure: Depend on gstreamer 1.9.2.1

2016-09-09 12:03:37 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapivideomemory.c:
	  Revert "vaapivideomemory: load VA Image when mapping to write"
	  This reverts commit c67edea4aba35f16d9e97c78a0b49ad1b590b112.

2016-09-10 20:52:21 +1000  Jan Schmidt <jan@centricular.com>

	* common:
	  Automatic update of common submodule
	  From b18d820 to f980fd9

2016-09-10 09:58:25 +1000  Jan Schmidt <jan@centricular.com>

	* common:
	  Automatic update of common submodule
	  From f49c55e to b18d820

2016-09-08 16:16:09 +0900  Hyunjun Ko <zzoon@igalia.com>

	* gst/vaapi/gstvaapipluginbase.c:
	  plugins: set allocator's image size to sinkpad bufferpool
	  Otherwise the buffer is always ditched by the bufferpool, losing performance.
	  https://bugzilla.gnome.org/show_bug.cgi?id=771035

2016-09-07 17:34:08 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapisurface.c:
	  libs: surface: ensure composite overlay is not bigger
	  Ensure the composition overlay rectangle (subtitles) is not bigger than
	  the surface where it is going to be composited and rendered.
	  https://bugzilla.gnome.org/show_bug.cgi?id=766978

2016-09-07 17:51:23 +0900  Hyunjun Ko <zzoon@igalia.com>

	* gst/vaapi/gstvaapivideomemory.c:
	  vaapivideomemory: load VA Image when mapping to write
	  When calling gst_video_frame_map() with GST_MAP_WRITE flag, it doesn't call
	  ensure_image_is_current(), which means it doesn't guarentee VAImage is valid
	  in this case.
	  https://bugzilla.gnome.org/show_bug.cgi?id=766978

2016-09-06 12:27:45 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecode.c:
	  vaapidecode: merge vc1 and wmv3 elements
	  This patch merges vaapivc1dec and vaapiwmv3dec into a single
	  vaapivc1dec. Also, removed the WMVA format, since it is not
	  supported by libva.
	  https://bugzilla.gnome.org/show_bug.cgi?id=734093

2016-09-06 11:19:05 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapidecoder_vc1.c:
	  decoder: vc1: fails only on advanced profile
	  In commit 2eb4394 the frame coding mode was verified for progressive
	  regardless the profile. But the FCM is only valid in the advanced
	  profile. This patch checks for the advanced profile before verifying FCM for
	  progressive.
	  https://bugzilla.gnome.org/show_bug.cgi?id=769250

2016-09-01 12:39:15 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapi.c:
	  vaapi: DISPLAY envvar as dependency
	  In a multiple video cards system, a X11 environment may have different VA
	  capabilities. This patch tracks the DISPLAY environment variable to
	  invalidates the GStreamer features cache. Also tracks WAYLAND_DISPLAY.
	  https://bugzilla.gnome.org/show_bug.cgi?id=770357

2016-08-26 14:55:17 -0700  Scott D Phillips <scott.d.phillips@intel.com>

	* gst-libs/gst/vaapi/gstvaapidecoder_vc1.c:
	  decoder: vc1: Fail only on actual interlaced frames
	  In the earlier patch:
	  f31d9f3 decoder: vc1: Print error on interlaced content
	  Decoding would error out if the interlace flag was set in the
	  sequence bdu. This isn't quite right because a video can have this
	  flag set and yet not have any interlaced pictures.
	  Here instead we error out when either parsing a field bdu or
	  decoding a frame bdu which has fcm set to anything other than
	  progressive.
	  Signed-off-by: Scott D Phillips <scott.d.phillips@intel.com>
	  https://bugzilla.gnome.org/show_bug.cgi?id=769250

2016-09-01 12:34:48 +0300  Sebastian Dröge <sebastian@centricular.com>

	* configure.ac:
	  Back to development

Sebastian Dröge's avatar
Sebastian Dröge committed
385
386
=== release 1.9.2 ===

Sebastian Dröge's avatar
Sebastian Dröge committed
387
2016-09-01 12:34:38 +0300  Sebastian Dröge <sebastian@centricular.com>
Sebastian Dröge's avatar
Sebastian Dröge committed
388

Sebastian Dröge's avatar
Sebastian Dröge committed
389
390
	* ChangeLog:
	* NEWS:
Sebastian Dröge's avatar
Sebastian Dröge committed
391
	* configure.ac:
Sebastian Dröge's avatar
Sebastian Dröge committed
392
393
	* gstreamer-vaapi.doap:
	  Release 1.9.2
Sebastian Dröge's avatar
Sebastian Dröge committed
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

2016-08-16 11:58:38 +0300  Scott D Phillips <scott.d.phillips@intel.com>

	* gst-libs/gst/vaapi/gstvaapidecoder_vc1.c:
	  decoder: vc1: Print error on interlaced content
	  Interlaced video is as yet unsupported in the vc1 element. Print
	  an error to make that more obvious.
	  https://bugzilla.gnome.org/show_bug.cgi?id=769250

2016-08-10 13:29:45 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapiencoder_h264.c:
	  encoder: h264: fix C90 mixed declarations and code
	  Commit 4259d1a introduced this compilation error. This patch fixes it.

2016-07-21 17:38:40 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapiencoder_h264.c:
	* gst-libs/gst/vaapi/gstvaapiencoder_h265.c:
	* gst-libs/gst/vaapi/gstvaapiencoder_mpeg2.c:
	* gst-libs/gst/vaapi/gstvaapiencoder_vp8.c:
	  encoder: h264,h265,mpeg2,vp8: use gst_util_uint64_scale() for bitrate
	  Use gst_util_uint64_scale() to calculate bitrate instead of normal arithmetic
	  to avoid overflows, underflows and loss of precision.
	  https://bugzilla.gnome.org/show_bug.cgi?id=768458

2016-07-05 20:07:15 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapiencoder_h264.c:
	* gst-libs/gst/vaapi/gstvaapiencoder_h265.c:
	  vaapiencode: h264,h265: validate fps numerator
	  Validate that fps numerator is non-zero so it can be used to calculate
	  the duration of the B frame.
	  Also it gst_util_uint64_scale() is used instead of normal arithmetic in
	  order to aviod overflows, underflows and loss of precision.
	  https://bugzilla.gnome.org/show_bug.cgi?id=768458

2016-08-06 12:54:17 +0100  Tim-Philipp Müller <tim@centricular.com>

	* gst/vaapi/gstvaapi.c:
	  encoders: demote to RANK_NONE since not fit for autoplugging yet
	  Encoders claim to support a whole bunch of input formats but then
	  just error out if the format is not actually supported, even if
	  there's a converter in front. This means they're not fit for
	  autoplugging in encodebin or camerabin yet and therefore should
	  not have a rank. People can still use them in custom pipelines.
	  https://bugzilla.gnome.org/show_bug.cgi?id=769266

2016-07-19 19:24:08 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginbase.c:
	  plugins: check dmabuf-import for sink pad allocator
	  Check earlier if upstream video source has activated the dmabuf-import
	  io-mode (hack to disappear soon), thus we can avoid the re-assignation of a
	  new allocator.

2016-07-19 20:02:54 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginbase.c:
	  plugins: reset allocators if video info changed
	  If the frame size or format, change, the allocators are reset, so a new ones
	  can be created with the new video info.

2016-07-19 19:27:27 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginbase.c:
	  plugins: remove sink pad allocator if caps change
	  If the negotiated sinkpad caps change, destroy the assignated allocator,
	  because it is not valid anymore.

2016-07-19 20:01:05 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginutil.c:
	* gst/vaapi/gstvaapipluginutil.h:
	  pluginutil: const params to gst_video_info_changed()
	  Since they are not modified, we should mark them as const.

2016-07-29 15:13:29 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginbase.c:
	* gst/vaapi/gstvaapivideomemory.c:
	* gst/vaapi/gstvaapivideomemory.h:
	  gstvaapivideomemory: allocator's image size getter
	  Add the method gst_allocator_get_vaapi_image_size() for the
	  GstVaapiVideoAllocator, which gets the size of the allocated images with the
	  current video info.
	  This method replaces the direct call to the allocator's image info when the
	  pool is configured.

2016-07-29 18:06:30 +0900  Hyunjun Ko <zzoon@igalia.com>

	* gst/vaapi/gstvaapipluginbase.c:
	  plugins: update buffer pool size with new allocator's image size
	  Depends on media, video size is sometimes updated with new allocator.
	  It leads to dismatch between bufferpool's set size and real allocated buffer size.
	  In this case, it causes every buffer is freed during release in bufferpool,
	  which should be reused. This affects performance.
	  https://bugzilla.gnome.org/show_bug.cgi?id=769248

2016-07-27 19:49:59 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* configure.ac:
	  configure: remove gmodule-2.0 EGL dependency
	  Since commit 27429ce, EGL support doesn't depend on dynamic loading libraries,
	  thus the dependency to gmodule-2.0 is not mandatory anymore.

2016-07-27 10:09:38 -0700  Scott D Phillips <scott.d.phillips@intel.com>

	* configure.ac:
	  configure: Fix non-fatal PKG_CHECK_MODULES invocations
	  Some invocations of PKG_CHECK_MODULES were intended to be non-fatal if
	  the package is missing, but action-if-not-found was given as an empty
	  string which still causes the default action to run, which halts
	  execution.
	  Signed-off-by: Scott D Phillips <scott.d.phillips@intel.com>
	  https://bugzilla.gnome.org/show_bug.cgi?id=769237

2016-07-13 18:34:57 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapidisplay_egl.c:
	  libs: egl: remove dynamic library loading code
	  Since the upstream of gstreamer-vaapi, the library is not a public shared
	  object anymore. But the EGL support depended on this dynamic library, so the
	  EGL support was broken.
	  This patch removes the dynamic library loading code and instantiates the
	  EGL display using either X11 or Wayland if available.
	  https://bugzilla.gnome.org/show_bug.cgi?id=767203

2016-07-12 23:47:41 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapi.c:
	* gst/vaapi/gstvaapidecode.c:
	* gst/vaapi/gstvaapidecode.h:
	  vaapidecode: register only the available decoders
	  In order to register only the available decoders, this patch queries the
	  created test VA display, which uses the currently used back-end (X11, Wayland,
	  DRM, …) on the used display device.
	  https://bugzilla.gnome.org/show_bug.cgi?id=724352

2016-06-28 11:43:15 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapi.c:
	* gst/vaapi/gstvaapipluginutil.c:
	* gst/vaapi/gstvaapipluginutil.h:
	  vaapi: register only the available encoders
	  In order to register only the available encoders, this patch queries the
	  created test VA display, which uses the currently used back-end (X11,
	  Wayland, DRM, …) on the used display device.
	  https://bugzilla.gnome.org/show_bug.cgi?id=724352

2016-06-07 16:28:07 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecode.c:
	* gst/vaapi/gstvaapidecodebin.c:
	  vaapidecode: split all the codecs
	  Split the vaapidecode to all the supported codecs with the format
	  vaapi{codec}dec.
	  vaapidecode is stil registered as a GObject type, but not as a
	  GStreamer feature, so it can be used internally by vaapidecodebin without
	  changing its code too much.
	  https://bugzilla.gnome.org/show_bug.cgi?id=734093

2016-07-12 22:19:37 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecodebin.c:
	  vaapidecodebin: simplify the code
	  Since the elements dependant of the VA video processor are now only registered
	  if it is available, vaapidecodebin code can be simplified a lot, removing all
	  the code required to check if the VA video processor was available.
	  https://bugzilla.gnome.org/show_bug.cgi?id=768899

2016-07-12 17:54:26 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecode.c:
	  vaapidecode: delay the GstVaapiDisplay instantiating
	  Delay the GstVaapiDisplay instantiating until when changing the state from
	  READY to PAUSE. In this way the element has more chances to find an already
	  created GstVaapiDisplay, or a GL context, in the pipeline.
	  https://bugzilla.gnome.org/show_bug.cgi?id=766206

2016-07-12 17:49:50 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginutil.c:
	  pluginutil: set GLX display type
	  The function gst_vaapi_create_display_from_gl_context() cretes a
	  GstVaapiDisplay given a GstGLContext. But it didn't created a GLX VA display
	  when the GL platform was GLX, but a plain X11 VA display.
	  This patch fixes that, by querying the GL platform earlier.
	  https://bugzilla.gnome.org/show_bug.cgi?id=766206

2016-06-02 19:57:08 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginbase.c:
	* gst/vaapi/gstvaapivideocontext.c:
	* gst/vaapi/gstvaapivideocontext.h:
	  plugins: add gst_vaapi_plugin_base_find_gl_context()
	  Using the GstContext mechanism, it is possible to find if the pipeline
	  shares a GstGLContext, even if we are not to negotiating GLTextureUpload
	  meta. This is interesting because we could negotiate system memory caps
	  feature, but enable DMABuf if the GstGLContext is EGL with some extensions.
	  https://bugzilla.gnome.org/show_bug.cgi?id=766206

2016-06-28 17:14:06 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginbase.c:
	* gst/vaapi/gstvaapipluginbase.h:
	  plugins: remove gst_vaapi_plugin_base_driver_is_whitelisted()
	  Since nobody is calling gst_vaapi_plugin_base_driver_is_whitelisted(),
	  it is deleted.

2016-07-12 18:24:10 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginbase.h:
	  plugins: remove common change_state() vmethod
	  Remove the common change_state() vmethod for all the plugins, since no one is
	  using it.

2016-07-12 20:38:07 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecode.c:
	  vaapidecode: remove change_state() vmethod
	  Since the driver checkup is done at registering, there is no need to do it
	  when changing the element state from NULL to READY. This patch remove this
	  vmethod from vaapidecode.

2016-07-12 20:29:12 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapi.c:
	  vaapi: register vaapipostproc only if supported
	  Query the GstVaapiDisplay to know if the driver supports video
	  postprocessing. If does, then register vaapipostproc and vaapidecodebin
	  elements.
	  This patch will simplify the design of vaapidecodebin.
	  https://bugzilla.gnome.org/show_bug.cgi?id=724352

2016-06-29 12:36:26 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapi.c:
	  vaapi: don't register if VA driver is unsupported
	  Using the test VA display, the driver name is queried, and if it is not
	  white-listed, the plugin rejects to register any element.
	  https://bugzilla.gnome.org/show_bug.cgi?id=724352

2016-06-28 17:14:06 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginbase.c:
	* gst/vaapi/gstvaapipluginutil.c:
	* gst/vaapi/gstvaapipluginutil.h:
	  plugins: add gst_vaapi_driver_is_whitelisted()
	  Move some of the logic in gst_vaapi_plugin_base_driver_is_whitelisted() to a
	  new function gst_vaapi_driver_is_whitelisted(), in this way, it can be used
	  when registering the plugin's feature set with the test VA display.
	  https://bugzilla.gnome.org/show_bug.cgi?id=724352

2016-07-12 19:56:02 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapi.c:
	  vaapi: instantiate a VA display when registering
	  This patch tries to instantiate a GstVaapiDisplay when registering the plugin
	  features, if it fails, no gstreamer-vaapi element is registering.
	  The purpose of this patch is to avoid a situation where the user has
	  gstreamer-vaapi installed but their VA-API setup is not functional, which may
	  lead to unexpected behavior.
	  https://bugzilla.gnome.org/show_bug.cgi?id=724352

2016-06-28 11:33:18 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* configure.ac:
	* gst/vaapi/gstvaapi.c:
	  vaapi: declare external dependencies
	  There are two main external dependencies that define the feature set of this
	  plugin: a) the kernel and b) the VA driver
	  This patch tracks both dependencies, if any of them change, GStreamer will
	  re-inspect the plugin.
	  The kernel is tracked through the device files /dev/dri/card*
	  The VA driver is tracked through the files VA_DRIVERS_PATH/*_drv_video.so,
	  where VA_DRIVERS_PATH is the one defined in libva package configuration. Also,
	  the environment variables LIBVA_DRIVERS_PATH and LIBVA_DRIVER_NAME are tracked
	  since they modify the driver lookup.
	  Additionally, the environment variable GST_VAAPI_ALL_DRIVERS is tracked too.
	  https://bugzilla.gnome.org/show_bug.cgi?id=724352

2016-07-19 16:02:27 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecode.c:
	  vaapidecode: remove unneeded initializations
	  GObject's memory is set to zero, so there is no need to initialize to zero or
	  NULL it's class variables.

2016-07-19 18:28:28 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipluginbase.h:
	  plugins: remove undefined macros

2016-07-19 17:43:28 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapisurface_drm.c:
	  Revert "gstvaapisurface_drm: release image when done"
	  This reverts commit 1dbcc8a0e199f2da6a0ab8e949f13341916128a3  and commit
	  372a03a9e38acbf435eb80bf31d9a9844069e504.
	  While the dmabuf handle is exported, the derive image must exist, otherwise
	  the image's VA buffer is invalid, thus the dmabuf handle is never released,
	  leading into a file descriptors leak.

2016-07-21 17:38:17 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapiencoder_h265.c:
	  encoder: h265: fix code-style

2016-07-22 16:55:59 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipostproc.c:
	  vaapipostproc: update filters at color balance
	  This is a fix for a regression of previous commit, which updates the filters
	  only when the property is set, because it is also required to update the
	  filter when the color balance interface change its values.

2016-07-22 12:10:23 +0900  Hyunjun Ko <zzoon@igalia.com>

	* gst/vaapi/gstvaapipostproc.c:
	* gst/vaapi/gstvaapipostproc.h:
	  vaapipostproc: make it enable/disable pass-through mode
	  In case that sink caps and src caps are same, and no filtering parameter set,
	  pass-through mode is enabled.
	  If new filtering parameter is set during playback, it makes it reconfiguring,
	  so that pass-through mode is changed
	  In addition, updating filter is performed during reconfiguration, if needed.
	  https://bugzilla.gnome.org/show_bug.cgi?id=751876

2016-07-22 11:51:26 +0900  Hyunjun Ko <zzoon@igalia.com>

	* gst-libs/gst/vaapi/gstvaapifilter.c:
	* gst-libs/gst/vaapi/gstvaapifilter.h:
	* gst/vaapi/gstvaapipostproc.c:
	  vaapipostproc: checking and updating filter parameter only when it's set
	  This patch is to avoid checking filter value at every frame.
	  https://bugzilla.gnome.org/show_bug.cgi?id=751876

2016-07-21 11:24:31 +0300  Allen Zhang <Zhang, Zhangfei>

	* gst-libs/gst/vaapi/gstvaapidecoder_h265.c:
	  decoder: h265: handle the SEI NAL units included in codec_data
	  The prefix/suffix SEI nal units can appear in codec_data too
	  which weren't handled before. Parse these SEI headers to
	  fix the segfault.
	  https://bugzilla.gnome.org/show_bug.cgi?id=768544

2016-07-15 16:32:26 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* docs/plugins/Makefile.am:
	  build: doc: do not redefine MAINTAINERCLEANFILES
	  MAINTAINERCLEANFILES is defined in gtk-doc-plugins.mak, thus instead of
	  overload it, the files should be added.

2016-07-15 14:41:27 +0300  Sreerenj Balachandran <sreerenj.balachandran@intel.com>

	* gst-libs/gst/vaapi/gstvaapiencoder_h264.c:
	  encoder: h264: Fix MVC encode while enabling dct8x8
	  Pack the transform_8x8_mode_flag and other necessary rbsp data
	  in packed_pps header for MVC encode.
	  https://bugzilla.gnome.org/show_bug.cgi?id=768647

2016-07-12 23:58:55 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapisink.c:
	  vaapisink: demote a debug message to trace
	  Reduces noise when debugging.

2016-07-13 17:21:01 +0900  Jagyum Koo <koojagyum@gmail.com>

	* gst-libs/gst/vaapi/gstvaapidisplay_wayland.c:
	  wayland: Error check before using cached wl_display
	  A planar(or some other) buffer allocation may fail on the driver, then
	  the wayland connection becomes invalid, not able to send request or
	  receive any event. So we need to set up a new wayland connection if
	  there's an error detected on the cached wl_display.
	  https://bugzilla.gnome.org/show_bug.cgi?id=768761
	  Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

2016-07-11 21:15:57 +0200  Stefan Sauer <ensonic@users.sf.net>

	* common:
	  Automatic update of common submodule
	  From ac2f647 to f49c55e

2016-07-05 18:23:22 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapiencode.c:
	  vaapiencode: demote a log to trace level
	  Removes noise when debugging.

2016-07-06 11:17:23 +0900  Hyunjun Ko <zzoon@igalia.com>

	* gst/vaapi/gstvaapiencode.c:
	  vaapiencode: implement flush() vmethod
	  In order to handle correctly seek and other operations, vaapiencode should
	  flush all the remaining data from the encoder without pushing it downstream.
	  This patch implements the flush() vmethod, only after of pausing the
	  source pad task, and restarting it again after the flush stop.
	  https://bugzilla.gnome.org/show_bug.cgi?id=767176
	  Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

2016-07-11 08:43:04 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapidecoder_vc1.c:
	  decoder: vc1: flush dpb only if opened
	  Flush the decode picture buffer, if and only if, the decoder is
	  started. Otherwise the dpb structure might be NULL.
	  https://bugzilla.gnome.org/show_bug.cgi?id=742922

2016-07-01 14:42:20 +0900  Hyunjun Ko <zzoon@igalia.com>

	* gst/vaapi/gstvaapidecode.c:
	* gst/vaapi/gstvaapidecode.h:
	  vaapidecode: drop non-keyframe in reverse playback
	  To avoid surface-exhausted situation during reverse playback,
	  drop frames except for key frame.
	  Also, to avoid the corruption of the parser state, flush() vmethod
	  doesn't destroy the VA decoder when playing in reverse.
	  https://bugzilla.gnome.org/show_bug.cgi?id=742922
	  Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

2016-07-10 19:33:14 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecode.c:
	  vaapidecode: unref output frame earlier
	  The queue in GstVaapiDecode adds an extra reference to the frames. This patch
	  unref that extra reference earlier making the code simpler to follow.
	  https://bugzilla.gnome.org/show_bug.cgi?id=768652

2016-07-10 19:01:17 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecode.c:
	  vaapidecode: remove gst_vaapidecode_internal_flush()
	  As gst_vaapidecode_finish() is the only callee of
	  gst_vaapidecode_internal_flush(), it is better to inline it.
	  https://bugzilla.gnome.org/show_bug.cgi?id=768652

2016-07-10 18:18:57 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecode.c:
	  vaapidecode: flush output adapter at drain()
	  Calling drain() vmethod means "decode any data it can at this point, but that
	  more data may arrive after". Hence, vaapidecode should check if there is data
	  in the output adapter and process them, without destroying the decoded picture
	  buffer (dpb).
	  Since this operation is done by gst_vaapidecode_internal_flush(), the operation
	  was refactored into a new function gst_vaapidecode_flush_output_adapter().
	  https://bugzilla.gnome.org/show_bug.cgi?id=768652

2016-07-10 13:46:25 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecode.c:
	  vaapidecode: call purge at flush()
	  Calling flush() vmethod means "to flush all remaining data from the decoder
	  without pushing it downstream".
	  Nonetheless flush() is calling gst_vaapidecode_internal_flush(), which calls
	  gst_video_decoder_have_frame() if there is still something in the input
	  adapter, which may push buffers to downstream by calling handle_frame().
	  This patch changes this behavior by calling gst_vaapidecode_purge() rather
	  than gst_vaapidecode_internal_flush(), which does what we want: flushes the VA
	  decoder and releases all the rest of decoded frames.
	  https://bugzilla.gnome.org/show_bug.cgi?id=768652

2016-07-06 18:38:37 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* tests/elements/Makefile.am:
	* tests/elements/test-vaapisink.c:
	  test: elements: remove spurious linkage
	  Element tests only need to link against gstreamer libraries.

2016-07-06 14:41:21 +0300  Sebastian Dröge <sebastian@centricular.com>

	* configure.ac:
	  configure: Require GLib >= 2.40 like everywhere else

2016-07-06 13:51:21 +0300  Sebastian Dröge <sebastian@centricular.com>

	* configure.ac:
	  Back to development

Sebastian Dröge's avatar
Sebastian Dröge committed
875
876
=== release 1.9.1 ===

Sebastian Dröge's avatar
Sebastian Dröge committed
877
2016-07-06 13:48:07 +0300  Sebastian Dröge <sebastian@centricular.com>
Sebastian Dröge's avatar
Sebastian Dröge committed
878

Sebastian Dröge's avatar
Sebastian Dröge committed
879
880
881
	* ChangeLog:
	* NEWS:
	* common:
Sebastian Dröge's avatar
Sebastian Dröge committed
882
	* configure.ac:
Sebastian Dröge's avatar
Sebastian Dröge committed
883
884
	* gstreamer-vaapi.doap:
	  Release 1.9.1
Sebastian Dröge's avatar
Sebastian Dröge committed
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

2016-07-05 20:59:49 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* tests/elements/test-vaapisink.c:
	  tests: elements: rotate orientation event

2016-07-01 16:01:54 +0900  Hyunjun Ko <zzoon@igalia.com>

	* configure.ac:
	* tests/Makefile.am:
	* tests/elements/Makefile.am:
	* tests/elements/test-vaapisink.c:
	  tests: elements: Add testsuite for vaapisink
	  https://bugzilla.gnome.org/show_bug.cgi?id=765798

2016-07-01 16:00:46 +0900  Hyunjun Ko <zzoon@igalia.com>

	* gst-libs/gst/vaapi/gstvaapitypes.h:
	* gst-libs/gst/vaapi/gstvaapivalue.c:
	* gst/vaapi/gstvaapisink.c:
	* gst/vaapi/gstvaapisink.h:
	  vaapisink: add support for GST_TAG_IMAGE_ORIENTATION
	  https://bugzilla.gnome.org/show_bug.cgi?id=765798

2016-06-29 13:57:02 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapipostproc.c:
	  vaapipostproc: return caps template if no display
	  This patch is a fix for my bad review of commit 6d73ca8d. The element should
	  be able to return the available raw caps handled by the VA display, but that
	  only should happen when there a VA display. If there's none, the element
	  should use the caps template.
	  https://bugzilla.gnome.org/show_bug.cgi?id=768161

2016-06-29 16:42:18 +1000  Matthew Waters <matthew@centricular.com>

	* gst/vaapi/gstvaapipostproc.c:
	  vaapipostproc: don't require a vaapi display for all caps queries
	  This delays the requirement of having a GstVaapiDisplay until later
	  https://bugzilla.gnome.org/show_bug.cgi?id=768161

2016-06-28 15:48:39 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst-libs/gst/vaapi/gstvaapiutils.c:
	  utils: report VP9 profiles
	  Add VP9Profile0-3 name mapping.

2016-06-28 14:05:51 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapi.c:
	  vaapi: nest includes under USE_ENCODER macro
	  This is a missed changeset from commit 1c05c53, since also header includes
	  should be nested.

2016-06-28 11:54:33 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapi.c:
	  vaapi: nest encoders under USE_ENCODER macro
	  Though USE_{JPEG,VP8,VP9,H265}_ENCODER macros definition depend on USE_ENCODER
	  macro, it is clearer to nest them, showing explicitly the dependency relation.

2016-06-24 12:05:24 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapivideocontext.c:
	  vaapivideocontext: check if query context is NULL
	  Under certain conditions the element might receive a positive context query
	  but without a context instance. This situation will lead to a segmentation
	  fault when traversing the context list in the pipeline.
	  https://bugzilla.gnome.org/show_bug.cgi?id=767946

2016-06-20 13:22:36 -0700  Scott D Phillips <scott.d.phillips@intel.com>

	* gst-libs/gst/vaapi/Makefile.am:
	* gst-libs/gst/vaapi/glibcompat.h:
	* gst-libs/gst/vaapi/sysdeps.h:
	  remove unused glibcompat.h
	  glibcompat.h is no longer doing anything. Remove it.
	  Signed-off-by: Scott D Phillips <scott.d.phillips@intel.com>
	  https://bugzilla.gnome.org/show_bug.cgi?id=767886

2016-06-22 14:28:44 -0700  Scott D Phillips <scott.d.phillips@intel.com>

	* gst-libs/gst/vaapi/gstvaapiencoder_h264.c:
	  encoder: h264: Use high profile by default
	  Change defaults for max-bframes, cabac, and dct8x8 to be enabled
	  by default. This will cause the default profile to be high instead
	  of baseline. In most situations this is the right decision, and
	  the profile can still be lowered in the case of caps restrictions.
	  Signed-off-by: Scott D Phillips <scott.d.phillips@intel.com>
	  https://bugzilla.gnome.org/show_bug.cgi?id=757941

2016-06-22 12:15:29 +0200  Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com>

	* gst/vaapi/gstvaapidecodebin.c:
	  vaapidecodebin: element warning if missing element
	  Raise an element warning if a required element is not available, thus the
	  pipeline will post a warning message and the application will be informed.

2016-06-22 15:11:56 +0300  Hyunjun Ko <zzoon@igalia.com>

	* gst-libs/gst/vaapi/gstvaapidecoder_h265.c:
	  decoder: h265: fix to release all dpb pictures
	  Without this, all dpb pictures are not released during flush,
	  because we used the global dpb_count variable for checking the
	  dpb fullness which get decremented in dpb_remove_index()
	  routine during each loop iteration.
	  https://bugzilla.gnome.org/show_bug.cgi?id=767934

2016-06-21 11:48:54 -0400  Nicolas Dufresne <nicolas.dufresne@collabora.com>

	* common:
	  Automatic update of common submodule
	  From ac2f647 to f363b32

2016-06-20 19:53:26 +0900  Hyunjun Ko <zzoon@igalia.com>