From: Karthick Jeyapal
Fixes bug id : 7638
---
libavformat/file.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/libavformat/file.c b/libavformat/file.c
index 1d321c4..e613b91 100644
--- a/libavformat/file.c
+++ b/libavformat/file.c
@@ -173,7 +173,11 @@ static int
On 31-12-2018 06:50 AM, Michael Niedermayer wrote:
On Sat, Dec 29, 2018 at 04:39:18PM +0530, Gyan wrote:
At Michael's suggestion, earlier patch broken into two. This one stops
discarded streams from being processed. A few more checks added.
Gyan
[...]
diff --git a/fftools/ffmpeg_opt.c
On Sun, Dec 30, 2018 at 10:57:23PM +0200, Alex Mogurenko wrote:
> fdct done twice for each block. first time during quant calculation, second
> during slice encoding. so if we pre-save dct coefficients no need to do fdct
> second time.
> disadvantages: requires more memory
> advantages: improves
On 12/30/2018 5:52 PM, Carl Eugen Hoyos wrote:
> 2018-12-30 21:37 GMT+01:00, Hendrik Leppkes :
>> On Sun, Dec 30, 2018 at 9:16 PM Carl Eugen Hoyos wrote:
>
>>> Attached patch fixes a Windows linking issue described in ticket #7642,
>>> only shared linking was tested so far.
>>
>> ole32 is a
On Sat, Dec 29, 2018 at 04:39:18PM +0530, Gyan wrote:
> At Michael's suggestion, earlier patch broken into two. This one stops
> discarded streams from being processed. A few more checks added.
>
> Gyan
>
[...]
> diff --git a/fftools/ffmpeg_opt.c b/fftools/ffmpeg_opt.c
> index
2018-12-30 21:16 GMT+01:00, Carl Eugen Hoyos :
> Attached patch fixes a Windows linking issue described in ticket #7642,
> only shared linking was tested so far.
Works fine with both static and dynamic linking.
Carl Eugen
___
ffmpeg-devel mailing list
2018-12-29 17:17 GMT+01:00, Manoj Gupta :
> On Sat, Dec 29, 2018 at 2:32 AM Carl Eugen Hoyos wrote:
>>
>> 2018-12-29 0:12 GMT+01:00, Manoj Gupta :
>>
>> > I recently had a problem building ffmpeg for AArch64 where lld
>> > linker complained about text relocations in readonly segment.
>> > The
This allows the underlying files to change their duration on subsequent
avformat context opens.
An example use case where this matters:
ffconcat version 1.0
file dummy.mxf
file dummy.mxf
ffmpeg -re -stream_loop -1 -i dummy.ffconcat -f sdl2 none
The user can seamlessly change the input by
fdct done twice for each block. first time during quant calculation, second
during slice encoding. so if we pre-save dct coefficients no need to do fdct
second time.
disadvantages: requires more memory
advantages: improves performance ~4-5%
---
libavcodec/proresenc_kostya.c | 74
2018-12-30 21:37 GMT+01:00, Hendrik Leppkes :
> On Sun, Dec 30, 2018 at 9:16 PM Carl Eugen Hoyos wrote:
>> Attached patch fixes a Windows linking issue described in ticket #7642,
>> only shared linking was tested so far.
>
> ole32 is a dependency of dxva2 already, it should already be pulled in
On Sun, Dec 30, 2018 at 9:16 PM Carl Eugen Hoyos wrote:
>
> Hi!
>
> Attached patch fixes a Windows linking issue described in ticket #7642,
> only shared linking was tested so far.
>
ole32 is a dependency of dxva2 already, it should already be pulled in
through that, shouldn't it?
- Hendrik
On Sun, 30 Dec 2018, Nicolas George wrote:
Marton Balint (2018-12-23):
Signed-off-by: Marton Balint
---
libavformat/concatdec.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
Looks good to me, thanks.
Applied, thanks.
Marton
Hi!
Attached patch fixes a Windows linking issue described in ticket #7642,
only shared linking was tested so far.
Please comment, Carl Eugen
From f01b6c216b5fc970b374160efdc0f834d99d328d Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Sun, 30 Dec 2018 21:04:14 +0100
Subject: [PATCH]
On Sun, 30 Dec 2018, Nicolas George wrote:
Marton Balint (2018-12-25):
Frame properties were not copied, so e.g. PTS was not set for the last frame.
Regression since ef3babb2c70f564dc1634b3f29c6e35a2b2dc239.
Signed-off-by: Marton Balint
---
libavfilter/af_asetnsamples.c | 6 ++
1
Attempts to pick the set of supported colour properties best matching the
input. Output is then set with the same values, except for the colour
matrix which may change when converting between RGB and YUV.
---
On 30/12/2018 19:14, Michael Niedermayer wrote:> On Sun, Dec 30, 2018 at
06:45:17PM
On 29/12/2018 07:02, Zachary Zhou wrote:
> It supports ICL platform.
When will this hardware be available?
Is this a new fixed-function feature, or will it be available on current
hardware as well?
> H2H (HDR to HDR): P010 -> RGB10
> H2S (HDR to SDR): P010 -> RGB8
>
> libva commit for HDR10
>
On Sun, Dec 30, 2018 at 06:45:17PM +, Mark Thompson wrote:
> Attempts to pick the set of supported colour properties best matching the
> input. Output is then set with the same values, except for the colour
> matrix which may change when converting between RGB and YUV.
> ---
>
On 12/30/18, Nicolas George wrote:
> Paul B Mahol (2018-12-30):
>> I will use +.
>
> That was my suggestion in the beginning, so I am obviously for. But what
> happened to your reasons for rejecting it?
I thought that adapted patch by me had this issue already resolved.
I did not carefully read
Marton Balint (2018-12-25):
> Frame properties were not copied, so e.g. PTS was not set for the last frame.
>
> Regression since ef3babb2c70f564dc1634b3f29c6e35a2b2dc239.
>
> Signed-off-by: Marton Balint
> ---
> libavfilter/af_asetnsamples.c | 6 ++
> 1 file changed, 6 insertions(+)
On Tue, 25 Dec 2018, Marton Balint wrote:
Frame properties were not copied, so e.g. PTS was not set for the last frame.
Regression since ef3babb2c70f564dc1634b3f29c6e35a2b2dc239.
Signed-off-by: Marton Balint
---
libavfilter/af_asetnsamples.c | 6 ++
1 file changed, 6 insertions(+)
diff
On Sun, Dec 30, 2018 at 07:15:49PM +0100, Marton Balint wrote:
>
>
> On Fri, 28 Dec 2018, Michael Niedermayer wrote:
>
> >On Wed, Dec 26, 2018 at 10:16:47PM +0100, Marton Balint wrote:
> >>
> >>
> >>On Wed, 26 Dec 2018, Paul B Mahol wrote:
> >>
> >>>On 12/26/18, Michael Niedermayer wrote:
>
Paul B Mahol (2018-12-30):
> I will use +.
That was my suggestion in the beginning, so I am obviously for. But what
happened to your reasons for rejecting it?
(Once again, too little information in your mail => wasted time for both
of us.)
--
Nicolas George
signature.asc
Description: PGP
On 12/30/18, Nicolas George wrote:
> Paul B Mahol (2018-12-30):
>> http://ffmpeg.org/ffmpeg-filters.html#aformat-1http://ffmpeg.org/ffmpeg-filters.html#aformat-1
>
> Your link was slightly broken.
>
>> Do you want to change above thing too?
>
> No, but I would have objected if I had noticed at
Paul B Mahol (2018-12-30):
> http://ffmpeg.org/ffmpeg-filters.html#aformat-1http://ffmpeg.org/ffmpeg-filters.html#aformat-1
Your link was slightly broken.
> Do you want to change above thing too?
No, but I would have objected if I had noticed at the time.
But thanks for finding that example:
2018-12-30 14:02 GMT+01:00, Nicolas George :
> Uwe Freese (2018-12-29):
>> +(double*)av_malloc((logo_w - 1) * (logo_h - 1) *
>> sizeof(double));
>
> No casting of malloc returns in C, this is a c++ thing. Also, use
> av_malloc_array().
While there, please don't use
The "out_color_matrix" and "out_range" properties match the same options
in vf_scale; the others attempt to follow the same pattern.
---
libavfilter/vf_scale_vaapi.c | 70
1 file changed, 70 insertions(+)
diff --git a/libavfilter/vf_scale_vaapi.c
Attempts to pick the set of supported colour properties best matching the
input. Output is then set with the same values, except for the colour
matrix which may change when converting between RGB and YUV.
---
libavfilter/vaapi_vpp.c| 265 -
On 12/30/18, Nicolas George wrote:
> Paul B Mahol (2018-12-30):
>> aformat for example use | to split channel layouts.
>
> Where?
http://ffmpeg.org/ffmpeg-filters.html#aformat-1http://ffmpeg.org/ffmpeg-filters.html#aformat-1
Do you want to change above thing too?
What you propose instead?
Paul B Mahol (2018-12-30):
> aformat for example use | to split channel layouts.
Where?
> Documentation follows old legacy usage.
I am talking about the documentation of the patch you are proposing.
> Can you please stop bikeshedding and arguing with me just because
> you enjoy it?
Can you
On 12/30/18, Nicolas George wrote:
> Paul B Mahol (2018-12-30):
>> Please no, | is used in bunch of scripts.
>
> What scripts? How can they use an API that is still in early discussion?
aformat for example use | to split channel layouts.
>
> Also, discussing this is moot until you rephrase the
Paul B Mahol (2018-12-30):
> Please no, | is used in bunch of scripts.
What scripts? How can they use an API that is still in early discussion?
Also, discussing this is moot until you rephrase the documentation.
--
Nicolas George
signature.asc
Description: PGP signature
On 12/30/18, Nicolas George wrote:
> Paul B Mahol (2018-12-30):
>> >> Input #0, wv, from
>> >> '/home/computer/Downloads/Run_The_Race_-_3rd_Order_Ambisonic_SN3D.wv':
>> >> Duration: 00:11:07.67, start: 0.00, bitrate: 6084 kb/s
>> >> Stream #0:0: Audio: wavpack, 44100 Hz, 16 channels
>>
Paul B Mahol (2018-12-30):
> >> Input #0, wv, from
> >> '/home/computer/Downloads/Run_The_Race_-_3rd_Order_Ambisonic_SN3D.wv':
> >> Duration: 00:11:07.67, start: 0.00, bitrate: 6084 kb/s
> >> Stream #0:0: Audio: wavpack, 44100 Hz, 16 channels
> >>
On Fri, 28 Dec 2018, Michael Niedermayer wrote:
On Wed, Dec 26, 2018 at 10:16:47PM +0100, Marton Balint wrote:
On Wed, 26 Dec 2018, Paul B Mahol wrote:
On 12/26/18, Michael Niedermayer wrote:
On Wed, Dec 26, 2018 at 04:32:17PM +0100, Paul B Mahol wrote:
On 12/25/18, Michael
On 25/12/2018 06:16, Zachary Zhou wrote:
> Swap width and height when do clock/cclock rotation
> Add reversal/reversal_flip options
>
> ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128
> -hwaccel_output_format vaapi -i input.264 -vf "transpose_vaapi=clock_flip"
> -c:v h264_vaapi
On 25/12/2018 06:03, Zachary Zhou wrote:
> Signed-off-by: Zachary Zhou
> ---
> libavfilter/vaapi_vpp.h| 2 ++
> libavfilter/vf_deinterlace_vaapi.c | 2 +-
> libavfilter/vf_misc_vaapi.c| 2 +-
> libavfilter/vf_procamp_vaapi.c | 2 +-
> libavfilter/vf_scale_vaapi.c |
On 30/12/2018 08:39, Jun Zhao wrote:
> preset used in more in line with similar encoders.
>
> Signed-off-by: Jun Zhao
> ---
> libavcodec/libxavs2.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/libavcodec/libxavs2.c b/libavcodec/libxavs2.c
> index
Signed-off-by: Paul B Mahol
---
libavfilter/x86/af_afir.asm| 15 ---
libavfilter/x86/af_afir_init.c | 6 ++
2 files changed, 18 insertions(+), 3 deletions(-)
diff --git a/libavfilter/x86/af_afir.asm b/libavfilter/x86/af_afir.asm
index 849d85e70f..e770420a21 100644
---
On 28/12/2018 21:22, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/mjpegbdec.c | 16
> 1 file changed, 8 insertions(+), 8 deletions(-)
OK.
- Derek
___
ffmpeg-devel mailing list
On 28/12/2018 21:22, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/mjpegbdec.c | 24 +---
> 1 file changed, 9 insertions(+), 15 deletions(-)
OK.
- Derek
___
ffmpeg-devel mailing list
On 29/12/2018 16:34, Derek Buitenhuis wrote:
> I think it's OK.
>
> I'll push it in 24 hours if noone else objects.
Pushed.
- Derek
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 12/30/18, Nicolas George wrote:
> Paul B Mahol (2018-12-30):
>> >> > av_get_channel_layout() used to use '+' instead of '|', and I think
>> >> > it
>> >> > is better. For once, '+' is not a special character for shells.
>> >>
>> >> Can not work if user wants to define custom channel layout
Paul B Mahol (2018-12-30):
> >> > av_get_channel_layout() used to use '+' instead of '|', and I think it
> >> > is better. For once, '+' is not a special character for shells.
> >>
> >> Can not work if user wants to define custom channel layout from
> >> already available channels.
> >
> > Please
On 12/30/18, Nicolas George wrote:
> Paul B Mahol (2018-12-30):
>> On 12/26/18, Nicolas George wrote:
>> >> + * The input string can be represented by:
>> >> + * - the formal channel layout name (returned by
>> >> av_channel_layout_describe())
>> >> + * - single or multiple channel names
Paul B Mahol (2018-12-30):
> On 12/26/18, Nicolas George wrote:
> >> + * The input string can be represented by:
> >> + * - the formal channel layout name (returned by
> >> av_channel_layout_describe())
> >> + * - single or multiple channel names (returned by av_channel_name()
> >> + *or
On 12/26/18, Nicolas George wrote:
>> + * The input string can be represented by:
>> + * - the formal channel layout name (returned by
>> av_channel_layout_describe())
>> + * - single or multiple channel names (returned by av_channel_name()
>> + *or concatenated with "|")
>> + * - a
On 12/30/18, Nicolas George wrote:
> Uwe Freese (2018-12-29):
>> The downside is that the term "power" (or "strength") would be more
>> generic
>> and would probably be better reusable for other modes.
>>
>> What do you think? Is "exponent" now ok, or should I change it back to
>> "power",
Helmut K. C. Tessarek (2018-12-30):
> > pow(sqrt(x * x * aspect2 + y * y), exponent / 2);
> There seems to be a mistake. You are taking the square root twice.
>
> Or am I missing something here?
Thanks, I wanted to remove the sqrt() and replace it with the /2, not
just add the /2.
Regards,
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-12-30 08:02, Nicolas George wrote:
>> +double d = pow(sqrt(x * x * aspect * aspect + y
>> * y), exponent);
> pow(sqrt(x * x * aspect2 + y * y), exponent / 2);
>
There seems to be a mistake. You are taking the square root
Moritz Barsnick (2018-12-27):
> So the limit shall be in "real" realtime? In other words, if the max
> sleep time limit is 2 seconds (default), it shall stay there, even if a
> speed < 1 slowdown extends all sleep times?
That was my point, but it is only an opinion.
> (The use case is, for
Marton Balint (2018-12-23):
> Signed-off-by: Marton Balint
> ---
> libavformat/concatdec.c | 9 +++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
Looks good to me, thanks.
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
Uwe Freese (2018-12-29):
> The downside is that the term "power" (or "strength") would be more generic
> and would probably be better reusable for other modes.
>
> What do you think? Is "exponent" now ok, or should I change it back to
> "power", "strength" or something alike?
I would say: do not
preset used in more in line with similar encoders.
Signed-off-by: Jun Zhao
---
libavcodec/libxavs2.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/libavcodec/libxavs2.c b/libavcodec/libxavs2.c
index 41c0b63..2ade923 100644
--- a/libavcodec/libxavs2.c
+++
Update standard libavcodec options for libxavs2
Signed-off-by: Jun Zhao
---
doc/encoders.texi | 17 ++---
1 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/doc/encoders.texi b/doc/encoders.texi
index c6fe923..b6f477d 100644
--- a/doc/encoders.texi
+++
V1: - Cosmetics: Fix indentation for switch statement in davs2/xavs2
- Rename option speed_level to preset
- Update standard libavcodec options in docs part for libxavs2
Jun Zhao (4):
lavc/libdavs2: Cosmetics: Fix indentation for switch statement
lavc/libxavs2: Cosmetics: Fix
Cosmetics: Fix indentation for switch statement like the Linux
kerenl style.
Signed-off-by: Jun Zhao
---
libavcodec/libdavs2.c | 34 +-
1 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/libavcodec/libdavs2.c b/libavcodec/libdavs2.c
index
Cosmetics: Fix indentation for switch statement like the Linux
kerenl style.
Signed-off-by: Jun Zhao
---
libavcodec/libxavs2.c | 32
1 files changed, 16 insertions(+), 16 deletions(-)
diff --git a/libavcodec/libxavs2.c b/libavcodec/libxavs2.c
index
57 matches
Mail list logo
