Selecting GPU inside the web client?

[HawkXP71 112]

Is it possible to select the GPU for rendering inside the web client? or only the windows store app?

[yocker 1247]

That would be a browser specific thing i think.

What i know is you can activate hardware acceleration in browsers (mostly on by default) and it will use the driver installed in the OS,

[HawkXP71 112]

15 hours ago, yocker said:

That would be a browser specific thing i think.

What i know is you can activate hardware acceleration in browsers (mostly on by default) and it will use the driver installed in the OS,

Yes, but it may choose the wrong gpu.  When plugged in, there doesn't seem to be any rhyme or reason as to which one it chooses. 

[js28194 36]

What browser?  Here is something from Reddit for Chrome...  Google be your friend as this is not Emby specific, it's browser specific.

 

[yocker 1247]

21 hours ago, HawkXP71 said:

Yes, but it may choose the wrong gpu.  When plugged in, there doesn't seem to be any rhyme or reason as to which one it chooses. 

I would think it would automatically use the GPU used as display for the OS, not sure how it works tbh.
You can try the suggestion from js28194.

[HawkXP71 112]

3 hours ago, yocker said:

I would think it would automatically use the GPU used as display for the OS, not sure how it works tbh.
You can try the suggestion from js28194.

In this case windows, the OS effectively sets which GPU to do based on its own internal metrics.  However an application can directly overwrite the choice in one or two ways.  The "generic" method the app can change it is to simply use calls that only on device driver supports.  You will get an error if that GPU is not available.  Ie picking the nvidia_hevc codec vs a generic hevc codec.  Thats effectively what happens when you transcode using ffmeg and select a particular hevc driver.

You can also, specifically set the GPU with a device ID in the application.

However, I am not sure if its possible to do so inside JavaScript applications running on a chromium core (Edge, Safar and Chrome all do).

In windows, you can set in the settings system that any particular application or app use a particular GPU.  Ive done so for the Emby App from the Windows Store. 

I have a number of 4k movies, that the embedded GPU cant keep up with, but the daughter card nVidia handles it no problem,.  Its not a network bottle neck, I upgraded to a 10gbe direct connection, and then titrated it down to a 1gbe and it didnt matter.  I also ran it running the server on the client machine itself with a localhost connection.  It turned out to be the GPU being chosen. 

Using the Emby App is fine, and handles it.  But was hoping for a webclient solution, without forcing all instances of the webrowser to use a particular GPU, as I would much rather have that balanced by the OS.  I do use the browser for more than just Emby after all  

 

[yocker 1247]

3 hours ago, HawkXP71 said:

In this case windows, the OS effectively sets which GPU to do based on its own internal metrics.  However an application can directly overwrite the choice in one or two ways.  The "generic" method the app can change it is to simply use calls that only on device driver supports.  You will get an error if that GPU is not available.  Ie picking the nvidia_hevc codec vs a generic hevc codec.  Thats effectively what happens when you transcode using ffmeg and select a particular hevc driver.

You can also, specifically set the GPU with a device ID in the application.

However, I am not sure if its possible to do so inside JavaScript applications running on a chromium core (Edge, Safar and Chrome all do).

In windows, you can set in the settings system that any particular application or app use a particular GPU.  Ive done so for the Emby App from the Windows Store. 

I have a number of 4k movies, that the embedded GPU cant keep up with, but the daughter card nVidia handles it no problem,.  Its not a network bottle neck, I upgraded to a 10gbe direct connection, and then titrated it down to a 1gbe and it didnt matter.  I also ran it running the server on the client machine itself with a localhost connection.  It turned out to be the GPU being chosen. 

Using the Emby App is fine, and handles it.  But was hoping for a webclient solution, without forcing all instances of the webrowser to use a particular GPU, as I would much rather have that balanced by the OS.  I do use the browser for more than just Emby after all  

 

Might be a browser extensions, They are like phone apps, every where are for every thing.  

[HawkXP71 112]

22 hours ago, yocker said:

Might be a browser extensions, They are like phone apps, every where are for every thing.  

Doing more research on it, the chromium core only allows it once per launch (not per window/process). 

There is already a chrome developer flag to make this choice, safari and edge dont have the flag accessable.