Am 04.03.16 um 23:44 schrieb Timothy Gu:
> [...]
> So here I propose the following for the master branch:
>
> n3.1-dev-N-78911-gf81c81c
>/ | \ \
> /| \\
> next distinguish commits since commit
> release from
Only copy/compare enough bytes for the bit depth in question.
--
Mats Peterson
http://matsp888.no-ip.org/~mats/
>From 32eaa0889f7356524d785fa7432d48dd89c32376 Mon Sep 17 00:00:00 2001
From: Mats Peterson
Date: Sat, 5 Mar 2016 07:32:12 +0100
Subject: [PATCH v5 1/4 v6]
On 03/05/2016 07:33 AM, Mats Peterson wrote:
Only copy/compare enough bytes for the bit depth in question.
Enough bytes of the palette, that is.
Mats
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On Fri, Mar 04, 2016 at 01:34:55PM +, Derek Buitenhuis wrote:
> On 3/3/2016 7:50 PM, Michael Niedermayer wrote:
> > The io_open/close callbacks afterwards seem direct access IIUC
> > so its not possible to remove or add any fields prior
> >
> > though maybe they have been added so recently
On 03/05/2016 04:48 AM, Mats Peterson wrote:
On 03/05/2016 04:43 AM, Mats Peterson wrote:
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This one only adds an xxpc chunk if it's not
On 3/5/2016 12:36 AM, Michael Niedermayer wrote:
> On Fri, Mar 04, 2016 at 11:52:50PM -0300, James Almer wrote:
>> Fixes compilation of fft with hardcoded tables
>>
>> Signed-off-by: James Almer
>> ---
>> fate-fft tests only up to 12 bits, so i ran fft-test -n17 manually
>> and
On 03/05/2016 04:43 AM, Mats Peterson wrote:
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This one only adds an xxpc chunk if it's not identical to the previosly
used palette. Good enough?
On 03/05/2016 04:38 AM, Mats Peterson wrote:
Something like this? It stores the palette in avist->old_palette, and
compares every new palette chunk with it, and only adds an xxpc chunk if
it differs.
Mats
___
ffmpeg-devel mailing list
Something like this? It stores the palette in avist->old_palette, and
compares every new palette chunk with it, and only adds an xxpc chunk if
it differs.
Mats
--
Mats Peterson
http://matsp888.no-ip.org/~mats/
>From abc3c5e67b1064e64d12f15b43c8063f29fb06ef Mon Sep 17 00:00:00 2001
From: Mats
On Fri, Mar 04, 2016 at 11:52:50PM -0300, James Almer wrote:
> Fixes compilation of fft with hardcoded tables
>
> Signed-off-by: James Almer
> ---
> fate-fft tests only up to 12 bits, so i ran fft-test -n17 manually
> and it didn't fail (It was also very slow).
> This change
On 03/05/2016 04:19 AM, Mats Peterson wrote:
On 03/05/2016 01:08 AM, Michael Niedermayer wrote:
On Fri, Mar 04, 2016 at 10:12:41PM +0100, Mats Peterson wrote:
On 03/04/2016 10:02 PM, Mats Peterson wrote:
On 03/04/2016 09:52 PM, Mats Peterson wrote:
On 03/04/2016 08:44 PM, Michael Niedermayer
On 03/05/2016 01:08 AM, Michael Niedermayer wrote:
On Fri, Mar 04, 2016 at 10:12:41PM +0100, Mats Peterson wrote:
On 03/04/2016 10:02 PM, Mats Peterson wrote:
On 03/04/2016 09:52 PM, Mats Peterson wrote:
On 03/04/2016 08:44 PM, Michael Niedermayer wrote:
On Fri, Mar 04, 2016 at 11:59:11AM
On Fri, 4 Mar 2016 14:44:28 -0800
Timothy Gu wrote:
> So after all the email exchanges, I think there are certain things
> that our version SHOULD contain:
>
> - The hash
> - The next release (i.e. n3.1)
> - A way to compare two versions
>
> The date is considered to be
Fixes compilation of fft with hardcoded tables
Signed-off-by: James Almer
---
fate-fft tests only up to 12 bits, so i ran fft-test -n17 manually
and it didn't fail (It was also very slow).
This change also generates sine tables for 17bit which are currently
unused, so they
Ok, something like this for now, then?
I'm new to ffmpeg development. When is the next version bump going to happen?
---
libavformat/matroskadec.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavformat/matroskadec.c b/libavformat/matroskadec.c
index d20568c..4c3e53a 100644
---
On Fri, Mar 04, 2016 at 10:12:41PM +0100, Mats Peterson wrote:
> On 03/04/2016 10:02 PM, Mats Peterson wrote:
> >On 03/04/2016 09:52 PM, Mats Peterson wrote:
> >>On 03/04/2016 08:44 PM, Michael Niedermayer wrote:
> >>>On Fri, Mar 04, 2016 at 11:59:11AM +0100, Mats Peterson wrote:
> On
On Fri, Mar 04, 2016 at 08:46:42PM +0100, Reimar Döffinger wrote:
> On 04.03.2016, at 11:24, Nicolas George wrote:
>
> > The Git (short) hash carries all the information by itself, so it should be
> > present. But extra, redundant, information can be added for the convenience
>
Am 04.03.16 um 22:50 schrieb Timothy Gu:
> On Fri, Mar 04, 2016 at 06:48:04PM +0100, Thilo Borgmann wrote:
>> Am 04.03.16 um 17:57 schrieb Timothy Gu:
>>> On Fri, Mar 04, 2016 at 10:55:42AM +0100, Thilo Borgmann wrote:
Am 04.03.16 um 08:58 schrieb wm4:
>
> Being able to see the, well,
On Fri, 4 Mar 2016 23:15:52 +0100
Michael Niedermayer wrote:
> On Mon, Feb 29, 2016 at 05:20:17PM -0800, Neil Birkbeck wrote:
> > Signed-off-by: Neil Birkbeck
> > ---
> > libavformat/dump.c | 21 +
> > 1 file changed, 21
On Fri, Mar 04, 2016 at 10:46:33PM +0100, Marton Balint wrote:
>
> On Thu, 3 Mar 2016, Michael Niedermayer wrote:
>
> >On Thu, Mar 03, 2016 at 02:27:52AM +0100, Marton Balint wrote:
> >>Signed-off-by: Marton Balint
> >>---
> >> tests/fate/gapless.mak | 3 +++
> >>
On Mon, Feb 29, 2016 at 05:20:17PM -0800, Neil Birkbeck wrote:
> Signed-off-by: Neil Birkbeck
> ---
> libavformat/dump.c | 21 +
> 1 file changed, 21 insertions(+)
applied
thanks
[...]
--
Michael GnuPG fingerprint:
On Thu, Mar 03, 2016 at 11:23:53PM -0800, Neil Birkbeck wrote:
> And yet another revision, where the syntax lists are actually terminated...
applied
thanks
[..]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
it is not once nor twice but times without number that
Mats Peterson skrev: (4 mars 2016 22:12:41
CET)
>On 03/04/2016 10:02 PM, Mats Peterson wrote:
>> On 03/04/2016 09:52 PM, Mats Peterson wrote:
>>> On 03/04/2016 08:44 PM, Michael Niedermayer wrote:
On Fri, Mar 04, 2016 at 11:59:11AM +0100, Mats Peterson
On Fri, Mar 04, 2016 at 06:48:04PM +0100, Thilo Borgmann wrote:
> Am 04.03.16 um 17:57 schrieb Timothy Gu:
> > On Fri, Mar 04, 2016 at 10:55:42AM +0100, Thilo Borgmann wrote:
> >> Am 04.03.16 um 08:58 schrieb wm4:
> >>>
> >>> Being able to see the, well, version in the version output (instead of
>
Now with ffmpeg-devel in CC
On Fri, Mar 04, 2016 at 04:37:41PM +0100, Clément Bœsch wrote:
> On Fri, Mar 04, 2016 at 04:22:44PM +0100, Michael Niedermayer wrote:
> > On Fri, Feb 26, 2016 at 10:01:51PM +0100, Clément Bœsch wrote:
> > > ffmpeg | branch: master | Clément Bœsch | Wed
On Thu, 3 Mar 2016, Michael Niedermayer wrote:
On Thu, Mar 03, 2016 at 02:27:52AM +0100, Marton Balint wrote:
Signed-off-by: Marton Balint
---
tests/fate/gapless.mak | 3 +++
tests/ref/fate/gapless-aac | 5 +
2 files changed, 8 insertions(+)
create mode 100644
On Fri, Mar 04, 2016 at 09:42:17PM +0100, Timo Rothenpieler wrote:
> ---
> configure | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
LGTM
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
For every action, there is an equal and opposite
On Fri, 4 Mar 2016 11:24:00 -0500
"Ronald S. Bultje" wrote:
> Hi,
>
> On Wed, Mar 2, 2016 at 4:11 PM, Ronald S. Bultje wrote:
>
> > Hi,
> >
> > On Wed, Mar 2, 2016 at 3:51 PM, wm4 wrote:
> >
> >> On Wed, 2 Mar 2016 15:48:11
On 03/04/2016 10:02 PM, Mats Peterson wrote:
On 03/04/2016 09:52 PM, Mats Peterson wrote:
On 03/04/2016 08:44 PM, Michael Niedermayer wrote:
On Fri, Mar 04, 2016 at 11:59:11AM +0100, Mats Peterson wrote:
On 03/04/2016 05:59 AM, Mats Peterson wrote:
Removed some unused variables in AVIStream.
On 03/04/2016 09:52 PM, Mats Peterson wrote:
On 03/04/2016 08:44 PM, Michael Niedermayer wrote:
On Fri, Mar 04, 2016 at 11:59:11AM +0100, Mats Peterson wrote:
On 03/04/2016 05:59 AM, Mats Peterson wrote:
Removed some unused variables in AVIStream.
I would like to remind you of the fact
On Fri, Mar 04, 2016 at 11:24:00AM -0500, Ronald S. Bultje wrote:
> Hi,
>
> On Wed, Mar 2, 2016 at 4:11 PM, Ronald S. Bultje wrote:
>
> > Hi,
> >
> > On Wed, Mar 2, 2016 at 3:51 PM, wm4 wrote:
> >
> >> On Wed, 2 Mar 2016 15:48:11 -0500
> >> "Ronald S.
On 03/04/2016 08:44 PM, Michael Niedermayer wrote:
On Fri, Mar 04, 2016 at 11:59:11AM +0100, Mats Peterson wrote:
On 03/04/2016 05:59 AM, Mats Peterson wrote:
Removed some unused variables in AVIStream.
I would like to remind you of the fact that this patch (and the one
for riffenc.c) is
---
configure | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index 81769ee..9b56a4d 100755
--- a/configure
+++ b/configure
@@ -5681,8 +5681,8 @@ enabled mmal &&
enabled netcdf&& require_pkg_config netcdf netcdf.h nc_inq_libvers
On Fri, Mar 04, 2016 at 05:08:07PM +0100, Timo Rothenpieler wrote:
> > breaks build here
> >
> > libavcodec/nvenc.c: In function ‘nvenc_encode_init’:
> > libavcodec/nvenc.c:952:56: error: ‘NV_ENC_CONFIG_HEVC’ has no member named
> > ‘hevcVUIParameters’
> > libavcodec/nvenc.c:953:56: error:
On 04.03.2016, at 11:24, Nicolas George wrote:
> Le quintidi 15 ventôse, an CCXXIV, Thilo Borgmann a écrit :
>> Neither a good play on words nor elaborative; not even helpful.
>>
>> You say they are random numbers, CE says it is continuous. What is correct?
>>
>> Let's assume
On Fri, Mar 04, 2016 at 11:59:11AM +0100, Mats Peterson wrote:
> On 03/04/2016 05:59 AM, Mats Peterson wrote:
> >Removed some unused variables in AVIStream.
> >
>
>
> I would like to remind you of the fact that this patch (and the one
> for riffenc.c) is needed for stream copying of Microsoft
Le quintidi 15 ventôse, an CCXXIV, Timothy Gu a écrit :
> One object that can be raised against this is that the current versioning and
> the new versioning are both compatible with Git. Try
>
> git show n3.1-dev-400-g3af71ac
> git show N-78863-g3af71ac
"git show 3af71ac" is enough. With
Am 04.03.16 um 17:57 schrieb Timothy Gu:
> On Fri, Mar 04, 2016 at 10:55:42AM +0100, Thilo Borgmann wrote:
>> Am 04.03.16 um 08:58 schrieb wm4:
>>>
>>> Being able to see the, well, version in the version output (instead of
>>> random numbers) sounds like a pretty convincing argument.
>>
>> Neither
On Fri, Mar 04, 2016 at 10:20:09AM +, Carl Eugen Hoyos wrote:
> Timo Rothenpieler rothenpieler.org> writes:
>
> > The current versioning scheme is indeed simple, but
> > useless in almost all other aspects.
>
> FFmpeg has a linear development scheme, how can you call
> a continuous
On Fri, Mar 04, 2016 at 11:24:31AM +0100, Nicolas George wrote:
> Basically, the version could be something like
> "g510046c:N78879-3.0master417-H20160303":
One object that can be raised against this is that the current versioning and
the new versioning are both compatible with Git. Try
git
On Fri, Mar 04, 2016 at 10:55:42AM +0100, Thilo Borgmann wrote:
> Am 04.03.16 um 08:58 schrieb wm4:
> >
> > Being able to see the, well, version in the version output (instead of
> > random numbers) sounds like a pretty convincing argument.
>
> Neither a good play on words nor elaborative; not
Hi,
On Wed, Mar 2, 2016 at 4:11 PM, Ronald S. Bultje wrote:
> Hi,
>
> On Wed, Mar 2, 2016 at 3:51 PM, wm4 wrote:
>
>> On Wed, 2 Mar 2016 15:48:11 -0500
>> "Ronald S. Bultje" wrote:
>>
>> > Hi,
>> >
>> > On Mon, Feb 29, 2016 at
On 3/4/2016 3:02 PM, James Almer wrote:
> ry to non break ABI just yet, leave it as last resort. We did it not even
> half a year ago, and we'd have to push every single scheduled deprecation.
> If this can be resolved moving only the new entries then that's preferable.
OK I did it this way.
-
> breaks build here
>
> libavcodec/nvenc.c: In function ‘nvenc_encode_init’:
> libavcodec/nvenc.c:952:56: error: ‘NV_ENC_CONFIG_HEVC’ has no member named
> ‘hevcVUIParameters’
> libavcodec/nvenc.c:953:56: error: ‘NV_ENC_CONFIG_HEVC’ has no member named
> ‘hevcVUIParameters’
>
On Fri, Mar 04, 2016 at 04:22:44PM +0100, Michael Niedermayer wrote:
> On Fri, Feb 26, 2016 at 10:01:51PM +0100, Clément Bœsch wrote:
> > ffmpeg | branch: master | Clément Bœsch | Wed Jan 6 13:43:23
> > 2016 +0100| [29412821241050c846dbceaad4b9752857659977] | committer: Clément
>
On Fri, Mar 04, 2016 at 10:51:10AM +0100, Timo Rothenpieler wrote:
> >>
> >> In case of the git send-email sends corrupted patch again, I attach the
> >> original patch file.
> >>
> >> Agatha Hu
> >>
> >
> > That's strange, does anyone received my patch sent at 17:22 GMT+8?
> > Looks like the
On 3/4/2016 10:34 AM, Derek Buitenhuis wrote:
> On 3/3/2016 7:50 PM, Michael Niedermayer wrote:
>> The io_open/close callbacks afterwards seem direct access IIUC
>> so its not possible to remove or add any fields prior
>>
>> though maybe they have been added so recently that its ok to move
>> them
Hi,
On Fri, Mar 4, 2016 at 7:52 AM, Paul B Mahol wrote:
> On 3/4/16, wm4 wrote:
> > On Fri, 4 Mar 2016 13:12:45 +0100
> > Paul B Mahol wrote:
> >
> >> On 3/4/16, Michael Niedermayer wrote:
> >> > On Fri, Mar
On 3/3/2016 7:50 PM, Michael Niedermayer wrote:
> The io_open/close callbacks afterwards seem direct access IIUC
> so its not possible to remove or add any fields prior
>
> though maybe they have been added so recently that its ok to move
> them above all "no direct access" fields
> or maybe iam
On 3/4/16, wm4 wrote:
> On Fri, 4 Mar 2016 13:12:45 +0100
> Paul B Mahol wrote:
>
>> On 3/4/16, Michael Niedermayer wrote:
>> > On Fri, Mar 04, 2016 at 11:21:23AM +0100, Paul B Mahol wrote:
>> >> On 3/4/16, Michael Niedermayer
On Fri, 4 Mar 2016 13:12:45 +0100
Paul B Mahol wrote:
> On 3/4/16, Michael Niedermayer wrote:
> > On Fri, Mar 04, 2016 at 11:21:23AM +0100, Paul B Mahol wrote:
> >> On 3/4/16, Michael Niedermayer wrote:
> >> > Hi
> >> >
> >>
On 3/4/16, Michael Niedermayer wrote:
> On Fri, Mar 04, 2016 at 11:21:23AM +0100, Paul B Mahol wrote:
>> On 3/4/16, Michael Niedermayer wrote:
>> > Hi
>> >
>> > patch to extend fft is attached (my git-send email atm doesnt work
>> > thanks to my
On Fri, Mar 04, 2016 at 11:21:23AM +0100, Paul B Mahol wrote:
> On 3/4/16, Michael Niedermayer wrote:
> > Hi
> >
> > patch to extend fft is attached (my git-send email atm doesnt work
> > thanks to my ISP)
> >
> > --
> > Michael GnuPG fingerprint:
On 03/04/2016 05:59 AM, Mats Peterson wrote:
Removed some unused variables in AVIStream.
I would like to remind you of the fact that this patch (and the one for
riffenc.c) is needed for stream copying of Microsoft Video 1 (CRAM) in
8-bit mode, Microsoft RLE4 and Microsoft RLE8. There are
>
> Thanks for that clarification. Unfortunately the http server is a third
> party camera that broadcasts a WiFi hotspot. Therefore we don't really
> have control over the underlying server. However, what I do know is
> that the ffmpeg command I quoted previously seems to be able to
> grab a
Le quintidi 15 ventôse, an CCXXIV, Thilo Borgmann a écrit :
> Neither a good play on words nor elaborative; not even helpful.
>
> You say they are random numbers, CE says it is continuous. What is correct?
>
> Let's assume the N-tag is not random, then it is a useful extension of the
>
Timo Rothenpieler rothenpieler.org> writes:
> The current versioning scheme is indeed simple, but
> useless in almost all other aspects.
FFmpeg has a linear development scheme, how can you call
a continuous versioning scheme useless? It reflects 1:1
on how FFmpeg is developed.
> It gives no
You are skipping everything I think about N-tags you want to patch away... why?
Am 04.03.16 um 11:07 schrieb Timo Rothenpieler:
>> So what about the release tag? Well it is a quite useful extension because of
>> the already mentioned possibility of determining the existing features at
>> once.
On 3/4/16, Michael Niedermayer wrote:
> Hi
>
> patch to extend fft is attached (my git-send email atm doesnt work
> thanks to my ISP)
>
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> I know you won't believe me, but the highest form of
wm4 googlemail.com> writes:
> Being able to see the, well, version in the version output
> (instead of random numbers)
What is random about the version number using current FFmpeg?
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
> So what about the release tag? Well it is a quite useful extension because of
> the already mentioned possibility of determining the existing features at
> once.
> I'm pro adding it to the version string.
The release tags are not made in the master branch, so git describe
won't pick them up.
On Thu, Mar 03, 2016 at 22:50:10 -0800, Timothy Gu wrote:
> This patched is corrupted by your mail client. What's wrong with the first
> patch you sent (with git-send-email)?
While the first one was mail-technically okay (probably), the patch
contained apparent whitespace changes and trailing
>> Of course, this argument operates on the premise that
>> making things easier for users is of utmost concern
>> for us. Please inspire me if this is not the case.
>
> On the contrary, I believe while the current versioing
> scheme is simple and understandable, the suggested one
> is
Am 04.03.16 um 08:58 schrieb wm4:
> On Fri, 4 Mar 2016 08:47:14 +0100
> Thilo Borgmann wrote:
>
>> Am 04.03.16 um 08:23 schrieb wm4:
>>> On Fri, 4 Mar 2016 00:55:35 + (UTC)
>>> Carl Eugen Hoyos wrote:
>>>
Timothy Gu gmail.com> writes:
>>
>> In case of the git send-email sends corrupted patch again, I attach the
>> original patch file.
>>
>> Agatha Hu
>>
>
> That's strange, does anyone received my patch sent at 17:22 GMT+8?
> Looks like the first mail (sent by git sent-email, no attachment) was somehow
> blocked.
>
> Agatha
On 2016年03月04日 17:26, ahu wrote:
>
> On 2016年03月04日 17:22, ahu wrote:
>> ---
>> libavcodec/nvenc.c | 27 +++
>> 1 file changed, 23 insertions(+), 4 deletions(-)
>>
>> diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c
>> index a3b02fa..5d78930 100644
>> ---
On 2016年03月04日 17:22, ahu wrote:
> ---
> libavcodec/nvenc.c | 27 +++
> 1 file changed, 23 insertions(+), 4 deletions(-)
>
> diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c
> index a3b02fa..5d78930 100644
> --- a/libavcodec/nvenc.c
> +++ b/libavcodec/nvenc.c
>
---
libavcodec/nvenc.c | 27 +++
1 file changed, 23 insertions(+), 4 deletions(-)
diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c
index a3b02fa..5d78930 100644
--- a/libavcodec/nvenc.c
+++ b/libavcodec/nvenc.c
@@ -868,14 +868,19 @@ static av_cold int
On Thu, Mar 3, 2016 at 11:28 PM, compn wrote:
> the mp4 format can either have an index at the start of the file or
> at the end of the file. you cannot read (easily) an mp4 file without its
> index.
>
> http://wiki.multimedia.cx/index.php?title=MP4
>
> http servers can be made
69 matches
Mail list logo