Jump to content

Intel HD 630 transcoding showing Software

Painkiller88

By Painkiller88
in General/Windows

 Share
Go to solution Solved by softworkz,

Recommended Posts

Painkiller88

Painkiller88 249

Posted
Posted (edited)

I Switched my Windows emby Server to an Intel NUC I9 Extreme. 

 

IT has the CPU: Intel Core i9-9980HK and an Intel UHD 630

 

i have emby Premiere and when i have a transcoding stream it Shows me Software instead of Hardware. 

 

I never used quickSync before but i think it also should Show me Hardware. 

 

Is There something special i Need to Do? 

 

Hardware transcoding is enabled and uhd 630 quickSync is recorgnized and Set as first Option. 

 

 

Thanks 

Edited by Painkiller8818
Happy2Play

Happy2Play 9780

Posted
Posted

Please provide server, ffmpeg, and hardware detection log.

Carlo

Carlo 4561

Posted
Posted

Besides what Happy2Play mentioned, do you have Premiere?

HW Transcoding does require a Premiere license.

  • 2 weeks later...
Painkiller88

Painkiller88 249

Posted
  • Author
Posted

OS: Win10
Emby: 4.5.4.0
Premiere: YES
Server: Intel NUC I9 Extreme
CPU: Intel Core i9-9980HK and an Intel UHD 630


Yes i have Premiere. I is working but some times it isn't, after restarting the emby server (just the service not the whole PC) it is working.

Took a bit now to get this case again and uploaded the logs now.

I had this now with h264 to h264 and also with h265 to h264 transcodes (h265 is not a 4k it is a normal 1080p i just did this to save space)

in ffmpeg i see could not create qsv stream, but can't figure out why, after restarting emby it is working, so not a problem with the video file.
 

embyserver-63755154475.txt ffmpeg-transcode.txt hardware_detection.txt

Carlo

Carlo 4561

Posted
Posted

You're getting a bunch of Direct3D11 failed errors in those logs.

Are you Intel drivers current?

Can you give us screen shots of your transcoding setup please?

Painkiller88

Painkiller88 249

Posted
  • Author
Posted

Yes my drivers are the most actual for my cpu/igpu for the nuc i9 i downloaded them directly from the website and the drivers check from my nuc also tells me i am up to date.

Here are the transcoding settings, i really took care to have the QuckSync option for every codec on the first position.

As i am connected via RDP to my Emby Server the resolution in the drivers pic is not the full, but drivers are up to date.

grafik.png

grafik.png

grafik.png

grafik.png

grafik.png

Painkiller88

Painkiller88 249

Posted
  • Author
Posted

ok strange the intel update assistant tells me i am acutal. maybe the DCH drivers are not checked if i have an OEM driver. Will install the DCH driver and have an eye on emby transcoding.

Thanks

Painkiller88

Painkiller88 249

Posted
  • Author
Posted

Ok strange, after installing the new DCH driver i checked transcoding and saw i got a new entry for every codec.

 

the new entry seems not to use D3D11, so i enabled it and put on the first place for all codecs

 

grafik.thumb.png.878e113d241eb37bf2f1d609ac9e1102.png

Carlo

Carlo 4561

Posted
Posted

Try setting the use hardware transcoding to NO and save it.

Then set it back to YES and save it.  That should allow Emby to reset these to what it thinks is best.
Try it like this before starting to change things to see if it works.

Let us know how this works for you.

Painkiller88

Painkiller88 249

Posted
  • Author
Posted

The problem is not solved with the newest intel driver

 

i have it again (internal myself now)

ffmpeg is uploaded.

 

 

ffmpeg-transcode.txt

rbjtech

rbjtech 5284

Posted
Posted

I've seen this 'cannot create QSV' before when I was testing the HDR trancoding - but can't fully remember why it happended and how I resolved.  @softworkz  may remember.

A couple of things to try -

In the BIOS of the PC, how much memory is allocated to the integrated graphics ?

If you have the option of allocating more, then try to give it the max you can.

Do you have an actual monitor plugged into this device ?  If not, then try again with a monitor installed (after a reboot).

Probably also worth posting your hardware detection log.

Painkiller88

Painkiller88 249

Posted
  • Author
Posted

Ok would be cool if he could remember.

My system has 16GB RAM, i haven't allocated something special but if i can trust the system (taskmanager) the GPU has 8GB Shared memory, but it never used more than a half GB

I don't have any monitors on this system as my NUC is in another room, i only connect via RDP to see whats up on the system. No direct Monitor on this system.

I will check the BIOS if i cas set a specific amount of shared RAM for the GPU.

grafik.thumb.png.cd97610f1f8d086b9f728476abf2adb0.png

Painkiller88

Painkiller88 249

Posted
  • Author
Posted

ok, but i just check things with RDP i don't watch via RDP on this device, i watch normally on my TV or on the browser of another device.

Just to make this clear, i don't watch on my NUC via RDP. but i will try this changes.

Thanks :)

rbjtech

rbjtech 5284

Posted
Posted

Sure - not saying you are - but there are issues running emby with h/w accelrations from within an RDP 'session'. (a virtual desktop).

If you can, temporarily plug in a keyboard, mouse and monitor into the physical NUC (emby server) - then reboot and run emby from a 'local' login session (not RDP).

I suspect hardware acceleration will then work fine with the other clients.

 

Painkiller88

Painkiller88 249

Posted
  • Author
Posted

ok thanks will try this.

Carlo

Carlo 4561

Posted
Posted

If this works a dummy plug may help.

Painkiller88

Painkiller88 249

Posted
  • Author
Posted

The Problem is not solved.

I have everything on the newest driver, also checked BIOS Update, but still using Software from time to time.

If i use Handbrake to shrink or reencode my movies from h264 to h265 qsv is working.

This is really strange.

Anything else i can do? Or is it emby not using it right?

ffmpeg-transcode-3293e802-efd5-4939-96dc-9808aa6401eb_1.txt

Carlo

Carlo 4561

Posted
Posted

Did you try the info presented above?

Painkiller88

Painkiller88 249

Posted
  • Author
Posted
2 hours ago, cayars said:

Did you try the info presented above?

yes sure, i already disabled Hardware Acceleration for RDP via GPO

 

i will play around with the Enoders/Decoders a bit, maybe i find a solution

rbjtech

rbjtech 5284

Posted
Posted

Did you connect a keyboard, mouse and screen and run emby server directly (without using RDP) - just as a test ?

 

 

  • Like 1
Painkiller88

Painkiller88 249

Posted
  • Author
Posted

Ok i think i am a step further.

Just setting the Hardware Acceleration to ON, does not help.

I set it to advanced and played around. Now it seems Disabling all Encoders/Decoders except the ones with D3D11 works till now.
I started the same stream about 30 Times with different settings, and this seems to be a solution for now. I just wonder why, because i had the normal QuickSync without D3D11 on the first place till now, as i have DX12 and not DX11 installed on my System.

 

i will investigate more time on this and see if it is a final solution

  • Solution
softworkz Emby Team

softworkz 5067

Posted
  • Solution
Posted

@Painkiller8818

I think you have screwed up things by using RDP for all the setup.

Generally, with the the use D3D11 codec variants, things should be working safely, even when logging in via RDP, but the two mistakes you probably made are these:

  • You must not do graphics driver installations from within an RDP session
  • You must not start Emby Server from within an RDP session

To clean up all that mess, you should do the following:

1. Find a way to access the computer without RDP

Either connect a real monitor and keyboard
or
install a non-RDP-based remote access software - like VNC or TeamViewer (you might or might not need a dummy plug for this

=> Don't even think about proceeding as long as you don't have that!

 

2. Get the graphics driver installation right

  • Have step 1 completed, don't be logged in via RDP
  • If you have any other GPU boards installed, remove them
  • Reboot the server
  • Make sure, nobody is logged in via RDP and nobody will log in via RDP
  • Uninstall all previous Intel Driver installations
    • Reboot after each uninstall
  • Reboot
  • Open a console as administrator
    • enter SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
    • enter devmgmt.msc
    • Menu: View >> Show Hidden Device
    • Group "Display Drivers": Make sure, no hidden devices exist, if there is any: Right-Click >> Uninstall
    • Next, check the graphics driver
      • If there's still an Intel driver (rather than the MS generic driver): Right-Click >> Uninstall
  • Reboot
  • Install the latest Intel Graphics driver
  • Reboot

 

3. Run Emby Server - The right way

There are two ways to do that: Either run as a service or run in the console session with auto-login

Preparation for both ways is the same:

  • Have steps 1 and 2 completed, don't be logged in via RDP
  • Uninstall any previous Emby Server installation
    • will need to login with the account under which it was previously installed
    • uninstall
  • Create a new user account under which Emby will run
  • Log in to that user account
  • Install Emby server for that account
  • Set up Emby Server
  • Make sure everything is working

Now you have two choices

  1. Set up Emby Server to run as a service
    • Instructions for this are available in the knowledge base
    • Make sure to run it under the newly created user account
  2. Configure Emby Server to run on "Windows startup"
    (this setting actually means "User Login" rather than Windows startup)
    • To make this work, you need to configure the console (=connected monitor, keyboard) session to automatically log on when Windows starts
      of course it must log on with the Emby user account
    • Instructions for this can be found on the web

 

Finally

Now all things will work fine and you can log in via RDP without issues

 

 

 

  • Like 2
rbjtech

rbjtech 5284

Posted
Posted
22 hours ago, softworkz said:

@Painkiller8818

I think you have screwed up things by using RDP for all the setup.

Generally, with the the use D3D11 codec variants, things should be working safely, even when logging in via RDP, but the two mistakes you probably made are these:

  • You must not do graphics driver installations from within an RDP session
  • You must not start Emby Server from within an RDP session

To clean up all that mess, you should do the following:

1. Find a way to access the computer without RDP

Either connect a real monitor and keyboard
or
install a non-RDP-based remote access software - like VNC or TeamViewer (you might or might not need a dummy plug for this

=> Don't even think about proceeding as long as you don't have that!

 

2. Get the graphics driver installation right

  • Have step 1 completed, don't be logged in via RDP
  • If you have any other GPU boards installed, remove them
  • Reboot the server
  • Make sure, nobody is logged in via RDP and nobody will log in via RDP
  • Uninstall all previous Intel Driver installations
    • Reboot after each uninstall
  • Reboot
  • Open a console as administrator
    • enter SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
    • enter devmgmt.msc
    • Menu: View >> Show Hidden Device
    • Group "Display Drivers": Make sure, no hidden devices exist, if there is any: Right-Click >> Uninstall
    • Next, check the graphics driver
      • If there's still an Intel driver (rather than the MS generic driver): Right-Click >> Uninstall
  • Reboot
  • Install the latest Intel Graphics driver
  • Reboot

 

3. Run Emby Server - The right way

There are two ways to do that: Either run as a service or run in the console session with auto-login

Preparation for both ways is the same:

  • Have steps 1 and 2 completed, don't be logged in via RDP
  • Uninstall any previous Emby Server installation
    • will need to login with the account under which it was previously installed
    • uninstall
  • Create a new user account under which Emby will run
  • Log in to that user account
  • Install Emby server for that account
  • Set up Emby Server
  • Make sure everything is working

Now you have two choices

  1. Set up Emby Server to run as a service
    • Instructions for this are available in the knowledge base
    • Make sure to run it under the newly created user account
  2. Configure Emby Server to run on "Windows startup"
    (this setting actually means "User Login" rather than Windows startup)
    • To make this work, you need to configure the console (=connected monitor, keyboard) session to automatically log on when Windows starts
      of course it must log on with the Emby user account
    • Instructions for this can be found on the web

 

Finally

Now all things will work fine and you can log in via RDP without issues

 

 

 

Nice write up @softworkz

@cayars - is it worth expanding the support article below with the details above ?  

I use RDP and found out the hard way that you cannot run emby under an RDP session - hence pointing the OP to the link below as soon as they mentioned RDP ;)

https://support.emby.media/support/solutions/articles/44001894172-hardware-acceleration-fails-with-remote-desktop-rdp-on-windows

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...