From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Multimedia Libs
Date: Sat, 28 Mar 2020 05:54:09 +0100 [thread overview]
Message-ID: <8103b678-8841-2c5c-340f-52a1fefea23f@ipfire.org> (raw)
In-Reply-To: <b5919ae3-e923-f121-b1c9-3e0c2e51dd09@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
Hi,
On 26.03.2020 10:30, Matthias Fischer wrote:
> Hi,
>
>> ...
>> There are a couple of reasons:
>>
>> The image libraries are used to generate graphs. There are multiple ways do encode those and there are plenty of interdependencies to it.
>
> Image libraries. Ok. I see the point. Can be useful.
>
>> The audio libraries are being used for libvirt, tshark to capture and decode audio and video, too.
>>
>> There are a couple of media streaming add-ons which also can re-encode things. It is of course up to everyone to decide if they want/need to use it.
>
> ACK.
> ...
Just to sum this up:
If nobody has any further suggestions or objections I would fire up a
'multimedia-branch' and try to build all found updates. or are there any
we can do without?
Best,
Matthias
next prev parent reply other threads:[~2020-03-28 4:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5C7D0AAC-730A-40BA-B398-8AED49A4867D@ipfire.org>
2020-03-25 20:55 ` Matthias Fischer
2020-03-25 21:11 ` Stephan Mending
2020-03-26 7:24 ` Matthias Fischer
2020-03-26 9:10 ` Michael Tremer
2020-03-26 9:30 ` Matthias Fischer
2020-03-28 4:54 ` Matthias Fischer [this message]
2020-03-28 7:41 ` Michael Tremer
2020-03-26 9:47 ` Stephan Mending
2020-03-30 5:08 ` Matthias Fischer
2020-03-30 5:17 ` Matthias Fischer
2020-03-30 9:10 ` Matthias Fischer
2020-03-30 9:31 ` Michael Tremer
2020-04-02 17:07 ` Matthias Fischer
2020-04-03 10:22 ` Michael Tremer
2020-05-23 10:08 ` Matthias Fischer
2020-05-25 9:29 ` Michael Tremer
2020-05-25 11:05 ` Matthias Fischer
2020-05-26 10:15 ` Michael Tremer
2020-05-26 17:13 ` Matthias Fischer
2020-05-28 11:54 ` Michael Tremer
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=8103b678-8841-2c5c-340f-52a1fefea23f@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox