Re: [FFmpeg-devel] avformat/mpegts: set AV_DISPOSITION_DESCRIPTIONS for OIPF cases

I have prepared a testcase. PMT data comes from org.hbbtv_HTML50420. Please review. Regards, *Łukasz Krzciuk* Developer Vewd ul. Grabarska 2, Pegaz 2A, 50-079 Wrocław, Polska On Thu, May 10, 2018 at 8:54 PM, Aman Gupta wrote: > On Thu, May 10, 2018 at 1:46 AM Łukasz Krzciuk

[FFmpeg-devel] [PATCH v2 1/3] lavc/h2645_parse: log more HEVC NAL type.

Signed-off-by: Jun Zhao --- libavcodec/h2645_parse.c | 97 ++-- libavcodec/hevc.h| 26 - 2 files changed, 94 insertions(+), 29 deletions(-) diff --git a/libavcodec/h2645_parse.c b/libavcodec/h2645_parse.c index

Re: [FFmpeg-devel] [PATCH 1/2] avformat/dashenc: Added option for Segment file format

On 5/12/18 8:47 PM, Jan Ekström wrote: > On Fri, May 4, 2018 at 9:32 AM, Karthick J wrote: >> From: Karthick Jeyapal >> >> Right now segment file format is chosen to be either mp4 or webm based on >> the codec format. >> This patch makes that choice

[FFmpeg-devel] [PATCH v2 2/3] lavc/h2645_parse: rename the nal_unit_name to hevc_nal_unit_name.

Rename the nal_unit_name to hevc_nal_unit_name, will add a h264_nal_unit_name function. Signed-off-by: Jun Zhao --- libavcodec/h2645_parse.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libavcodec/h2645_parse.c b/libavcodec/h2645_parse.c index

Re: [FFmpeg-devel] Add IRC nicknames to MAINTAINERS?

ons 2018-04-25 klockan 11:42 +0200 skrev Paul B Mahol: > On 4/25/18, Tomas Haerdin wrote: > > ons 2018-04-25 klockan 09:55 +0100 skrev Josh de Kock: > > > On 2018/04/25 9:35, Paul B Mahol wrote: > > > > On 4/25/18, Tomas Haerdin wrote: > > > > > [...] > >

[FFmpeg-devel] [PATCH v2 2/2] avformat/dashenc: Added a warning for incorrect segment name extension

From: Karthick Jeyapal Applicable only to webm output format. By default all the segment filenames end with .m4s extension. When someone chooses webm output format, we recommend they also override the relevant segment name options to end with .webm extension. This patch

Re: [FFmpeg-devel] [PATCH v2 1/2] avformat/dashenc: Added option for Segment file format

On 5/14/18 11:55 AM, Gyan Doshi wrote: > > > On 5/14/2018 11:41 AM, Karthick J wrote: > >> Right now segment file format is chosen to be either mp4 or webm based on >> the codec format. >> This patch makes that choice configurable by the user, instead of being >> decided by the muxer. > > Can

[FFmpeg-devel] [PATCH v2 3/3] lavc/h2645_parse: add h264_nal_unit_name for h264 NAL type.

Signed-off-by: Jun Zhao --- libavcodec/h264.h| 23 ++- libavcodec/h2645_parse.c | 46 -- 2 files changed, 66 insertions(+), 3 deletions(-) diff --git a/libavcodec/h264.h b/libavcodec/h264.h index

Re: [FFmpeg-devel] [PATCH v2 1/2] avformat/dashenc: Added option for Segment file format

On 5/14/2018 11:41 AM, Karthick J wrote: Right now segment file format is chosen to be either mp4 or webm based on the codec format. This patch makes that choice configurable by the user, instead of being decided by the muxer. Can you update the docs to reflect on the differences between

[FFmpeg-devel] [PATCH v2 1/2] avformat/dashenc: Added option for Segment file format

From: Karthick Jeyapal Right now segment file format is chosen to be either mp4 or webm based on the codec format. This patch makes that choice configurable by the user, instead of being decided by the muxer. Also with this change per-stream choice segment file

[FFmpeg-devel] [PATCH v2 0/3] Enhancement NAL type debug

v2: - cover all h264/hevc NAL unit type - use table replace switch when map NAL type to string/name Jun Zhao (3): lavc/h2645_parse: log more HEVC NAL type. lavc/h2645_parse: rename the nal_unit_name to hevc_nal_unit_name. lavc/h2645_parse: add h264_nal_unit_name for h264 NAL type.

Re: [FFmpeg-devel] [PATCH] lavc/amfenc: moving amf common code (library and context) to lavu/hwcontext_amf from amfenc to be reused in other amf components

Hi Mark, Thank you for your comments. Could you see my comments bellow > -Original Message- > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of Mark > Thompson > Sent: Sunday, May 13, 2018 1:41 AM > To: ffmpeg-devel@ffmpeg.org > Subject: Re: [FFmpeg-devel] [PATCH]

[FFmpeg-devel] [PATCH] avfilter: add aderivative and aintegral filter

Signed-off-by: Paul B Mahol --- doc/filters.texi | 6 ++ libavfilter/Makefile | 2 + libavfilter/af_aderivative.c | 207 +++ libavfilter/allfilters.c | 2 + 4 files changed, 217 insertions(+) create mode

[FFmpeg-devel] [PATCH] avcodec: Disable new iterate API for ossfuzz

A few days ago ossfuzz stoped testing new FFmpeg as it run out of diskspacee https://oss-fuzz-build-logs.storage.googleapis.com/index.html An alternative would be to revert the API. This changes for example -rwxr-x--- 1 michael michael 144803654 May 14 12:54 tools/target_dec_ac3_fixed_fuzzer*

[FFmpeg-devel] [PATCH 5/5] doc/examples: add missing ignore files

From: Zhao Zhili --- doc/examples/.gitignore | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/examples/.gitignore b/doc/examples/.gitignore index 154c841..75152cb 100644 --- a/doc/examples/.gitignore +++ b/doc/examples/.gitignore @@ -20,3 +20,5 @@ /scaling_video

[FFmpeg-devel] [PATCH 4/5] examples/filtering_video: fix memory leak

From: Zhao Zhili --- doc/examples/filtering_video.c | 15 +-- 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/doc/examples/filtering_video.c b/doc/examples/filtering_video.c index 2cc55e8..324d566 100644 --- a/doc/examples/filtering_video.c +++

[FFmpeg-devel] [PATCH] lavc/amfenc: moving amf common code (library and context) to lavu/hwcontext_amf from amfenc to be reused in other amf components

This patch moves AMF common parts from amfenc to hwcontext_amf. Now av_hwdevice_ctx API is used for AMF context creation/destroying. This patch does not change component behaviour. it contains only restructurization for further patches with new amf components --- Sending updated patch based on

[FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

Hello all. This is a little rambling / stream of thought, but take it as you will, and perhaps some discussion or change comes of it. Or, more likely, personal attacks, flames, and no change. Or 1 few will reply and then the thread will die and people will go on like it never happened. Sorry to

[FFmpeg-devel] [PATCH 2/5] examples/filtering_video: drop an always true condition

From: Zhao Zhili --- doc/examples/filtering_video.c | 34 -- 1 file changed, 16 insertions(+), 18 deletions(-) diff --git a/doc/examples/filtering_video.c b/doc/examples/filtering_video.c index 225dccc..170a675 100644 ---

[FFmpeg-devel] [PATCH 3/5] examples/filtering_video: add missing headers

From: Zhao Zhili --- doc/examples/filtering_video.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/examples/filtering_video.c b/doc/examples/filtering_video.c index 170a675..2cc55e8 100644 --- a/doc/examples/filtering_video.c +++ b/doc/examples/filtering_video.c

[FFmpeg-devel] [PATCH 1/5] examples/filtering_video: fix memory leak

From: Zhao Zhili --- doc/examples/filtering_video.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/examples/filtering_video.c b/doc/examples/filtering_video.c index 38ff9bb..225dccc 100644 --- a/doc/examples/filtering_video.c +++

Re: [FFmpeg-devel] [PATCH]configure: Support libxml2 on systems without pkg-config

Carl Eugen Hoyos (2018-05-14): > Attached patch allows to easily enable the dash demuxer on systems > without pkg-config. I am rather for letting them install pkg-config. Regards, -- Nicolas George signature.asc Description: Digital signature ___

Re: [FFmpeg-devel] [PATCH]configure: Support libxml2 on systems without pkg-config

2018-05-14 21:58 GMT+02:00, Nicolas George : > Carl Eugen Hoyos (2018-05-14): >> Sorry if this was really not clear: >> I do not have installation rights on every system where I >> (at least from time to time) test FFmpeg. > > Then install pkg-config in a local directory. If you

[FFmpeg-devel] [PATCH v5 1/2] avcodec/bitpacked: add interlace support

From: Damien Riegel This codec is already capable of depacking some combinations of pixel formats and depth as defined in the RFC4175. The only difference between progressive and interlace is that either a packet will contain the whole frame, or only a field

[FFmpeg-devel] [PATCH v5 2/2] avformat/rtpdec_rfc4175: handle interlace format

From: Damien Riegel In order to handle the interlaced formats, the demuxer has only a few things to do: - parse the SDP correctly and propagate the information - check the field bit in the RFC4175 header, and pass that information to the decoder In

Re: [FFmpeg-devel] [PATCH]configure: Support libxml2 on systems without pkg-config

Carl Eugen Hoyos (2018-05-14): > Which - as you know - can be impossible. I doubt there are systems where ffmpeg can be installed but not pkg-config. But if you really think there are, the best solution is to provide a minimalistic emulation of pkg-config. I would not object if you propose a

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On 14 May 2018 at 19:23, Derek Buitenhuis wrote: > > We can agree to disagree. There's not much point in arguing > over one specific event. This mail was not about clearing up > a specific event, but a general problem. There's not much point > in devolving into that.

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On Mon, May 14, 2018 at 8:54 PM, Rostislav Pehlivanov wrote: > We can't agree to disagree in this case, not if you seriously think that > this is an attack. Would you continue to interpret such vague events as > attacks? You gave it as an example after all. You can use the

Re: [FFmpeg-devel] [PATCH v5 1/2] avcodec/bitpacked: add interlace support

On 14 May 2018 at 20:29, Patrick Keroulas wrote: > From: Damien Riegel > > This codec is already capable of depacking some combinations of pixel > formats and depth as defined in the RFC4175. The only difference between

Re: [FFmpeg-devel] [PATCH]configure: Support libxml2 on systems without pkg-config

On Mon, May 14, 2018 at 10:42 PM, Carl Eugen Hoyos wrote: > 2018-05-14 21:39 GMT+02:00, Nicolas George : >> Carl Eugen Hoyos (2018-05-14): >>> Attached patch allows to easily enable the dash demuxer on systems >>> without pkg-config. >> >> I am rather for

Re: [FFmpeg-devel] [PATCH]configure: Support libxml2 on systems without pkg-config

Carl Eugen Hoyos (2018-05-14): > Sorry if this was really not clear: > I do not have installation rights on every system where I > (at least from time to time) test FFmpeg. Then install pkg-config in a local directory. If you can compile ffmpeg, then you can install pkg-config. > My primary

Re: [FFmpeg-devel] [PATCH]configure: Support libxml2 on systems without pkg-config

2018-05-14 21:39 GMT+02:00, Nicolas George : > Carl Eugen Hoyos (2018-05-14): >> Attached patch allows to easily enable the dash demuxer on systems >> without pkg-config. > > I am rather for letting them install pkg-config. Which - as you know - can be impossible. Carl Eugen

Re: [FFmpeg-devel] [PATCH]configure: Support libxml2 on systems without pkg-config

2018-05-14 21:46 GMT+02:00, Nicolas George : > Carl Eugen Hoyos (2018-05-14): >> Which - as you know - can be impossible. > > I doubt there are systems where ffmpeg can be installed but not > pkg-config. Sorry if this was really not clear: I do not have installation rights on

Re: [FFmpeg-devel] [PATCH] libavformat: add mbedTLS based TLS

Dave Gregory (2018-05-14): > First, a bit of context on our motivation. We write software that runs on > IP cameras to connect them to our cloud service. We started off by > using GnuTLS to secure our connections but there's very limited disk > space on the cameras and the relatively large binary

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On Mon, May 14, 2018 at 7:10 PM, Rostislav Pehlivanov wrote: > That's a greeting, a welcoming back. You know, you're with friends, you get > some money together, one of you goes to the store to grab a few beers, he > comes back, "Ah, and you're back, and you bought enough

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On 5/14/18, Derek Buitenhuis wrote: >>> Lies, Lies and Lies. >> >> >> I don't think it's a good thing to call a dev a liar based on limited >> available information. If you have doubts, you can express it as such, but >> don't assert doubts as truths. > > Hmm... there

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On Mon, 14 May 2018 17:50:25 +0100 Derek Buitenhuis wrote: > Hello all. > > This is a little rambling / stream of thought, but take it as you will, > and perhaps some discussion or change comes of it. Or, more likely, personal > attacks, flames, and no change. Or 1

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On 5/14/2018 1:50 PM, Derek Buitenhuis wrote: > Hello all. > > This is a little rambling / stream of thought, but take it as you will, > and perhaps some discussion or change comes of it. Or, more likely, personal > attacks, flames, and no change. Or 1 few will reply and then the thread will >

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On 14 May 2018 at 17:50, Derek Buitenhuis wrote: > Hello all. > > This is a little rambling / stream of thought, but take it as you will, > and perhaps some discussion or change comes of it. Or, more likely, > personal > attacks, flames, and no change. Or 1 few will

[FFmpeg-devel] [RFC][PATCH][Type 2] Revert "doc/developer.texi: Add a code of conduct"

It was never enforced, and there is no documented way to enforce it, rendering it useless. This reverts commit 89e9393022373bf97d528e6e9f2601ad0b3d0fc1. --- doc/developer.texi | 29 - 1 file changed, 29 deletions(-) diff --git a/doc/developer.texi

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On 5/14/18, Derek Buitenhuis wrote: > Hello all. > > This is a little rambling / stream of thought, but take it as you will, > and perhaps some discussion or change comes of it. Or, more likely, personal > attacks, flames, and no change. Or 1 few will reply and then

[FFmpeg-devel] [RFC][PATCH][Type 1] developers: Add a section on CoC enforcemnet

This is currently directly copied from the VideoLAN CoC[1] in order to spur discussion. [1] https://wiki.videolan.org/Code_of_Conduct/#Disciplinary_actions Signed-off-by: Derek Buitenhuis --- doc/developer.texi | 83

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

Hi, On Mon, May 14, 2018 at 12:58 PM, Paul B Mahol wrote: > On 5/14/18, Derek Buitenhuis wrote: > > Hello all. > > > > This is a little rambling / stream of thought, but take it as you will, > > and perhaps some discussion or change comes of it.

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On 14 May 2018 at 18:45, Derek Buitenhuis wrote: > On Mon, May 14, 2018 at 6:28 PM, Rostislav Pehlivanov > wrote: > > iive just noticed you joined, said hi, and you left saying you were > > attacked. Since when is a normal form of welcoming back

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On 5/14/2018 3:10 PM, Rostislav Pehlivanov wrote: > On 14 May 2018 at 18:45, Derek Buitenhuis > wrote: > >> On Mon, May 14, 2018 at 6:28 PM, Rostislav Pehlivanov >> wrote: >>> iive just noticed you joined, said hi, and you left saying you were

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On Mon, May 14, 2018 at 6:24 PM, James Almer wrote: > As it currently stands, the only way to enforce the CoC is with a vote, > from a committee made from a list of ~20 devs about three or so years > ago who may or may not still be active, and who may or may not even know >

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

>> Lies, Lies and Lies. > > > I don't think it's a good thing to call a dev a liar based on limited > available information. If you have doubts, you can express it as such, but > don't assert doubts as truths. Hmm... there must be some reason that people continue ad hominem attacks even though we

Re: [FFmpeg-devel] [PATCH] libavformat: add mbedTLS based TLS

Hi all, I am an engineer working at Manything (https://manything.com). We develop software that allows users to view their security cameras over the Internet. Thomas has been working with us to develop this mbedTLS integration. Thanks for your feedback on his patch; we have run some tests that I

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

Hello, On Mon, 14 May 2018, at 19:28, Rostislav Pehlivanov wrote: > 2's a nice option. The recent llvm fiasco demonstrated the dangers of CoCs > being used by the wrong people. This is the danger with very political and very vague CoC, emphasing on "political correctness", like LLVM's

Re: [FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

On Mon, May 14, 2018 at 6:28 PM, Rostislav Pehlivanov wrote: > iive just noticed you joined, said hi, and you left saying you were > attacked. Since when is a normal form of welcoming back considered an > attack? I agree with jamrial, you definitely overreacted. If you

Re: [FFmpeg-devel] [PATCH] libavformat: add mbedTLS based TLS

> Have you considered BearSSL? Thanks Nicolas; it sounds great but we disregarded it because the web site declares it to be beta-quality. We will certainly keep an eye on it. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

[FFmpeg-devel] [PATCH]configure: Support libxml2 on systems without pkg-config

Hi! Attached patch allows to easily enable the dash demuxer on systems without pkg-config. Please comment, Carl Eugen From 896d75ec2c78580fbf65bc6718f205060afac215 Mon Sep 17 00:00:00 2001 From: Carl Eugen Hoyos Date: Mon, 14 May 2018 20:56:37 +0200 Subject: [PATCH]

[FFmpeg-devel] [PATCH 1/3] hwcontext: Do not call device_init again when deriving an existing device

The change in 309d660775e2b47af6723a0477c4d753bc0c54f4 to call device_init when doing derivation missed this case - we should only call it if we actually made a new device. --- libavutil/hwcontext.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/libavutil/hwcontext.c

[FFmpeg-devel] [PATCH 2/3] lavu/Makefile: Fix alignment and ordering

--- libavutil/Makefile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/libavutil/Makefile b/libavutil/Makefile index a63ba523c9..4fe470748c 100644 --- a/libavutil/Makefile +++ b/libavutil/Makefile @@ -160,14 +160,14 @@ OBJS = adler32.o

[FFmpeg-devel] [PATCH] configure: error out on unsupported MSVC versions

The FATE tests for MSVC versions older than 2013 are untested in FATE and apparently are no longer supported. This commit makes the configure process error out in case an older version is used, and suggests to use a supported version of MSVC to compile. As discussed on IRC: 2018-05-12 19:45:16

Re: [FFmpeg-devel] [PATCH] doc/developer: update style guidelines to include for loops with declarations

On 12 May 2018 at 20:49, Rostislav Pehlivanov wrote: > > > On 8 November 2017 at 21:26, Rostislav Pehlivanov > wrote: > >> Signed-off-by: Rostislav Pehlivanov >> --- >> doc/developer.texi | 3 +++ >> 1 file changed, 3

[FFmpeg-devel] [PATCH] lavc/amfenc: moving amf common code (library and context) to lavu/hwcontext_amf from amfenc to be reused in other amf components

This patch moves AMF common parts from amfenc to hwcontext_amf. Now av_hwdevice_ctx API is used for AMF context creation/destroying. This patch does not change component behaviour. it contains only restructurization for further patches with new amf components --- Sending updated patch based on

Re: [FFmpeg-devel] [PATCH] doc/developer: update style guidelines to include for loops with declarations

On 14/05/18 22:38, Rostislav Pehlivanov wrote: > On 12 May 2018 at 20:49, Rostislav Pehlivanov wrote: >> On 8 November 2017 at 21:26, Rostislav Pehlivanov >> wrote: >> >>> Signed-off-by: Rostislav Pehlivanov >>> --- >>>

[FFmpeg-devel] [PATCH v6 2/3] avcodec/bitpacked: add interlace support

From: Damien Riegel This codec is already capable of depacking some combinations of pixel formats and depth as defined in the RFC4175. The only difference between progressive and interlace is that either a packet will contain the whole frame, or only a field

Re: [FFmpeg-devel] [PATCH] doc/developer: update style guidelines to include for loops with declarations

On 14/05/18 23:30, Rostislav Pehlivanov wrote: > On 14 May 2018 at 22:57, Mark Thompson wrote: >> On 14/05/18 22:38, Rostislav Pehlivanov wrote: >>> On 12 May 2018 at 20:49, Rostislav Pehlivanov >> wrote: On 8 November 2017 at 21:26, Rostislav Pehlivanov

Re: [FFmpeg-devel] [PATCH] doc/developer: update style guidelines to include for loops with declarations

On Tue, May 15, 2018 at 12:30 AM, Rostislav Pehlivanov wrote: > On 14 May 2018 at 22:57, Mark Thompson wrote: > >> On 14/05/18 22:38, Rostislav Pehlivanov wrote: >> > On 12 May 2018 at 20:49, Rostislav Pehlivanov >> wrote: >> >> On 8

Re: [FFmpeg-devel] [PATCH] doc/developer: update style guidelines to include for loops with declarations

On 14 May 2018 at 23:59, Hendrik Leppkes wrote: > On Tue, May 15, 2018 at 12:30 AM, Rostislav Pehlivanov > wrote: > > On 14 May 2018 at 22:57, Mark Thompson wrote: > > > >> On 14/05/18 22:38, Rostislav Pehlivanov wrote: > >> > On 12 May

Re: [FFmpeg-devel] [PATCH] doc/developer: update style guidelines to include for loops with declarations

On 14 May 2018 at 22:57, Mark Thompson wrote: > On 14/05/18 22:38, Rostislav Pehlivanov wrote: > > On 12 May 2018 at 20:49, Rostislav Pehlivanov > wrote: > >> On 8 November 2017 at 21:26, Rostislav Pehlivanov > >> wrote: > >> > >>>

[FFmpeg-devel] [PATCH] avformat/mpegts: add merge_pmt_versions option

From: Aman Gupta This new optional flag makes it easier to deal with mpegts samples where the PMT is updated and elementary streams move to different PIDs in the middle of playback. Previously, new AVStreams were created per PID, and it was up to the user to figure out which

Re: [FFmpeg-devel] libavutil/encryption_info: Allow multiple init info.

On Tue, May 8, 2018 at 3:47 PM, Michael Niedermayer wrote: > On Mon, May 07, 2018 at 04:59:33PM -0700, Jacob Trimble wrote: >> On Mon, May 7, 2018 at 3:18 PM, Michael Niedermayer >> wrote: >> > On Mon, Apr 23, 2018 at 11:03:57AM -0700, Jacob

[FFmpeg-devel] [PATCH] avutil/hwcontext_cuda: fix YUV420P cuda_get_buffer

Regression since ece068a771ac3f725e854c681ecbef08e792addc. Signed-off-by: Marton Balint --- libavutil/hwcontext_cuda.c | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/libavutil/hwcontext_cuda.c b/libavutil/hwcontext_cuda.c index

[FFmpeg-devel] [PATCH 3/3] hwcontext: Add test for device creation and derivation

This uses any devices it can find on the host system - on a system with no hardware device support or in builds with no support included it will do nothing and pass. --- libavutil/Makefile | 1 + libavutil/tests/hwdevice.c | 234 +

[FFmpeg-devel] [PATCH v6 1/3] avcodec: add flags for packets with top/bottom field

Signed-off-by: Patrick Keroulas --- doc/APIchanges | 3 +++ libavcodec/avcodec.h | 8 libavcodec/version.h | 4 ++-- 3 files changed, 13 insertions(+), 2 deletions(-) diff --git a/doc/APIchanges b/doc/APIchanges index bbefc83..d06868e 100644

[FFmpeg-devel] [PATCH v6 3/3] avformat/rtpdec_rfc4175: handle interlace format

From: Damien Riegel In order to handle the interlaced formats, the demuxer has only a few things to do: - parse the SDP correctly and propagate the information - check the field bit in the RFC4175 header, and pass that information to the decoder In

Re: [FFmpeg-devel] [PATCH] configure: error out on unsupported MSVC versions

On Tue, May 15, 2018 at 12:57:00AM +0100, Rostislav Pehlivanov wrote: > The FATE tests for MSVC versions older than 2013 are untested in FATE > and apparently are no longer supported. > > This commit makes the configure process error out in case an older version > is used, and suggests to use a

Re: [FFmpeg-devel] [PATCH 3/3] hwcontext: Add test for device creation and derivation

On Mon, 2018-05-14 at 22:58 +0100, Mark Thompson wrote: > This uses any devices it can find on the host system - on a system with no > hardware device support or in builds with no support included it will do > nothing and pass. > --- > libavutil/Makefile | 1 + >

Re: [FFmpeg-devel] [PATCH 3/3] hwcontext: Add test for device creation and derivation

On Mon, May 14, 2018 at 10:58:58PM +0100, Mark Thompson wrote: > This uses any devices it can find on the host system - on a system with no > hardware device support or in builds with no support included it will do > nothing and pass. > --- > libavutil/Makefile | 1 + >

Re: [FFmpeg-devel] [PATCH 1/3] hwcontext: Do not call device_init again when deriving an existing device

2018-05-15 5:58 GMT+08:00 Mark Thompson : > The change in 309d660775e2b47af6723a0477c4d753bc0c54f4 to call device_init > when doing derivation missed this case - we should only call it if we > actually made a new device. > --- > libavutil/hwcontext.c | 7 +++ > 1 file changed,

Re: [FFmpeg-devel] [PATCH 3/3] hwcontext: Add test for device creation and derivation

On 5/14/2018 6:58 PM, Mark Thompson wrote: > This uses any devices it can find on the host system - on a system with no > hardware device support or in builds with no support included it will do > nothing and pass. > --- I'd rather not have a fate test try to run anything on my GPU. It's usually

[FFmpeg-devel] [PATCH v2] configure: error out on unsupported MSVC versions

The FATE tests for MSVC versions older than 2013 are untested in FATE and apparently are no longer supported. This commit makes the configure process error out in case an older version is used, and suggests to use a supported version of MSVC to compile. As discussed on IRC: 2018-05-12 19:45:16

Re: [FFmpeg-devel] [PATCH] qsv: Use the installed mfx include headers if possibile

> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf > Of Xiang, Haihao > Sent: Monday, May 14, 2018 10:38 AM > To: ffmpeg-devel@ffmpeg.org > Subject: Re: [FFmpeg-devel] [PATCH] qsv: Use the installed mfx include > headers if possibile > > On Mon, 2018-05-14 at 00:50 +,