On 19.05.2024 02:00, Brad Smith wrote:
configure: enable ffnvcodec, nvenc, nvdec for FreeBSD
Signed-off-by: Brad Smith
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index b16722d83d..96b181fd21 100755
--- a/configure
+++ b/configure
@
Timo Rothenpieler (11):
avformat/flvenc: add enhanced audio codecs
avformat/flvenc: remove !size check for audio packets
avformat/flvdec: add enhanced audio codecs
avformat/flvenc: refactor fourcc writing
avformat/flvenc: write enhanced rtmp multichannel info for audio with
more than
From: Dennis Sädtler via ffmpeg-devel
Based on enhanced-rtmp v2 spec published by Veovera:
https://veovera.github.io/enhanced-rtmp/docs/enhanced/enhanced-rtmp-v2
This implementation maintains some backwards compatibility by only
writing the track information for track indices > 0. This means tha
From: Dennis Sädtler via ffmpeg-devel
Based on enhanced-rtmp v2 spec published by Veovera:
https://veovera.github.io/enhanced-rtmp/docs/enhanced/enhanced-rtmp-v2
Signed-off-by: Dennis Sädtler
---
libavformat/flvdec.c | 117 +++
1 file changed, 96 inserti
---
libavformat/flv.h| 6 ++
libavformat/flvenc.c | 143 +++
2 files changed, 111 insertions(+), 38 deletions(-)
diff --git a/libavformat/flv.h b/libavformat/flv.h
index 653c2bc82c..d030d576f3 100644
--- a/libavformat/flv.h
+++ b/libavformat/flv.h
@@
---
libavformat/flvenc.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/libavformat/flvenc.c b/libavformat/flvenc.c
index 4e79b06499..13e06aedbb 100644
--- a/libavformat/flvenc.c
+++ b/libavformat/flvenc.c
@@ -1067,11 +1067,6 @@ static int flv_write_packet(AVFormatContext *s, AVPacket
---
libavformat/rtmpproto.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/libavformat/rtmpproto.c b/libavformat/rtmpproto.c
index bc3d9df7b9..7bbb6d5313 100644
--- a/libavformat/rtmpproto.c
+++ b/libavformat/rtmpproto.c
@@ -356,9 +356,16 @@ static int gen_connect(
---
libavformat/flvdec.c | 44 ++--
1 file changed, 22 insertions(+), 22 deletions(-)
diff --git a/libavformat/flvdec.c b/libavformat/flvdec.c
index 5877828c52..4f98ff348c 100644
--- a/libavformat/flvdec.c
+++ b/libavformat/flvdec.c
@@ -1394,8 +1394,8 @@ re
---
libavformat/flvdec.c | 570 +++
1 file changed, 306 insertions(+), 264 deletions(-)
diff --git a/libavformat/flvdec.c b/libavformat/flvdec.c
index 4f98ff348c..ee22db2ce2 100644
--- a/libavformat/flvdec.c
+++ b/libavformat/flvdec.c
@@ -1273,6 +1273,7 @@
---
libavformat/flv.h| 8 +++
libavformat/flvdec.c | 119 +++
2 files changed, 116 insertions(+), 11 deletions(-)
diff --git a/libavformat/flv.h b/libavformat/flv.h
index d030d576f3..8926db6388 100644
--- a/libavformat/flv.h
+++ b/libavformat/flv.h
@@
---
libavformat/flvenc.c | 96 ++--
1 file changed, 47 insertions(+), 49 deletions(-)
diff --git a/libavformat/flvenc.c b/libavformat/flvenc.c
index 13e06aedbb..94d633fbca 100644
--- a/libavformat/flvenc.c
+++ b/libavformat/flvenc.c
@@ -492,6 +492,45 @@ sta
---
libavformat/flvenc.c | 93
1 file changed, 85 insertions(+), 8 deletions(-)
diff --git a/libavformat/flvenc.c b/libavformat/flvenc.c
index 94d633fbca..056940afc5 100644
--- a/libavformat/flvenc.c
+++ b/libavformat/flvenc.c
@@ -711,10 +711,82 @@ sta
---
libavformat/flvdec.c | 41 +
1 file changed, 25 insertions(+), 16 deletions(-)
diff --git a/libavformat/flvdec.c b/libavformat/flvdec.c
index ee2a1931b2..890958351a 100644
--- a/libavformat/flvdec.c
+++ b/libavformat/flvdec.c
@@ -1335,8 +1335,6 @@ retry
---
libavformat/flvenc.c | 90 +---
1 file changed, 67 insertions(+), 23 deletions(-)
diff --git a/libavformat/flvenc.c b/libavformat/flvenc.c
index 056940afc5..ab729702a5 100644
--- a/libavformat/flvenc.c
+++ b/libavformat/flvenc.c
@@ -131,7 +131,7 @@ type
---
libavformat/flvdec.c | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/libavformat/flvdec.c b/libavformat/flvdec.c
index 890958351a..5877828c52 100644
--- a/libavformat/flvdec.c
+++ b/libavformat/flvdec.c
@@ -1336,12 +1336,26 @@ retry:
pkt_
On 21.05.2024 20:48, Dennis Sädtler wrote:
From: Dennis Sädtler via ffmpeg-devel
I wonder what happened here, did I make a mistake when submitting the
original patch to the ML so the actual commit author name/email got
lost?
That's just what happens if your mailserver has strict SPF/DMARC co
On 22.05.2024 02:02, Michael Niedermayer wrote:
On Tue, May 21, 2024 at 11:02:22AM +0200, Timo Rothenpieler wrote:
---
libavformat/flvdec.c | 570 +++
1 file changed, 306 insertions(+), 264 deletions(-)
infinite loops
[flv @ 0x555e803d2940] Video
---
libavformat/flvdec.c | 574 +++
1 file changed, 311 insertions(+), 263 deletions(-)
diff --git a/libavformat/flvdec.c b/libavformat/flvdec.c
index 4f98ff348c..fe5a44a715 100644
--- a/libavformat/flvdec.c
+++ b/libavformat/flvdec.c
@@ -1273,6 +1273,7 @@
On 26.05.2024 07:22, Brad Smith wrote:
On 2024-05-19 7:24 a.m., Timo Rothenpieler wrote:
On 19.05.2024 02:00, Brad Smith wrote:
configure: enable ffnvcodec, nvenc, nvdec for FreeBSD
Signed-off-by: Brad Smith
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
applied, thanks
___
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...@ffmpeg.org with subject "unsubscribe".
On 28.05.2024 17:14, Andrew Sayers wrote:
On Tue, May 21, 2024 at 11:02:09AM +0200, Timo Rothenpieler wrote:
This is based on the preliminary spec for enhanced rtmp v2:
https://veovera.org/docs/enhanced/enhanced-rtmp-v2
The spec is not final, and can still undergo breaking changes, hence this
On 31/05/2024 10:53, Martin Storsjö wrote:
This allows ending up with a normal, non-fragmented file when
the file is finished, while keeping the file readable if writing
is aborted abruptly at any point. (Normally when writing a
mov/mp4 file, the unfinished file is completely useless unless it
On 31.05.2024 23:06, averne wrote:
Le 30/05/2024 à 22:42, Rémi Denis-Courmont a écrit :
Le torstaina 30. toukokuuta 2024, 22.43.05 EEST averne a écrit :
These files are taken with minimal modifications from nvidia's Linux4Tegra
(L4T) tree. nvmap enables management of memory-mapped buffers for h
From: BtbN
Fixes for example rtmps streaming over schannel.
---
libavformat/tls_schannel.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/libavformat/tls_schannel.c b/libavformat/tls_schannel.c
index 214a47a218..7265a9794d 100644
--- a/libavformat/tls_schanne
On 08.06.2024 21:49, Vittorio Giovara wrote:
On Sat, Jun 8, 2024 at 6:02 PM Michael Niedermayer
wrote:
On Tue, May 14, 2024 at 01:38:16AM +0200, Michael Niedermayer wrote:
Hi all
To keep people updated (and as this is not vissible on the ML)
heres my current list of issues marked as false po
On 10.06.2024 14:37, Vittorio Giovara wrote:
On Mon, Jun 10, 2024 at 12:04 AM Michael Niedermayer
wrote:
On Sun, Jun 09, 2024 at 03:10:09PM +0200, Vittorio Giovara wrote:
On Sun, Jun 9, 2024 at 12:50 AM Timo Rothenpieler
On 08.06.2024 21:49, Vittorio Giovara wrote:
On Sat, Jun 8, 2024 at 6
On 03.06.2024 22:28, Timo Rothenpieler wrote:
From: BtbN
This is fixed locally
Fixes for example rtmps streaming over schannel.
---
libavformat/tls_schannel.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/libavformat/tls_schannel.c b/libavformat
On 13/06/2024 14:50, Martin Storsjö wrote:
On Wed, 5 Jun 2024, Martin Storsjö wrote:
This allows ending up with a normal, non-fragmented file when
the file is finished, while keeping the file readable if writing
is aborted abruptly at any point. (Normally when writing a
mov/mp4 file, the unfini
On 14/06/2024 12:44, Martin Storsjö wrote:
On Fri, 14 Jun 2024, Gyan Doshi wrote:
On 2024-06-14 02:18 am, Martin Storsjö wrote:
On Thu, 13 Jun 2024, Gyan Doshi wrote:
On 2024-06-13 06:20 pm, Martin Storsjö wrote:
I'd otherwise want to push this, but I'm not entirely satisfied
with the opt
On 11.06.2024 15:10, Timo Rothenpieler wrote:
On 03.06.2024 22:28, Timo Rothenpieler wrote:
From: BtbN
This is fixed locally
Fixes for example rtmps streaming over schannel.
---
libavformat/tls_schannel.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git
On 18.06.2024 18:56, Gyan Doshi wrote:
FWIW, I had to do the same for securetransport on a project a couple of
years back to get rtmps working. Worked fine, and did not get any
reports of ill-effects.
You mean the FFmpeg implementation of rtmps?
Cause if so, I think that only makes use of nonb
On 20/06/2024 15:46, Martin Storsjö wrote:
On Wed, 19 Jun 2024, Martin Storsjö wrote:
This allows ending up with a normal, non-fragmented file when
the file is finished, while keeping the file readable if writing
is aborted abruptly at any point. (Normally when writing a
mov/mp4 file, the unfin
On 03.06.2024 22:28, Timo Rothenpieler wrote:
From: BtbN
Fixes for example rtmps streaming over schannel.
---
libavformat/tls_schannel.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/libavformat/tls_schannel.c b/libavformat/tls_schannel.c
index
On 24/06/2024 00:07, Timo Rothenpieler wrote:
On 03.06.2024 22:28, Timo Rothenpieler wrote:
From: BtbN
Fixes for example rtmps streaming over schannel.
---
libavformat/tls_schannel.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/libavformat
---
fftools/ffplay_renderer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fftools/ffplay_renderer.c b/fftools/ffplay_renderer.c
index 80b700b3c5..f272cb46f1 100644
--- a/fftools/ffplay_renderer.c
+++ b/fftools/ffplay_renderer.c
@@ -766,7 +766,7 @@ static void destroy(VkRend
On 01.07.2024 18:52, Josh Allmann wrote:
On Thu, 20 Jun 2024 at 17:39, Josh Allmann wrote:
In intra-only mode, frameIntervalP is 0, which means the frame
data array is smaller than the number of surfaces. This causes a
crash when closing the encoder.
Fix this by making sure the frame data arr
On 01.07.2024 15:39, Michael Niedermayer wrote:
Hi all
coverity seems to have started to do a new thing. Namely if theres a
return statement it assumes it can independant of everything occurr
an example would be av_rescale() which on overflow returns INT64_MIN
also with the right flags av_resc
On 01.07.2024 20:05, Dennis Mungai wrote:
On Mon, 1 Jul 2024 at 21:01, Timo Rothenpieler
wrote:
On 01.07.2024 18:52, Josh Allmann wrote:
On Thu, 20 Jun 2024 at 17:39, Josh Allmann
wrote:
In intra-only mode, frameIntervalP is 0, which means the frame
data array is smaller than the number
On 28.09.2021 18:22, Roman Arzumanyan wrote:
Hello,
This patch makes nvenc copy incoming hwaccel frames instead of ref count
increase.
It fixes the bug which may happen when on-GPU transcoding is done and encoder
is set to use B frames.
How to reproduce the bug:
./ffmpeg \
-hwaccel cuda -h
On 28.09.2021 19:58, Timo Rothenpieler wrote:
On 28.09.2021 18:22, Roman Arzumanyan wrote:
Hello,
This patch makes nvenc copy incoming hwaccel frames instead of ref
count increase.
It fixes the bug which may happen when on-GPU transcoding is done and
encoder is set to use B frames.
How to
On 28.09.2021 19:58, Timo Rothenpieler wrote:
Hmm, so far my approach to deal with this was to inject a
scale_cuda=passthrough=0 into the filter chain, which pretty much does
exactly this, but only controllable by the user.
But I do agree that this is a bit of a clutch and not all that user
On 13.09.2021 11:07, Roman Arzumanyan wrote:
This patch adds scale2ref_npp video filter which is similar to scale2ref, but
accelerated by NPP. CLI sample:
./ffmpeg \
-hwaccel cuda -hwaccel_output_format cuda \
-i ./bbb_sunflower_1080p_30fps_normal.mp4 \
-i ./920px-Wilber-huge-alpha
From 0df6297bd3664beb05c813c5fc62852e61616fa9 Mon Sep 17 00:00:00 2001
From: Roman Arzumanyan
Date: Mon, 6 Sep 2021 14:26:27 +0300
Subject: [PATCH] sharpen_npp video filter added
Same as the other patch, should be as the mail subject.
---
configure| 5 +-
libavfilter/Ma
---
fftools/ffmpeg.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
Not sure if there is any downside to this.
Threading for hwaccel does not make a whole lot of sense, and at least
in case of nvdec wastes a lot of VRAM for no performance gain, and
specially on high core
On 29.09.2021 19:17, Dennis Mungai wrote:
A potential downside to this would be on QSV's side, which needs at least
2 threads to prevent dead-locking, see
https://github.com/Intel-Media-SDK/MediaSDK/blob/master/_studio/mfx_lib/scheduler/linux/src/mfx_scheduler_core_ischeduler.cpp#L90-L93
Is th
On 29.09.2021 19:31, Dennis Mungai wrote:
On Wed, 29 Sept 2021 at 20:22, Timo Rothenpieler
wrote:
On 29.09.2021 19:17, Dennis Mungai wrote:
A potential downside to this would be on QSV's side, which needs at least
2 threads to prevent dead-locking, see
https://github.com/Intel-Medi
On 30.09.2021 02:02, Andreas Rheinhardt wrote:
Timo Rothenpieler:
On 29.09.2021 19:31, Dennis Mungai wrote:
On Wed, 29 Sept 2021 at 20:22, Timo Rothenpieler
wrote:
On 29.09.2021 19:17, Dennis Mungai wrote:
A potential downside to this would be on QSV's side, which needs at
least
2 th
On 30.09.2021 20:51, Roman Arzumanyan wrote:
Thanks for review, Timo.
Please find revised patch attached.
(de)interlacing is now removed, doc entry was added as well.
applied with a few minor amendments, thanks!
While testing this via "-vf scale_npp=format=yuv420p,sharpen_npp" I
discovered
On 08.10.2021 15:32, James Almer wrote:
Some packages may not define custom cflags, in which case a simple
"pkg-config --cflags" call will return an empty string.
This change will be useful to get a valid include path that can be
used in library checks.
Is that at all a standard thing with pkgc
From: Roman Arzumanyan
Signed-off-by: Timo Rothenpieler
---
Here's my revised version of the patch.
It brings its order of operation much more in line with normal scale/scale2ref.
Also gets rid of differences in option parsing between the 2ref and non-2ref
version of the filters.
I also
On 31.10.2021 14:35, Timo Rothenpieler wrote:
From: Roman Arzumanyan
Signed-off-by: Timo Rothenpieler
---
Here's my revised version of the patch.
It brings its order of operation much more in line with normal scale/scale2ref.
Also gets rid of differences in option parsing between the 2re
On 31.10.2021 14:54, Timo Rothenpieler wrote:
On 31.10.2021 14:35, Timo Rothenpieler wrote:
From: Roman Arzumanyan
Signed-off-by: Timo Rothenpieler
---
Here's my revised version of the patch.
It brings its order of operation much more in line with normal
scale/scale2ref.
Also gets r
On 15.11.2021 19:21, Dennis Mungai wrote:
Hello.
Were you able to build FFmpeg with this filter enabled?
So far, building this package does not generate any pkgconfig file in the
configured prefix, and FFmpeg's ./configure cannot detect it.
I filed the issue on libplacebo's project page, with
+for (i = 0; i < nb_pixel / 4; i++) {
+
+int *dx_cur = dxdy + 8 * i;
+int *dy_cur = dxdy + 8 * i + 4;
+
+call_horiz(ctx, 1, src_dptr, src_width, src_height, src_pitch,
+ integ_img, dx_cur, dy_cur, pixel_size);
+
+call_vert(ctx, 1, src_width, sr
On 06.10.2023 18:43, Hendrik Leppkes wrote:
On Fri, Oct 6, 2023 at 3:47 PM Timo Rothenpieler wrote:
I'm quite confused why this specific instance suddenly causes so much upset.
Because its bad form to break compilation of master, if all it took to
avoid that is change the order of push
On 14.10.2023 19:24, Stefano Sabatini wrote:
Fix rendering of int values within a side data element, which was
broken since commit d2d3a83ad93, where the side data element was
correctly marked as a variable fields element. Logic to render a
string variable was implemented already, but it was not
On 22.10.2023 13:24, Gyan Doshi wrote:
The vidstab library added support in Nov 2020 for writing/reading
the transforms data in binary in addition to ASCII. The library default
was changed to binary format but no changes were made to the AVfilters
resulting in data file for writing or reading bei
On 22.10.2023 13:57, Gyan Doshi wrote:
On 2023-10-22 05:04 pm, Timo Rothenpieler wrote:
On 22.10.2023 13:24, Gyan Doshi wrote:
The vidstab library added support in Nov 2020 for writing/reading
the transforms data in binary in addition to ASCII. The library default
was changed to binary
On 06.11.2023 16:19, Michael Riedl wrote:
Signed-off-by: Michael Riedl
---
libavformat/webrtc.c | 398 +++
libavformat/webrtc.h | 70
2 files changed, 468 insertions(+)
create mode 100644 libavformat/webrtc.c
create mode 100644 libavforma
On 24/11/2023 10:38, Paul B Mahol wrote:
Can not access irc anymore.
Does it tell you which specific ban affects you?
A bunch of likely way too broad bans were installed yesterday.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.o
I don't quite understand the commit message.
It should start with "avcodec/nvenc:" and then state what it's changing
and why.
On 24/11/2023 08:04, GOOR, Jean-Noel wrote:
Signed-off-by: GOOR, Jean-Noël
---
libavcodec/nvenc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
FFmpeg has instances of DECLARE_ALIGNED(32, ...) in a lot of structs,
which then end up heap-allocated.
By declaring any variable in a struct, or tree of structs, to be 32 byte
aligned, it allows the compiler to safely assume the entire struct
itself is also 32 byte aligned.
This might make the co
On 05.12.2023 09:15, Xiang, Haihao wrote:
From: Haihao Xiang
2M is suitable for more cases, e.g. 4K video.
Signed-off-by: Haihao Xiang
---
libavcodec/qsvenc_av1.c | 2 +-
libavcodec/qsvenc_h264.c | 2 +-
libavcodec/qsvenc_hevc.c | 2 +-
libavcodec/qsvenc_mpeg2.c | 2 +-
libavcodec/q
On 06/12/2023 07:51, Xiang, Haihao wrote:
On Di, 2023-12-05 at 12:47 +0100, Timo Rothenpieler wrote:
On 05.12.2023 09:15, Xiang, Haihao wrote:
From: Haihao Xiang
2M is suitable for more cases, e.g. 4K video.
Signed-off-by: Haihao Xiang
---
libavcodec/qsvenc_av1.c | 2 +-
libavcodec
On 03/12/2023 21:10, Timo Rothenpieler wrote:
FFmpeg has instances of DECLARE_ALIGNED(32, ...) in a lot of structs,
which then end up heap-allocated.
By declaring any variable in a struct, or tree of structs, to be 32 byte
aligned, it allows the compiler to safely assume the entire struct
itself
On 06/12/2023 13:31, James Almer wrote:
On 12/3/2023 5:10 PM, Timo Rothenpieler wrote:
FFmpeg has instances of DECLARE_ALIGNED(32, ...) in a lot of structs,
which then end up heap-allocated.
By declaring any variable in a struct, or tree of structs, to be 32 byte
aligned, it allows the compiler
On 06/12/2023 14:25, Martin Storsjö wrote:
On Sun, 3 Dec 2023, Timo Rothenpieler wrote:
FFmpeg has instances of DECLARE_ALIGNED(32, ...) in a lot of structs,
which then end up heap-allocated.
By declaring any variable in a struct, or tree of structs, to be 32 byte
aligned, it allows the
On 06.12.2023 14:25, Martin Storsjö wrote:
On Sun, 3 Dec 2023, Timo Rothenpieler wrote:
FFmpeg has instances of DECLARE_ALIGNED(32, ...) in a lot of structs,
which then end up heap-allocated.
By declaring any variable in a struct, or tree of structs, to be 32 byte
aligned, it allows the
On 08.12.2023 11:01, Andreas Rheinhardt wrote:
Timo Rothenpieler:
FFmpeg has instances of DECLARE_ALIGNED(32, ...) in a lot of structs,
which then end up heap-allocated.
By declaring any variable in a struct, or tree of structs, to be 32 byte
aligned, it allows the compiler to safely assume the
On 26/03/2019 13:47, Yufei He wrote:
Hi
Is there option for scaling on transcoding ?
e.g. transcoding from a quadhd file to 640 * 480.
Thanks.
Yufei.
Yes there is, but this is ffmpeg-devel, so not the place to ask user
questions.
smime.p7s
Description: S/MIME Cryptographic Signature
More a general question regarding OpenCL filters than related to this
specific one.
We are not integrating OpenCL acceleration into the relevant native
filter anymore, like the very old original OpenCL infra worked, are we?
So that vf_colorkey would just use OpenCL acceleration on its own
whenev
On 18/04/2019 09:49, Gyan wrote:
Patchwork can incorrectly assign ownership. See
https://patchwork.ffmpeg.org/patch/12680/
The author is Sam John as identified by Message ID as well as the From
field in the headers, yet Patchwork attributes this patch to "Oliver
Collyer via ffmpeg-devel", a
Ok. Then shouldn't it assign 'Sam John via ffmpeg-devel' as the author?
It did do that for 'Oliver Collyer via ffmpeg-devel', the string wrongly
substituted here.
This looks like a parser failure in Patchwork.
Gyan
If the patch is sent with git send-email, the From: header of the E-Mail
is
applied, thanks.
smime.p7s
Description: S/MIME Cryptographic Signature
___
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...@ffmpeg.org w
On 24/04/2019 01:38, Carl Eugen Hoyos wrote:
2017-12-29 13:16 GMT+01:00, Cyber Sinh :
Sorry for the diff instead of regular git patch. Here is the patch.
Only saw this today after wondering
why nobody tried using wsl before...
I'm using WSL since a while, but never bothered trying to setup M
On 28/04/2019 22:02, Marton Balint wrote:
Hi All,
There has been discussion on the mailing list several times about the
inclusion of support for closed source components (codecs, formats,
filters, etc) in the main ffmpeg codebase.
Also the removal of libNDI happened without general consensus
applied
smime.p7s
Description: S/MIME Cryptographic Signature
___
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...@ffmpeg.org with subje
applied
smime.p7s
Description: S/MIME Cryptographic Signature
___
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...@ffmpeg.org with subje
On 04.05.2019 16:13, Paul B Mahol wrote:
Signed-off-by: Paul B Mahol
---
doc/filters.texi | 18 +++
libavfilter/Makefile | 1 +
libavfilter/allfilters.c | 1 +
libavfilter/vf_colorkey.c | 102 +-
4 files changed, 121 insertions(+)
On 10/05/2019 15:55, Gyan wrote:
At present, if the command args passed to drawtext contain any invalid
values, ffmpeg may crash or, at best, stop drawing any text.
Attached patch gets the filter to continue with existing parameters, if
not all of the changes can be parsed or applied. This allow
On 14.05.2019 05:12, Philip Langdale wrote:
After Sergey's bug report, I went and fixed a couple of other things
I noticed while I was looking at the filter.
Philip Langdale (3):
avfilter/vf_scale_cuda: Fix incorrect scaling of > 8bit content
avfilter/vf_scale_cuda: Add support for YUV444P
On 22.05.2019 08:59, lance.lmw...@gmail.com wrote:
From: Limin Wang
The testing command for the HDR10 output with nvenc:
$ ./ffmpeg_g -y -i 4K.mp4 -c:v hevc_nvenc -g 7 -color_primaries bt2020
-colorspace bt2020_ncl -color_trc smpte2084 -sei hdr10 \
-master_display
"G(13250,34500)B(75
On 23.05.2019 10:06, Asaf Kave wrote:
Hello all,
I am using FFmpeg libarary in my software to do HW decoding for video
(H.264\H.265) on windows machine.
My decoding is based on 'hw_decode.c' example, and after i call decode a
frame i am using AVFrame::data[3] to get the pointer to
the IDirect3DS
On 24/05/2019 01:49, Josh Allmann wrote:
Makes certain usages of the lavfi API easier.
---
libavfilter/vf_scale_cuda.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/libavfilter/vf_scale_cuda.c b/libavfilter/vf_scale_cuda.c
index b7cdb81081..6b1ef2bb6f 100644
On 24.05.2019 18:27, Josh Allmann wrote:
On Fri, 24 May 2019 at 06:00, Timo Rothenpieler wrote:
On 24/05/2019 01:49, Josh Allmann wrote:
Makes certain usages of the lavfi API easier.
---
libavfilter/vf_scale_cuda.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff
On 24.05.2019 18:39, Josh Allmann wrote:
The first frame is scaled correctly, and subsequent frames are
over-scaled / cropped since the frame data is reset with the
hwframe after each invocation of the scaler.
The hwframe-allocated frame has a width/height that is 32-bit
aligned. The scaler uses
On 24.05.2019 21:32, Сергей Свечников wrote:
Actually, I've submitted the fix a while ago and got ignored. I then wrote
to Timo directly to his email and got ignored again.
https://github.com/Svechnikov/ffmpeg-scale-cuda-problem
I simply missed the original mail to the list, sorry about that.
On 27.05.2019 23:49, Lance Wang wrote:
On Saturday, May 25, 2019, James Almer wrote:
On 5/22/2019 3:59 AM, lance.lmw...@gmail.com wrote:
From: Limin Wang
The testing command for the HDR10 output with nvenc:
$ ./ffmpeg_g -y -i 4K.mp4 -c:v hevc_nvenc -g 7 -color_primaries bt2020
-colorspace
applied
smime.p7s
Description: S/MIME Cryptographic Signature
___
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...@ffmpeg.org with subje
On 30.07.2019 09:51, Rodger Combs wrote:
This avoids using the CUDA SDK at all; instead, we provide a minimal
reimplementation of the basic functionality that lavfi actually uses.
It generates very similar code to what NVCC produces.
The header contains no implementation code derived from the SD
On 02.08.2019 11:18, Stefan Schoenefeld wrote:
Hi all,
Recently we encountered an issue when decoding a h.263 file:
FFmpeg will freeze when decoding h.263 video with NVDEC. Turns out this is not
directly related to NVDEC but is a problem that shows with several other HW
decoders like VDPAU, t
On 04.08.2019 07:56, Michael Niedermayer wrote:
On Sun, Jul 21, 2019 at 07:11:40PM +0200, Michael Niedermayer wrote:
On Mon, May 20, 2019 at 08:39:45PM +0200, Michael Niedermayer wrote:
Hi
Its quite some time since 4.1 so its probably getting time to branch
4.2.
If there are any bugs you want
On 02.08.2019 11:18, Stefan Schoenefeld wrote:
Hi all,
Recently we encountered an issue when decoding a h.263 file:
FFmpeg will freeze when decoding h.263 video with NVDEC. Turns out this is not
directly related to NVDEC but is a problem that shows with several other HW
decoders like VDPAU, t
On 30.07.2019 09:51, Rodger Combs wrote:
This avoids using the CUDA SDK at all; instead, we provide a minimal
reimplementation of the basic functionality that lavfi actually uses.
It generates very similar code to what NVCC produces.
The header contains no implementation code derived from the SD
On 04.08.2019 23:52, Andreas Rheinhardt wrote:
It uses a nonstandard inclusion guard.
Is there any problem with just fixing the inclusion guard instead?
I forgot that this exists, but the inclusion guard in it looked fairly
standard to me.
Feel free to just fix it.
smime.p7s
Description: S
On 05/08/2019 03:09, Andreas Rheinhardt wrote:
cuda_runtime.h as well as dynlink_loader.h used nonstandard inclusion
guards with an AV_ prefix, although these files are not in an libav*/
path. So change the inclusion guards and adapt the ref file of the
source fate test accordingly.
Signed-off-b
On 05.08.2019 21:47, Ricardo Constantino wrote:
MSYS2 converts paths to MinGW-based applications from unix to
pseudo-windows paths on execution time.
Since there was no space between '-include' and the path, MSYS2 doesn't
detect the path properly.
---
configure | 2 +-
1 file changed, 1 insert
On 08/08/2019 20:33, OvchinnikovDmitrii wrote:
Added linux support for amf encoder through vulkan.
To use h.264(AMD VCE) encoder on linux amdgru-pro version 19.20+ and
amf-amdgpu-pro package(amdgru-pro contains, but does not install automatically)
are required.
This driver can be installed usi
On 12/08/2019 12:35, Дмитрий Овчинников wrote:
Yes, it is possible, but it is required to implement separate patch with
selector dx9, dx11, vulkan. We could do it when this one is committed.
I will double check with opencl interop and will comeback.
There is no standardized OpenCL/Vulkan Intero
---
libavcodec/avcodec.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
index 31e50d5a94..5ec7a2430b 100644
--- a/libavcodec/avcodec.h
+++ b/libavcodec/avcodec.h
@@ -1616,6 +1616,7 @@ typedef struct AVCodecContext {
* The allocated memory shou
1 - 100 of 1371 matches
Mail list logo
