From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Handbrake: Is it is or is it ain't in portage
Date: Tue, 17 Aug 2010 15:35:38 +0100 [thread overview]
Message-ID: <2B2EE339-EE96-464B-ADC3-441AEE95E11C@stellar.eclipse.co.uk> (raw)
In-Reply-To: <AANLkTikkvfNPUVdr1-jZ8DPoiaDCr9J2Szm=KTDAv-Uz@mail.gmail.com>
On 17 Aug 2010, at 15:08, Kevin O'Gorman wrote:
> ...
> The clips do not play in any reasonable form. I get moments of
> sound, and a few pixels changing on screen; nothing coherent. I'd
> been told that H264 needs a lot of CPU and I guess an old 4-core 32-
> bit XEON (effectively 800 MHz each) on 2 GB ECC DDR1 is not enough.
> Okay.
Hi-def needs a lot of horses to play, I'm not sure about H264 compared
to other codecs. H264 is designed so that specialised deciding chips
(in mobile phones and set-top-boxes) can be built cheaply to aid
playback, but on generic hardware I would imagine it would be a chunk
more demanding than (say) the MPEG2 of the DVD standard written over a
decade ago.
If you mean 4 *processors* at 800mhz, then that's Pentium III
territory, and you have no chance. You'd really be requiring a Core2
class machine. A Pentium 4 is likely to struggle.
Video playback does parallelise, if the player is written for that.
But 800mhz is still massively underpowered for hi-def video.
Stroller.
next prev parent reply other threads:[~2010-08-17 14:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 0:43 [gentoo-user] Handbrake: Is it is or is it ain't in portage Kevin O'Gorman
2010-08-16 0:55 ` Dale
2010-08-16 1:45 ` Stroller
2010-08-16 2:22 ` Dale
2010-08-16 3:02 ` Kevin O'Gorman
2010-08-16 4:49 ` Indexer
2010-08-16 20:00 ` Kevin O'Gorman
2010-08-16 7:35 ` Stroller
2010-08-16 19:52 ` Kevin O'Gorman
2010-08-17 0:59 ` Stroller
2010-08-16 15:13 ` Bill Longman
2010-08-16 20:21 ` Paul Hartman
2010-08-17 14:08 ` Kevin O'Gorman
2010-08-17 14:35 ` Stroller [this message]
2010-08-17 16:06 ` Paul Hartman
2010-08-17 18:18 ` Kevin O'Gorman
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=2B2EE339-EE96-464B-ADC3-441AEE95E11C@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--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