Additional Field request in Stats for Nerds

[HawkXP71 112]

I have two GPUs, an embedded intel GPU on the CPU, and an external nVidia card.

The client is
 

Name:	Emby Windows
Version:	2.234.2.0

Would it be possible to add the "GPU in use" in the screen?

I was having a problem with "skipping" and it turns out the intel GPU cant keep up with a 4k direct play stream.  

Adding a custom setting in my system settings, so Emby gets the nVidia, fixed the problem.

However, it took a while to realize the gpu was the issue (nothing was showing up in any log).  I found the issue in the App Settings->Display Control and I saw that screen was tied to the intel GPU.

In the stats for nerds, if it listed "Rendering on display: Display 0" as well as "Rendering via GPU: Intel xxx ""

I would have realized earlier what was a potential cause.

Once I selected the correct GPU, all skipping goes away with direct play.

Thanks.
 

[brothom 177]

11 hours ago, HawkXP71 said:

However, it took a while to realize the gpu was the issue (nothing was showing up in any log).  I found the issue in the App Settings->Display Control and I saw that screen was tied to the intel GPU.

@HawkXP71I'm curious as to where you are seeing these "found the issue in the App Settings->Display Control and I saw that screen was tied to the intel GPU." fields?
Chrome and the Emby Android app don't have "Display Control" in their settings.

Stats for nerds only shows basic streaming info:

If this prompt doesn't display Direct Play for even one of the three (Stream/Video/Audio) options, some sort of transcoding or remuxing is happening.

Besides, if GPU usage would be added, why not also add CPU usage, or RAM usage or better yet drive usage? This data isn't really relevant for the stream and should stay serversided imo to keep the views clearer.

[ebr 16168]

I believe this is only relevant to the native Windows app.  Moving there.

[HawkXP71 112]

4 hours ago, brothom said:

@HawkXP71I'm curious as to where you are seeing these "found the issue in the App Settings->Display Control and I saw that screen was tied to the intel GPU." fields?
Chrome and the Emby Android app don't have "Display Control" in their settings.

Stats for nerds only shows basic streaming info:

If this prompt doesn't display Direct Play for even one of the three (Stream/Video/Audio) options, some sort of transcoding or remuxing is happening.

Besides, if GPU usage would be added, why not also add CPU usage, or RAM usage or better yet drive usage? This data isn't really relevant for the stream and should stay serversided imo to keep the views clearer.

As stated in my post, this is only on the native app from the windows store. 

[brothom 177]

2 hours ago, HawkXP71 said:

As stated in my post, this is only on the native app from the windows store. 

Both the words "app" and "store" are missing from your post description. 

@ebralready moved your post I guess so nevermind me.

[HawkXP71 112]

4 hours ago, brothom said:

Both the words "app" and "store" are missing from your post description. 

@ebralready moved your post I guess so nevermind me.

The client is
 

Name:	Emby Windows
Version:	2.234.2.0

Only applies to the windows store app.

[Luke 42077]

HI ,yes we can look at improving this. Thanks.

[brothom 177]

18 hours ago, Luke said:

HI ,yes we can look at improving this. Thanks.

Would also be interesting to see if we can get some kind of graph data in the Stats for Nerds side in the other clients like web/android/chromecast. 

[HawkXP71 112]

23 hours ago, Luke said:

HI ,yes we can look at improving this. Thanks.

Brings up another point, and if you want I can create a new topic on this.

Is there anything in any log, or any reporting that would show the reason for the skipping/pausing is due to a GPU being not performant enough?

Its 100% reproducible with the 4k movies Im choosing, but I never saw anything, not even a missed frame report. It happens on both the Windows App as well the web client.  

 

 

[Luke 42077]

1 hour ago, HawkXP71 said:

Brings up another point, and if you want I can create a new topic on this.

Is there anything in any log, or any reporting that would show the reason for the skipping/pausing is due to a GPU being not performant enough?

Its 100% reproducible with the 4k movies Im choosing, but I never saw anything, not even a missed frame report. It happens on both the Windows App as well the web client.  

 

 

Generally no. Most video players have a developer api to track dropped frames, but not the reason for it.

[brothom 177]

On 23/01/2026 at 20:41, HawkXP71 said:

Brings up another point, and if you want I can create a new topic on this.

Is there anything in any log, or any reporting that would show the reason for the skipping/pausing is due to a GPU being not performant enough?

Its 100% reproducible with the 4k movies Im choosing, but I never saw anything, not even a missed frame report. It happens on both the Windows App as well the web client.  

Dropped frames are not the same as late responses. If the player hangs because the server is busy transcoding and doesn't respond with the chunk in time, the frame isn't considered dropped. Frames are generally considered dropped due to bitrate/playback issues (missing frames etc) or when network packages are only received partially.

Dropped frames cán also occur during transcoding when the application (ffmpeg) has difficulty processing the format or when the source file isn't "complete". So there's a bunch of reasons which sometimes only the server knows, sometimes only the player knows, unless each chunk also contains messages about it's processing.

[HawkXP71 112]

6 hours ago, brothom said:

Dropped frames are not the same as late responses. If the player hangs because the server is busy transcoding and doesn't respond with the chunk in time, the frame isn't considered dropped. Frames are generally considered dropped due to bitrate/playback issues (missing frames etc) or when network packages are only received partially.

Dropped frames cán also occur during transcoding when the application (ffmpeg) has difficulty processing the format or when the source file isn't "complete". So there's a bunch of reasons which sometimes only the server knows, sometimes only the player knows, unless each chunk also contains messages about it's processing.

Understood.  the problem I had/have, was I was effectively dropping frames.  However I had no ability to debug/diagnose the cause of the problem because on the client side we are limited in logging ability.  I realized in a browser, there is less Emby can do to help, as the browsers API is doing much of the heavy lifting of the streaming, but I was hoping in the app there was more information available.  

Not blaming anyone, simply hoping for a solution to the problem.