summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2017-02-12libav: Update to n3.0.71.8Sebastian Dröge1-0/+0
2017-02-08avaudenc/dec: Don't do range comparisons against ↵Iain Lane2-0/+22
AV_CODEC_ID_PCM_S16BE_PLANAR for < 3.0 Prior to ffmpeg 3.0, this constant had a specified value. Excluding all plugins in a range bounded by this value was throwing out plugins that we want to keep. Instead switch to enumerating the values to exclude, for < 3.0. https://bugzilla.gnome.org/show_bug.cgi?id=778283
2016-12-08libav: Update to n3.0.5Sebastian Dröge1-0/+0
2016-11-12avmux: blacklist fifo pluginTim-Philipp Müller1-0/+1
Avoids criticals in gst-inspect-1.0 -a
2016-11-12avvidenc/dec: Disable more hardware encoder/decodersleigh123linux@googlemail.com2-1/+15
Important when using a system ffmpeg/libav. https://bugzilla.gnome.org/show_bug.cgi?id=774278
2016-11-12configure: fix target_os when cross-compiling for armMichael Olbrich1-1/+1
For arm 'host_os' is '*-gnueabi' or '*-gnueabihf' so sed needs to cut of more. Otherwise configuring ffmpeg will fail with "Unknown OS 'linuxeabi'." or something like that. https://bugzilla.gnome.org/show_bug.cgi?id=774215
2016-11-12avaudenc/dec: Allow compilation against ffmpeg < 3.2 againSebastian Dröge2-0/+8
2016-11-12avaudenc/dec: Ignore S64BE/LE pseudo-codecsSebastian Dröge2-2/+2
2016-10-25libav: Update to ffmpeg n3.0.4Sebastian Dröge1-0/+0
2016-09-30av: Cast AVContext::bit_rate to a guint before passing to varargs functionsSebastian Dröge3-11/+11
We expect it to be a int or uint, however it changed the type to a int64_t in later versions of ffmpeg. As such it would be passed as a 64 bit value to varargs functions, while the consumer of the arguments assumes only 32 bits. This causes crashes. https://bugzilla.gnome.org/show_bug.cgi?id=771092
2016-09-05libav: Update to ffmpeg n3.0.3Sebastian Dröge1-0/+0
2016-09-03Only use AV_CODEC_ID_WRAPPED_AVFRAME on new enough libavcodecsIain Lane2-4/+10
https://bugzilla.gnome.org/show_bug.cgi?id=770753
2016-08-19Release 1.8.31.8.3Sebastian Dröge7-577/+107
2016-08-17configure: Explicitly disable CrystalHD decoderSebastian Dröge1-0/+2
Otherwise it will pick it up when the system has the relevant headers, and then linking produces an unusable plugin later as we don't ensure that the plugin also links against the crystalhd library. Also backport a few other similar cases from master at the same time. https://bugzilla.gnome.org/show_bug.cgi?id=769809
2016-08-16avvidec: Ensure skipping strategy gets properly resetEdward Hervey1-13/+20
When switching playback modes, like from TRICKMODE or TRICKMODE_KEY_UNITS back to regular playback, we need to make sure we set the skip mode back to the default setting. While this field would be properly reset when we *have* feedback from downstream (i.e. diff != G_MAXINT64), it would not be reset during the initial phase (i.e. when the decoder hasn't pushed a buffer yet, and therefore the sink hasn't sent back QoS information). This avoids dropping plenty of frames when going back to regular playback
2016-07-25libav: Ignore more quasi-codecsSebastian Dröge4-10/+31
2016-07-25libav: Ignore VAAPI decoders and VAAPI/nvenc encodersSebastian Dröge2-0/+21
These can show up when having a build against a system version of ffmpeg.
2016-07-25avvidenc: Create caps from the codec context after it is openedSebastian Dröge1-17/+23
We won't get codec_data and various other information otherwise.
2016-07-25avaudenc: Create caps from the codec context after it is openedSebastian Dröge1-14/+15
We won't get codec_data and various other information otherwise.
2016-07-25avaudenc: Use gst_caps_fixate() instead of gst_caps_truncate()Sebastian Dröge1-1/+1
Just truncating might not be enough.
2016-06-09Release 1.8.21.8.2Sebastian Dröge6-27/+109
2016-05-14avvidec: Don't set bogus latencyEdward Hervey1-5/+7
We might have cases where the framerate is not known (0/1).
2016-05-13avvidec: Report the latency once we're fully configuredEdward Hervey1-0/+8
Several decoders will only be able to report a real latency (has_b_frames) once they're actually initialized (i.e. when they return their first frame). Doing it earlier (in set_format) doesn't guarantee that the AVCodecContext has_b_frames has been properly initialized. https://bugzilla.gnome.org/show_bug.cgi?id=766362
2016-05-03libav: Update to ffmpeg n3.0.2Sebastian Dröge1-0/+0
2016-05-02avauddec: Finish frames if they are header buffers only and don't produce ↵Sebastian Dröge1-2/+3
any output Otherwise we will consider them as one frame of raw audio that is still pending, and shift all timestamps by the amount of time spent with header buffers. https://bugzilla.gnome.org/show_bug.cgi?id=765797
2016-05-02avauddec: If decoding a frame failed, skip itSebastian Dröge1-0/+3
Otherwise the next successfully decoded frame will get its timestamp and we will slowly let a/v sync drift apart. https://bugzilla.gnome.org/show_bug.cgi?id=765797
2016-04-28avaudenc: Set all required fields in the AVFrameSebastian Dröge1-0/+4
Various functions in libavcodec need them, like the format, sample rate, etc. and just having them in the context is not enough. This fixes draining for codecs like MP2 that require a fixed frame size and require libav to pad the last frame if required.
2016-04-26avcfg: Use av_strdup() instead of g_strdup() for strings owned by ffmpegSebastian Dröge1-1/+1
It has its own allocator that depending on the configuration is incompatible with GLib's and just causes a segmentation fault. Like on Windows. https://bugzilla.gnome.org/show_bug.cgi?id=760266
2016-04-20Release 1.8.11.8.1Sebastian Dröge6-795/+69
2016-04-20avdeinterlace: Register all filters and only disable all except for yadif ↵Sebastian Dröge2-1/+3
during compilation Otherwise avdeinterlace won't find any filters, and we only use yadif in there. https://bugzilla.gnome.org/show_bug.cgi?id=765319
2016-04-15libav: Update to n3.0.1Sebastian Dröge1-0/+0
2016-03-24Release 1.8.01.8.0Sebastian Dröge6-15/+833
2016-03-21configure: Restore CPPFLAGS after the last checkEgor Zaharov1-1/+1
The next checks can also set CPPFLAGS. https://bugzilla.gnome.org/show_bug.cgi?id=763940
2016-03-15Release 1.7.911.7.91Sebastian Dröge6-12/+40
2016-03-11avcodecmap: Only set the bitrate if we actually got it from the capsSebastian Dröge1-2/+2
Otherwise we set a random value from the stack as bitrate. The default (0) is a better choice and doesn't upset valgrind.
2016-03-01Release 1.7.901.7.90Sebastian Dröge6-24/+77
2016-02-26Automatic update of common submoduleSebastian Dröge1-0/+0
From b64f03f to 6f2d209
2016-02-23avdeinterlace: Don't assume that get_current_caps() returns non-NULL caps ↵Sebastian Dröge1-4/+3
after has_current_caps() Remove calls to gst_pad_has_current_caps() which then go on to call gst_pad_get_current_caps() as the caps can go to NULL in between. Instead just use gst_pad_get_current_caps() and check for NULL. https://bugzilla.gnome.org/show_bug.cgi?id=759539
2016-02-21win32: remove outdated build cruftTim-Philipp Müller4-201/+1
This hasn't been touched for generations, doesn't work, and is just causing confusion. We also don't want to maintain these files manually.
2016-02-20Don't use exported but undeclared core debug category symbolsTim-Philipp Müller4-8/+8
It's not right and won't work on Windows with MSVC.
2016-02-19Back to developmentSebastian Dröge1-3/+3
2016-02-19Release 1.7.21.7.2Sebastian Dröge7-41/+191
2016-02-16avcfg: rc-min-rate and rc-max-rate are now 64bit integersEdward Hervey1-2/+27
Switch the gobject properties and internal handling to support that
2016-02-16avvidenc: Set width/height and format in the AVFrame we pass to the encoder APISebastian Dröge1-0/+4
2016-02-16docs: Update docs to not have unstaged changes after build againSebastian Dröge4-38/+648
There are some new codec IDs that we probably would like to map too, e.g. Dirac/VC2 and Cineform HD.
2016-02-15libav: Update to n3.0Sebastian Dröge1-0/+0
2016-02-05Automatic update of common submoduleThiago Santos2-0/+2
From 86e4663 to b64f03f
2016-01-25avaudenc: Also use av_free() instead of g_free()Sebastian Dröge1-2/+2
2016-01-25avaudenc: Use av_malloc() instead of GLib malloc() wrappers for memory freed ↵Sebastian Dröge1-2/+2
by ffmpeg It has its own allocator that is not necessarily doing the same as malloc and will then usually crash. E.g. on Windows or when memalign() is available.
2016-01-21avvidec: Bring mpeg video decoders up to PRIMARY rankEdward Hervey1-0/+2
We should have done that ages ago ... https://bugzilla.gnome.org/show_bug.cgi?id=574461