Search Issue Tracker

Fixed in 2018.2

Fixed in 2018.1

Votes

6

Found in

2017.1.0p2

Issue ID

935547

Regression

No

[Windows] Changing Default Audio Output Device does not change audio output device in Editor and Build

Audio

-

The expected behavior is that when you change Default Output Device, the sound starts to play on that device. This is how all applications line Chrome, Firefox, VLC etc. work. Also, this is default behavior on macOS.
This affects both Editor and Builds.

To reproduce this issue, at least 2 Audio Output devices are needed, for example laptop (with speaker) and external monitor (with speaker).

Steps to reproduce:
1. Open attached project (Sample.zip)
2. Enter Play mode
3. Press on Speaker icon button in the Windows bottom left
4. Select different Playback device

Expected behavior: sound starts to play via selected Playback device.
Actual behavior: sound stays playing on previously selected Playback device.

Reproduced with: 2017.2.0b5 - 5.5.2p4.

Comments (2)

  1. 60b00d4ccaa6580d10f0629635b938ad?d=mm

    ecappello

    Feb 25, 2020 06:06

    I'm having the issue as well. This expected functionality is really a must-have for VR development. I need to be able to hear audio out of a device other than my headset (in my case my speakers) when working in the editor. And then when I run the game I need the audio to come out of my headset.

    However at the moment, to change audio devices in Unity I have to:
    1) Close Unity entirely
    2) change my Windows default audio device to Rift Headphones
    3) reboot Unity
    4) load up the Project
    5) open the appropriate Scene
    5) play the Scene

    Ideally the steps would be:
    1) change my Windows default audio device to Rift Headphones
    2) play the Scene

    The current workflow wastes about 5 min every time I want to change audio devices in Unity. This is also the only application I know of with such a limitation that you need to restart it to change it's audio output device.

  2. 72a69bf4a8be68fc30a717e908bd36cb?d=mm

    JohnHacker

    Feb 05, 2020 18:35

    The fix is not working on Unity 2019.1.11f1.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.