From: nunojsilva@ist.utl.pt (Nuno J. Silva)
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: [OT] codec for video embedded in presentation
Date: Wed, 02 Jan 2013 00:19:14 +0200 [thread overview]
Message-ID: <87bod85yxp.fsf@ist.utl.pt> (raw)
In-Reply-To: 3C8C81DA-7057-4076-AA80-D1154BF86306@stellar.eclipse.co.uk
On 2013-01-01, Stroller wrote:
> On 30 December 2012, at 11:39, Nuno J. Silva wrote:
>> ...
>> The AVI container has been used by windows for a long time, so I'd say
>> chances are that it will work on more systems, but I can't say for sure.
>
> But h264 in an AVI is invalid.
>
> AVI is dated and just plain nasty.
>
> You should use something else (like h264 in an MP4) if you possibly can.
AVI is old, AVI has issues. AVI is not compatible with some
codecs. *But* AVI has been around for long enough to be supported by
many versions of Windows and Office, and what we're looking for here is
whatever offers the broadest support. I don't even think Windows (at
least up to 7) has a builtin h264 decoder. At least I remember having to
install codecs in Vista and 7 machines in order to view h264 Youtube
videos.
--
Nuno Silva (aka njsg)
http://njsg.sdf-eu.org/
next prev parent reply other threads:[~2013-01-01 22:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 2:04 [gentoo-user] [OT] codec for video embedded in presentation Francisco Ares
2012-12-30 2:11 ` Michael Mol
2012-12-30 11:39 ` [gentoo-user] " Nuno J. Silva
2012-12-30 23:35 ` Francisco Ares
2012-12-31 4:27 ` Kevin Chadwick
2013-01-01 15:16 ` Francisco Ares
2013-01-01 22:57 ` Kevin Chadwick
2013-01-01 22:13 ` Nuno J. Silva
2012-12-30 23:36 ` Francisco Ares
2012-12-31 22:38 ` [gentoo-user] " Stroller
2013-01-01 15:22 ` Francisco Ares
2013-01-02 21:08 ` Stroller
2013-01-02 21:52 ` [gentoo-user] " Nuno J. Silva
2013-01-01 22:19 ` Nuno J. Silva [this message]
2013-01-02 0:45 ` Michael Mol
2013-01-02 16:29 ` Francisco Ares
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=87bod85yxp.fsf@ist.utl.pt \
--to=nunojsilva@ist.utl.pt \
--cc=gentoo-user@lists.gentoo.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