Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Post
  • Reply
Mr VacBob
Aug 26, 2003
Was yea ra chs hymmnos mea

Alereon posted:

As an alternative, Intel has provided a media processor that performs pure hardware decoding of high definition MPEG2/VC-1 (WMV9)/AVC (H.264) video. In addition, it offers pure hardware encoding of AVC (H.264) video. The idea is that you'll be able to transcode video faster, and with lower power usage, on the CPU using the media engine than you would using a program that supports nVidia's CUDA or OpenCL on a dedicated GPU. This does require that you use a program that supports the Sandy Bridge media processor, but it's expected that support will be integrated into programs like Cyberlink's Media Show Espresso at launch, allowing performance comparisons with CUDA. We also don't know what kind of video quality it will produce, but probably likely that it won't be quite as good as dedicated software encoders like x264.

Not only would it be not as good as x264, it won't even be faster. My slower CPU gets the same speed (180fps) for small video sizes using the x264 "faster" preset. A CPU is a much better video encoder than any kind of GPU for all kinds of great reasons; the only reason to avoid one is power budgeting.

Adbot
ADBOT LOVES YOU

Mr VacBob
Aug 26, 2003
Was yea ra chs hymmnos mea

TOOT BOOT posted:

Couldn't the GPU be used for a really-fast first pass, since it can look at tons of frames in parallel?

The last method tried was to move x264's lookahead thread onto the GPU - this runs about ~50 frames ahead of actual encoding and is used to decide some stuff like frame types and visual importance.

It also avoids one of the worst problems with GPGPU; the motion decisions and so on are chosen just as much for how well the MVs compress as how well they match. This is really easy when you run all the decisions in the same order they're being encoded in... but GPUs do everything at the same time, so that doesn't work. Badaboom/etc most likely just don't bother doing any of it, so they're fast because they suck.

Anyway, the two people working on it still haven't finished after months, so it still can't be that easy...

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply