Audio reverting to default 16bits/48khz at new session #2671
Comments
|
With the latest pre-releases the logs should have a line detailing the settings used for the Opus audio codec. You might want to check the logs again with a pre-release. (And post your results) |
Hey thanks for the reply! Sorry For this late reply, the notifications don't seem to work for me and i fortget.. i'm on holiday right now, so not able to check, but i'll do asap when i'll get home ;) |
|
Using anything other than 48kHz will be detrimental because opus codec can't do anything else. |
Ok yeah i see, in fact, that's not a big issue, that's a minor thing. At least, Sunshine supports 5.1/7.1 audio for free, not like much of remote gaming apps ahah I'll always be surprised that the latency is so low, that's really enjoyable |
|
#2873 will switch capture/encoding pipeline to floating point samples. I think this issue can be closed. |
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the latest beta/pre-release?
Describe the Bug
Moonlight is on last version (same issue with the previous one) & Sunshine is updated too.
GPU doesn't have the last driver because last of us won't launch otherwise, but same issue with the last driver.
Host:
I7-7700k
32g
Full Nvmes and one dedicated for the OS, the other for games.
Gigabit Ethernet
Client is a Thinkpad t460:
I7-6600 (not sure)
12g
SSD
IGPU
Hdmi output supports every audio format I need.
Gigabit Ethernet
The issue:
Everytime I launch a session from the client (Win 10 laptop) to the host (Win 10 desktop), the host Steam audio drivers go back to 16bits/48KHz.
If i switch to 32bits/196KHz on the host while streaming, it works ok, no dropout, bug or whatever but if i exit the moonlight session and reconnect again, the host settings switch to the default (16bits/48KHz).
Same behavior if i kill the session & start a new one.
Same behavior from different hosts & clients, reverts back to default at launch of a session.
Steam audio drivers are up to date, tried reinstalling from GitHub, reset settings etc... same behavior.
Is it possible to lock the steam audio drivers settings completely? What exactly interacts with the driver settings? The launch command from Moonlight? A backend script from Sunshine?
Moonlight's team told me it's a sunshine issue as moonlight has no control on the host audio.
Thanks!
(I'm sorry if this is not the right section but I wasn't really sure)
Expected Behavior
Steam streaming audio drivers should keep the defined user settings.
For example:
Additional Context
_You'll tell me, what's the matter? 16bits/48KHz are ok! Maybe, but i have an audiophile setup, a dedicated & audio treated cinema room, 5.1, you can hear the difference between 32bits/196KHz & 16bits/48KHz.
And also, I can do it and have the setup for, so why not? :)_
Host Operating System
Windows
Operating System Version
Windows 10 Pro 22H2 Build 19045.4474 Feature Experience Pack 1000.19058.1000.0
Architecture
64 bit
Sunshine commit or version
0.23.1
Package
Windows - installer
GPU Type
Nvidia
GPU Model
RTX 2060 6go
GPU Driver/Mesa Version
522.44
Capture Method (Linux Only)
No response
Config
resolutions = [ 1280x720, 1920x1080, 2560x1080, 2560x1440, 3440x1440, 1920x1200, 3840x2160, 3840x1600 ] gamepad = x360 nvenc_preset = 7 fps = [60] sunshine_name = *private info* nvenc_twopass = full_res nvenc_spatial_aq = enabledApps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: