Announcement

Collapse
No announcement yet.

Chrome Further Optimizes Its OpenH264 Encoder With More Assembly x86

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

  • Chrome Further Optimizes Its OpenH264 Encoder With More Assembly x86

    Phoronix: Chrome Further Optimizes Its OpenH264 Encoder With More Assembly x86

    Chrome/Chromium users on x86 dealing with H.264 encoding from the browser should notice faster performance coming down the pipe...

    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
    Ok, this sound good, but why is there a video encoder on a web browser? O_o

    Comment


    • #3
      But does Chrome/Chromium not mostly do H.264 decoding?

      Comment


      • #4
        Why not using x264? it's GPL and already heavily optimized.

        Comment


        • #5
          Originally posted by devius View Post
          Ok, this sound good, but why is there a video encoder on a web browser? O_o
          Video call mainly I guess

          Comment


          • #6
            Originally posted by karasu View Post

            Video call mainly I guess
            The legendary answer to the question that baffled many...

            TBH I didn't even know Chromium was responsible for encoding webcam streams.

            Comment


            • #7
              Hey, web browser developers -- here's a shocking thought:

              BROWSERS ARE NOT OPERATING SYSTEMS.

              Quit making the browser do what the operating system already does -- GUI drawing, video encoding, or anything else. You're duplicating functionality.

              Comment


              • #8
                Originally posted by mulenmar View Post
                Hey, web browser developers -- here's a shocking thought:

                BROWSERS ARE NOT OPERATING SYSTEMS.

                Quit making the browser do what the operating system already does -- GUI drawing, video encoding, or anything else. You're duplicating functionality.
                Chrome was designed as operating system (ChromeOS), so don't tell them what to do.

                Comment


                • #9
                  Originally posted by mulenmar View Post
                  Hey, web browser developers -- here's a shocking thought:

                  BROWSERS ARE NOT OPERATING SYSTEMS.

                  Quit making the browser do what the operating system already does -- GUI drawing, video encoding, or anything else. You're duplicating functionality.
                  Well, then tell web designers to go back to late 90's age of webpage resources, with only HTML/jpeg files and nothing more. Otherwise, your browser will need OS like levels of functionality. To use only what the OS provides to the browser, is inviting a compatibility nightmare to the developers deal with.

                  Comment


                  • #10
                    Originally posted by karasu View Post
                    Why not using x264? it's GPL and already heavily optimized.
                    Patents mostly. That would explain Mozilla anyway, not sure about Google.
                    They couldn't use something that's GPL, since they release Chrome under a different license, though x264 also has a paid license available.

                    Comment

                    Working...
                    X