On Tue, Feb 24, 2015 at 4:12 PM, Michael Niedermayer
wrote:
> On Tue, Feb 24, 2015 at 02:27:01PM +0530, arwa arif wrote:
> > Hello,
> >
> > I have written a very primitive code for porting FFT domain filter. It
> > accepts only gray8 format images. The output should be a grayscale image,
> > but
On Wed, Feb 25, 2015 at 12:05:27AM +0100, Carl Eugen Hoyos wrote:
> On Tuesday 09 April 2013 03:21:33 pm Carl Eugen Hoyos wrote:
> > Hi!
> >
> > Attached patch fixes remuxing of h264 into mpeg-ts for some wtv input
> > files.
>
> Updated patch attached, WMP and QT play such samples.
> Fixes ticket
Signed-off-by: James Almer
---
I decided to go the configure route since other features (cmov, clz) also do
it , but if prefered this could instead be done with a new intmath.h header
in the x86/ folder containing something like
#if defined(__GNUC__) && defined(__POPCNT__)
#define av_popcoun
On Tuesday 09 April 2013 03:21:33 pm Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch fixes remuxing of h264 into mpeg-ts for some wtv input
> files.
Updated patch attached, WMP and QT play such samples.
Fixes ticket #4324.
Please comment, Carl Eugen
diff --git a/libavformat/mpegtsenc.c b/libavfo
On 2/24/2015 5:46 PM, Robert Krüger wrote:
>> is this correct for all mov, mp4, 3gp, psp, ... ?
>> or should it be writteb by default only for some of them ?
Good point, but this raises the whole ugly question of the least crappy
way of setting a default for only one format in the monster that is
On Tue, Feb 24, 2015 at 6:34 PM, Michael Niedermayer
wrote:
> On Tue, Feb 24, 2015 at 03:11:44PM +, Derek Buitenhuis wrote:
> > Some formats require this, such as v210. The consensus seems to be
> > to write it by default.
> >
> > Signed-off-by: Derek Buitenhuis
> > ---
> > This is a silent
On Tue, Feb 24, 2015 at 03:11:44PM +, Derek Buitenhuis wrote:
> Some formats require this, such as v210. The consensus seems to be
> to write it by default.
>
> Signed-off-by: Derek Buitenhuis
> ---
> This is a silent behavior change, and I have updated the API doc
> accordingly.
> ---
> doc
On Fri, Feb 20, 2015 at 07:00:48PM +0100, Michael Niedermayer wrote:
> On Fri, Feb 20, 2015 at 04:04:52PM +, Kevin Wheatley wrote:
> > On Fri, Feb 20, 2015 at 11:36 AM, Michael Niedermayer
> > wrote:
> > > applied the case for DNxHD, for the more general case, please
> > > explain which case(
Only add it when in MOV mode, its in the QT spec
This matches libquicktime
See: 0216 11:49 Kevin Wheatley ( 38K) [FFmpeg-devel] [PATCH] avformat:
Outputting DNxHD into .mov containers 'corrupts' following atoms until end of
stsd
See: libquicktime/src/stsdtable.c
Signed-off-by: Michael Niederma
On date Tuesday 2015-02-24 13:23:56 +0100, Tobias Rapp encoded:
> Attached patch updates the filter option documentation text to link to
> ffmpeg-utils documentation for video size syntax description.
> From 3c73ad81f31eedde3ed7f500af1ed23a5458652b Mon Sep 17 00:00:00 2001
> From: Tobias Rapp
> D
On Tue, Feb 24, 2015 at 10:10:21AM +, Kevin Wheatley wrote:
> On Fri, Feb 20, 2015 at 5:51 PM, Michael Niedermayer wrote:
>
> > theres some code that memcpies extradata into vos_data and that is
> > skiped if TAG_IS_AVCI(trk->tag), try to also skip this for DNxHD
>
> Michael,
>
> thanks for
Hi,
I am currently trying to interpret the index data of HuffYuv/PCM AVI
files written by FFmpeg. If the file is larger than 2GiB an "AVIX" RIFF
chunk is added for each 2GiB-block, each of these blocks gets an OpenDML
chunk index "ix00" and an OpenDML super index chunk "indx" is written
for e
Some formats require this, such as v210. The consensus seems to be
to write it by default.
Signed-off-by: Derek Buitenhuis
---
This is a silent behavior change, and I have updated the API doc
accordingly.
---
doc/APIchanges| 3 +++
libavformat/movenc.c | 2 +-
libavformat/version.h | 4
Value taken from the decoder implementation
Signed-off-by: Michael Niedermayer
---
libavformat/dss.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/dss.c b/libavformat/dss.c
index 85cd26a..12a4034 100644
--- a/libavformat/dss.c
+++ b/libavformat/dss.c
@@ -228,
On 2/24/2015 2:49 PM, Clément Bœsch wrote:
> Well, unfortunately this breaks the API. I'd just add the flag to the
> default values. People who set flags are supposed to use a + as a prefix
> so that won't be a problem.
Right.
- Derek
___
ffmpeg-devel m
Several formats require the colr atom, and the consensus seems
to be to write it by default.
Signed-off-by: Derek Buitenhuis
---
Changing the flag as I do here is one approach. Comments needed.
---
libavformat/movenc.c | 4 ++--
libavformat/movenc.h | 2 +-
libavformat/version.h | 4 ++--
3 fi
Signed-off-by: Michael Niedermayer
---
libavformat/dss.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/dss.c b/libavformat/dss.c
index 66a30aa..76538d77 100644
--- a/libavformat/dss.c
+++ b/libavformat/dss.c
@@ -143,7 +143,7 @@ static int dss_read_header(AVFor
Signed-off-by: Michael Niedermayer
---
libavformat/dss.c |8
1 file changed, 8 insertions(+)
diff --git a/libavformat/dss.c b/libavformat/dss.c
index 76538d77..c595982 100644
--- a/libavformat/dss.c
+++ b/libavformat/dss.c
@@ -54,6 +54,8 @@ typedef struct DSSDemuxContext {
int
This assumes CBR (which is true for all samples i have)
Signed-off-by: Michael Niedermayer
---
libavformat/dss.c | 39 +++
1 file changed, 39 insertions(+)
diff --git a/libavformat/dss.c b/libavformat/dss.c
index c595982..72c7e1a 100644
--- a/libavformat/ds
Attached patch updates the filter option documentation text to link to
ffmpeg-utils documentation for video size syntax description.
From 3c73ad81f31eedde3ed7f500af1ed23a5458652b Mon Sep 17 00:00:00 2001
From: Tobias Rapp
Date: Tue, 24 Feb 2015 13:14:07 +0100
Subject: [PATCH] doc/filters.texi: Ad
On Tue, Feb 24, 2015 at 10:14:27AM +0100, Christophe Gisquet wrote:
> Hi,
>
> 2015-02-05 16:53 GMT+01:00 Christophe Gisquet :
> > when running fate-hevc under valgrind + memory poisoning, I ran into
> > this issue when running with THREAD_TYPE=slice and THREADS>1.
> >
> > pthread is not my forte a
On Tue, Feb 24, 2015 at 08:00:07AM +, tim nicholson wrote:
> On 21/02/15 01:34, Dave Rice wrote:
> > Hi Robert, Kevin,
> >
> >> On Feb 20, 2015, at 9:56 AM, Robert Krüger wrote:
> >>
> >> Am Freitag, 20. Februar 2015 schrieb Kevin Wheatley :
> >>
> >>> On Fri, Feb 20, 2015 at 1:30 PM, Robert
On Tue, Feb 24, 2015 at 11:41:02AM +0100, Carl Eugen Hoyos wrote:
> On Monday 23 February 2015 02:02:42 pm Clément Bœsch wrote:
> > On Mon, Feb 23, 2015 at 01:59:45PM +0100, Michael Niedermayer wrote:
> > > On Mon, Feb 23, 2015 at 03:27:54AM +0100, Carl Eugen Hoyos wrote:
>
> > > > +int wi
On Tue, Feb 24, 2015 at 02:27:01PM +0530, arwa arif wrote:
> Hello,
>
> I have written a very primitive code for porting FFT domain filter. It
> accepts only gray8 format images. The output should be a grayscale image,
> but the ouput image is coming out to be a black and white image. Also, I am
>
On Monday 23 February 2015 02:02:42 pm Clément Bœsch wrote:
> On Mon, Feb 23, 2015 at 01:59:45PM +0100, Michael Niedermayer wrote:
> > On Mon, Feb 23, 2015 at 03:27:54AM +0100, Carl Eugen Hoyos wrote:
> > > +int width = av_pix_fmt_desc_get(frame->format)->flags &
> > > AV_PIX_FMT_FLAG_PLAN
Thilo Borgmann mail.de> writes:
> You just misread me, I know what the first patch is for
> - which is what you just wrote. However, my question
> was about reason for the second "#define" patch.
My comment was only about the second patch.
Is the second patch ok?
Carl Eugen
Am 23.02.15 um 19:46 schrieb Carl Eugen Hoyos:
> Thilo Borgmann mail.de> writes:
>
>> For the second, what is that patch needed for?
>
> It is meant to fix warnings when compiling avfoundation
> for ios, see for example:
> http://fate.ffmpeg.org/log.cgi?time=20150223010210&log=compile&slot=aarc
On Fri, Feb 20, 2015 at 5:51 PM, Michael Niedermayer wrote:
> theres some code that memcpies extradata into vos_data and that is
> skiped if TAG_IS_AVCI(trk->tag), try to also skip this for DNxHD
Michael,
thanks for the pointer, there are actually two points in the code that
appear to need the
Hi,
2015-02-05 16:53 GMT+01:00 Christophe Gisquet :
> when running fate-hevc under valgrind + memory poisoning, I ran into
> this issue when running with THREAD_TYPE=slice and THREADS>1.
>
> pthread is not my forte at all, and I'm not sure I'm handling the
> thread/... signalling correctly before
Hello,
I have written a very primitive code for porting FFT domain filter. It
accepts only gray8 format images. The output should be a grayscale image,
but the ouput image is coming out to be a black and white image. Also, I am
getting confused when to do the vertical pass. After taking irdft of t
On 21/02/15 01:34, Dave Rice wrote:
> Hi Robert, Kevin,
>
>> On Feb 20, 2015, at 9:56 AM, Robert Krüger wrote:
>>
>> Am Freitag, 20. Februar 2015 schrieb Kevin Wheatley :
>>
>>> On Fri, Feb 20, 2015 at 1:30 PM, Robert Krüger >> > wrote:
if I read the code correctly, the colr atom is only wri
31 matches
Mail list logo
