daldana 47 Posted January 29, 2020 Share Posted January 29, 2020 @@softworkz I tried the latest beta, 4.4.0.10, and I get different results but unfortunately hardware acceleration still doesn't work on mpeg2 files (logs attached). Also, when I play h264 files, it shows as direct playing so I don't have any ffmpeg logs. Let me know what else you need. ffmpeg-transcode-b95e4b67-7efc-4c30-833e-786c77e8e397_1.txt ffmpeg-transcode-71e63608-a81e-4742-a092-55c67a86d2af_1.txt Link to comment Share on other sites More sharing options...
Luke 37119 Posted January 29, 2020 Share Posted January 29, 2020 Did you follow our hardware acceleration setup guide? https://github.com/MediaBrowser/Wiki/wiki/Hardware-Acceleration-Overview Link to comment Share on other sites More sharing options...
daldana 47 Posted January 29, 2020 Share Posted January 29, 2020 Yes I did and I tried multiple combinations of decoders and encoders. The only way I could get Live TV to play was to use the Quicksync Intel HD Graphics - MPEG-2 decoder with the Quicksync Intel HD Graphics - D3D11 - H.264 (AVC) encoder. That combo got me software acceleration, but at least I got the video to play. Link to comment Share on other sites More sharing options...
softworkz 3341 Posted January 29, 2020 Share Posted January 29, 2020 Yes I did and I tried multiple combinations of decoders and encoders. The only way I could get Live TV to play was to use the Quicksync Intel HD Graphics - MPEG-2 decoder with the Quicksync Intel HD Graphics - D3D11 - H.264 (AVC) encoder. That combo got me software acceleration, but at least I got the video to play. I don't understand what you mean by "software acceleration". Could you please post a log? Could you please also try QuickSync D3D11 decoder + QuickSync D3D11 encoder and post a log? Wait - was that your case where the user connected via remote desktop and no QuickSync was working anymore, not even D3D11 ?? Link to comment Share on other sites More sharing options...
nmkaufman 49 Posted January 29, 2020 Share Posted January 29, 2020 Try attaching a monitor (or HDMI emulator dongle) and logging into the machine locally, or using Chrome Remote desktop (rather than windows RDP) and trying again. RDP creates a virtual graphics card, so the intel graphics (and HW acceleration) are no longer active. I have to use the same trick to use Nvidia Gamestream from my headless server. RDP disables the Nvidia graphics entirely, until I log back in either locally or using a non-RDP remote desktop solution. Link to comment Share on other sites More sharing options...
daldana 47 Posted January 29, 2020 Share Posted January 29, 2020 @@softworkz, I shouldn't have used the phrase software acceleration, I meant software encoding. Attached is the log using D3D11 for both decoder and encoder, the video took about three minutes to start. I was doing the tests directly on the server, no RDP. The attached log is from monitoring the server with a web browser, again no RDP. nmkaufman, I have a monitor attached to the server and am able to get hardware acceleration from the stable server. I didn't use RDP for any of the recent tests. ffmpeg-transcode-3bd0cbad-8948-43d4-af6d-1f1856bda6de_1.txt 1 Link to comment Share on other sites More sharing options...
softworkz 3341 Posted January 29, 2020 Share Posted January 29, 2020 Thanks for the log. That's really unexpected because it cannot even create the D3D11 device. Would you mind trying a few things? You would need to install the Diagnostics plugin first: https://mediabrowser.github.io/Emby.DiagnosticsPlugin/ Then reboot Wait 1 min until hw detection is completed In the diagnostic options page, choose log-level "verbose" Retry the same as above (on both sides QuickSync D3D11) and check whether the same error occurs If yes, please post the hw detection log and the ffmpeg log (I want to make sure that nothing happens between the detection and the failure) Second Test In the Diagnostic options, activate "use legacy command building"(if the same error occurs, no need to post logs)Third Test Deactivate legacy command building Activate "disable scaling" and retry Thanks Link to comment Share on other sites More sharing options...
daldana 47 Posted January 29, 2020 Share Posted January 29, 2020 First test set of logs. It took a long time to start playing again. ffmpeg-transcode-c8218d92-1fa6-481b-b61e-81f197893129_1.txt hardware_detection-63715906917.txt Link to comment Share on other sites More sharing options...
daldana 47 Posted January 29, 2020 Share Posted January 29, 2020 Second test, same error. Third test,same error. Logs attached for this test. ffmpeg-transcode-6ed8364e-363b-46cd-bcea-b01b99e09db1_1.txt hardware_detection-63715908608.txt Link to comment Share on other sites More sharing options...
softworkz 3341 Posted January 29, 2020 Share Posted January 29, 2020 I think you can stop... I just realized that your Intel drivers are too old to support D3D11 at all. What's your Widndows version and your hardware (CPU)? Link to comment Share on other sites More sharing options...
daldana 47 Posted January 30, 2020 Share Posted January 30, 2020 Windows 10 Pro version 1909, Intel i5-3470 CPU. Link to comment Share on other sites More sharing options...
daldana 47 Posted January 30, 2020 Share Posted January 30, 2020 I guess my question is why can I get hardware acceleration on the stable server with the non D3D11 decoders/encoders. Link to comment Share on other sites More sharing options...
pwhodges 1534 Posted January 30, 2020 Share Posted January 30, 2020 Recent betas have introduced big improvements for acceleration on Intel cpus, I believe. Paul Link to comment Share on other sites More sharing options...
softworkz 3341 Posted January 30, 2020 Share Posted January 30, 2020 (edited) I guess my question is why can I get hardware acceleration on the stable server with the non D3D11 decoders/encoders. The beta includes an ffmpeg version which is built against a newer SDK version. It's possible that this causes problems with old driver versions. Did you install the latest graphics driver from the Intel website? Edited January 30, 2020 by softworkz Link to comment Share on other sites More sharing options...
softworkz 3341 Posted January 30, 2020 Share Posted January 30, 2020 Your installed driver matches QuickSync SDK 1.11 - that had been released 6 years ago. The current version is 1.31. Link to comment Share on other sites More sharing options...
softworkz 3341 Posted January 30, 2020 Share Posted January 30, 2020 Try this driver: https://downloadcenter.intel.com/download/29311?product=68316 The included QuickSync runtime is still old, but it might be a little newer than yours at least. Link to comment Share on other sites More sharing options...
daldana 47 Posted February 8, 2020 Share Posted February 8, 2020 Softworx, Just an update, using the driver you suggested above and beta version 4.4.0.10 still did not get hardware acceleration, but 4.4.0.12 did it! Sorry, I didn't get to try .11 beforehand to see if it would work. Thanks for all of your help! Dave Link to comment Share on other sites More sharing options...
Luke 37119 Posted February 8, 2020 Share Posted February 8, 2020 Thanks for the feedback. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now