There seems to be an indentation issue here:
> +if (avctx->profile == FF_PROFILE_UNKNOWN) {
> switch (avctx->codec_tag) {
> case MKTAG('a','p','c','o'):
and here:
> av_log(avctx, AV_LOG_WARNING, "Unknown prores profile %d\n",
> avctx->codec_tag);
> }
> +}
___
> // Change all the ' --' strings to '~--' so that
> // they can be identified as tokens.
> while ((conflist = strstr(str, " --")) != NULL) {
> -strncpy(conflist, "~--", 3);
> +conflist[0] = '~';
> }
Doesn't this simply replace -- with ~- ?
The comment seems wro
> FFABS is slower than fabs.
Not generally. That is highly dependent on compiler/flags/architecture.
In some cases, FFABS may actually be faster, in others maybe not.
The expected result would be on-par performance.
___
ffmpeg-devel mailing list
ffmpeg
rom 00c9203f0349dbae6e701104d5a7f6c4e6fa0159 Mon Sep 17 00:00:00 2001
From: Gregor Riepl
Date: Tue, 24 May 2016 15:17:22 +0200
Subject: [PATCH] ffserver: fixed deallocation bug in build_feed_streams
Signed-off-by: Gregor Riepl
---
ffserver.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/ffserver.c b/ffserve
the issue tracker was incorrect and
changed other parts of the segment calculation logic. With this
patch, only the interpretation of the attributes is changed.
Some warnings are added to account for potential errors in manifests.
Fixes: #8522
Signed-off-by: Gregor Riepl
---
libavformat
+#include
Not sure this header can be used every enveriment. Or what about use
#define TRUE 1
#define FALSE 0
> ?
You are right, this is C99.
I'd rather not define a custom boolean type just for this, it would be
better if FFmpeg had something like FF_TRUE/FF_FALSE.
fftools/ffmpeg_opt.c se
what's done in fftools/ffmpeg_opt.c.
Fixes: #8522
Signed-off-by: Gregor Riepl
---
libavformat/dashdec.c | 209 --
1 file changed, 161 insertions(+), 48 deletions(-)
diff --git a/libavformat/dashdec.c b/libavformat/dashdec.c
index 29d4680c68..df5d4
The result should be no need to provide "crypto://". The ffmpeg file format
detection should detect that ".crypto" should be handled by the crypto
plugin.
Instead of a custom descriptor file format that is only used for this
particular special case, you could also define a custom URI, such as:
I can't find a single thing about this in the ffmpeg documentation.
How is this called, where can I read more about it and - most importantly -
does it work out of the box?
No, it does not.
This was a suggestion that sounds like a better option than a custom
metadata descriptor file that is onl
> What we are looking for is pretty straight forward. I like to capture
> the HDMI video/audio output of a Chromecast dongle and distribute it
> into a LAN network via UDP multicast. Something like this:
>
> Chromecast -> HDMI -> HDMI-USB Capture -> RPi4/8G (with FFmpeg) ->
> UDP/Multicast -> LAN
10 matches
Mail list logo
