Bugfixes and a few extras:
2013-09-19 20:17:01 +0200 Sebastian Dröge <sl...@circular-chaos.org>
* gst/audiofxbad/gstaudiofxbad.c:
audiofxbad: Change plugin name to audiofxbad from audiochannelmix
2013-09-18 22:36:51 +0200 Sebastian Dröge <sl...@circular-chaos.org>
* ext/eglgles/gstegladaptation.c:
* ext/eglgles/gstegladaptation_egl.c:
* ext/eglgles/gsteglglessink.c:
eglglessink: Update for new GstContext API
2013-09-18 22:24:07 +0200 Sebastian Dröge <sl...@circular-chaos.org>
* gst-libs/gst/egl/egl.c:
* gst-libs/gst/egl/egl.h:
egl: Update for new GstContext API
2013-09-17 17:41:39 -0400 Olivier Crête <olivier.cr...@collabora.com>
* ext/hls/gsthlsdemux.c:
hlsdemux: Reset GstUriDownloader cancellation when restarting to play
2013-09-04 10:58:24 +0100 Julien Isorce <julien.iso...@collabora.co.uk>
* ext/eglgles/gsteglglessink.c:
eglglessink: change pool->sink->last_buffer to pool->last_buffer
So that GstEGLImageBufferPool does not depend on GstEglGlesSink
The goal is still to move it into gstegl lib
2013-09-04 10:56:12 +0100 Julien Isorce <julien.iso...@collabora.co.uk>
* ext/eglgles/gsteglglessink.c:
eglglessink: buffer pool does not need to maintain a ref on the display
Because it does not use it and also it may not know it when
we create the pool
2013-09-04 10:52:51 +0100 Julien Isorce <julien.iso...@collabora.co.uk>
* ext/eglgles/gsteglglessink.c:
eglglessink: add GstEGLImageBufferPoolSendBlockingAllocate callback
The goal here is to prepare GstEGLBufferPool to be moved into
gstegl lib. So it has to not depend on 'gst_eglglessink_queue_object'
2013-09-04 10:48:34 +0100 Julien Isorce <julien.iso...@collabora.co.uk>
* ext/eglgles/gstegladaptation.h:
* ext/eglgles/gstegladaptation_egl.c:
* ext/eglgles/gsteglglessink.c:
eglglessink: prepare gst_egl_adaptation_allocate_eglimage to be moved
into gstegl lib or splited between gstegl lib and gstgl lib
because it both depends on egl and gl
So it has to not depend on GstEglAdaptationContext
2013-08-30 13:54:40 +0100 Alex Ashley <bugzi...@ashley-family.net>
* gst/videoparsers/gsth264parse.c:
* tests/check/elements/h264parse.c:
h264parse: Add support for stream-format=avc3
When outputting in AVC3 stream format, the codec_data should not
contain any SPS or PPS, because they are embedded inside the stream.
In case of avc->bytestream h264parse will push the SPS and PPS from
codec_data downstream at the start of the stream, at intervals
controlled by "config-interval" and when there is a codec_data change.
In the case of avc3->bytstream h264parse detects that there is
already SPS/PPS in the stream and sets h264parse->push_codec to FALSE.
Therefore avc3->bytstream was already supported, except for the stream
type.
In the case of bystream->avc h264parse will generate codec_data caps
from the parsed SPS/PPS in the stream. However it does not remove these
SPS/PPS from the stream. bytestream->avc3 is the same as bytestream->avc
except that the codec_data must not have any SPS/PPS in it.
|--------------+-------------+-------------------|
|stream-format | SPS in-band | SPS in codec_data |
|--------------+-------------+-------------------|
| avc | maybe | always |
|--------------+-------------+-------------------|
| avc3 | always | never |
|--------------+-------------+-------------------|
Amendment 2 of ISO/IEC 14496-15 (AVC file format) is defining a new
structure for fragmented MP4 called "avc3". The principal difference
between AVC1 and AVC3 is the location of the codec initialisation
data (e.g. SPS, PPS). In AVC1 this data is placed in the initial MOOV box
(moov.trak.mdia.minf.stbl.stsd.avc1) but in AVC3 this data goes in the
first sample of every fragment.
https://bugzilla.gnome.org/show_bug.cgi?id=702004
2013-08-12 10:16:16 +0000 Jorge Luis Zapata <jzap...@fluendo.com>
* sys/androidmedia/gstamc-constants.h:
* sys/androidmedia/gstamc.c:
* sys/androidmedia/gstamcvideodec.c:
androidmedia: add support for a new qualcomm colorspace
2013-06-26 11:07:14 +0900 Kazunori Kobayashi <kkoba...@igel.co.jp>
* configure.ac:
* ext/directfb/dfbvideosink.c:
* ext/directfb/dfbvideosink.h:
dfbvideosink: port to 1.0
including the following supports and fixes:
* Create DirectFB surfaces from GstBufferPool
* Add NV12 pixel format support
* Don't use the cursor in the exclusive mode
- EnableCusor() can be only used when the administrative mode is set
in DirectFB 1.6.0 and later.
* Support multiple plane rendering for planar color formats
- This accommodates the chroma plane offsets of the framebuffer
in planar formats.
* Invoke SetConfiguration regardless of video mode setting in setcaps()
- SetConfiguration() method should be invoked regardless of
the result of gst_dfbvideosink_get_best_vmode(), since the two are
unrelated.
* Disable DirectFB signal handler
- "--dfb:no-sighandler" option is passed to DirectFBInit().
This prevents DirectFB from trying to kill the process and allows
GStreamer's termination sequence to proceed normally.
https://bugzilla.gnome.org/show_bug.cgi?id=703520
2013-08-28 14:26:04 +0200 Bernhard Miller
<bernhard.mil...@streamunlimited.com>
* sys/bluez/a2dp-codecs.h:
* sys/bluez/gstavdtpsrc.c:
* sys/bluez/gstavdtputil.c:
bluez: support aac in avdtpsrc
Signed-off-by: Bernhard Miller <bernhard.mil...@streamunlimited.com>
** Attachment added: "gst-plugins-bad1.0-1.2.0.changelog"
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1233832/+attachment/3854059/+files/gst-plugins-bad1.0-1.2.0.changelog
** Bug watch added: GNOME Bug Tracker #708326
https://bugzilla.gnome.org/show_bug.cgi?id=708326
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233832
Title:
[FFe] Updating gstreamer 1.0 stack to the final 1.2 release
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1233832/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
