-
-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KDE changing setting in pavucontrol required for audio output #104
Comments
Hi, could you perform the test below with PulseEffcts closed? close PulseEffects and run: Put this code in a file test.py and run it(execute in a terminal
While the program is running open pavucontrol and see if it is recording from To unload the null sink created for the test run |
The reason why I ask this test can be seen in this issue #1. It is not the first time this problem happens and I never understood why it happens only to a few people. What is happening is that for some reason gstreamer is not obeying the I never had this issue in any of my machines but I use gnome in all of them. So it could be desktop related. The correct devices are hard coded in PulseEffects. We just have to find out why in some installations gstreamer is ignoring these settings. Maybe there is some kind of global setting or application telling it to do otherwise |
The entries with One of them must record from Other entries with |
Now this is strange after running the commands above and after unloading with pacmd unload-module... Starting PulseEffects now works correctly without changing any setting. Need to test that again after reboot. EDIT: yes works even after reboot. So maybe after installing PulseEffects a reboot is required? Or after changing pavucontrol settings once a reboot is required to make it work automatically? Or can it be that the commands from above changed something and now it works? |
What happened in your machine is not the same that happened to other people. Otherwise the test code would not have worked. But I don't know why you faced this problem. There is no reason to reboot the system after installing PulseEffects. I did not have to do this in any of my non development machines. It should not be needed to restart Pulseaudio too. Pulseaudio tries to remember the input and output devices set in Pavucontrol. So it is possible that it is working because it remembers the right device. if |
result of Without PulseEffects running
With PulseEffects running and active
No idea what to look at, I hope this is somehow useful, but since it is working fine now I can't reproduce the state that led to the issue. |
It is ok. I see nothing that would give a hint to the cause of the problem. For now I will close this issue. Feel free to reopen it if the problem returns. |
Hi, this is not really a bug report but I think it should be specified somewhere that on KDE (tested on Arch Linux and Manjaro KDE) pulseeffects requires manual intervention through the pavucontrol application to get audio output working. This is required on each start of pulseeffects and is not preserved after exit.
Steps required to get audio working:
open pavucontrol, change to "Recording" tab, this is how it looks without pulseeffects running
start pulseeffects, now pavucontrol looks like this:
in pavucontrol change the second entry (first one doesn't work) of "Pulseeffetcs: record stream from" setting to "Monitor of pulseffects(app)"
Maybe there's a way to apply that setting automatically on pulseeffects start?
And it's a bit odd, that there are two identical entries for "record stream from..." but only the second one works.
The text was updated successfully, but these errors were encountered: