Announcement

Collapse
No announcement yet.

HandBrake 0.10 Brings H.265 & VP8 Encoders

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • HandBrake 0.10 Brings H.265 & VP8 Encoders

    Phoronix: HandBrake 0.10 Brings H.265 & VP8 Encoders

    Version 0.10 of the HandBrake open-source video transcoder has been released...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Bicubic (OpenCL) (Experimental)

    Available on the Command Line (All Platforms) and Windows GUI. (Mac / Linux GUI's will come in a later release)
    Currently only available in OpenCL form so requires a AMD or Intel GPU supporting OpenCL 1.1 or later. Nvidia GPU's are not currently supported.
    When downscaling, up to 5% performance improvement can be achieved. No benefit when not downscaling.
    Small loss in quality over the Lanczos scaler.
    What part of Device Agnostic do developers not grasp about OpenCL? This should be available on any OpenCL 1.1 or newer AMD CPU or Intel CPU, not to mention a system that has other OpenCL devices.

    Comment


    • #3
      Originally posted by Marc Driftmeyer View Post
      What part of Device Agnostic do developers not grasp about OpenCL? This should be available on any OpenCL 1.1 or newer AMD CPU or Intel CPU, not to mention a system that has other OpenCL devices.
      The part where every GPU vendor implements OpenCL in a different way and your code doesn't always work as expected in their platforms? 1.1 should work on nVidia, but thay've got to have a reason for saying it's unsupported.

      Comment


      • #4
        What took VP8 support so long and where is VP9 support?

        Comment


        • #5
          Originally posted by Marc Driftmeyer View Post
          What part of Device Agnostic do developers not grasp about OpenCL? This should be available on any OpenCL 1.1 or newer AMD CPU or Intel CPU, not to mention a system that has other OpenCL devices.
          Here is one example: Last time I used it, Nvidia's implementation does not provide the C++ bindings for OpenCL. Probably because it makes OpenCL more comfortable to use than Cuda. So you can't build an OpenCL application based on C++.

          Since C++ bindings are one million times better in every way than the standard C interface, programmers like to use them. They really make OpenCL a breeze. Nvidia is the only vendor that got this wrong.

          You can get things to work with Nvidia, but you have to drop cl.hpp from some other implementation into your /usr/include and this is not something anybody wants to recommend or support.

          Disclaimer -- I don't know if this is the problem Hanbrake is having, but it was the problem I was having. Getting people to compile my code on Nvidia was difficult.

          Comment


          • #6
            Originally posted by uid313 View Post
            What took VP8 support so long and where is VP9 support?
            H.265 being so ?shiny??

            Comment

            Working...
            X