STEAM GROUP
Steam Remote Play homestream
Join Group
STEAM GROUP
Steam Remote Play homestream
147,427
MEMBERS
3,899
IN-GAME
39,327
ONLINE
Founded
November 7, 2013
Overview Announcements Discussions Events Members Comments
TC2 Aug 26, 2019 @ 5:52am
Stuttering/Cracking Audio on RPI 3B+ Streaming from Windows 10
Hi,

Thank you for your help.

I've been using SteamLink on my RPI3B+ (Stretch) for months quite happily, until recently when the audio has started to constantly stutter/crackle and make the whole experience awful (a shame as the video is still fine).

The only thing I can see in logs is the following, and happens when audio is transmitted (the following block, longer than quoted, appears even when I am just moving between tiles on Steam Big Picture home screen):
[2019-08-26 13:22:55] CLIENT: Flushing audio, 70 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:55] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:55] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:55] CLIENT: Flushing audio, 70 ms queued, 50 ms maximum, delivery delay = 0

This leads me to believe there's some audio transmission issue, but I'm not sure what. I have tried changing host resolution and turning on/off host hardware encoding but so far nothing has changed. I have also ensured I have sound output settings on the Windows host at 24bit, 48000Hz (default), and I've changed no sound options on the PI yet (other than forcing output through HDMI, which is where I need it outputting).

I'm wondering if the wider community has any other suggestions on how to try to fix the issue? I have an actual Steam Link else where in my home and that works fine (both audio and video), so believe it to be host -> pi, or the PI itself.

I'll post a full streaming_log.txt in a follow-up comment as it's quite long. Thank you for reading.
The author of this topic has marked a post as the answer to their question.
Click here to jump to that post.
Originally posted by naimen:
Finally I figure out the problem, it's in the driver configuration of the pulse audio on the pi.

This fix did the trick
https://steamcommunity.com/app/353380/discussions/6/1642042464753800526/
< >
Showing 1-7 of 7 comments
TC2 Aug 26, 2019 @ 5:54am 
[2019-08-26 13:22:51] Initializing audio with 2 channels and 48000 samples/sec [2019-08-26 13:22:51] Audio mix: start=3888064940, returned=0 [2019-08-26 13:22:51] Audio source [System Windows]: init=0, through=0, last_start=0, mixed=0, drop_before=0, drop_after=0 [2019-08-26 13:22:51] Changing record window: 00080448 [2019-08-26 13:22:51] CLIENT: Got control packet k_EStreamControlSetQoS [2019-08-26 13:22:51] CLIENT: Got control packet k_EStreamControlSetTargetBitrate [2019-08-26 13:22:51] CLIENT: Starting audio stream: frequency=48000, channels=2 [2019-08-26 13:22:51] CLIENT: Opened audio device: format=2, channels=2, frequency=48000 [2019-08-26 13:22:51] CLIENT: Initialized audio decoder: codec=3, sample rate=48000, channels=2 [2019-08-26 13:22:51] CLIENT: Got control packet k_EStreamControlStartAudioData [2019-08-26 13:22:51] Recording system audio [2019-08-26 13:22:51] >>> Switching video stream from NONE to Desktop_MovieStream [2019-08-26 13:22:51] Recording on device: Speakers (Steam Streaming Speakers) [2019-08-26 13:22:51] Audio client mix format: [2019-08-26 13:22:51] format: 65534 [2019-08-26 13:22:51] channels: 2 [2019-08-26 13:22:51] samples/sec: 48000 [2019-08-26 13:22:51] bytes/sec: 384000 [2019-08-26 13:22:51] alignment: 8 [2019-08-26 13:22:51] bits/sample: 32 [2019-08-26 13:22:51] channel mask: 0x3 [2019-08-26 13:22:51] data format: {00000003-0000-0010-8000-00AA00389B71} [2019-08-26 13:22:51] Initializing audio with 2 channels and 48000 samples/sec [2019-08-26 13:22:51] CLIENT: Got control packet k_EStreamControlSetSpectatorMode [2019-08-26 13:22:51] CLIENT: Got control packet k_EStreamControlSetCaptureSize [2019-08-26 13:22:51] CLIENT: Got control packet k_EStreamControlSetTitle [2019-08-26 13:22:51] CLIENT: Got control packet k_EStreamControlSetIcon [2019-08-26 13:22:51] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:51] CLIENT: Got control packet k_EStreamControlHideCursor [2019-08-26 13:22:51] CDesktopCaptureDWM: Reinitializing D3D for adapter 0xc9d3 [2019-08-26 13:22:51] Video adapter: NVIDIA GeForce RTX 2060, vendor ID: 0x10de, device ID: 0x1f08 [2019-08-26 13:22:51] CDesktopCaptureDWM: desktop duplication enabled [2019-08-26 13:22:51] >>> Capture method set to Steam D3D10 NV12 + NVENC H264 [2019-08-26 13:22:51] >>> Capture resolution set to 1280x720 [2019-08-26 13:22:51] >>> Client video decoder set to Raspberry Pi hardware decoding [2019-08-26 13:22:51] CLIENT: Sending HID device 28de/1142/0 Valve Software Steam Controller at /dev/hidraw0 [2019-08-26 13:22:51] CLIENT: Sending HID device 28de/1142/1 Valve Software Steam Controller at /dev/hidraw1 [2019-08-26 13:22:51] CLIENT: Sending HID device 28de/1142/2 Valve Software Steam Controller at /dev/hidraw2 [2019-08-26 13:22:51] CLIENT: Sending HID device 28de/1142/3 Valve Software Steam Controller at /dev/hidraw3 [2019-08-26 13:22:51] CLIENT: Sending HID device 28de/1142/4 Valve Software Steam Controller at /dev/hidraw4 [2019-08-26 13:22:51] CLIENT: Video size: 1280x720, output size: 1824x984 [2019-08-26 13:22:51] CLIENT: Video rect: 1750x984 at 37,0 [2019-08-26 13:22:51] CLIENT: Texture rect: 1280x720 at 0,0 [2019-08-26 13:22:51] CLIENT: Raspberry Pi hardware decoding [2019-08-26 13:22:51] CLIENT: Got control packet k_EStreamControlStartVideoData [2019-08-26 13:22:51] CLIENT: Got control packet k_EStreamControlVideoEncoderInfo [2019-08-26 13:22:51] CLIENT: Marking frame 0 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:51] CLIENT: Video size: 1280x720, output size: 1824x984 [2019-08-26 13:22:51] CLIENT: Video rect: 1750x984 at 37,0 [2019-08-26 13:22:51] CLIENT: Texture rect: 1280x720 at 0,0 [2019-08-26 13:22:51] CLIENT: Marking frame 2 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:51] CLIENT: Marking frame 3 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:51] CLIENT: Marking frame 4 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:52] Setting target bitrate to 5000 Kbit/s, burst bitrate is 25000 Kbit/s [2019-08-26 13:22:52] CLIENT: Got control packet k_EStreamControlSetTargetBitrate [2019-08-26 13:22:52] CLIENT: Flushing audio, 1380 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:53] CLIENT: Marking frame 67 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:53] CLIENT: Marking frame 69 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:53] CLIENT: Marking frame 71 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:53] CLIENT: Flushing audio, 80 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:53] CLIENT: Marking frame 73 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:53] CLIENT: Marking frame 74 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:53] CLIENT: Marking frame 76 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:53] CLIENT: Marking frame 77 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:53] CLIENT: Flushing audio, 80 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:53] CLIENT: Marking frame 82 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:53] CLIENT: Marking frame 83 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:53] CLIENT: Marking frame 84 complete with status k_EStreamFrameResultDroppedLate [2019-08-26 13:22:53] CLIENT: Flushing audio, 80 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:53] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:53] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:53] CLIENT: Flushing audio, 80 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:53] CLIENT: Flushing audio, 70 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:53] CLIENT: Flushing audio, 70 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:54] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:54] CLIENT: Flushing audio, 70 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:54] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:54] CLIENT: Flushing audio, 90 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:54] CLIENT: Flushing audio, 70 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:54] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:54] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:55] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:55] CLIENT: Flushing audio, 70 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:55] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:55] CLIENT: Flushing audio, 70 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:55] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:55] CLIENT: Flushing audio, 60 ms queued, 50 ms maximum, delivery delay = 0 [2019-08-26 13:22:55] CLIENT: Flushing audio, 70 ms queued, 50 ms maximum, delivery delay = 0
#1
naimen Aug 30, 2019 @ 7:42am 
I'm also have the same problem after have updated windows to 1903 yesterday

The sound configuration on Pi is able to play stream music though VLC without problem.

I have reinstalled the steam sound driver on my windows, but it didn't help at all.

Have you figured anything out?
#2
TC2 Aug 31, 2019 @ 3:02pm 
Hmm, interesting note about Windows - I'm on 1903 but can't remember when I upgraded! I'll got a laptop still on 1807 (or whatever the previous one is) - I'll try that during the week and see how it works.
#3
naimen Sep 7, 2019 @ 1:26am 
So after some digging around, there's some weird ♥♥♥♥ going on.
I have uninstalled the drivers, restarted and then get into remote play to see what would happen.
Then I realized the suttering and booming sound is actually getting tough to the PI, even tho the sound drivers ain't listed in device manager.

So i suspect that the 1903 update did some black magic to the drivers.
#4
TC2 Sep 7, 2019 @ 7:17am 
As an update from my end, it might be a little more generic for Windows, as I've just tried with a machine on 1809 and the experience is exactly the same. :steamsad:

The Steam Link I have works perfectly with both, not sure why Windows would output differently between a real Steam Link and the SteamLink app for pi...

I've also just tried my 1903 Windows machine with the SteamLink app on my phone on a 5GHz network, and it worked perfectly!

So Windows 10 (version seemingly irrelevant) + Pi + SteamLink is not a happy mixture.
#5
The author of this thread has indicated that this post answers the original topic.
naimen Sep 11, 2019 @ 10:02am 
Finally I figure out the problem, it's in the driver configuration of the pulse audio on the pi.

This fix did the trick
https://steamcommunity.com/app/353380/discussions/6/1642042464753800526/
#6
TC2 Sep 11, 2019 @ 12:18pm 
Awesome, cheers for the pointer, I'll give this a go!
#7
< >
Showing 1-7 of 7 comments
Per page: 1530 50

All Discussions > General Discussion > Topic Details
Date Posted: Aug 26, 2019 @ 5:52am
Posts: 7
Start a New Discussion

Discussions Rules and Guidelines