Failed to Initialize IAudioClient
Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number R9 390
Enter RAM memory size in GB 32
What is your gamertag/PSN ID/EA Account name? epilepticfairy
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible.
Which Legend were you playing (if applicable)?
Which Legends were your squad mates using (if applicable)?
Where did the issue occur? In the lobby (waiting area before the match)
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. Occurs just after initial load modal before the game goes full screen.
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. Loading the game.
Did your squad mates also experience the issue? I don't know
How many matches had you played in a row before the issue occurred? 0
When did this happen? (dd.mm.yy hh:mm) 24.03.19 11:00
How often does the bug occur? Often (50% - 99%)
How severe is your issue? Minor impact to gameplay
What happens when the bug occurs? The game does not load. Following error appears: Couldn't Initialize Sound. Please make sure you have a sound playback device that is enabled and properly configured. Failed in: MilesDriverCreate Miles output follows: Audio Hardware Error: Failed to initialize IAudioClient (shared, event mode, float, chans=2, rate=96000, HR=AUDCLNT_E_DEVICE_IN_USE) Failed to initialized WASAPI audio hardware, trying XAudio. Couldn't create XAudio2 master voice.
What should be happening instead? Game loads.
Steps: How can we find the bug ourselves? It seems that the MilesDriver component in the Apex engine is struggling to bind to any audio device set over a sample rate of 44100hz.
I found that this bug was also reported for TitanFall 2 for a different audio device (mine is a HyperX Cloud Revolver Pro USB headset). It looks like both games are using the same function to bind to WASAPI. Sticking plaster fix is to lower the sound quality of my device in Windows but it would be preferable if the game could bind at higher sample rates.
Hi Blueberry. Thanks, but I really pinched it from some people who had the same problem with Titanfall.
The main downside with the solution is that USB headsets can reset to defaults when they are plugged in or when drivers are updated. For my headset, this defaults to a sample rate which is not supported by IAudioClient. This means you have to go back through preferences and change the setting every time you plug the headphones in, which for me, with a KVM switch for other machines, is quite often.
