Initial audio delay present when using framework13 intel core series 1 with WD22TB4 Dock

Community Support
,
1

I am seeing or “hearing” an audio delay when I use my framework13 with the WD22TB4 dock. The reason I am using this dock is because I already happen to have it for my WFH dell PC (which btw doesn’t have this issue).

The issue is that when I start playing a video the audio will not be there for 2-3 seconds. Then the audio will “turn on” as if it were on the whole time. This doesn’t happen 100% time but happens pretty often.

I tried this solution but it didn’t seem to work: Solved: Re: System Sound Delay - Page 2 - HP Support Community - 6224970

Another suggestion I found on the internet but I can’t find a similar setting: ElegantWin1694 comments on Few seconds audio delay when connected through HDMI/DP

I should have the latest framework13 drives and latest dock drivers

This is on Windows 11

There are no audio delays of any kind when not using the dock

2

Any thoughts? Thanks.

3

I also tried unchecking the “make this device exclusive” (this device being my monitor) but that didn’t work as well.

4

Update unchecking “Allow the computer to turn off this device to save power” on all the Generic USB Hubs in device manager did not work

5

The issue is still occurring. At this point I am thinking of getting a new dock.

6

At this point I can confidently say that dell docks do not work with frameworks

7

I use a WD19TBS, the Thunderbolt 3 variety of the same dock albeit without an onboard audio chip (that’s what the S indicates) and have had no trouble with it on either my original 11th gen Intel or first-gen AMD laptops.

My monitor has an audio output that I plugged my speakers into and it has no startup lag when I begin playing sound. I just selected HDMI/Displayport for the audio output and it worked fine. I run Linux though, not Windows.

Have you tried a different USB audio interface? Have you updated the firmware on the dock?

8

What do you mean by this like? Like using headphones plugged into the framework?

9

This is definitely a powersaving issue. Somewhere along the line, something is being turned off to save power. I run into this myself with a non-Framework (in my case, it’s on the desktop with a USB-C IEM cable, but I only run into this when I first plug it in b/c it takes a little bit to turn on), so it’s not Framework-specific, though the Framework design might be causing issues you don’t run into with your other devices.

At this point, I don’t know enough about Windows to help you debug further, unfortunately (I use Linux exclusively on my personal devices), but I know the issue you are describing. You need to check the powersaving settings on every part of that pipeline — for some reason, the power is getting turned off at some part of the pipeline, causing your issues.