Description of problem: Running an application relying on openal-soft, I was unable to move audio streams to the desired playback device. After finding openal-soft-qt I was able to figure that by default this option is disabled. Version-Release number of selected component (if applicable): openal-soft-1.18.0-3.fc27.x86_64 openal-soft-qt-1.18.0-3.fc27.x86_64 How reproducible: Haven't tried to reproduce, I never touched openal configuration before. Steps to Reproduce: 1. run alsoft-config 2. open "Backends" tab 3. select "PulseAudio" Actual results: The option "Allow Moving Streams" is disabled. Expected results: The option "Allow Moving Streams" should be enabled, PulseAudio being default on Fedora, and seeing no particular reason to prevent users from customizing playback. Additional info: After discovering this via the GUI, I noticed in /etc/openal/alsoft.conf that allow-moves defaults to false :)
Thank you for the report, I'm currently preparing an update for Fedora 27 and later fixing this.
openal-soft-1.18.2-5.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-91006aeaa5
openal-soft-1.18.2-5.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-91006aeaa5
Thank you for the update. Since I made local modifications to allow myself to move streams, I'd like to revert them to try the update. I didn't find where in my home directory those settings were saved. Just in case it's supposed to land in gsettings or dsettings or something depending on my DE, I'm using the Xfce spin.
I just realized I was looking for openal instead of alsoft... I found it in ~/.config/alsoft.conf right after sending the previous comment.
openal-soft-1.18.2-5.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.