Hardware Decoding suddenly stopped working for Steam In-Home Streaming?











up vote
0
down vote

favorite












Steam In-Home streaming suddenly started refusing to use hardware decoding. Have been using this for some time without issue. The client PC is too weak for software decoding.



Running Steam Client on Ubuntu 14.04 64-bit with nvidia-384 drivers, and a GT710.



Have tried reinstalling steam and nvidia drivers to no avail. Keeps defaulting back to software decoding.



Started steam from a shell, and noticed this in the output when streaming a game:



ffmpeg verbose: Opened VA display via X11 display :0.
libva info: VA-API version 0.39.0`
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so
libva info: va_openDriver() returns -1
ffmpeg error: Failed to initialise VAAPI connection: -1 (unknown libva error).
CVAAPIAccel: av_hwdevice_ctx_create() failed
libavcodec software decoding with 2 threads


Sure enough, there is no nvidia_drv_video.so present. At a complete loss here.










share|improve this question


























    up vote
    0
    down vote

    favorite












    Steam In-Home streaming suddenly started refusing to use hardware decoding. Have been using this for some time without issue. The client PC is too weak for software decoding.



    Running Steam Client on Ubuntu 14.04 64-bit with nvidia-384 drivers, and a GT710.



    Have tried reinstalling steam and nvidia drivers to no avail. Keeps defaulting back to software decoding.



    Started steam from a shell, and noticed this in the output when streaming a game:



    ffmpeg verbose: Opened VA display via X11 display :0.
    libva info: VA-API version 0.39.0`
    libva info: va_getDriverName() returns 0
    libva info: Trying to open /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so
    libva info: va_openDriver() returns -1
    ffmpeg error: Failed to initialise VAAPI connection: -1 (unknown libva error).
    CVAAPIAccel: av_hwdevice_ctx_create() failed
    libavcodec software decoding with 2 threads


    Sure enough, there is no nvidia_drv_video.so present. At a complete loss here.










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Steam In-Home streaming suddenly started refusing to use hardware decoding. Have been using this for some time without issue. The client PC is too weak for software decoding.



      Running Steam Client on Ubuntu 14.04 64-bit with nvidia-384 drivers, and a GT710.



      Have tried reinstalling steam and nvidia drivers to no avail. Keeps defaulting back to software decoding.



      Started steam from a shell, and noticed this in the output when streaming a game:



      ffmpeg verbose: Opened VA display via X11 display :0.
      libva info: VA-API version 0.39.0`
      libva info: va_getDriverName() returns 0
      libva info: Trying to open /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so
      libva info: va_openDriver() returns -1
      ffmpeg error: Failed to initialise VAAPI connection: -1 (unknown libva error).
      CVAAPIAccel: av_hwdevice_ctx_create() failed
      libavcodec software decoding with 2 threads


      Sure enough, there is no nvidia_drv_video.so present. At a complete loss here.










      share|improve this question













      Steam In-Home streaming suddenly started refusing to use hardware decoding. Have been using this for some time without issue. The client PC is too weak for software decoding.



      Running Steam Client on Ubuntu 14.04 64-bit with nvidia-384 drivers, and a GT710.



      Have tried reinstalling steam and nvidia drivers to no avail. Keeps defaulting back to software decoding.



      Started steam from a shell, and noticed this in the output when streaming a game:



      ffmpeg verbose: Opened VA display via X11 display :0.
      libva info: VA-API version 0.39.0`
      libva info: va_getDriverName() returns 0
      libva info: Trying to open /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so
      libva info: va_openDriver() returns -1
      ffmpeg error: Failed to initialise VAAPI connection: -1 (unknown libva error).
      CVAAPIAccel: av_hwdevice_ctx_create() failed
      libavcodec software decoding with 2 threads


      Sure enough, there is no nvidia_drv_video.so present. At a complete loss here.







      14.04 nvidia steam






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 22 at 21:10









      sunshine

      217




      217






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote



          accepted










          Well, apparently something did get removed. Ran sudo apt-get install vdpau-va-driver:i386. Now all is well.



          For anyone else wondering, dpkg -S /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so showed the package that needed to be installed.



          Edit 11/25/2018:
          This behavior persists on a new install of 16.04, the same steps were needed to remedy the issue.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1018366%2fhardware-decoding-suddenly-stopped-working-for-steam-in-home-streaming%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote



            accepted










            Well, apparently something did get removed. Ran sudo apt-get install vdpau-va-driver:i386. Now all is well.



            For anyone else wondering, dpkg -S /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so showed the package that needed to be installed.



            Edit 11/25/2018:
            This behavior persists on a new install of 16.04, the same steps were needed to remedy the issue.






            share|improve this answer



























              up vote
              0
              down vote



              accepted










              Well, apparently something did get removed. Ran sudo apt-get install vdpau-va-driver:i386. Now all is well.



              For anyone else wondering, dpkg -S /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so showed the package that needed to be installed.



              Edit 11/25/2018:
              This behavior persists on a new install of 16.04, the same steps were needed to remedy the issue.






              share|improve this answer

























                up vote
                0
                down vote



                accepted







                up vote
                0
                down vote



                accepted






                Well, apparently something did get removed. Ran sudo apt-get install vdpau-va-driver:i386. Now all is well.



                For anyone else wondering, dpkg -S /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so showed the package that needed to be installed.



                Edit 11/25/2018:
                This behavior persists on a new install of 16.04, the same steps were needed to remedy the issue.






                share|improve this answer














                Well, apparently something did get removed. Ran sudo apt-get install vdpau-va-driver:i386. Now all is well.



                For anyone else wondering, dpkg -S /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so showed the package that needed to be installed.



                Edit 11/25/2018:
                This behavior persists on a new install of 16.04, the same steps were needed to remedy the issue.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 26 at 3:49

























                answered Mar 23 at 3:37









                sunshine

                217




                217






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1018366%2fhardware-decoding-suddenly-stopped-working-for-steam-in-home-streaming%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                    Eduardo VII do Reino Unido