Search Issue Tracker
Fixed
Fixed in 2021.3.38f1, 2022.3.27f1, 2023.2.20f1, 6000.0.0b12, 7000.0.0a1
Votes
33
Found in
2021.3.31f1
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a8
Issue ID
UUM-53143
Regression
Yes
[Linux] No audio output when playing audio
Reproduction steps:
1. Create a new project
2. Move the “TestBugNoAudio” file to the Assets directory
3. In the Project window, select “TestbugNoAudio”
Expected result: Audio is played
Actual result: No audio is played
Reproducible with: 2021.3.31f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b11, 2023.2.0b12, 2023.3.0a8
Not reproducible with: 2021.3.30f1, 2023.2.0b10
Reproducible on: Ubuntu 23.04
Not reproducible on: Windows 10 Pro 22H2, Ubuntu 22.04
Notes:
* Audio is not played anywhere (Player builds, Play Mode, Inspector)
* Does not reproduce for everyone
-
Snorris108
Oct 24, 2024 00:46
What is the fix for this issue? I’ve connected my Steam Deck to my LG G3 tv (HDMI ARC audio) via Valve Dock, and the audio comes from the Deck directly, not HDMI. Seems this is not fixed.
-
NorthernBorn
Jul 17, 2024 08:16
I was also having this issue after removing pulse, jack, and alsa. I replaced them with [wireplumber, pipewire, pipewire-jack, pipewire-alsa, pipewire-pulse]. This had all the audio on my system working extremely well but then Unity stopped working.
Basically what happens in this case is Unity spawns it's playback node called 'FMOD Ex App' and then routes it into the most generic output nodes it can find like: Realtek Audio, Starship/Matisse, and of course NVIDIA HDMI. I use an audio interface on my computer so that's the node I actually want to receive the audio.
This exact solution only works with package configuration that I mentioned but unused devices/nodes should work no matter what in cases like this
My solution was to either get the Unity playback node to target my audio interface or to remove all nodes that I would never want to route audio to. I made a wireplumber.conf file located at '~/.config/wireplumber/wireplumber.conf.d/51-disable-nodes.conf'. I then added the devices that I didn't want to it like so:
```
monitor.alsa.rules = [
{
matches = [
{
node.name = "alsa_output.pci-0000_0a_00.1.hdmi-stereo"
}
]
actions = {
update-props = {
node.disabled = true
}
}
}
{
matches = [
{
node.name = "alsa_output.pci-0000_0c_00.4.iec958-stereo"
}
]
actions = {
update-props = {
node.disabled = true
}
}
}
]
```If you are struggling to find devices you can use `coppwr` to get a graph where you can see audio connections being made as well as all the node properties. You can also just use `pw-cli info all` to get a print out of everything. You can also route that to a .log file with `pw-cli info all > devices.log 2>&1`
After making changes be sure to restart wireplumber daemon
-
Esteban_Noxfall
May 09, 2024 15:38
So this issue was fixed in 2022.3.27f1 (I was able to test it) and now is listed again as a known issue in 2022.3.28f1?
-
LaserJaguar
Mar 26, 2024 14:07
Seems like this issue is because in some Linux systems default sound device is HDMI audio, which may exists on GPU but not on the display.
So as a workaround you can disable it (in BIOS, or in your Linux). Type something like this in terminal:
pacmd list-cards
remember name of top-most card in that list (Without symbols < > ). Most likely it will be something like alsa_card_pci_manyNumbers. Should contain description how it is indeed HDMI. Then type:
pacmd set-card-profile YourHDMICardName off
Reboot.
Enjoy.
-----
Or you can disable it in some audio controlling software or in some BIOS, but use it only if you are certain you don't need HDMI audio at all. -
rmd41m
Mar 22, 2024 08:07
manjaro 2022.3.22f1, 2022.3.14f1. same problem
-
love_wessman
Jan 10, 2024 11:00
Can confirm that this is still an issue in 2022.3.16f, running a player built for linux, on Ubuntu 22.04. Switching from one audio output device and back "fixes" the issue, but only for the duration of the apps runtime.
-
unity_C4B0EE9C22CBCD6B06ED
Dec 30, 2023 20:24
Having the same issue on ubuntu 23.10, unity version 2022.3.14f1
-
Irina-uk
Dec 12, 2023 16:59
I wrote on the fmod forum about this problem, the administrator replied that the unity editor uses an old version of this mod to output sound. By the way, this problem with the ports was also on their forum with fmod, the sound was also sent to port 0, but the active port of the sound speakers is different. They somehow solved it, but they couldn't help me with the unity audio engine. Thank you for your work.
-
JulianNeil
Dec 09, 2023 09:50
As a possible workaround, I managed to get audio working again after updating to a version that had no audio. See https://forum.unity.com/threads/audio-in-unity-2022-3-14f1-lts-linux-not-working.1521397/#post-9519508
-
JulianNeil
Dec 09, 2023 07:27
@IRINA-UK which logs are you looking at?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
Resolution Note (fix version 6000.0.0b12):
In our Linux Pulse audio driver, make sure to select the correct default output device. Previously, on some systems and some versions of Linux, we could end up with no audio output or audio output being routed to an unexpected device.