This fix targets (rare) cases where multiple input pads have a
.filter_frame function. ff_request_frame_to_filter needs
to call ff_request_frame with the correct input pad
instead of the hardcoded first one.
Signed-off-by: softworkz
---
libavfilter/avfilter.c | 18 +-
1 file chan
- overlaytextsubs {VS -> V)
Overlay text subtitles onto a video stream.
- textsubs2video {S -> V)
Converts text subtitles to video frames
Signed-off-by: softworkz
---
configure| 2 +
doc/filters.texi | 113 ++
libavfilter/Makefile |
- textmod {S -> S)
Modify subtitle text in a number of ways
- censor {S -> S)
Censor subtitles using a word list
- show_speaker {S -> S)
Prepend speaker names from ASS subtitles to the visible text lines
Signed-off-by: softworkz
---
doc/filters.texi | 206
libavfilte
- stripstyles {S -> S)
Remove all inline styles from subtitle events
Signed-off-by: softworkz
---
doc/filters.texi | 37 +++
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/sf_stripstyles.c | 196 +++
4 fi
- splitcc {V -> VS)
Extract closed-caption (A53) data from video
frames as subtitle Frames
ffmpeg -y -loglevel verbose -i
"https://streams.videolan.org/streams/ts/CC/NewsStream-608-ac3.ts";
-filter_complex
"[0:v]splitcc[vid1],textmod=mode=remove_chars:find='@',[vid1]overlay_textsubs"
outpu
Signed-off-by: softworkz
---
configure| 1 +
doc/filters.texi | 55 +
libavfilter/Makefile | 2 +
libavfilter/allfilters.c | 1 +
libavfilter/sf_graphicsub2text.c | 354 +++
5 files changed, 413 ins
Signed-off-by: softworkz
---
configure | 1 +
doc/filters.texi | 164 +++
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/sf_subscale.c | 883 ++
5 files changed, 1050 insertions(+)
create mode 1
o avutil, add new and deprecate old values
>
> On Fri, Dec 03, 2021 at 07:31:06PM +, Soft Works wrote:
> > Signed-off-by: softworkz
> > ---
> > doc/APIchanges | 6
> > libavcodec/avcodec.h | 19 +
> > l
> -Original Message-
> From: ffmpeg-devel On Behalf Of Lynne
> Sent: Sunday, December 5, 2021 5:40 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH v20 02/20] avutil/frame: Prepare AVFrame
> for subtitle handling
>
> 5 Dec 2021, 17:23 by softwo.
> -Original Message-
> From: ffmpeg-devel On Behalf Of Hendrik
> Leppkes
> Sent: Sunday, December 5, 2021 5:45 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH v20 02/20] avutil/frame: Prepare AVFrame
> for subtitle handling
>
> On Sun, Dec 5, 2
> -Original Message-
> From: ffmpeg-devel On Behalf Of Lynne
> Sent: Sunday, December 5, 2021 5:40 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH v20 02/20] avutil/frame: Prepare AVFrame
> for subtitle handling
>
> 5 Dec 2021, 17:23 by softwo.
New in V21
- Rebased. Patchset was broken again.
- Don't declare AVFrame.subtitle_pts as deprecated and clarify doc text
- Remove AVFilter.subs_list and AVFilter.sub_fmt from APIchanges
- Change include in formats.c
New in V20
- Rebased. V19 didn't apply cleanly anymore
New in V19
- Document A
Signed-off-by: softworkz
---
doc/APIchanges | 6
libavcodec/avcodec.h | 19 +
libavutil/Makefile | 1 +
libavutil/subfmt.h | 66
libavutil/version.h | 1 +
5 files changed, 75 insertions(+), 18 deletions(-)
create mode 1
Root commit for adding subtitle filtering capabilities.
In detail:
- Add type (AVMediaType) field to AVFrame
Replaces previous way of distinction which was based on checking
width and height to determine whether a frame is audio or video
- Add subtitle fields to AVFrame
- Add new struct AVSubt
Signed-off-by: softworkz
---
libavcodec/Makefile | 56 +++
libavcodec/ass.h | 147 ++
libavcodec/assdec.c | 2 +-
libavcodec/assenc.c | 2 +-
libavcodec/ccaption_dec
Signed-off-by: softworkz
---
doc/APIchanges | 3 +
libavcodec/assenc.c| 90 +
libavcodec/avcodec.h | 5 +-
libavcodec/dvbsubenc.c | 96 +--
libavcodec/dvdsubenc.c | 100 +++-
Signed-off-by: softworkz
---
libavcodec/ass.h | 2 +-
libavcodec/assdec.c| 2 +-
libavcodec/dvbsubdec.c | 2 +-
libavcodec/dvdsubdec.c | 2 +-
libavcodec/dvdsubenc.c | 2 +-
libavcodec/pgssubdec.c | 2 +-
libavcodec/xsubdec.c | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)
d
Signed-off-by: softworkz
---
fftools/ffplay.c | 102 +-
fftools/ffprobe.c | 48 ++
2 files changed, 78 insertions(+), 72 deletions(-)
diff --git a/fftools/ffplay.c b/fftools/ffplay.c
index e7b20be76b..0af32888da 100644
--- a/fftoo
- Add avcodec_decode_subtitle3 which takes subtitle frames,
serving as compatibility shim to legacy subtitle decoding
- Add additional methods for conversion between old and new API
Signed-off-by: softworkz
---
doc/APIchanges | 7 ++
libavcodec/avcodec.h| 8 +-
libavcodec/code
Analog to avfilter/video.c and avfilter/audio.c
Signed-off-by: softworkz
---
libavfilter/Makefile| 1 +
libavfilter/avfilter.c | 4 +++
libavfilter/internal.h | 1 +
libavfilter/subtitles.c | 63 +
libavfilter/subtitles.h | 44
Signed-off-by: softworkz
---
libavfilter/avfilter.c | 8 +---
libavfilter/avfilter.h | 11 +++
libavfilter/avfiltergraph.c | 5 +
libavfilter/formats.c | 22 ++
libavfilter/formats.h | 3 +++
libavfilter/internal.h | 18 +++
Signed-off-by: softworkz
---
libavfilter/vf_subtitles.c | 54 +-
1 file changed, 42 insertions(+), 12 deletions(-)
diff --git a/libavfilter/vf_subtitles.c b/libavfilter/vf_subtitles.c
index 377160c72b..a240cbd415 100644
--- a/libavfilter/vf_subtitles.c
+++ b/l
Signed-off-by: softworkz
---
configure| 2 +-
libavfilter/allfilters.c | 2 ++
libavfilter/buffersink.c | 54 ++
libavfilter/buffersink.h | 7
libavfilter/buffersrc.c | 72
libavfilter/buffersrc.h | 1
- overlaygraphicsubs (VS -> V)
Overlay graphic subtitles onto a video stream
- graphicsub2video {S -> V)
Converts graphic subtitles to video frames (with alpha)
Gets auto-inserted for retaining compatibility with
sub2video command lines
Signed-off-by: softworkz
---
doc/filters.texi
This commit actually enables subtitle filtering in ffmpeg by
sending and receiving subtitle frames to and from a filtergraph.
The heartbeat functionality from the previous sub2video implementation
is retained and applied to all subtitle frames (bitmap, text, ..).
The other part of sub2video funct
This fix targets (rare) cases where multiple input pads have a
.filter_frame function. ff_request_frame_to_filter needs
to call ff_request_frame with the correct input pad
instead of the hardcoded first one.
Signed-off-by: softworkz
---
libavfilter/avfilter.c | 18 +-
1 file chan
- overlaytextsubs {VS -> V)
Overlay text subtitles onto a video stream.
- textsubs2video {S -> V)
Converts text subtitles to video frames
Signed-off-by: softworkz
---
configure| 2 +
doc/filters.texi | 113 ++
libavfilter/Makefile |
- textmod {S -> S)
Modify subtitle text in a number of ways
- censor {S -> S)
Censor subtitles using a word list
- show_speaker {S -> S)
Prepend speaker names from ASS subtitles to the visible text lines
Signed-off-by: softworkz
---
doc/filters.texi | 206
libavfilte
- stripstyles {S -> S)
Remove all inline styles from subtitle events
Signed-off-by: softworkz
---
doc/filters.texi | 37 +++
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/sf_stripstyles.c | 196 +++
4 fi
- splitcc {V -> VS)
Extract closed-caption (A53) data from video
frames as subtitle Frames
ffmpeg -y -loglevel verbose -i
"https://streams.videolan.org/streams/ts/CC/NewsStream-608-ac3.ts";
-filter_complex
"[0:v]splitcc[vid1],textmod=mode=remove_chars:find='@',[vid1]overlay_textsubs"
outpu
Signed-off-by: softworkz
---
configure| 1 +
doc/filters.texi | 55 +
libavfilter/Makefile | 2 +
libavfilter/allfilters.c | 1 +
libavfilter/sf_graphicsub2text.c | 354 +++
5 files changed, 413 ins
Signed-off-by: softworkz
---
configure | 1 +
doc/filters.texi | 164 +++
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/sf_subscale.c | 883 ++
5 files changed, 1050 insertions(+)
create mode 1
Hi,
I'm wondering who is the maintainer of the "nv-codec-headers" repo and what
procedure I would need to follow to get something added there?
Actually it's not a big issue, I would just like to have the
"cuDeviceGetAttribute" function (from cuda.h) to be added there.
Thanks,
softworkz
__
0001-Add-CUDA-function-cuDeviceGetAttribute.patch
Description: 0001-Add-CUDA-function-cuDeviceGetAttribute.patch
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Signed-off-by: softworkz
---
include/ffnvcodec/dynlink_cuda.h | 104 +
include/ffnvcodec/dynlink_loader.h | 2 +
2 files changed, 106 insertions(+)
diff --git a/include/ffnvcodec/dynlink_cuda.h b/include/ffnvcodec/dynlink_cuda.h
index 373215d..b16e9a5 100644
--- a
> That enum is _way_ too massive. Most of that seems entirely useless in
> the context of ffmpeg anyway, like all the 1D and 3D stuff, and probably
> most of the 2D stuff as well.
I copied the full enum to have an exact match to cuda.h, but no problem, I can
trim it down.
> Can you trim it down
Signed-off-by: softworkz
---
include/ffnvcodec/dynlink_cuda.h | 26 ++
include/ffnvcodec/dynlink_loader.h | 2 ++
2 files changed, 28 insertions(+)
diff --git a/include/ffnvcodec/dynlink_cuda.h b/include/ffnvcodec/dynlink_cuda.h
index 373215d..069acd1 100644
--- a/incl
> Those headers come straight from nvidia under a free license(MIT) and
> are just slightly modified for better compatibility.
> There is no such thing for CUDA sadly.
Thanks. I made the requested changes and submitted a new patch.
In this context, I wonder if there is some explanation somewher
Hi Phil,
thank you very much for taking the time to respond.
I've understood the differences regarding the parser.
> The hwaccels are officially called 'cuvid' and 'nvdec'. As a
> convenience, we alias 'cuda' to 'nvdec'. The confusion is that the HW
> pix_fmt and hwcontext are called 'cuda' beca
> LGTM, will apply next time I get a chance.
Thank you very much!
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
nstants
>
> On Tue, Feb 18, 2020 at 02:40:49 +, Soft Works wrote:
> > It's often not obvious how option constants relate to numerical values.
> > Defaults are sometimes printed as numbers and from/to are always
> printed as numbers.
> > Printing the numeric values
> -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 DX
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Artem Galin
> Sent: Tuesday, March 10, 2020 5:10 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v2] lavc/qsv: adding DX11 support
>
> Any comments on updated patch by lin
On Tue, Mar 10, 2020 at 10:36 PM Soft Works
> wrote:
>
> >
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of
> > > Artem Galin
> > > Sent: Tuesday, March 10, 2020 5:10 PM
> > > To: FFmpeg development discussions and
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Hendrik Leppkes
> On Wed, Mar 11, 2020 at 10:58 PM Soft Works
> wrote:
> >
> > The submitted patch is far away from being complete. I know it
> > because I've already done a full implementat
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Max Dmitrichenko
> Sent: Thursday, March 12, 2020 9:57 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> >
> DX11 support has certain and strong benefits.
>
> we have this patch for DX11 support already no cle
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> artem.ga...@gmail.com
> Sent: Thursday, April 9, 2020 7:51 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Artem Galin
> Subject: [FFmpeg-devel] [PATCH 4/4] libavutil/qsv: enabling d3d11va support
>
> From: Artem Galin
>
> Makes selectio
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Mark Thompson
> Sent: Sunday, April 26, 2020 8:54 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v3 4/4] libavutil/qsv: enabling d3d11va
> support
>
> On 24/04/2020 15:52, artem.ga...@gmail.com wrote:
> > From
> -Original Message-
> From: ffmpeg-devel On Behalf Of Xu
> Guangxin
> Sent: Monday, February 22, 2021 9:45 AM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Xu Guangxin
> Subject: [FFmpeg-devel] [PATCH] avutils/hwcontext_qsv: set the source
> device in qsv_device_create
>
> opencl_device_derive
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Artem Galin
> Sent: Wednesday, February 24, 2021 4:40 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: [FFmpeg-devel] Proposal of two projects for GSoC
>
>
> Please find the proposal for the fol
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Artem Galin
> Sent: Tuesday, November 3, 2020 7:46 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Artem Galin
> Subject: [FFmpeg-devel] [PATCH v7 2/8] libavutil/hwcontext_qsv: supporting
> d3d11va device type
>
> This enables usage of no
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Artem Galin
> Sent: Tuesday, November 3, 2020 7:46 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Artem Galin
> Subject: [FFmpeg-devel] [PATCH v7 8/8] libavfilter/vf_deinterlace_qsv:
> enabling d3d11va support, added mfxhdlpair
>
> Addin
enabling d3d11va support, added mfxhdlpair
>
> On Wed, 24 Feb 2021 at 17:50, Soft Works wrote:
>
> >
> >
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of
> > > Artem Galin
> > > Sent: Tuesday, November 3, 2020 7:46 P
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Artem Galin
> Sent: Thursday, February 25, 2021 12:31 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Proposal of two projects for GSoC
>
> On Wed,
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Artem Galin
> Sent: Tuesday, November 3, 2020 7:46 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Artem Galin
> Subject: [FFmpeg-devel] [PATCH v7 3/8] libavutil/hwcontext_qsv: enabling
> d3d11va usage by default, add usage child_device_ty
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Soft Works
> Sent: Thursday, February 25, 2021 8:50 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Cc: Artem Galin
> Subject: Re: [FFmpeg-devel] [PATCH v7 3/8] libavutil/hwcontext
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> RADSL
> Sent: Saturday, April 3, 2021 4:23 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] 4.4 Release Name
>
>
> On 4/3/2021 6:02 AM, Lynne wrote:
> > Apr 3, 2021, 12:19 by j...@videolan.org:
> >
> >> On Sat, 3 Ap
> From: ffmpeg-devel On Behalf Of
> Hendrik Leppkes
> Sent: Friday, May 8, 2020 10:27 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v4 03/11] libavutil/hwcontext_d3d11va:
> adding more texture information to the D3D11 hwcontext API
>
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Hendrik Leppkes
> Sent: Saturday, May 9, 2020 9:08 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v4 03/11] libavutil/hwcontext_d3d11va:
> adding more texture information t
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Hendrik Leppkes
> > >
> >
> > Of course there is a choice. Only support the new stuff. Afterall we
> > havent supported it at all for years now, so only supporting it on
> > newer drivers isn't the end of the world.
> >
>
> To give
more texture information to the D3D11 hwcontext API
>
> On Sat, May 9, 2020 at 7:41 PM Soft Works wrote:
> >
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of
> > > Hendrik Leppkes
> > > Sent: Saturday, May 9, 2020 9:08 AM
&g
> adding more texture information to the D3D11 hwcontext API
>
> On Sat, May 9, 2020 at 8:31 PM Soft Works wrote:
>
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of
> > > Hendrik Leppkes
> > > Sent: Saturday, May 9, 2020 7:54 PM
>
> adding more texture information to the D3D11 hwcontext API
>
> On Sat, May 9, 2020 at 8:13 PM Soft Works wrote:
>
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of
> > > Hendrik Leppkes
> > > > >
> > > >
> > >
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Max Dmitrichenko
> Sent: Saturday, May 9, 2020 10:42 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v4 03/11] libavutil/hwcontext_d3d11va:
> adding more texture information
e texture information to the D3D11 hwcontext API
>
> On Sat, 9 May 2020 at 22:29, Soft Works wrote:
>
> > You replied:
> > > yes, it is only a hint for D11 when possible.
> >
> > I would understand 'when possible' in a way that D3D9 would be used
>
Hello,
I've seen the commit about the option for dumping the filtergraph and that
reminded me about something that I'd be willing to contribute in case anybody
likes it.
A while ago I was looking for a way to get information about the filtergraphs
that ffmpeg builds at runtime, the individual
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> lance.lmw...@gmail.com
> Sent: Sunday, May 24, 2020 1:24 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] ffmpeg Filtergraph Output
>
> On Sun, May 24, 2020 at 02:43:52AM +, Sof
These conditions are:
- Dimensions are aligned to 16/32 byte (e.g. 1920x800)
- No scaling is done
- Color format conversion (e.g. 10bit to 8bit)
Example command:
ffmpeg -c:v hevc_qsv -hwaccel qsv -i hevc_10bit_1920_800.mkv -filter_complex
"scale_qsv=format=nv12" -c:v h264_qsv out.mkv
Fix:
- Incr
> On Sun, 24 May 2020 at 05:44, Soft Works
> wrote:
> >> [...]
> >> Eventually I have implemented a feature that iterates all filters,
> >> their connections and the negotiated media formats during runtime and
> >> writes them out as json or xml (using the
i
> Sent: Sunday, May 24, 2020 2:47 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] avfilter/qsvvpp: Work around a bug in
> MSDK where VPP processing hangs under certain conditions
>
> Soft Works 于2020年5月24
ere VPP processing hangs under certain conditions
>
> On Sun, May 24, 2020 at 8:13 PM Soft Works
> wrote:
> >
> > These conditions are:
> > - Dimensions are aligned to 16/32 byte (e.g. 1920x800)
> > - No scaling is done
> > - Color format conversion (e.g. 1
ere VPP processing hangs under certain conditions
>
> On Sun, May 24, 2020 at 2:13 PM Soft Works
> wrote:
> > Fix:
> > - Increase the frame height to the next alignment value
> >
>
>
> there is a strong feeling that adjustments are enforced in more cases
These are:
- Dimensions are already aligned (e.g. 1920x800)
- No scaling is done
- Color format conversion (e.g. 10bit to 8bit)
Example command:
ffmpeg -c:v hevc_qsv -hwaccel qsv -i hevc_10bit_1920_800.mkv -filter_complex
"scale_qsv=format=nv12" -c:v h264_qsv out.mkv
Fix:
- Increase the frame he
SDK where VPP processing hangs under certain conditions
>
> I don't understand functionally, but:
>
> On Sun, May 24, 2020 at 12:13:07 +, Soft Works wrote:
> > +int height_align_adjust = 0;
> > int i, ret;
> >
> > +
> > /* check
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Zhang, Guiyong
> Sent: Thursday, May 28, 2020 4:12 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] aubmit Verisilicon VPE hardware codec
> implementation
>
Hello Guiyong,
I'm curious - which actual products does that s
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Zhang, Guiyong
> Sent: Thursday, May 28, 2020 4:38 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: [FFmpeg-devel] 答复: aubmit Verisilicon VPE hardware codec
> implementation
>
> Hi softworkz,
>
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Zhang, Guiyong
> Sent: Thursday, May 28, 2020 4:58 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: [FFmpeg-devel] 答复: 答复: aubmit Verisilicon VPE hardware codec
> implementation
>
> Hi softworkz,
>
SDK where VPP processing hangs under certain conditions
>
> On Mon, May 25, 2020 at 12:40 AM Soft Works
> wrote:
>
> > These are:
> > - Dimensions are already aligned (e.g. 1920x800)
> > - No scaling is done
> > - Color format conversion (e.g. 10bit to 8bit)
&g
SDK where VPP processing hangs under certain conditions
>
> On Sat, Jun 6, 2020 at 7:29 AM Soft Works wrote:
>
> >
> >
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of
> > > Max Dmitrichenko
> > > Sent: Friday,
SDK where VPP processing hangs under certain conditions
>
> On Sat, Jun 6, 2020 at 7:29 AM Soft Works wrote:
>
> >
> >
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of
> > > Max Dmitrichenko
> > > Sent: Friday,
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Friday, June 26, 2020 7:17 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Cc: Limin Wang
> Subject: Re: [FFmpeg-devel] [PATCH 4/6] avutil/bprint: use
> AV_BPRINT_SIZE_AUTOMATIC inst
E_AUTOMATIC instead of 1
>
> Soft Works (12020-06-26):
> > Isn't it a clear benefit to have a named constant where the name of
> > the constant indicates a meaning while a plain number does not?
>
> No. If you know the API enough to use it properly, then the meaning of 1 is
&g
Hello all,
I’ve implemented a solution for a problem then creating WebVTT segments with
the segment muxer, but before I submit a patch I wanted to check back for
opinions about the approach.
THE REQUIREMENT
I need to do HLS segmentation for video/audio while additionally creating one
or more
Hi,
I’m not sure whether this has been discussed, considered or disregarded before.
I have some code ready for adding timestamps to the log output, similar to this:
$ ffmpegd -loglevel +timing
ffmpeg version 4.2.git Copyright (c) 2000-2019 the FFmpeg developers….
built with msvc
00:57:06.469 H
This commit adds two logging flags: 'timing' and 'datetiming'.
Usage: ffmpeg -logleve +timing
Timing information will only be added to log lines once transcoding has started.
---
fftools/cmdutils.c | 14 ++
fftools/ffmpeg.c | 3 +++
libavutil/log.c| 37 +++
> Why this restriction? I think all log lines should be start with
> time/date if corresponding flag is present. This makes the log to be
> easy to parse by scripts.
Initially I didn’t have this restriction, but it doesn’t work well together
with some multi-line logging.
See below for an example
0001-Add-option-to-log-timing.patch
Description: 0001-Add-option-to-log-timing.patch
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ..
> Michael Niedermayer wrote:
> >
> > > Why this restriction? I think all log lines should be start with
> > > time/date if corresponding flag is present. This makes the log to be
> > > easy to parse by scripts.
> >
> > Initially I didn’t have this restriction, but it doesn’t work well together
>
This allows having a video stream as reference stream when using the segment
muxer
---
libavformat/webvttenc.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/libavformat/webvttenc.c b/libavformat/webvttenc.c
index 61b7f54622..be85c03130 100644
--- a/libavformat/webvt
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Carl Eugen Hoyos
>
> Am Mi., 4. Sept. 2019 um 22:43 Uhr schrieb Soft Works
> :
> >
> >
> > This allows having a video stream as reference stream when using the
> > segment muxer
>
> From: ffmpeg-devel On Behalf Of
> Michael Niedermayer
> Sent: Friday, September 6, 2019 8:56 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] Add option to log timing
>
> On Wed, Sep 04, 2019 at 07:35:11PM
Michael - you probably missed my question...
-Original Message-
From: Soft Works
Sent: Friday, September 6, 2019 11:44 PM
To: FFmpeg development discussions and patches
Subject: RE: [FFmpeg-devel] [PATCH] Add option to log timing
> From: ffmpeg-devel On Behalf Of
> M
gt; On Wed, Sep 11, 2019 at 08:43:36PM +, Soft Works wrote:
> > Michael - you probably missed my question...
> >
> > -----Original Message-
> > From: Soft Works
> > Sent: Friday, September 6, 2019 11:44 PM
> > To: FFmpeg development discussions and patches
This commit adds two logging flags: 'timing' and 'datetiming'.
Usage:
ffmpeg -loglevel +timing
or
ffmpeg -loglevel +datetiming
---
fftools/cmdutils.c | 14 ++
libavutil/log.c| 37 -
libavutil/log.h| 10 ++
3 files changed, 56 inse
An int32 option cannot have a maximum of UINT32_MAX
Before this patch
-trans_color .D.V. color value (ARGB) that is used
instead of transparent color (from 0 to UINT32_MAX)
Afterwards:
-trans_color .D.V. color value (ARGB) that is used
instead of transpar
Integer values should not be printed using format specifier '%g' which leads to
inexact display in case of higher values.
Before this patch:
-trans_color .D.V. color value [...] (default
1.67772e+07)
Afterwards:
-trans_color .D.V. color value [...] (defau
It's often not obvious how option constants relate to numerical values.
Defaults are sometimes printed as numbers and from/to are always printed as
numbers.
Printing the numeric values of options constants avoids this confusion.
It also allows to see which constants are equivalent.
Before this pa
> From: ffmpeg-devel On Behalf Of
> James Almer
> Sent: Tuesday, September 17, 2019 3:11 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] Fix gif decoder max option
>
> On 9/16/2019 10:05 PM, Soft Works wrote:
> > An int32 option cannot h
This allows mapping a video stream as reference stream for creating vtt
segments when using the segment muxer. Example:
ffmpeg -i INPUT -map 0:3 -c:0 webvtt -map 0:0 -c:v:0 copy -f segment
-segment_format webvtt -segment_time 6 -write_empty_segments 1 -y
"sub_segment3%d.vtt"
The mpegts segment
Integer values should not be printed using format specifier '%g' which leads to
inexact display in case of higher values.
Before this patch:
-trans_color .D.V. color value [...] (default
1.67772e+07)
Afterwards:
-trans_color .D.V. color value [...] (defau
401 - 500 of 1691 matches
Mail list logo
