On 4/5/2018 5:02 PM, Paul B Mahol wrote:
> On 4/3/18, Bodecs Bela wrote:
>> Dear All,
>>
>> I added some more information about default value of bind_address option
>> and its abbreviated
>> version (b). I modified the example to have named instanced filter and
>> to show
>> its use.
>>
>> please
On Thu, Apr 5, 2018, at 12:04 PM, Lou Logan wrote:
>
> It needs some minor work. I will plan to fix and apply later today.
Pushed after some meddling.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Fri, 30 Mar 2018 14:47:25 +0200
Bodecs Bela wrote:
> Hi All,
>
> regularly, on different forums and mailing lists a requirement popups
> for a feature to automatically failover switching between main input and a
> secondary input in case of main input unavailability.
>
> The base motivation
On Thu, Apr 05, 2018 at 01:51:10PM +0200, Vittorio Giovara wrote:
> ---
> > On Wed, Apr 04, 2018 at 05:30:24PM +0200, Vittorio Giovara wrote:
> > > libavutil/display.c | 92
> > > +
> > > libavutil/display.h | 53 ++
>
On Fri, Mar 30, 2018 at 02:47:25PM +0200, Bodecs Bela wrote:
> Hi All,
>
> regularly, on different forums and mailing lists a requirement popups for a
> feature to automatically failover switching between main input and a
> secondary input in case of main input unavailability.
>
> The base motiva
2018-04-05 20:08 GMT+02:00, Michael Niedermayer :
> On Thu, Apr 05, 2018 at 12:45:18AM +0200, Carl Eugen Hoyos wrote:
>> amr.c | 10 ++
>> 1 file changed, 6 insertions(+), 4 deletions(-)
>> 64ad2690251aff3bf4ce981e2b09e5102df0ba44
>> 0001-lavf-amr-Stricter-heuristic-for-auto-detection.p
On 2018/04/05 22:34, Hendrik Leppkes wrote:
On Thu, Apr 5, 2018 at 11:09 PM, Josh de Kock wrote:
Signed-off-by: Josh de Kock
---
libavdevice/.gitignore | 2 ++
libavfilter/.gitignore | 1 +
2 files changed, 3 insertions(+)
create mode 100644 libavdevice/.gitignore
create mode 100644 li
On Thu, Apr 5, 2018 at 11:09 PM, Josh de Kock wrote:
> Signed-off-by: Josh de Kock
> ---
> libavdevice/.gitignore | 2 ++
> libavfilter/.gitignore | 1 +
> 2 files changed, 3 insertions(+)
> create mode 100644 libavdevice/.gitignore
> create mode 100644 libavfilter/.gitignore
>
> diff --git a/
Signed-off-by: Josh de Kock
---
libavdevice/.gitignore | 2 ++
libavfilter/.gitignore | 1 +
2 files changed, 3 insertions(+)
create mode 100644 libavdevice/.gitignore
create mode 100644 libavfilter/.gitignore
diff --git a/libavdevice/.gitignore b/libavdevice/.gitignore
new file mode 100644
in
On 2018/04/02 18:53, mi...@brew.sh wrote:
segafilm muxer
Thanks, pushed. I also clarified with wm4 on IRC that while he was
against it he wasn't blocking the muxer if someone else pushes it.
--
Josh
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg
The AMLogic meson V4L2 M2M I'm developping (https://github.com/Elyotna/linux)
can fare with only one OUTPUT buffer for data input.
Granted, only 1 CAPTURE buffer is probably not going to cut it, but still,
I don't see the reason behind restricting the FFmpeg user to try with 1 (in
the end the driv
On 04/05/2018 06:42 PM, Maxime Jourdan wrote:
Reduce the minimum amount of CAPTURE and OUTPUT buffers to 1.
makes sense to me if that is indeed the case.
could you provide a real life use case?
There are drivers that may work with such drastic settings,
and FFmpeg doesn't complain.
---
liba
>
> I will wait few days, if someone have other comments, before pushing.
>
> Martin
>
>
>
Mention the quality improvment in the commit msg, and pushed
Thanks
Martin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinf
On Thu, Apr 5, 2018, at 12:02 PM, Paul B Mahol wrote:
>
> anybody, please apply this.
It needs some minor work. I will plan to fix and apply later today.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-deve
On 4/3/18, Bodecs Bela wrote:
> Dear All,
>
> I added some more information about default value of bind_address option
> and its abbreviated
> version (b). I modified the example to have named instanced filter and
> to show
> its use.
>
> please review this patch.
>
> thanky you in advance,
>
> be
ping
2018.04.03. 16:23 keltezéssel, Bodecs Bela írta:
Dear All,
I added some more information about default value of bind_address
option and its abbreviated
version (b). I modified the example to have named instanced filter and
to show
its use.
please review this patch.
thanky you in adva
On Tue, Apr 3, 2018, at 12:30 AM, Tobias Rapp wrote:
> Updates documentation after the changes to loglevel flag prefix parsing
> in 4b736bc921ed96ad6d312ce0cbe0de29b9e3fe81.
>
> Signed-off-by: Tobias Rapp
> ---
> doc/fftools-common-opts.texi | 26 ++
> 1 file changed, 18
2018-03-17 19:44 GMT+01:00 Martin Vignali :
> Hello
>
> Patch in attach add SIMD for 16 bit version of
> grainextract
> grainmerge
> average
> extremity
> negation
>
> 003 : modify DIFFERENCE macro to reduce line duplication
> 004 : add SIMD for grainextract, grainmerge, average, extremity, negati
On 4/5/2018 8:14 PM, Rostislav Pehlivanov wrote:
> I think it makes sense to have it in AVStream rather than as side data.
> I don't have an opinion on whether codec switches should be indicated. It
> would be nice for them to be a separate segment if that's possible and
> reliable, since it would
On 5 April 2018 at 16:26, Derek Buitenhuis
wrote:
> On 4/3/2018 5:26 PM, wm4 wrote:
> > Uh no idea. One angle:
> >
> > The idea with AVStream side data is that it can be attached as AVPacket
> > side data. So if an API user is fine with treating all kinds of side
> > data per AVPacket, it can cal
>
> This breaks the testcase described in
> https://trac.ffmpeg.org/ticket/6990 which is basically the same as the
> one you described in this patch.
>
> I get the following spammed repeatedly:
>
> [AVHWFramesContext @ 0502d340] Static surface pool size exceeded.
> [mpeg2video @
On Thu, 5 Apr 2018 19:51:49 +0100
Derek Buitenhuis wrote:
> Hi,
>
> If you wish to address me, please do so publicly in the future. Nobody
> benefits from this stuff happening in private. CCing ffmpeg-devel where
> this belongs.
>
> On 4/5/2018 7:44 PM, Nicolas George wrote:
> > This remark wou
On 4/5/2018 3:25 PM, Lou Logan wrote:
> On Sun, Mar 25, 2018, at 10:51 PM, Valery Kot wrote:
>>
>> Just wondering: is there an active maintainer for avcodec/libopenh264?
>
> Doesn't appear to be so.
>
>> If yes - can he or she please review my patch. If no - how does
>> maintenance works for "orp
Hi,
If you wish to address me, please do so publicly in the future. Nobody
benefits from this stuff happening in private. CCing ffmpeg-devel where
this belongs.
On 4/5/2018 7:44 PM, Nicolas George wrote:
> This remark would have more weight if you also made it to people who
> actually deserve it,
On 4/5/2018 7:35 PM, Nicolas George wrote:
> A completely braindead API versus using a data structure the way it is
> supposed to be used, by adding fields when necessary? You call this a
> trade-off?
You could have voiced your opinion without being a jackass about it. Cut
it out.
- Derek
___
Derek Buitenhuis (2018-04-05):
> I got what you mean. I still don't have an opinion one way or another.
> It's a trade-off between Yet Another AVStream Field vs a more complex
> API and implementation as side data. I may be slightly erring towards
> an AVStream field.
>
> I would be interested to
Reduce the minimum amount of CAPTURE and OUTPUT buffers to 1.
There are drivers that may work with such drastic settings,
and FFmpeg doesn't complain.
---
libavcodec/v4l2_m2m.h | 2 +-
libavcodec/v4l2_m2m_dec.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/
On Thu, 5 Apr 2018 10:17:30 -0800
Lou Logan wrote:
> This seems to confuse Github users into thinking that we may accept pull
> requests. We do not accept pull requests.
>
> Sending patches to the ffmpeg-devel mailing list is our preferred method
> for users to contribute code.
>
> Signed-off-
On Sun, Mar 25, 2018, at 10:51 PM, Valery Kot wrote:
>
> Just wondering: is there an active maintainer for avcodec/libopenh264?
Doesn't appear to be so.
> If yes - can he or she please review my patch. If no - how does
> maintenance works for "orphaned" modules?
Any developer simply decides to r
On Wed, Apr 04, 2018 at 12:30:56PM -0700, Jacob Trimble wrote:
> Signed-off-by: Jacob Trimble
> ---
> libavformat/mov.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
will apply
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
If a bugfix only cha
This seems to confuse Github users into thinking that we may accept pull
requests. We do not accept pull requests.
Sending patches to the ffmpeg-devel mailing list is our preferred method
for users to contribute code.
Signed-off-by: Lou Logan
---
doc/developer.texi | 6 ++
1 file changed, 2
On Thu, Apr 05, 2018 at 12:45:18AM +0200, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch fixes ticket #7125, the jpg file in question contains a
> repeated pattern up to PROBE_SIZE that plays as amr_nb:
> 000d3290 05 14 51 40 05 14 51 40 05 14 51 40 05 14 51 40 |..Q@..Q@..Q@..Q@|
> *
> 001129
On 4/5/2018 12:23 PM, Alexander Kravchenko wrote:
>
> This fixes frame corruption issue when decoder started reusing frames while
> they are still in use of encoding process
> Issue with frame corruption was reproduced using:
> ffmpeg.exe -y -hwaccel d3d11va -hwaccel_output_format d3d11 -i input
Newly allocated data buffers (wavpack, prores, compressed buffers)
are padded to meet the requirements of AVPacket.
About 10x speed up in matroska_parse_frame().
Signed-off-by: James Almer
---
Rebased after the prores fix in Patch 2/3 v2.
libavformat/matroskadec.c | 45
On 4/3/2018 5:26 PM, wm4 wrote:
> Uh no idea. One angle:
>
> The idea with AVStream side data is that it can be attached as AVPacket
> side data. So if an API user is fine with treating all kinds of side
> data per AVPacket, it can call av_format_inject_global_side_data() and
> ignore AVStream sid
Simplifies code in matroska_parse_frame(). This is in preparation for
the following patch.
Signed-off-by: James Almer
---
Not overloading dst this time...
libavformat/matroskadec.c | 50 +++
1 file changed, 38 insertions(+), 12 deletions(-)
diff --gi
This fixes frame corruption issue when decoder started reusing frames while
they are still in use of encoding process
Issue with frame corruption was reproduced using:
ffmpeg.exe -y -hwaccel d3d11va -hwaccel_output_format d3d11 -i input.h264 -an
-c:v h264_amf output.mkv
Previous questions and
On Wed, 4 Apr 2018 21:42:31 +0200
Michael Niedermayer wrote:
> On Wed, Apr 04, 2018 at 06:07:20PM +0200, wm4 wrote:
> > The pseudo palette allocation is optional now. But if it's still
> > allocated (like the internal get_buffer2 implementation does, for
> > compatibility), it shouldn't print a w
On Wed, Apr 04, 2018 at 08:43:33PM -0300, James Almer wrote:
> Simplifies code in matroska_parse_frame(). This is in preparation for
> the following patch.
>
> Signed-off-by: James Almer
> ---
> Prores specific stuff untested, as FATE doesn't cover it.
>
> libavformat/matroskadec.c | 50
>
Hey there,
I have recently switched to using FFmpeg for conversions of 24bit stereo WAV to
16bit stereo WAV (with dithering).
For some very large files, I occasionally encountered a segmentation fault in
_sum2_float. Unfortunately, I was not able to reproduce the issue in a small
test setting,
Good day,
were the technical things (changes into standard network code) resolved in the
mean time? I've the feeling that it is looking at the patch.
On https://github.com/Haivision/srt/pull/140, there is at least a PR to make a
debian package for it.
I think the name is a minor problem which
---
> On Wed, Apr 04, 2018 at 05:30:24PM +0200, Vittorio Giovara wrote:
> > libavutil/display.c | 92
> > +
> > libavutil/display.h | 53 ++
> > 2 files changed, 145 insertions(+)
> It might be more usefull to fu
ping
2018.03.30. 14:47 keltezéssel, Bodecs Bela írta:
Hi All,
regularly, on different forums and mailing lists a requirement popups
for a feature to automatically failover switching between main input
and a
secondary input in case of main input unavailability.
The base motivation: let's sa
43 matches
Mail list logo
