From: Arne Babenhauserheide <arne_bab@web.de>
To: Leo Famulari <leo@famulari.name>
Cc: 34050-done@debbugs.gnu.org
Subject: [bug#34050] [PATCH] gnu: Add libaom and activate AV1 support in ffmpeg. updated
Date: Wed, 06 Mar 2019 20:24:03 +0100 [thread overview]
Message-ID: <87d0n3957w.fsf@web.de> (raw)
In-Reply-To: <20190305233041.GA24016@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]
Leo Famulari <leo@famulari.name> writes:
> On Tue, Mar 05, 2019 at 03:12:07PM -0500, Leo Famulari wrote:
>> On Sat, Jan 19, 2019 at 12:13:49AM +0100, Arne Babenhauserheide wrote:
>> > +(define-public libaom
>> > + (package
>> > + (name "libaom")
>> > + (version "22b150bf040608028a56d8bf39e72f771383d836") ;; master
>>
>> Typically we only package tagged releases. I think the latest libaom
>> release is 'v1.0.0-errata1'. Can we use that or did it not work for you?
>> If you didn't try it, I can do it here.
>
> To answer my own question, 1.0.0-errata1 installs a broken pkg-config
> .pc file [0].
Thank you for checking!
(I do not remember why I chose the commit instead of the tag)
> This is fixed in a later commit [1] ... we might as well use the commit
> you chose originally, which is later than the pkg-config fix commit.
Sounds good.
> This library's decoder is *very* expensive — it can't even decode
> 1280x720 in realtime on my Ivy Bridge i5-3230M. I'm sure it only gets
> faster as they keep working on it.
I take it that you did not test the encoder yet … it takes roughly an
hour per second :-)
But this is a reference for seeing the quality, not for fast de- and
encoding.
> I changed the libaom package to be more idiomatic about versioning from
> Git [2] and edited the synopsis and description, and pushed as
> 84eb265eb8076876d2b569bcdff1e44b44b4b295
>
> Thanks a lot!
Thank you for taking care of the patch!
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]
next prev parent reply other threads:[~2019-03-06 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 0:24 [bug#34050] [PATCH] gnu: Add libaom and activate AV1 support in ffmpeg Arne Babenhauserheide
[not found] ` <handler.34050.B.154725368427570.ack@debbugs.gnu.org>
2019-01-12 12:13 ` [bug#34050] Aw: bug#34050: Acknowledgement ([PATCH] gnu: Add libaom and activate AV1 support in ffmpeg.) Arne Babenhauserheide
2019-01-12 23:33 ` Leo Famulari
2019-01-13 22:19 ` Ludovic Courtès
2019-01-18 23:13 ` [bug#34050] [PATCH] gnu: Add libaom and activate AV1 support in ffmpeg. updated Arne Babenhauserheide
2019-03-05 3:18 ` Leo Famulari
2019-03-05 15:57 ` Arne Babenhauserheide
2019-03-05 20:08 ` Leo Famulari
2019-03-05 20:12 ` Leo Famulari
2019-03-05 23:30 ` bug#34050: " Leo Famulari
2019-03-06 19:24 ` Arne Babenhauserheide [this message]
2019-03-06 20:02 ` [bug#34050] " Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0n3957w.fsf@web.de \
--to=arne_bab@web.de \
--cc=34050-done@debbugs.gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.