Diederick Niehorster:
> Signed-off-by: Diederick Niehorster
> ---
> configure | 2 +
> doc/examples/.gitignore| 1 +
> doc/examples/Makefile | 47
> doc/examples/Makefile.example | 1 +
> doc/examples/device_ge
Michael Fabian 'Xaymar' Dirks:
> On 2021-05-24 22:15, Andreas Rheinhardt wrote:
>> michael.di...@xaymar.com:
>>> From: Michael Fabian 'Xaymar' Dirks
>>>
>>> Adds "timestamp_precision" to the available options for Matroska muxing.
>>> The option enables users and developers to change the precision
On Fri, Jun 4, 2021 at 4:56 PM Valerii Zapodovnikov
wrote:
> v2 is done by "git send-email -v2 -1" not what you did here.
>
Thanks, I didn't know that. I am unclear -- do you want me to resubmit the
patch? I can just apply and push it myself if there are no objections,
although I am not the m
On Saturday, 5 June 2021 2:49:01 AM AEST Timo Rothenpieler wrote:
> Pushed a very much refactored version of this patch and some more
> refactoring on top of it.
>
> It still shows the crash, but both the previous code and this code seem
> fine to me in that regard.
Thanks for the work, and the gu
v2 is done by "git send-email -v2 -1" not what you did here.
___
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 "u
Yes, RGB is signalled by Identity matrix if and only if XYZ is not
in transfer. XYZ primaires are just normal primaries that can be
used for normal RGB, no problem, so I do not check for them.
No need to test for sRGB primaries (that is AVCOL_PRI_BT709), as
ffplay does not know what that is (is not
пн, 24 мая 2021 г., 6:42 Valerii Zapodovnikov :
> ---
> libavfilter/vf_hqdn3d.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavfilter/vf_hqdn3d.c b/libavfilter/vf_hqdn3d.c
> index 8d71ae316d..bd3eb2d01c 100644
> --- a/libavfilter/vf_hqdn3d.c
> +++ b/libavfilter/vf_h
Yeah, 0 to 3, but this is 4. We are counting from 0, not from 1. So that
would be some kind of fifth profile.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or emai
You may want to wait for at least some review and then of course, Andreas,
for example, sometimes sends 200 patch series.
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20201203003628.778278-6-andreas.rheinha...@gmail.com/
___
ffmpeg-devel mailing list
Hi All,
If instead of the various separate patch series i have sent the last
few days, you would like to see one integrated series where all are
applied on top of each other and conflicts resolves, please see all
the commits ahead of master (currently 22) on the develop branch here:
https://github
Hi,
On Wed, Jun 2, 2021 at 1:55 PM Valerii Zapodovnikov
wrote:
>
> HDR10+ test bitstream https://www.webmproject.org/vp9/levels/
>
> BTW, who knows what is Profile 4 VP9 (i.e. VP9.4)?
> https://stackoverflow.com/questions/61413665
>
This link is talking about a file with DRM. VP9 allows for 4 p
Pushed a very much refactored version of this patch and some more
refactoring on top of it.
It still shows the crash, but both the previous code and this code seem
fine to me in that regard.
smime.p7s
Description: S/MIME Cryptographic Signature
__
On 6/1/2021 12:48 PM, James Almer wrote:
They should not be accessed outside of libavformat.
Signed-off-by: James Almer
---
fftools/ffmpeg.c | 10 ++
fftools/ffmpeg.h | 1 +
fftools/ffmpeg_opt.c | 1 +
3 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/fftools
Hi Nicolas,
On Fri, Jun 4, 2021 at 11:06 AM Nicolas George wrote:
> I do not understand: you did send them as a large patch series. Twice,
> by the way, which is confusing.
Yes, the first series got messed up, send it a second time correctly.
I've cleaned up patchwork, it only shows the right on
Hi,
On Fri, 9 Apr 2021, Camille Gonnet wrote:
Parityfec (RFC 2733) and ulpfec (RFC 5109) generic FEC encoding for RTP streams.
Signed-off-by: Camille Gonnet
---
Changelog | 1 +
doc/general_contents.texi | 1 +
doc/protocols.texi| 106 +
libavformat/Makefile
On Thu, 13 May 2021, Josh Allmann wrote:
Previously, one or the other would have been ignored, but not both.
Since the probe terminates at three streams, it could exit
prematurely if both data and subtitles are present along with
slightly trailing media, usually video trailing audio.
Trailing m
Diederick C. Niehorster (12021-06-04):
> Just sent the patch, it completes my push together with my other
> patches of the last few days to make the dshow device fully
> programmatically controllable and discoverable.
>
> By the way, each of these patch series applies to master, but not on
> top o
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of ?
> ?
> Sent: Friday, June 4, 2021 9:27 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] libavformat/movenc: Support encryption of
> H265 stream in AnnexB format
>
>
> Ping.
>
> This change is
From: Zhao Zhili
---
v2: update doc
doc/protocols.texi | 5 +
libavformat/libsrt.c | 5 -
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/doc/protocols.texi b/doc/protocols.texi
index 8b21ce046e..d3095c88c6 100644
--- a/doc/protocols.texi
+++ b/doc/protocols.texi
@@ -161
From: Zhao Zhili
There is no good use case for out of order delivery of data. For live
streaming with TSBPD enabled by default, the receiver get data in order
based on the timestamps. However, if TSBPD is disabled, the data can
be delivered out of order.
---
libavformat/libsrt.c | 2 +-
1 file c
Add 'srt_streamid' option as an alias for 'streamid'.
---
doc/protocols.texi | 3 +++
libavformat/libsrt.c | 1 +
2 files changed, 4 insertions(+)
diff --git a/doc/protocols.texi b/doc/protocols.texi
index 8371f83059..8b21ce046e 100644
--- a/doc/protocols.texi
+++ b/doc/protocols.texi
@@ -1558,
21 matches
Mail list logo
