On Mon, Apr 16, 2018 at 1:24 PM, Michael Niedermayer
wrote:
> On Sat, Apr 14, 2018 at 02:04:43PM +0200, Michael Niedermayer wrote:
>> On Fri, Apr 13, 2018 at 12:53:08AM +0200, Michael Niedermayer wrote:
>> > On Mon, Feb 19, 2018 at 02:50:08AM +0100, Michael Niedermayer
On Wed, Apr 18, 2018 at 4:34 PM, Hendrik Leppkes wrote:
> Without properly grouping the checks, the second test would execute for
> MSVC cl.exe, which results in configure getting stuck since cl.exe -? is
> an interactive paginated help screen, waiting for input.
> ---
>
Without properly grouping the checks, the second test would execute for
MSVC cl.exe, which results in configure getting stuck since cl.exe -? is
an interactive paginated help screen, waiting for input.
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure
From: Karthick Jeyapal
There is a separate muxer(webmdashenc.c) for supporting VP9+webm output in DASH.
Hence in this muxer we will focus on supporting VP9 in MP4
Have verified playout support of VP9+MP4 in Chrome and Firefox.
---
libavformat/dashenc.c | 3 +--
1 file
From: Karthick Jeyapal
Otherwise some versions of chrome browser returns "codec not supported" error
---
libavformat/dashenc.c | 79 ++-
1 file changed, 78 insertions(+), 1 deletion(-)
diff --git a/libavformat/dashenc.c
On 18 April 2018 at 03:46, Steven Liu wrote:
>
>
> > On 18 Apr 2018, at 09:01, Richard Shaffer wrote:
> >
> > On Mon, Apr 16, 2018 at 10:24 PM, Steven Liu wrote:
> >
> >>
> >>
> >>> On 16 Apr 2018, at 08:37, Jun Zhao
Should be useful for muxers that require values as defined in the
vpcc atom but don't need to write the atom itself.
Signed-off-by: James Almer
---
libavformat/vpcc.c | 29 -
libavformat/vpcc.h | 11 +++
2 files changed, 35 insertions(+), 5
On 4/18/2018 4:38 PM, Paul B Mahol wrote:
+@item alpha
+@item beta
+@item gamma
+@item delta
+Set blocking detection thresholds. Allowed range is 0 to 1.
+Defaults are: @var{0.098} for @var{alpha} and @var{0.05} for the rest.
+Using higher threshold gives more deblocking strength.
+Setting
On 17.04.2018 19:42, Thomas Mundt wrote:
Please do also remove interlace.h and x86/vf_interlace_init.c. Adapt
x86/Makefile accordingly.
Otherwise the patch is ok.
When sending the LGPL vf_reinterlace patch, please do also send a patch
that renames vf_reinterlace to vf_tinterlace and replaces
Signed-off-by: Paul B Mahol
---
doc/filters.texi | 59 +++
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/vf_deblock.c | 409 +++
4 files changed, 470 insertions(+)
create mode 100644
On 4/18/18, Vasile Toncu wrote:
>
>
> On 17.04.2018 19:42, Thomas Mundt wrote:
>>
>> Please do also remove interlace.h and x86/vf_interlace_init.c. Adapt
>> x86/Makefile accordingly.
>> Otherwise the patch is ok.
>>
>> When sending the LGPL vf_reinterlace patch, please
On 4/18/2018 9:03 AM, Karthick J wrote:
> From: Karthick Jeyapal
>
> Otherwise some versions of chrome browser returns "codec not supported" error
> ---
> libavformat/dashenc.c | 79
> ++-
> 1 file changed, 78 insertions(+),
---
libavformat/tls_schannel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/tls_schannel.c b/libavformat/tls_schannel.c
index 9a6e0c92e3..3986b88667 100644
--- a/libavformat/tls_schannel.c
+++ b/libavformat/tls_schannel.c
@@ -515,7 +515,7 @@ cleanup:
if
On Mon, Apr 16, 2018 at 03:53:23PM +0200, Matthieu Bouron wrote:
> On Wed, Apr 11, 2018 at 3:14 PM, Matthieu Bouron
> wrote:
>
> > Fixes decoding on the Samsung Chromebook Pro which do not set the codec
> > output format stride and slice-height fields.
> > ---
> >
On Tue, Apr 17, 2018 at 7:11 PM, Michael Niedermayer
wrote:
> On Tue, Apr 03, 2018 at 04:08:51PM -0700, Jacob Trimble wrote:
>> >>
>> >> Ping again. I know this is low priority, but I would like to get
>> >> these merged soon.
>> >
>> > Ping. Despite being almost 2
On Wed, 18 Apr 2018 14:10:03 +0200
Hendrik Leppkes wrote:
> ---
> libavformat/tls_schannel.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/tls_schannel.c b/libavformat/tls_schannel.c
> index 9a6e0c92e3..3986b88667 100644
> ---
On Wed, Apr 18, 2018 at 01:08:07PM +0200, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> doc/filters.texi | 59 +++
> libavfilter/Makefile | 1 +
> libavfilter/allfilters.c | 1 +
> libavfilter/vf_deblock.c | 409
>
On Wed, Apr 18, 2018 at 08:28:05AM +0200, Łukasz Krzciuk wrote:
> Any updates on this?
has someone crosschecked this with the spec ?
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Many that live deserve death. And some that die deserve life. Can you give
it to
On Wed, 18 Apr 2018 23:01:00 +0200
Nicolas George wrote:
> wm4 (2018-04-18):
> > There was a simple patch that would have solved that issue locally in
> > the UDP code.
>
> This is not true. The patch would have fixed the author's use case but
> would have broken all
On 4/18/18, Michael Niedermayer wrote:
> On Wed, Apr 18, 2018 at 01:08:07PM +0200, Paul B Mahol wrote:
>> Signed-off-by: Paul B Mahol
>> ---
>> doc/filters.texi | 59 +++
>> libavfilter/Makefile | 1 +
>> libavfilter/allfilters.c |
On Wed, 18 Apr 2018 23:35:11 +0200
Nicolas George wrote:
> wm4 (2018-04-18):
> > Like I said, this didn't even work. And the EOF behavior was changed
> > anyway, how is that not an API break? That change also broke a whole
> > lot of other things, so I can't quite understand
On Tue, Apr 17, 2018 at 11:47:00AM -0400, Vittorio Giovara wrote:
> - enable the parsing code
> - use the new buffer instead of replacing the context one
> - do not push/pop configuration, just discard the exiting one
> - propagate errors correctly
> ---
>
> ping
>
>
>
Jan Ekström (2018-04-18):
> While I have kind of felt like this for a while now, I am just not
> sure if we can find all the things where with or without mention
> things have been poked to fix issues with it, which would now have to
> all be reverted. Also we already angered API users once with
On Tue, Apr 17, 2018 at 09:50:15PM +0200, Marton Balint wrote:
>
>
> On Tue, 17 Apr 2018, Michael Niedermayer wrote:
>
> >On Tue, Apr 17, 2018 at 01:27:48AM +0200, Marton Balint wrote:
> >>
> >>
> >>On Mon, 16 Apr 2018, Michael Niedermayer wrote:
> >>
> >>>Hi
> >>>
> >>>On Sat, Nov 04, 2017 at
On Wed, 18 Apr 2018 22:50:19 +0200
Nicolas George wrote:
> Jan Ekström (2018-04-18):
> > While I have kind of felt like this for a while now, I am just not
> > sure if we can find all the things where with or without mention
> > things have been poked to fix issues with it,
wm4 (2018-04-18):
> There was a simple patch that would have solved that issue locally in
> the UDP code.
This is not true. The patch would have fixed the author's use case but
would have broken all applications that rely on empty UDP packets. Since
it is about public API, we cannot assume
On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes wrote:
> On Mon, Apr 16, 2018 at 1:24 PM, Michael Niedermayer
> wrote:
> > On Sat, Apr 14, 2018 at 02:04:43PM +0200, Michael Niedermayer wrote:
> >> On Fri, Apr 13, 2018 at 12:53:08AM +0200, Michael Niedermayer
On Wed, 18 Apr 2018 23:21:30 +0200
Nicolas George wrote:
> wm4 (2018-04-18):
> > Which applications (in context of FFmpeg) need to detect empty UDP
> > packets? Which applications would be broken by a trivial patch in the
> > UDP code?
>
> One last time: this is public API:
wm4 (2018-04-18):
> Like I said, this didn't even work. And the EOF behavior was changed
> anyway, how is that not an API break? That change also broke a whole
> lot of other things, so I can't quite understand your argument here. In
> fact, you should have rejected the EOF change patch which you
On Tue, Apr 17, 2018 at 08:59:48PM +0100, Derek Buitenhuis wrote:
> The track's media duration from the mdhd atom takes precedence
> over both the stts and elst atom for calculating and setting
> the track's total duraion.
>
> Technically, we shouldn't be using the stts atom at all for
>
On Wed, 18 Apr 2018 23:15:47 +0200
Michael Niedermayer wrote:
> On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes wrote:
> > On Mon, Apr 16, 2018 at 1:24 PM, Michael Niedermayer
> > wrote:
> > > On Sat, Apr 14, 2018 at 02:04:43PM +0200,
On Tue, Apr 17, 2018 at 08:48:23PM +0900, Yuusei KUWANA wrote:
>
> avformat/mpegts: also ignore new stream in PMT while seeking
>
> Signed-off-by: Yuusei KUWANA
> ---
> libavformat/mpegts.c | 4
> 1 file changed, 4 insertions(+)
This causes a regression with
On Sun, 15 Apr 2018, Marton Balint wrote:
Show a more useful error message which specifies the required driver version
for the build, and use the correct context in the error message for WIN32.
Signed-off-by: Marton Balint
---
libavdevice/decklink_common.cpp | 28
On Wed, Apr 18, 2018 at 11:11:30PM +0200, Paul B Mahol wrote:
> On 4/18/18, Michael Niedermayer wrote:
> > On Wed, Apr 18, 2018 at 01:08:07PM +0200, Paul B Mahol wrote:
> >> Signed-off-by: Paul B Mahol
> >> ---
> >> doc/filters.texi | 59
wm4 (2018-04-18):
> Which applications (in context of FFmpeg) need to detect empty UDP
> packets? Which applications would be broken by a trivial patch in the
> UDP code?
One last time: this is public API: any existing application can rely on
it. Including unpublished applications. This patch
On 4/18/18, wm4 wrote:
> On Wed, 18 Apr 2018 23:15:47 +0200
> Michael Niedermayer wrote:
>
>> On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes wrote:
>> > On Mon, Apr 16, 2018 at 1:24 PM, Michael Niedermayer
>> >
2018-04-16 1:08 GMT+02:00, James Almer :
> On 4/15/2018 7:00 PM, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch is supposed to silence several user-reported warnings,
>> I cannot currently test here.
>>
>> Please review, Carl Eugen
>>
>>
>>
On Wed, Apr 18, 2018 at 7:53 PM, wm4 wrote:
>
> Maybe we should consider reverting this whole avio EOF change for the
> release? So many breakages...
While I have kind of felt like this for a while now, I am just not
sure if we can find all the things where with or without
2018-04-16 0:19 GMT+02:00, Carl Eugen Hoyos :
> Hi!
>
> rtmpe_write() exploits knowledge about av_rc4_crypt() internals and
> passes the same
> pointer as src and dst. I assume this is intentional for performance
> reasons, the only
> way to silence the resulting warning is a
Fixes part of ticket #7146.
Signed-off-by: James Almer
---
libavdevice/iec61883.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavdevice/iec61883.c b/libavdevice/iec61883.c
index b09929eb56..dcf7553926 100644
--- a/libavdevice/iec61883.c
+++ b/libavdevice/iec61883.c
Fixes part of ticket #7146, dealing with leaks of packet data since
commit 87c88122703f2befcf96383d05bdf14373c22df9.
Signed-off-by: James Almer
---
libavdevice/iec61883.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git
tis 2018-04-17 klockan 14:24 +0200 skrev Michael Niedermayer:
> On Tue, Apr 17, 2018 at 10:32:16AM +0200, Tomas Härdin wrote:
> > tis 2018-04-17 klockan 02:13 +0200 skrev Michael Niedermayer:
> > > Speeds up decoding from 8 to 3 seconds for 6302/clusterfuzz-
> > >
2018-04-18 21:10 GMT+02:00, James Almer :
> On 4/18/2018 2:45 PM, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch is supposed to fix a warning (and a bug), is this the
>> right and preferred fix?
>>
>> Please comment, Carl Eugen
>>
>>
>>
---
libavformat/tls_schannel.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/libavformat/tls_schannel.c b/libavformat/tls_schannel.c
index 9a6e0c92e3..f41b007773 100644
--- a/libavformat/tls_schannel.c
+++ b/libavformat/tls_schannel.c
@@ -413,11 +413,13 @@ static
On 4/18/2018 3:34 PM, Jan Ekström wrote:
> On Wed, Apr 18, 2018 at 7:53 PM, wm4 wrote:
>>
>> Maybe we should consider reverting this whole avio EOF change for the
>> release? So many breakages...
>
> While I have kind of felt like this for a while now, I am just not
> sure
On Wed, 18 Apr 2018 15:46:55 -0300
James Almer wrote:
> On 4/18/2018 3:34 PM, Jan Ekström wrote:
> > On Wed, Apr 18, 2018 at 7:53 PM, wm4 wrote:
> >>
> >> Maybe we should consider reverting this whole avio EOF change for the
> >> release? So many
On Wed, 18 Apr 2018 21:52:45 +0200
Carl Eugen Hoyos wrote:
> From cf7d2aefc1a3b3a2e9f578ede43906ed6ee96bfd Mon Sep 17 00:00:00 2001
> From: Carl Eugen Hoyos
> Date: Wed, 18 Apr 2018 19:42:57 +0200
> Subject: [PATCH] lavf/dashdec: Do not use memcpy() to
2018-04-16 0:57 GMT+02:00, James Almer :
> On 4/15/2018 7:03 PM, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch is supposed to silence a user-reported warning, I
>> cannot currently test.
>>
>> libavdevice/vfwcap.c: In function 'vfw_read_header':
>>
On Wed, Apr 18, 2018 at 3:10 PM, Hendrik Leppkes wrote:
> ---
> libavformat/tls_schannel.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/tls_schannel.c b/libavformat/tls_schannel.c
> index 9a6e0c92e3..3986b88667 100644
> ---
On Wed, Apr 18, 2018 at 3:03 PM, Karthick J wrote:
> From: Karthick Jeyapal
>
> There is a separate muxer(webmdashenc.c) for supporting VP9+webm output in
> DASH.
> Hence in this muxer we will focus on supporting VP9 in MP4
> Have verified playout
On Wed, 18 Apr 2018 16:10:26 -0300
James Almer wrote:
> On 4/18/2018 2:45 PM, Carl Eugen Hoyos wrote:
> > Hi!
> >
> > Attached patch is supposed to fix a warning (and a bug), is this the
> > right and preferred fix?
> >
> > Please comment, Carl Eugen
> >
> >
> >
From: Misty De Meo
This improves on the previous patch by using the data defined in the
container rather than by calculating the duration by iterating over
packets.
Misty De Meo (1):
segafilm: fetch duration from the container
libavformat/segafilm.c | 20
Hi!
Attached patch is supposed to fix a warning (and a bug), is this the
right and preferred fix?
Please comment, Carl Eugen
From cf7d2aefc1a3b3a2e9f578ede43906ed6ee96bfd Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Wed, 18 Apr 2018 19:42:57 +0200
Subject: [PATCH]
2018-04-16 1:33 GMT+02:00, Carl Eugen Hoyos :
> Hi!
>
> Attached patch is supposed to silence a user-reported warning when
> inet_aton() is missing but getaddrinfo() is supported.
> Untested.
Ping?
Thank you, Carl Eugen
___
On 4/18/2018 2:45 PM, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch is supposed to fix a warning (and a bug), is this the
> right and preferred fix?
>
> Please comment, Carl Eugen
>
>
> 0001-lavf-dashdec-Do-not-use-memcpy-to-copy-a-struct.patch
>
>
> From
On Wed, Apr 18, 2018 at 9:37 PM, Hendrik Leppkes wrote:
> ---
> libavformat/tls_schannel.c | 10 ++
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/libavformat/tls_schannel.c b/libavformat/tls_schannel.c
> index 9a6e0c92e3..f41b007773 100644
> ---
From: Misty De Meo
---
libavformat/segafilm.c | 20 +++-
1 file changed, 3 insertions(+), 17 deletions(-)
diff --git a/libavformat/segafilm.c b/libavformat/segafilm.c
index e72c26b144..1529fc385e 100644
--- a/libavformat/segafilm.c
+++
>
>
> -elif $_cc -nologo- 2>&1 | grep -q Microsoft; then
> +elif $_cc -nologo- 2>&1 | grep -q Microsoft || $_cc -v 2>&1 | grep -q
> clang && $_cc -? > /dev/null 2>&1; then
> _type=msvc
> _ident=$($_cc 2>&1 | head -n1)
> _DEPCMD='$(DEP$(1)) $(DEP$(1)FLAGS)
Hello Sir,
I have implemented the suggested changes, now the filter does not break
builds, also now it works for all inputs and
ffplay -f lavfi -i testsrc -vf hellosubs
works.
Sir I think passing the text using metadata to drawtext filter would not be
an efficient way in terms of time as
Any updates on this?
Regards,
*Łukasz Krzciuk*
Developer
Vewd
ul. Grabarska 2, Pegaz 2A, 50-079 Wrocław, Polska
On Mon, Apr 16, 2018 at 9:16 AM, Łukasz Krzciuk wrote:
> I agree, AV_LOG_INFO has been changed to AV_LOG_DEBUG.
>
> Regards,
>
> *Łukasz Krzciuk*
> Developer
>
2018-04-18 16:27 GMT+08:00 Timo Rothenpieler :
> On 18.04.2018 10:05, Wang Bin wrote:
> >>
> >>
> >> -elif $_cc -nologo- 2>&1 | grep -q Microsoft; then
> >> +elif $_cc -nologo- 2>&1 | grep -q Microsoft || $_cc -v 2>&1 | grep
> -q
> >> clang && $_cc -? > /dev/null
On 18.04.2018 10:05, Wang Bin wrote:
>>
>>
>> -elif $_cc -nologo- 2>&1 | grep -q Microsoft; then
>> +elif $_cc -nologo- 2>&1 | grep -q Microsoft || $_cc -v 2>&1 | grep -q
>> clang && $_cc -? > /dev/null 2>&1; then
>> _type=msvc
>> _ident=$($_cc 2>&1 | head -n1)
>>
On Thu, Feb 1, 2018 at 11:52 AM, Alexander Bilyak
wrote:
> When using clang-cl it expects parameters passed in MSVC-style, so
> appropriate toolchain should be selected.
> As soon as both clang and clang-cl report themselfs as "clang" with -v option
> the only chance
On 4/18/18 7:12 PM, James Almer wrote:
> On 4/18/2018 9:03 AM, Karthick J wrote:
> > From: Karthick Jeyapal
> >
> > Otherwise some versions of chrome browser returns "codec not supported"
> > error
> > ---
> > libavformat/dashenc.c | 79
> >
On 4/19/18 12:23 AM, Jan Ekström wrote:
>On Wed, Apr 18, 2018 at 3:03 PM, Karthick J wrote:
>> From: Karthick Jeyapal
>>
>> There is a separate muxer(webmdashenc.c) for supporting VP9+webm output in
>> DASH.
>> Hence in this muxer we will focus on
On Wed, 18 Apr 2018, Michael Niedermayer wrote:
On Tue, Apr 17, 2018 at 09:50:15PM +0200, Marton Balint wrote:
On Tue, 17 Apr 2018, Michael Niedermayer wrote:
On Tue, Apr 17, 2018 at 01:27:48AM +0200, Marton Balint wrote:
On Mon, 16 Apr 2018, Michael Niedermayer wrote:
Hi
On Sat,
On Wed, Apr 18, 2018 at 11:55:09PM +0200, Paul B Mahol wrote:
> On 4/18/18, wm4 wrote:
> > On Wed, 18 Apr 2018 23:15:47 +0200
> > Michael Niedermayer wrote:
> >
> >> On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes wrote:
> >> > On Mon, Apr
On Tue, Apr 17, 2018 at 12:36:45PM -0700, Rahul Chaudhry wrote:
> On Tue, Apr 17, 2018 at 6:17 AM, Michael Niedermayer
> wrote:
> > why does it go through the PLT at all ?
>
> You're right. The branches don't have to go through the PLT at all.
>
> Here's an alternate
On Thu, 19 Apr 2018 00:40:21 +0200
Michael Niedermayer wrote:
> On Wed, Apr 18, 2018 at 11:55:09PM +0200, Paul B Mahol wrote:
> > On 4/18/18, wm4 wrote:
> > > On Wed, 18 Apr 2018 23:15:47 +0200
> > > Michael Niedermayer
On Thu, Apr 19, 2018 at 12:56:05AM +0200, wm4 wrote:
> On Thu, 19 Apr 2018 00:40:21 +0200
> Michael Niedermayer wrote:
>
> > On Wed, Apr 18, 2018 at 11:55:09PM +0200, Paul B Mahol wrote:
> > > On 4/18/18, wm4 wrote:
> > > > On Wed, 18 Apr 2018
On Thu, Apr 19, 2018 at 12:35 AM, Michael Niedermayer
wrote:
>
> This breaks fate: (have not tested anything beyond this)
>
> TESTadtstoasc_ticket3715
> --- ./tests/ref/fate/adtstoasc_ticket3715 2018-04-17 14:20:30.500366780
> +0200
> +++
On Tue, 17 Apr 2018 14:49:48 +0200
Michael Niedermayer wrote:
> On Tue, Apr 17, 2018 at 01:27:48AM +0200, Marton Balint wrote:
> >
> >
> > On Mon, 16 Apr 2018, Michael Niedermayer wrote:
> >
> > >Hi
> > >
> > >On Sat, Nov 04, 2017 at 06:28:58PM +, Marton Balint
Hi.
Can I improve something here?
On Fri, Mar 30, 2018 at 2:43 AM, Rostislav Pehlivanov
wrote:
> On 30 March 2018 at 00:12, Даниил Чередник
> wrote:
>
> > Actually this test does not make a sense since encoder now use floating
> > point math. I
On Wed, Apr 18, 2018 at 3:46 PM, Michael Niedermayer
wrote:
> please make sure this works on apple based arm (unless you know it works)
> (ive tested qemu linux based)
>
> Also please add a commit message
If by 'apple based arm' you mean llvm/clang assembler, then yes,
> On 19 Apr 2018, at 03:20, wm4 wrote:
>
> On Wed, 18 Apr 2018 16:10:26 -0300
> James Almer wrote:
>
>> On 4/18/2018 2:45 PM, Carl Eugen Hoyos wrote:
>>> Hi!
>>>
>>> Attached patch is supposed to fix a warning (and a bug), is this the
>>> right and
On Tue, Apr 17, 2018 at 11:45:08PM +0200, Stephan Holljes wrote:
> On Fri, Mar 30, 2018 at 3:13 PM, Stephan Holljes
> wrote:
> > On Fri, Jan 12, 2018 at 8:47 PM, Michael Niedermayer
> > wrote:
> >> On Fri, Jan 12, 2018 at 07:16:30PM +0100,
On Tue, Apr 17, 2018 at 11:45:38PM +0200, Stephan Holljes wrote:
> On Thu, Apr 12, 2018 at 2:07 AM, Stephan Holljes
> wrote:
> > ---
> > I found this bug while working on my qualification task. When closing
> > a listening HTTP AVIOContext http_shutdown() tries to write
On 4/18/2018 3:41 PM, James Almer wrote:
> Fixes part of ticket #7146, dealing with leaks of packet data since
> commit 87c88122703f2befcf96383d05bdf14373c22df9.
>
> Signed-off-by: James Almer
> ---
> libavdevice/iec61883.c | 17 +
> 1 file changed, 13
On Wed, Apr 18, 2018 at 09:47:17AM -0700, Jacob Trimble wrote:
> On Tue, Apr 17, 2018 at 7:11 PM, Michael Niedermayer
> wrote:
> > On Tue, Apr 03, 2018 at 04:08:51PM -0700, Jacob Trimble wrote:
> >> >>
> >> >> Ping again. I know this is low priority, but I would like to
> Note that OpenCL <-> D3D11 won't work on AMD for normal video surfaces
> (NV12) because there is no support for multiple-plane textures, so it's only
> going
> to work with DXVA2 currently. Intel has an extension
> ("cl_intel_d3d11_nv12_media_sharing") which adds a simple hack overloading
>
80 matches
Mail list logo