On 3/6/20, Michael Niedermayer wrote:
> On Fri, Mar 06, 2020 at 09:18:50PM +0100, Paul B Mahol wrote:
>> Fixes decoding of came2_2020-01-13__20-38-58_21-00-00__Chn2.avi
>>
>> Signed-off-by: Paul B Mahol
>> ---
>> libavformat/avidec.c | 2 ++
>> libavformat/riff.c | 1 +
>> 2 files changed, 3
I was applying fx to my audio file on my ios app(using Xcode-swift app) and
also from my mac (using terminal).
I need to create ROBOT effect (similar to transformer movie Transformer's
voice). In Android, I was able to apply the FX using the following command:
ffmpeg -i inputFile.m4a -af
Long time user, first time contributor to FFmpeg. Would motion blur be a
good introductory task and would it be accepted as within the scope of
FFmpeg?
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 07-03-2020 03:21 am, Carl Eugen Hoyos wrote:
Am Fr., 6. März 2020 um 06:36 Uhr schrieb Gyan Doshi :
-@section mov/mp4/3gp/QuickTime
+@section mov/mp4/3gp
Is this really an improvement?
Yes, redundancy removed.
Gyan
___
ffmpeg-devel mailing
> 2020年3月7日 上午11:51，Andreas Rheinhardt 写道：
>
> Steven Liu:
>> make the options same as segments for the http put method
>>
>> Signed-off-by: Steven Liu
>> ---
>> libavformat/hlsenc.c | 18 ++
>> 1 file changed, 14 insertions(+), 4 deletions(-)
>>
>> diff --git
Steven Liu:
> make the options same as segments for the http put method
>
> Signed-off-by: Steven Liu
> ---
> libavformat/hlsenc.c | 18 ++
> 1 file changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
> index
make the options same as segments for the http put method
Signed-off-by: Steven Liu
---
libavformat/hlsenc.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index f6dd894343..4b28c412fa 100644
---
> 2020年3月7日 上午11:06，Andreas Rheinhardt 写道：
>
> Steven Liu:
>> make the options same as segments for the http put method
>>
>> Signed-off-by: Steven Liu
>> ---
>> libavformat/hlsenc.c | 11 ---
>> 1 file changed, 8 insertions(+), 3 deletions(-)
>>
>> diff --git a/libavformat/hlsenc.c
> 2020年3月6日 上午11:58，Hongcheng Zhong 写道：
>
> This patch fixes Bug #8469
> If x264 baseline profile is used with other profiles,
> start_pts will be initialized to audio stream's first pts,
> while the duration is calculated based on video stream's pts.
> In this patch the start_pts is
Steven Liu:
> make the options same as segments for the http put method
>
> Signed-off-by: Steven Liu
> ---
> libavformat/hlsenc.c | 11 ---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
> index f6dd894343..88062ac536
I just realised that there is a range coder implementation
already present in libavcodec. I'll look into it.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or
make the options same as segments for the http put method
Signed-off-by: Steven Liu
---
libavformat/hlsenc.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index f6dd894343..88062ac536 100644
--- a/libavformat/hlsenc.c
On 3/6/2020 7:42 PM, Timo Rothenpieler wrote:
> On 06.03.2020 23:39, James Almer wrote:
>> On 3/6/2020 7:35 PM, Timo Rothenpieler wrote:
>>> On 06.03.2020 23:17, James Almer wrote:
On 3/6/2020 11:45 AM, James Almer wrote:
> On 3/6/2020 10:35 AM, Timo Rothenpieler wrote:
>> This
On Thu, Mar 05, 2020 at 10:56:28PM +0100, Marton Balint wrote:
> The packet durations might not be set properly which can cause the MXF muxer
> to write more than one packet of a stream to an edit unit messing up the
> constant byte per element index...
>
> Also use nb_samples directly to
On 06.03.2020 23:39, James Almer wrote:
On 3/6/2020 7:35 PM, Timo Rothenpieler wrote:
On 06.03.2020 23:17, James Almer wrote:
On 3/6/2020 11:45 AM, James Almer wrote:
On 3/6/2020 10:35 AM, Timo Rothenpieler wrote:
This ensures old commandlines using -hwaccel cuvid don't break due to
the
On 3/6/2020 7:35 PM, Timo Rothenpieler wrote:
> On 06.03.2020 23:17, James Almer wrote:
>> On 3/6/2020 11:45 AM, James Almer wrote:
>>> On 3/6/2020 10:35 AM, Timo Rothenpieler wrote:
This ensures old commandlines using -hwaccel cuvid don't break due to
the recent removal of the the
On 06.03.2020 23:17, James Almer wrote:
On 3/6/2020 11:45 AM, James Almer wrote:
On 3/6/2020 10:35 AM, Timo Rothenpieler wrote:
This ensures old commandlines using -hwaccel cuvid don't break due to
the recent removal of the the cuvid-specific hwaccel bringup.
---
fftools/ffmpeg_opt.c | 26
On 06.03.2020 15:45, James Almer wrote:
On 3/6/2020 10:35 AM, Timo Rothenpieler wrote:
This ensures old commandlines using -hwaccel cuvid don't break due to
the recent removal of the the cuvid-specific hwaccel bringup.
---
fftools/ffmpeg_opt.c | 26 ++
1 file changed,
On 3/6/2020 11:45 AM, James Almer wrote:
> On 3/6/2020 10:35 AM, Timo Rothenpieler wrote:
>> This ensures old commandlines using -hwaccel cuvid don't break due to
>> the recent removal of the the cuvid-specific hwaccel bringup.
>> ---
>> fftools/ffmpeg_opt.c | 26 ++
>> 1
On Fri, Mar 06, 2020 at 09:18:50PM +0100, Paul B Mahol wrote:
> Fixes decoding of came2_2020-01-13__20-38-58_21-00-00__Chn2.avi
>
> Signed-off-by: Paul B Mahol
> ---
> libavformat/avidec.c | 2 ++
> libavformat/riff.c | 1 +
> 2 files changed, 3 insertions(+)
>
> diff --git
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Artem Galin
> Sent: Friday, March 6, 2020 2:10 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Artem Galin
> Subject: [FFmpeg-devel] [PATCH v4] lavc/qsv: adding DX11 support
>
> This enables DX11 support for QSV with higher priority than
Am Fr., 6. März 2020 um 06:36 Uhr schrieb Gyan Doshi :
> -@section mov/mp4/3gp/QuickTime
> +@section mov/mp4/3gp
Is this really an improvement?
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
Am Fr., 6. März 2020 um 22:11 Uhr schrieb Paul B Mahol :
>
> On 3/6/20, Carl Eugen Hoyos wrote:
> > Am Fr., 6. März 2020 um 00:25 Uhr schrieb :
> >
> >> +AVCOL_TRC_CINE_LIN2LOG = 19, ///< Default Cineon/DPX linear to log 1D
> >> curve
> >
> > Isn't it possible to use a random large number
On 3/6/20, Carl Eugen Hoyos wrote:
> Am Fr., 6. März 2020 um 00:25 Uhr schrieb :
>
>> +AVCOL_TRC_CINE_LIN2LOG = 19, ///< Default Cineon/DPX linear to log 1D
>> curve
>
> Isn't it possible to use a random large number here?
No, because that would be big hack on top of big pile of hacks that
On Fri, 6 Mar 2020, Andreas Rheinhardt wrote:
Marton Balint:
The packet durations might not be set properly which can cause the MXF muxer
to write more than one packet of a stream to an edit unit messing up the
constant byte per element index...
Also use nb_samples directly to calculate dts
Ping
> On 2 Mar 2020, at 21:30, Ross Nicholson wrote:
>
> phunkyfish in the history is fine thanks ;)
>
>> On 2 Mar 2020, at 21:00, Marton Balint wrote:
>>
>>
>>
On Mon, 2 Mar 2020, Ross Nicholson wrote:
>>>
>>> Updated to correct header.
>>
>> Can you resend the patch with the
Am Fr., 6. März 2020 um 00:25 Uhr schrieb :
> +AVCOL_TRC_CINE_LIN2LOG = 19, ///< Default Cineon/DPX linear to log 1D
> curve
Isn't it possible to use a random large number here?
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
El 06/03/20 a las 16:33, Mark Reid escribió:
You would perhaps be better creating a specialist filter and
implementing it using OCIO (as suggested
https://github.com/AcademySoftwareFoundation/tac/tree/master/gsoc), or
extending the current 3D LUT code to read Cinespace or other 3D LUT
formats
Fixes decoding of came2_2020-01-13__20-38-58_21-00-00__Chn2.avi
Signed-off-by: Paul B Mahol
---
libavformat/avidec.c | 2 ++
libavformat/riff.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/libavformat/avidec.c b/libavformat/avidec.c
index 412e4a8479..7fdc0fbf8b 100644
---
On Fri, Mar 6, 2020 at 5:03 AM Kevin Wheatley
wrote:
> On Fri, Mar 6, 2020 at 10:19 AM Hendrik Leppkes
> wrote:
> > AVColorTransferCharacteristic should follow ISO/IEC 23001-8 and its
> > following standards (ISO/IEC 23091 I believe). Not sure we have a
> > solution for specialized variants,
The parser has been tested and is able to correctly identify the start
of the compressed bitstream. The patch has a set of printf statements
which print a "tracing table" of the behaviour. Upon Nicolas George's
suggestion I have made it so that the varints are read into a uint64_t.
Hence the
Em sex., 6 de mar. de 2020 às 00:52, myp...@gmail.com
escreveu:
>
> On Tue, Feb 25, 2020 at 5:24 PM Guo, Yejun wrote:
> >
> > The Y channel is handled by dnn, and also resized by dnn. The UV channels
> > are resized with swscale.
> For me, this is a little weird to resize Y with dnn backend but
Em qui., 5 de mar. de 2020 às 20:57, Guo, Yejun escreveu:
>
>
>
> > -Original Message-
> > From: Guo, Yejun
> > Sent: Tuesday, February 25, 2020 5:15 PM
> > To: ffmpeg-devel@ffmpeg.org
> > Cc: Guo, Yejun
> > Subject: [PATCH V2 3/3] avfilter/vf_dnn_processing.c: add frame size change
> >
> From: ffmpeg-devel On Behalf Of
> Moritz Barsnick
> Sent: Friday, March 6, 2020 18:24
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] lavc/vaapi_encode_h265: fix
> conf_win_xxx_offset for 4:2:2/4:4:4 encoding
>
> On Thu, Mar 05, 2020 at
On 3/6/2020 10:35 AM, Timo Rothenpieler wrote:
> This ensures old commandlines using -hwaccel cuvid don't break due to
> the recent removal of the the cuvid-specific hwaccel bringup.
> ---
> fftools/ffmpeg_opt.c | 26 ++
> 1 file changed, 14 insertions(+), 12 deletions(-)
On Fri, Mar 06, 2020 at 12:37:30AM +0100, Michael Niedermayer wrote:
> On Sun, Dec 15, 2019 at 11:56:00PM +0100, Michael Niedermayer wrote:
> > On Sat, Dec 14, 2019 at 11:19:13PM +0100, Andreas Rheinhardt wrote:
> > > There can be at most 31 SPS and 255 PPS in the mp4/Matroska extradata.
> > >
This ensures old commandlines using -hwaccel cuvid don't break due to
the recent removal of the the cuvid-specific hwaccel bringup.
---
fftools/ffmpeg_opt.c | 26 ++
1 file changed, 14 insertions(+), 12 deletions(-)
diff --git a/fftools/ffmpeg_opt.c b/fftools/ffmpeg_opt.c
This enables DX11 support for QSV with higher priority than DX9.
In case of multiple GPUs configuration, DX9 API does not allow to get
access to QSV device in some cases - headless.
Implementation based on DX11 resolves that restriction by enumerating list of
available GPUs and finding device
On Fri, Mar 6, 2020 at 10:19 AM Hendrik Leppkes wrote:
> AVColorTransferCharacteristic should follow ISO/IEC 23001-8 and its
> following standards (ISO/IEC 23091 I believe). Not sure we have a
> solution for specialized variants, but adding one right there would
> collide with the next addition
On Thu, Mar 05, 2020 at 15:41:17 +0800, Linjie Fu wrote:
> +int SubWidthC, SubHeightC;
Style nit:
ffmpeg's own variables don't use CamelCase.
Moritz
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On Fri, Mar 6, 2020 at 12:25 AM wrote:
>
> From: Mark Reid
>
> Hi,
> The following patch adds a cineon lin2log color transfer characteristic to
> exr.
> The purpose of this patch is to allow preserving of the dynamic range of an
> exr file when converting to DPX or when using video filter such
On 3/5/20, mindm...@gmail.com wrote:
> From: Mark Reid
>
> Hi,
> The following patch adds a cineon lin2log color transfer characteristic to
> exr.
> The purpose of this patch is to allow preserving of the dynamic range of an
> exr file when converting to DPX or when using video filter such as 3d
42 matches
Mail list logo
