Hi!
Attached patch intends to fix ticket #5975, rfc 2435 says stream type
64 should be treated like 0.
Please review, Carl Eugen
From 690f2fccf766f3cbb23a1ef45e235e25c355b197 Mon Sep 17 00:00:00 2001
From: Carl Eugen Hoyos
Date: Fri, 5 Jan 2018 05:40:30 +0100
Subject: [PATCH] lavf/rtpdec_jpeg: T
2018-01-05 3:24 GMT+01:00 Rostislav Pehlivanov :
> On 4 January 2018 at 04:38, Carl Eugen Hoyos wrote:
>> Attached patch fixes a warning here when compiling the opus encoder.
> I don't like this patch and I'm planning on using that variable in the
> future.
New patch attached.
Thank you, Carl
i think we do not need lock. and we need keep on the last codec pointer.
On Fri, Jan 5, 2018 at 2:28 AM, wm4 wrote:
> On Thu, 4 Jan 2018 15:19:04 -0300
> James Almer wrote:
>
> > Signed-off-by: James Almer
> > ---
> > With this, the last users of libavutil's atomic wrappers are dealt
> > wi
On 2018/1/5 10:24, Rostislav Pehlivanov wrote:
> On 4 January 2018 at 04:38, Carl Eugen Hoyos wrote:
>
>> Hi!
>>
>> Attached patch fixes a warning here when compiling the opus encoder.
>>
>> Please comment, Carl Eugen
>>
>> ___
>> ffmpeg-devel mailing
On Thu, Jan 04, 2018 at 07:52:17AM +, Marc-Antoine ARNAUD wrote:
> Sorry, I have upgrade and re-generate patches.
will apply
thanks
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The real ebay dictionary, page 1
"Used only once"- "Some unspecified defe
On 4 January 2018 at 04:38, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch fixes a warning here when compiling the opus encoder.
>
> Please comment, Carl Eugen
>
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> http://ffmpeg.org/mailman/l
On 2018/1/4 12:38, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch fixes a warning here when compiling the opus encoder.
>
> Please comment, Carl Eugen
LGTM
>
>
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> http://ffmpeg.org/mailman/lis
Hello All,
I have made dump of DTMB streams (digital TV standard in China, like
DVB-T in Europe, etc).
Here is all files shared (50MB from each multiplex frequency):
https://drive.google.com/drive/folders/1FOdZyQitKQXwBoyRlnRu34mP9fXcVBLn?usp=sharing
Here is noted issues:
* artifacts if we try
Signed-off-by: James Almer
---
libavfilter/avfilter.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/libavfilter/avfilter.c b/libavfilter/avfilter.c
index b98b32bacb..ff7df672fd 100644
--- a/libavfilter/avfilter.c
+++ b/libavfilter/avfilter.c
@@ -19,7 +19,6 @
Signed-off-by: James Almer
---
libavformat/format.c | 34 +++---
1 file changed, 23 insertions(+), 11 deletions(-)
diff --git a/libavformat/format.c b/libavformat/format.c
index 38ca2a3465..759b5b1ab4 100644
--- a/libavformat/format.c
+++ b/libavformat/format.c
@@ -19
Signed-off-by: James Almer
---
libavcodec/utils.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/libavcodec/utils.c b/libavcodec/utils.c
index dfbfe98d63..4d736d2e7d 100644
--- a/libavcodec/utils.c
+++ b/libavcodec/utils.c
@@ -26,7 +26,6 @@
*/
#include "conf
On 1/4/2018 8:55 PM, Michael Niedermayer wrote:
> On Thu, Jan 04, 2018 at 03:19:02PM -0300, James Almer wrote:
>> Signed-off-by: James Almer
>> ---
>> libavcodec/parser.c | 11 +++
>> 1 file changed, 7 insertions(+), 4 deletions(-)
>
> LGTM
>
> thx
Pushed, thanks.
_
On Thu, Jan 04, 2018 at 03:19:02PM -0300, James Almer wrote:
> Signed-off-by: James Almer
> ---
> libavcodec/parser.c | 11 +++
> 1 file changed, 7 insertions(+), 4 deletions(-)
LGTM
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Many things micr
On Thu, Jan 04, 2018 at 03:19:01PM -0300, James Almer wrote:
> Signed-off-by: James Almer
> ---
> libavcodec/utils.c | 15 +--
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/libavcodec/utils.c b/libavcodec/utils.c
> index dfbfe98d63..61acf36c4b 100644
> --- a/liba
On Thu, Jan 04, 2018 at 10:08:08AM +0100, Paul B Mahol wrote:
> On 1/3/18, Michael Niedermayer wrote:
> > Fixes: signed integer overflow: 1024 + 2147483640 cannot be represented in
> > type 'int'
> > Fixes: 4671/clusterfuzz-testcase-minimized-6027464343027712
> >
> > Found-by: continuous fuzzing p
On Thu, Jan 04, 2018 at 01:36:01AM +0100, Marton Balint wrote:
>
>
> On Wed, 3 Jan 2018, Michael Niedermayer wrote:
>
> >On Wed, Jan 03, 2018 at 08:00:24PM +0100, Marton Balint wrote:
> >>
> >>
> >>On Wed, 3 Jan 2018, Marton Balint wrote:
> >>
> >>>
> >>>On Tue, 2 Jan 2018, Michael Niedermayer w
The framerate filter was quite convoluted with some filter_frame /
request_frame logic bugs. It seemed easier to rewrite the whole filter_frame /
request_frame part and also the frame interpolation ratio calculation part in
one step.
Notable changes:
- The filter now only stores 2 frames instead o
Hello,
after my last update, I got not any response. Is there still something
wrong with the patch?
Regards
Jonathan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Sat, 30 Dec 2017, Marton Balint wrote:
On Mon, 25 Dec 2017, Michael Niedermayer wrote:
On Sat, Dec 23, 2017 at 11:17:38PM +0100, Marton Balint wrote:
It was truncated to int later on anyway. Fate test changes are due to
rounding
instead of truncation.
Signed-off-by: Marton Balint
--
Allows Wayland users to use vaapi without having to specify a
vaapi drm device path.
"wayland-0" is the default display name (like ":0") under Wayland,
and given there's no way to get the display name from a connection,
use it.
Signed-off-by: Rostislav Pehlivanov
---
configure
On Thu, 4 Jan 2018 20:33:16 +
Rostislav Pehlivanov wrote:
> Allows Wayland users to use vaapi without having to specify a
> vaapi drm device path.
>
> Signed-off-by: Rostislav Pehlivanov
> ---
> configure | 6 +-
> libavutil/hwcontext_vaapi.c | 29 ++
On 04/01/18 20:33, Rostislav Pehlivanov wrote:
> Allows Wayland users to use vaapi without having to specify a
> vaapi drm device path.
>
> Signed-off-by: Rostislav Pehlivanov
> ---
> configure | 6 +-
> libavutil/hwcontext_vaapi.c | 29 +
> 2 f
Allows Wayland users to use vaapi without having to specify a
vaapi drm device path.
Signed-off-by: Rostislav Pehlivanov
---
configure | 6 +-
libavutil/hwcontext_vaapi.c | 29 +
2 files changed, 34 insertions(+), 1 deletion(-)
diff --git a/con
On Wed, Jan 03, 2018 at 07:14:23PM +1100, mi...@brew.sh wrote:
> From: Misty De Meo
>
> ---
> libavcodec/adpcm.c | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/libavcodec/adpcm.c b/libavcodec/adpcm.c
> index be206c55ba..50ffba0db6 100644
> --- a/libavcodec/adpcm.c
> +++ b/libav
On Wed, Jan 03, 2018 at 07:14:22PM +1100, mi...@brew.sh wrote:
> From: Misty De Meo
>
> Certain AIFF files encode XA ADPCM compressed audio using a chunk
> with the tag `APCM`. Aside from this custom chunk type, they're
> otherwise standard AIFF files. I've only observed these files in the
> Sega
On Tue, Jan 02, 2018 at 08:15:07AM +, endus...@gmail.com wrote:
> From: Author Name
This looks like unintended as commit author
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Those who are best at talking, realize last or never when they are wrong.
sign
On 1/4/2018 3:28 PM, wm4 wrote:
> On Thu, 4 Jan 2018 15:19:04 -0300
> James Almer wrote:
>
>> Signed-off-by: James Almer
>> ---
>> With this, the last users of libavutil's atomic wrappers are dealt
>> with.
>
> Technically, you need to lock when reading the next pointers too? Don't
> know if t
Signed-off-by: James Almer
---
fftools/cmdutils.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fftools/cmdutils.c b/fftools/cmdutils.c
index 6920ca0764..f66591548a 100644
--- a/fftools/cmdutils.c
+++ b/fftools/cmdutils.c
@@ -550,7 +550,9 @@ int opt_default(void *optctx, const char *opt,
Having all the public functions marked as deprecated is enough.
This gets rid of a warning spam when compiling any file including
libavresample/avresample.h even when avresample is not enabled, like
it's the case with fftools/cmdutils.c
Signed-off-by: James Almer
---
libavresample/avresample.h
On 1/4/2018 7:50 AM, wm4 wrote:
> On Thu, 4 Jan 2018 01:14:08 -0300
> James Almer wrote:
>
>> w32threads and os2threads both support static mutex initialization now,
>> so don't limit it to pthreads only.
>>
>> Signed-off-by: James Almer
>> ---
>> libavutil/log.c | 14 --
>> 1 file
On Thu, 4 Jan 2018 15:19:04 -0300
James Almer wrote:
> Signed-off-by: James Almer
> ---
> With this, the last users of libavutil's atomic wrappers are dealt
> with.
Technically, you need to lock when reading the next pointers too? Don't
know if that actually matters.
__
On 1/4/2018 3:17 PM, Michael Niedermayer wrote:
> On Thu, Jan 04, 2018 at 01:14:07AM -0300, James Almer wrote:
>> Signed-off-by: James Almer
>> ---
>> fftools/ffmpeg.c | 19 ---
>> fftools/ffmpeg.h | 7 ++-
>> fftools/ffmpeg_opt.c | 2 +-
>> 3 files changed, 11 inser
Signed-off-by: James Almer
---
libavcodec/parser.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/libavcodec/parser.c b/libavcodec/parser.c
index 670680ea7c..747ea2ee8a 100644
--- a/libavcodec/parser.c
+++ b/libavcodec/parser.c
@@ -25,9 +25,9 @@
#include
#inc
Signed-off-by: James Almer
---
With this, the last users of libavutil's atomic wrappers are dealt
with.
libavfilter/avfilter.c | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/libavfilter/avfilter.c b/libavfilter/avfilter.c
index b98b32bacb..945fc65e5f 10064
Signed-off-by: James Almer
---
libavcodec/utils.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/libavcodec/utils.c b/libavcodec/utils.c
index dfbfe98d63..61acf36c4b 100644
--- a/libavcodec/utils.c
+++ b/libavcodec/utils.c
@@ -26,7 +26,6 @@
*/
#include "c
Signed-off-by: James Almer
---
libavformat/format.c | 35 +--
1 file changed, 21 insertions(+), 14 deletions(-)
diff --git a/libavformat/format.c b/libavformat/format.c
index 38ca2a3465..bc443f41ce 100644
--- a/libavformat/format.c
+++ b/libavformat/format.c
@@ -1
On Thu, Jan 04, 2018 at 01:14:07AM -0300, James Almer wrote:
> Signed-off-by: James Almer
> ---
> fftools/ffmpeg.c | 19 ---
> fftools/ffmpeg.h | 7 ++-
> fftools/ffmpeg_opt.c | 2 +-
> 3 files changed, 11 insertions(+), 17 deletions(-)
LGTM
thx
[...]
--
Michael
On Thu, Jan 04, 2018 at 12:07:12AM +, Mark Thompson wrote:
> ---
> On 03/01/18 23:41, Michael Niedermayer wrote:
> > On Wed, Jan 03, 2018 at 10:47:21PM +, Mark Thompson wrote:
> >> ---
> >> configure | 1 +
> >> libavfilter/Makefile| 2 +
> >> libavfil
Observator Casualis (2018-01-04):
> I tried to concatenate two .mp4 videos (both H264 1920x1080 25fps + AAC
> stereo 48000Hz) by concat protocol and concat demuxer. The second video
> was very short (less than a second).
> The result was that the concatenated video did not show the short video.
>
Hi there,
the documentation for "concat" seems so be lacking a detail on
https://ffmpeg.org/ffmpeg-filters.html#concat
I tried to concatenate two .mp4 videos (both H264 1920x1080 25fps + AAC
stereo 48000Hz) by concat protocol and concat demuxer. The second video
was very short (less than a second
On Sun, 31 Dec 2017 13:23:44 +
Rostislav Pehlivanov wrote:
> On 31 December 2017 at 13:13, wm4 wrote:
>
> > On Sun, 31 Dec 2017 13:07:28 +
> > Rostislav Pehlivanov wrote:
> >
> > > The new decoding API supports 1 avpkt -> multiple avframes natively.
> > >
> > > Signed-off-by: Rostisl
On 1/4/2018 2:02 PM, Ronald S. Bultje wrote:
> Hi,
>
> On Wed, Jan 3, 2018 at 11:35 PM, James Almer wrote:
>
>> At least version 0.6.2 is needed since commit
>> df3222d4bb18cbceda443def17b1b29067ed6e3f.
>>
>> Signed-off-by: James Almer
>> ---
>> configure | 2 +-
>> 1 file changed, 1 insertion
On Thu, 4 Jan 2018 12:01:02 -0500
"Ronald S. Bultje" wrote:
> Hi,
>
> On Thu, Jan 4, 2018 at 11:07 AM, wm4 wrote:
>
> > If the stream was aborted using the libavformat interrupt callback, we
> > don't want it to log the reconnect warning. (Exiting after logging this
> > warning worked well, so
Hi,
On Thu, Jan 4, 2018 at 11:07 AM, wm4 wrote:
> If the stream was aborted using the libavformat interrupt callback, we
> don't want it to log the reconnect warning. (Exiting after logging this
> warning worked well, so this is only for avoiding the ugly warning.)
> ---
> I don't want to stick
Hi,
On Wed, Jan 3, 2018 at 11:35 PM, James Almer wrote:
> At least version 0.6.2 is needed since commit
> df3222d4bb18cbceda443def17b1b29067ed6e3f.
>
> Signed-off-by: James Almer
> ---
> configure | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure b/configure
>
On Thu, Jan 4, 2018 at 7:49 AM, wm4 wrote:
> On Wed, 3 Jan 2018 15:22:15 -0800
> Humberto Ribeiro wrote:
>
>> This prevents a possible crash in CreateDeviceEx when using faulty response
>> from GetAdapterDisplayModeEx and allows ffmpeg to fallback to classic d3d9.
>> ---
...
>>
>
> Tested, slig
If the stream was aborted using the libavformat interrupt callback, we
don't want it to log the reconnect warning. (Exiting after logging this
warning worked well, so this is only for avoiding the ugly warning.)
---
I don't want to stick this as an additional condition into the 150
column while() c
It was sort of optional before - if you didn't call it, networking was
initialized on demand, and an ugly warning was logged. Also, the doxygen
comments threatened that it would be made strictly required one day.
Make it explicitly optional. I would prefer to deprecate it fully, but
there might st
On Wed, 3 Jan 2018 15:22:15 -0800
Humberto Ribeiro wrote:
> This prevents a possible crash in CreateDeviceEx when using faulty response
> from GetAdapterDisplayModeEx and allows ffmpeg to fallback to classic d3d9.
> ---
> libavutil/hwcontext_dxva2.c | 6 +-
> 1 file changed, 5 insertions(+
On Wed, 3 Jan 2018 15:22:15 -0800
Humberto Ribeiro wrote:
> This prevents a possible crash in CreateDeviceEx when using faulty response
> from GetAdapterDisplayModeEx and allows ffmpeg to fallback to classic d3d9.
> ---
> libavutil/hwcontext_dxva2.c | 6 +-
> 1 file changed, 5 insertions(+
On Tue, 2 Jan 2018 17:19:14 +0100
wm4 wrote:
> It makes no sense to return an error after the first reconnect, and then
> somehow resume the next time it's called. Usually this will lead to
> demuxer errors. Make reconnecting block instead, until it has either
> successfully reconnected, or give
On Thu, Jan 04, 2018 at 00:42:43 +, Colin NG wrote:
> @@ -1315,6 +1426,7 @@ static int read_from_url(struct representation *pls,
> struct fragment *seg,
> } else {
> ret = avio_read(pls->input, buf, buf_size);
> }
> +
> if (ret > 0)
> pls->cur_seg_offset += ret
On 12/29/2017 8:38 AM, Michael Niedermayer wrote:
On Thu, Dec 28, 2017 at 12:50:00PM -0900, Lou Logan wrote:
On Thu, Dec 28, 2017, at 11:51 AM, Michael Niedermayer wrote:
who maintains vf_vidstabtransform.c ?
Realistically, nobody. Ideally, should have been Georg Martius who is the original
On Tue, 2 Jan 2018 17:19:14 +0100
wm4 wrote:
> It makes no sense to return an error after the first reconnect, and then
> somehow resume the next time it's called. Usually this will lead to
> demuxer errors. Make reconnecting block instead, until it has either
> successfully reconnected, or give
On Thu, 4 Jan 2018 01:14:08 -0300
James Almer wrote:
> w32threads and os2threads both support static mutex initialization now,
> so don't limit it to pthreads only.
>
> Signed-off-by: James Almer
> ---
> libavutil/log.c | 14 --
> 1 file changed, 4 insertions(+), 10 deletions(-)
>
On 1/3/18, Michael Niedermayer wrote:
> Fixes: signed integer overflow: 1024 + 2147483640 cannot be represented in
> type 'int'
> Fixes: 4671/clusterfuzz-testcase-minimized-6027464343027712
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
>
56 matches
Mail list logo
