2016-08-24 23:24 GMT+02:00 Oliver Collyer :
> In summary (and this ties-in with the NVidia documentation which
> details the steps for 10-bit encoding):
>
> a) to get 10-bit encoding you need to set up a 10-bit input buffer.
Thank you for the tests!
No more comments from me, I cannot test.
Carl
On Wed, Aug 24, 2016 at 06:42:16PM -0700, Sasi Inguva wrote:
> hmm. strange. I just rebased my branch on top of head, and reran the test,
> and it succeeds along with all other fate tests. I am attaching the 4
> patches again here.
you need to build with
--assert-level=2
to see the failure
[...]
On Wed, Aug 24, 2016 at 10:20:11PM +0800, Steven Liu wrote:
> Making sure bestpos is initialized to zero to prevent gcc from kvetching.
> It's harmless (although it's not obvious that it's harmless)
> from code inspection:
> tests/audiomatch.c: In function ‘main’:
> tests/audiomatch.c:40: warning:
Davinder Singh wrote:
On Tue, Aug 23, 2016 at 5:38 AM Andy Furniss
wrote:
[...]
Nice I can see the edges are better than the last version.
The doc/filters.texi hunk doesn't apply to git master.
I was going to post some comparisons with mcfps tonight, but I'll
need to redo them to see what's
On Mon, Aug 15, 2016 at 07:04:57PM -0700, Sasi Inguva wrote:
> Signed-off-by: Sasi Inguva
> ---
> libavformat/mov.c | 334 +++-
> tests/Makefile |1 +
> tests/fate/mov.mak | 28 +
> tests/ref/fate/
On Wed, Aug 24, 2016 at 09:40:55PM +0800, Steven Liu wrote:
> 2016-08-24 19:14 GMT+08:00 Steven Liu :
>
> >
> >
> > 2016-08-24 18:57 GMT+08:00 Michael Niedermayer :
> >
> >> On Wed, Aug 24, 2016 at 06:28:08PM +0800, Steven Liu wrote:
> >> > 2016-08-24 18:23 GMT+08:00 Michael Niedermayer >> >:
> >
Hi,
patch attached.
0001-avfilter-add-vaguedenoiser-filter.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Wed, Aug 24, 2016 at 03:55:24PM +0100, Derek Buitenhuis wrote:
> This breaks files with legitimate single-entry edit lists,
> and the hack, introduced in f03a081df09f9c4798a17d7e24446ed47924b11b,
> has no link to any known sample in its commit message, nor
> does it actually fix the problem prop
> On 24 Aug 2016, at 20:57, Carl Eugen Hoyos wrote:
>
> Hi!
>
> 2016-08-24 10:00 GMT+02:00 Oliver Collyer :
>> I’m not sure what would happen - currently the nvenc.c code enforces
>> 10-bit encoding when it gets a 10-bit input pixel format.
>
> Yes, my question was about what happens if you re
On Wed, Aug 24, 2016 at 18:57:57 +0200, Paul B Mahol wrote:
> +The @code{yuvtestsrc} source generates an YUV test pattern. You should
^ a
> +see a y, cb and cr stripe from top to bottom.
This makes it sound like the stripes go from top to bottom, i.e.
the
On 8/24/2016 3:11 PM, Orion Poplawski wrote:
> On 08/24/2016 11:54 AM, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> 2016-08-24 18:51 GMT+02:00 Orion Poplawski :
>>> Would the ffmpeg developers be willing treat any particular release as a
>>> long-term-support release and try to do security updates for it
On Wednesday, August 24, 2016, Nicolas George wrote:
> L'octidi 8 fructidor, an CCXXIV, Paul B Mahol a écrit :
> > patch attached.
>
> Does it support pixel formats that testsrc2 does not?
>
>
Because of gradients it creates, afaik it cannot use drawutils.
thus only yuv nonsubsampled are supporte
L'octidi 8 fructidor, an CCXXIV, Paul B Mahol a écrit :
> patch attached.
Does it support pixel formats that testsrc2 does not?
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmp
On 24/08/2016 17:57, Paul B Mahol wrote:
Hi,
patch attached.
This looks fine.
--
Josh
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 8/24/2016 7:00 PM, Carl Eugen Hoyos wrote:
> Does this patch also fix the issue?
> http://ffmpeg.org/pipermail/ffmpeg-devel/2016-August/197817.html
It doesn't. The patch I sent fixes a problem with a current workaround
in the mov demuxer. Edit lists are just one way it could have triggered
it.
On 08/24/2016 11:54 AM, Carl Eugen Hoyos wrote:
> Hi!
>
> 2016-08-24 18:51 GMT+02:00 Orion Poplawski :
>> Would the ffmpeg developers be willing treat any particular release as a
>> long-term-support release and try to do security updates for it?
>
> Could you define "long-term"?
>
> Carl Euge
Hi!
2016-08-24 16:38 GMT+02:00 Burt P. :
> On Tue, Aug 23, 2016 at 2:29 PM, Carl Eugen Hoyos wrote:
>> It seems safer to me to use the actual number of channels than the
>> channel layout.
>
> Alright, new patch version incoming.
No more comments from me.
(I hope you tested it...)
Thank you, Ca
On 8/24/2016 6:50 PM, Carl Eugen Hoyos wrote:
>> This breaks files with legitimate single-entry edit lists,
>> and the hack, introduced in f03a081df09f9c4798a17d7e24446ed47924b11b,
>> has no link to any known sample in its commit message, nor
>
> I suspect the commit message links to this sample:
Hi!
2016-08-24 16:53 GMT+02:00 Erkki Seppälä :
>
> On 08/23/2016 10:00 PM, Carl Eugen Hoyos wrote:
>>>
>>> +if (mov->mode == MODE_MP4 && mov->major_brand)
>>> +ffio_wfourcc(pb, mov->major_brand); /* write major brand as a
>>> compatible brand */
>>
>> How can I reproduce the issue this
2016-08-24 16:44 GMT+02:00 Sasi Inguva :
> ping!
I will apply this if nobody objects.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
2016-08-24 16:55 GMT+02:00 Derek Buitenhuis :
> I am sending this patch in a professional context, as it is
> a problem I have run into at work, with legitimate files,
> produced by x264 and L-SMASH.
Does this patch also fix the issue?
http://ffmpeg.org/pipermail/ffmpeg-devel/2016-August/197817.ht
Hi!
2016-08-24 10:00 GMT+02:00 Oliver Collyer :
> I’m not sure what would happen - currently the nvenc.c code enforces
> 10-bit encoding when it gets a 10-bit input pixel format.
Yes, my question was about what happens if you remove the enforcement /
force an 8bit profile.
And of course if it is
Hi!
2016-08-24 18:51 GMT+02:00 Orion Poplawski :
> Would the ffmpeg developers be willing treat any particular release as a
> long-term-support release and try to do security updates for it?
Could you define "long-term"?
Carl Eugen
___
ffmpeg-devel m
Hi Derek!
2016-08-24 16:55 GMT+02:00 Derek Buitenhuis :
> This breaks files with legitimate single-entry edit lists,
> and the hack, introduced in f03a081df09f9c4798a17d7e24446ed47924b11b,
> has no link to any known sample in its commit message, nor
I suspect the commit message links to this samp
Hi,
patch attached.
0001-avfilter-add-yuvtestsrc-source-filter.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Hello -
We're about to get rpmfusion up and running with EL7 support, and we're
debating what version of ffmpeg to start with. In general on the EL platform
we try to keep versions stable and not introduce any ABI changes unless
absolutely necessary.
Would the ffmpeg developers be willing t
This breaks files with legitimate single-entry edit lists,
and the hack, introduced in f03a081df09f9c4798a17d7e24446ed47924b11b,
has no link to any known sample in its commit message, nor
does it actually fix the problem properly, but instead has
a one-off heuristic to try and "fix" them at the exp
Hello,
On 08/23/2016 10:00 PM, Carl Eugen Hoyos wrote:
+if (mov->mode == MODE_MP4 && mov->major_brand)
+ffio_wfourcc(pb, mov->major_brand); /* write major brand as a
compatible brand */
How can I reproduce the issue this is trying to fix?
The issue we were fixing was that in the
ping!
On Fri, Aug 19, 2016 at 9:49 AM, Sasi Inguva wrote:
> I don't know who the owner of MOV demuxer is. If somebody could do a
> deeper review of this patch and approve it that would be great.
>
> Thanks,
> Sasi
>
> On Wed, Aug 17, 2016 at 8:59 AM, Sasi Inguva wrote:
>
>> Thanks
>>
>> On Aug
On 08/23/2016 08:49 PM, Nicolas George wrote:
+int speaker_position; /** an OutputChannelPosition from ISO/IEC 23001-8 */
I think most our API users and even developers have better use for 158 Swiss
Francs than feeding the ISO. Please make the API self-sufficient; I suggest
an enum.
I'll
On Tue, Aug 23, 2016 at 2:29 PM, Carl Eugen Hoyos wrote:
> It seems safer to me to use the actual number of channels than the
> channel layout.
Alright, new patch version incoming.
--
Burt
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://f
Mostly just re-arranges some code to make it easier to update this
filter and libhdcd together. filter_frame() is much simpler as a
result.
* use the HDCD detection data structure and functions from libhdcd,
moved detection code out of filter_frame()
* moved analyze_mode preparation out of filte
Making sure bestpos is initialized to zero to prevent gcc from kvetching.
It's harmless (although it's not obvious that it's harmless)
from code inspection:
tests/audiomatch.c: In function ‘main’:
tests/audiomatch.c:40: warning: ‘bestpos’ may be used uninitialized in this
function
Thanks to Moritz
applied
--
Burt
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
applied
--
Burt
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
2016-08-24 19:14 GMT+08:00 Steven Liu :
>
>
> 2016-08-24 18:57 GMT+08:00 Michael Niedermayer :
>
>> On Wed, Aug 24, 2016 at 06:28:08PM +0800, Steven Liu wrote:
>> > 2016-08-24 18:23 GMT+08:00 Michael Niedermayer > >:
>> >
>> > > On Wed, Aug 24, 2016 at 03:04:59PM +0800, Steven Liu wrote:
>> > > >
Hi
As i got a bit annoyed by accumulating duplicate and non applicable
patches or rather the need to manually weed them out of patchwork
ive yesterday quickly written the attached script
Does something like this already exist ?
or is this usefull and it would make sense to throw this on some publ
2016-08-24 18:57 GMT+08:00 Michael Niedermayer :
> On Wed, Aug 24, 2016 at 06:28:08PM +0800, Steven Liu wrote:
> > 2016-08-24 18:23 GMT+08:00 Michael Niedermayer :
> >
> > > On Wed, Aug 24, 2016 at 03:04:59PM +0800, Steven Liu wrote:
> > > > On OSX test:
> > > > localhost:ffmpeg liuqi$ uname -a
>
On Wed, Aug 24, 2016 at 06:28:08PM +0800, Steven Liu wrote:
> 2016-08-24 18:23 GMT+08:00 Michael Niedermayer :
>
> > On Wed, Aug 24, 2016 at 03:04:59PM +0800, Steven Liu wrote:
> > > On OSX test:
> > > localhost:ffmpeg liuqi$ uname -a
> > > Darwin localhost 15.5.0 Darwin Kernel Version 15.5.0: Tue
Signed-off-by: liujingchao
---
libavformat/tcp.c | 8
1 file changed, 8 insertions(+)
mode change 100644 => 100755 libavformat/tcp.c
diff --git a/libavformat/tcp.c b/libavformat/tcp.c
old mode 100644
new mode 100755
index c105479..fd10a56
--- a/libavformat/tcp.c
+++ b/libavformat/tcp.c
Ok thanks, Timo.
So I’ve split this into two patches and revised as per the discussions and they
are attached here.
The only thing to be decided is whether my conversion code to enable YUV420P10
support should be included in this or not.
It’s in the attached patch but I’m happy to remove it if
2016-08-24 18:23 GMT+08:00 Michael Niedermayer :
> On Wed, Aug 24, 2016 at 03:04:59PM +0800, Steven Liu wrote:
> > On OSX test:
> > localhost:ffmpeg liuqi$ uname -a
> > Darwin localhost 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36
> > PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_
On Wed, Aug 24, 2016 at 03:04:59PM +0800, Steven Liu wrote:
> On OSX test:
> localhost:ffmpeg liuqi$ uname -a
> Darwin localhost 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36
> PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64
> localhost:ffmpeg liuqi$ make fate-filter-hls-append
> H
Hi,
patch attached.
0001-avfilter-add-lut2-filter.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Did you mean empty line?
发件人: Nicolas George
发送时间: 2016年8月24日 10:01
收件人: FFmpeg development discussions and patches
抄送: liu jc
主题: Re: [FFmpeg-devel] [PATCH] workaround for IOS9 getaddrinfo in IPv6 only
network use hardcode IPv4 address can not resolve port num
L'octidi 8 fructidor, an CCXXIV, liu jc a écrit :
> Signed-off-by: liujingchao
> ---
> libavformat/tcp.c | 8
> 1 file changed, 8 insertions(+)
> mode change 100644 => 100755 libavformat/tcp.c
>
> diff --git a/libavformat/tcp.c b/libavformat/tcp.c
> old mode 100644
> new mode 100755
>
Signed-off-by: liujingchao
---
libavformat/tcp.c | 8
1 file changed, 8 insertions(+)
mode change 100644 => 100755 libavformat/tcp.c
diff --git a/libavformat/tcp.c b/libavformat/tcp.c
old mode 100644
new mode 100755
index c105479..9f7112d
--- a/libavformat/tcp.c
+++ b/libavformat/tcp.c
L'octidi 8 fructidor, an CCXXIV, liu jc a écrit :
> Signed-off-by: liujingchao
> ---
> libavformat/tcp.c | 10 ++
> 1 file changed, 10 insertions(+)
> mode change 100644 => 100755 libavformat/tcp.c
>
> diff --git a/libavformat/tcp.c b/libavformat/tcp.c
> old mode 100644
> new mode 10075
Signed-off-by: liujingchao
---
libavformat/tcp.c | 10 ++
1 file changed, 10 insertions(+)
mode change 100644 => 100755 libavformat/tcp.c
diff --git a/libavformat/tcp.c b/libavformat/tcp.c
old mode 100644
new mode 100755
index c105479..61b68ca
--- a/libavformat/tcp.c
+++ b/libavformat/t
L'octidi 8 fructidor, an CCXXIV, liu jc a écrit :
> Signed-off-by: liujingchao
> ---
> libavformat/tcp.c | 11 +++
> 1 file changed, 11 insertions(+)
> mode change 100644 => 100755 libavformat/tcp.c
>
> diff --git a/libavformat/tcp.c b/libavformat/tcp.c
> old mode 100644
> new mode 1007
Signed-off-by: liujingchao
---
libavformat/tcp.c | 11 +++
1 file changed, 11 insertions(+)
mode change 100644 => 100755 libavformat/tcp.c
diff --git a/libavformat/tcp.c b/libavformat/tcp.c
old mode 100644
new mode 100755
index c105479..289bcd8
--- a/libavformat/tcp.c
+++ b/libavformat/
2016-08-24 17:05 GMT+08:00 Moritz Barsnick :
> On Wed, Aug 24, 2016 at 15:04:59 +0800, Steven Liu wrote:
> > [root@localhost ffmpeg]# make fate-filter-hls-append
> [...]
> > tests/audiomatch.c: 在函数‘main’中:
> > tests/audiomatch.c:40: 警告：此函数中的‘bestpos’在使用前可能未初始化
>
>
Sorry, That's Chinese font. Warni
On Wed, Aug 24, 2016 at 15:04:59 +0800, Steven Liu wrote:
> [root@localhost ffmpeg]# make fate-filter-hls-append
[...]
> tests/audiomatch.c: 在函数‘main’中:
> tests/audiomatch.c:40: 警告：此函数中的‘bestpos’在使用前可能未初始化
Just a hint: For improved readability on this list, please use
something like
$ LANG=C make
Am 24.08.2016 um 10:21 schrieb Oliver Collyer:
>> In any case, please split the rate control patch from the 10bit patch.
>>
>
> Just double-checking this - both changes require a bump of the minimum NVENC
> version to 7. Do you still want them as separate patches or does this tie
> them together
Awesome the second workaround seem a better way i will try it.
发件人: ffmpeg-devel 代表 Michael Niedermayer
发送时间: 2016年8月24日 8:11
收件人: FFmpeg development discussions and patches
主题: Re: [FFmpeg-devel] 答复: [PATCH] IOS-IPv6-only-network-use-hardcode-IPv4-fix
On Wed,
Yes it is better to modify it in all protocol that need call getaddrinfo. This
patch just can fix one usage scenarios . I think it is enough for the Video
APP that use FFMPEG to pass the APPLEreview for IPv6. Other than that APPLE
already know this bug i think it will be fix in the future.
_
AVFrame certainly sounds a good solution. For AVData I followed the lead
from AVSubtitle as they are quite similar concepts. And AVFrame did
really look quite a big struct ;).
I'll rework the code to replace AVData with AVFrame.
Thanks for review!
_
> In any case, please split the rate control patch from the 10bit patch.
>
Just double-checking this - both changes require a bump of the minimum NVENC
version to 7. Do you still want them as separate patches or does this tie them
together? If they are to be separate patches then obviously one
On Wed, Aug 24, 2016 at 07:15:29AM +, liu jc wrote:
> It is not a ios hack, It compatible with any system that in accordance with
> the POSIX standards. The second parameter of function getaddrinfo can accept
> the port name or a service name. If you give a service name to it it will
> tra
> On 24 Aug 2016, at 10:50, Carl Eugen Hoyos wrote:
>
> Hi!
>
> 2016-08-24 9:41 GMT+02:00 Oliver Collyer :
>>
>>> On 23 Aug 2016, at 21:21, Carl Eugen Hoyos wrote:
>>>
>>> 2016-08-23 19:10 GMT+02:00 Oliver Collyer :
+AV_PIX_FMT_YUV420P10LE,
>>>
>>> I know this is theoretical but th
I’m not sure what would happen - currently the nvenc.c code enforces 10-bit
encoding when it gets a 10-bit input pixel format.
Whether the underlying engine allows it, or what would happen I don’t know.
> On 24 Aug 2016, at 10:56, Carl Eugen Hoyos wrote:
>
> Hi!
>
> 2016-08-24 8:43 GMT+02:00
Hi!
2016-08-24 8:43 GMT+02:00 Oliver Collyer :
> Yes, I can confirm AV_PIX_FMT_YUV444P16 works fine so I can
> now ditch the conversion and do a straight plane copy.
I am curious: If you feed the encoder with
NV_ENC_BUFFER_FORMAT_YUV444_10BIT can you still
select 8bit encoding? Is this technicall
Hi!
2016-08-24 9:41 GMT+02:00 Oliver Collyer :
>
>> On 23 Aug 2016, at 21:21, Carl Eugen Hoyos wrote:
>>
>> 2016-08-23 19:10 GMT+02:00 Oliver Collyer :
>>> +AV_PIX_FMT_YUV420P10LE,
>>
>> I know this is theoretical but the Nvidia header seems to indicate
>> native endianness to me, so this sho
On 08/23/2016 10:18 PM, Carl Eugen Hoyos wrote:
2016-08-23 11:03 GMT+02:00 :
+if (id <= 0 &&
+st->codecpar->codec_type == AVMEDIA_TYPE_DATA) {
+id = ff_codec_get_id(ff_codec_metadata_tags, format);
+if (id > 0)
+
On 08/23/2016 10:21 PM, Carl Eugen Hoyos wrote:
2016-08-23 11:03 GMT+02:00 :
+/** Assign track ids. If use_stream_ids_as_track_ids is set, the
+stream ids are used as track ids special case is taken to generate
+track ids for generated tracks, which don't have a 1:1 stream to
+copy
> On 23 Aug 2016, at 21:21, Carl Eugen Hoyos wrote:
>
> Hi!
>
> 2016-08-23 19:10 GMT+02:00 Oliver Collyer :
>> +AV_PIX_FMT_YUV420P10LE,
>
> I know this is theoretical but the Nvidia header seems to indicate
> native endianness to me, so this should be AV_PIX_FMT_YUV420P10
>
>> +AV_PIX
On OSX test:
localhost:ffmpeg liuqi$ uname -a
Darwin localhost 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36
PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64
localhost:ffmpeg liuqi$ make fate-filter-hls-append
HOSTCC tests/base64.o
HOSTLD tests/base64
HOSTCC tests/tiny_psnr.o
HOSTLD
2016-08-24 15:19 GMT+08:00 liu jc :
> Yes you can. But if you are in the IPv6 only network and use a hardcode
> IPv4 address ,in latest IOS version if you just use a port number as the
> second parameter of function getaddrinfo, you will get a connection fail
> when you connect to you server.
>
>
Yes you can. But if you are in the IPv6 only network and use a hardcode IPv4
address ,in latest IOS version if you just use a port number as the second
parameter of function getaddrinfo, you will get a connection fail when you
connect to you server.
发件人: ffmpeg
It is not a ios hack, It compatible with any system that in accordance with
the POSIX standards. The second parameter of function getaddrinfo can accept
the port name or a service name. If you give a service name to it it will
translate it to a standard port number.
On 08/23/2016 06:20 PM, Yusuke Nakamura wrote:
-avio_wb16(pb, 2);
+avio_wb16(pb, track->par->channels);
No. the ChannelCount field is templated. It may be fixed to 2 by derived
specs or the specs of codec encapsulations. I mean the current
implemetation is wrong, and your
71 matches
Mail list logo
