Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frame processing latency false values with Windows.Graphics.Capture method #3364

Open
2 tasks done
xenophobentx opened this issue Nov 3, 2024 · 1 comment
Open
2 tasks done

Comments

@xenophobentx
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Is your issue described in the documentation?

  • I have read the documentation

Is your issue present in the latest beta/pre-release?

This issue is present in the latest pre-release

Describe the Bug

With the new beta Capture method the host processing latency showing false numbers which are constantly increasing from the start of the sunshine executable reaching really huge numbers which for sure are not actual values as the performance is pretty good not getting such huge latenies.

Example debug log entry:

Debug: Frame processing latency (min/max/avg): 304.40ms/321.20ms/305.11ms

Expected Behavior

Show actual host latency values just like with the dekstop duplication API.

Additional Context

No response

Host Operating System

Windows

Operating System Version

10 22H2

Architecture

amd64/x86_64

Sunshine commit or version

v2024.1102.190004

Package

Windows - portable (not recommended)

GPU Type

Nvidia

GPU Model

RTX 3060 TI

GPU Driver/Mesa Version

566.03

Capture Method

Windows.Graphics.Capture (Windows)

Config

No response

Apps

No response

Relevant log output

[2024-11-03 11:19:11.762]: Debug: NvEnc: encoded frame sizes in kB (min/max/avg): 0.55/30.33/7.74
[2024-11-03 11:19:11.763]: Debug: Frame processing latency (min/max/avg): 305.70ms/307.70ms/306.38ms
[2024-11-03 11:19:11.764]: Debug: Network: each FEC block latency (min/max/avg): 0.00ms/0.01ms/0.00ms
[2024-11-03 11:19:11.765]: Debug: Network: each send_batch() latency (min/max/avg): 0.01ms/0.07ms/0.03ms
[2024-11-03 11:19:11.766]: Debug: Network: frame's overall network latency (min/max/avg): 0.03ms/0.12ms/0.05ms
[2024-11-03 11:19:31.778]: Debug: NvEnc: encoded frame sizes in kB (min/max/avg): 0.77/31.06/6.44
[2024-11-03 11:19:31.778]: Debug: Frame processing latency (min/max/avg): 306.90ms/327.40ms/307.58ms
[2024-11-03 11:19:31.779]: Debug: Network: each FEC block latency (min/max/avg): 0.00ms/0.03ms/0.00ms
[2024-11-03 11:19:31.780]: Debug: Network: each send_batch() latency (min/max/avg): 0.01ms/0.10ms/0.03ms
[2024-11-03 11:19:31.780]: Debug: Network: frame's overall network latency (min/max/avg): 0.03ms/0.19ms/0.05ms
[2024-11-03 11:19:39.542]: Debug: type [IDX_INVALIDATE_REF_FRAMES]
@xenophobentx
Copy link
Author

xenophobentx commented Nov 4, 2024

Somehow it is connected to boot time. On a freshly booted windows it has small values and constantly increasing to unreal numbers like 3700ms until next reboot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant