Velamniro
commented
3 months ago Correction: version 7.1.7
Open Velamniro opened 3 months ago
Velamniro
commented
3 months ago Correction: version 7.1.7
Velamniro
commented
3 months ago 
violetmage
commented
3 months ago Can you confirm that this happens to most all applications?
Also, try doing the same thing using pavucontrol, to see if the problem is specific to easyeffects
wwmm
commented
3 months ago Probably the same as #3214 and #3246. In both cases reinstalling through a different kind of package somehow fixed the issue. I wonder why... Most likely some kind of problem in a system library. Whatever it is it does not seem something that can be fixed from our side.
Velamniro
commented
3 months ago In both cases reinstalling through a different kind of package somehow fixed the issue.
Okay, I'll try it when I can (in about a week).
Velamniro
commented
3 months ago Okay, I did it with pavucontrol, I cannot increase volume with easyeffects, but I can with pavucontrol If the problem isn't in easyeffects, you can close the issue
Velamniro
commented
3 months ago But I cannot increase options in effects
wwmm
commented
3 months ago If the problem isn't in easyeffects, you can close the issue
As it does not happen on my computer it does not seem to be something broken in EasyEffects. But at the same time it is not clear why the other users were able to fix this issue just by reinstalling through a different kind of package. So either some distributions are having issues when building our package or some system library is misbehaving in the affected computers.
Bundy01
commented
3 months ago Hi,
I had the same problem with Arch when I tried to change the volume of Quodlibet.
@wwmm, I followed https://github.com/wwmm/easyeffects/issues/3214 and I can confirm that deleting ~/.local/state/wireplumber solves the problem for me.
wwmm
commented
3 months ago Hi,
I had the same problem with Arch when I tried to change the volume of Quodlibet.
@wwmm, I followed #3214 and I can confirm that deleting
~/.local/state/wireplumbersolves the problem for me.
Interesting. I did not consider that wireplumber state cache could be somehow related.
Velamniro
commented
3 months ago On version 7.1.6 everything works fine
Bundy01
commented
3 months ago I repeated the test and as soon as I set the sound to 0%, it bugs.
I made a comparison between the bugged files in Public and the correct files in .local/state:
diff Public/wireplumber/stream-properties .local/state/wireplumber/stream-properties
2,6c2,6
< Audio/Sink:application.id:com.github.wwmm.easyeffects={"channelMap":["FL", "FR"], "channelVolumes":[1.000000, 1.000000], "volume":1.000000, "mute":false}
< Audio/Sink:node.name:auto_null={"channelMap":["FL", "FR"], "channelVolumes":[1.000000, 1.000000], "volume":1.000000, "mute":false}
< Audio/Source/Virtual:application.id:com.github.wwmm.easyeffects={"channelMap":["FL", "FR"], "channelVolumes":[1.000000, 1.000000], "volume":1.000000, "mute":false}
< Output/Audio:application.name:paplay={"channelMap":["MONO"], "channelVolumes":[1.000000], "mute":false, "volume":1.000000}
< Output/Audio:media.role:Music={"mute":false, "channelMap":["FL", "FR"], "target":"easyeffects_sink", "channelVolumes":[0.000000, 0.000000], "volume":1.000000}
---
> Audio/Sink:application.id:com.github.wwmm.easyeffects={"mute":false, "channelMap":["FL", "FR"], "volume":1.000000, "channelVolumes":[1.000000, 1.000000]}
> Audio/Sink:node.name:auto_null={"channelVolumes":[1.000000, 1.000000], "channelMap":["FL", "FR"], "volume":1.000000, "mute":false}
> Audio/Source/Virtual:application.id:com.github.wwmm.easyeffects={"channelVolumes":[1.000000, 1.000000], "channelMap":["FL", "FR"], "volume":1.000000, "mute":false}
> Output/Audio:application.name:paplay={"target":"easyeffects_sink", "mute":false, "channelMap":["MONO"], "channelVolumes":[1.000000], "volume":1.000000}
> Output/Audio:media.role:Music={"target":"easyeffects_sink", "mute":false, "channelMap":["FL", "FR"], "channelVolumes":[1.000000, 1.000000], "volume":1.000000}
diff Public/wireplumber/default-routes .local/state/wireplumber/default-routes
2c2
< bluez_card.EC_81_93_EA_73_45:output:headset-output={"channelMap":["FL", "FR"], "channelVolumes":[0.024728, 0.024728], "latencyOffsetNsec":0, "mute":false}
---
> bluez_card.EC_81_93_EA_73_45:output:headset-output={"mute":false, "channelMap":["FL", "FR"], "latencyOffsetNsec":0, "channelVolumes":[0.024728, 0.024728]}
Maybe you should consider deleting the % volume option until you fix the problem?
wwmm
commented
3 months ago Maybe you should consider deleting the % volume option until you fix the problem?
The problem with this approach is that this bug does not happen on my computers and probably it also does not happen on the computers of many other users. Otherwise some of the users that regularly come here would also have reported this bug. This volume issue is probably coming from something different in the system libraries of the affected computers. The question is what.
mickol-schiz
commented
1 month ago issue still persists running easyeffects 7.1.8-2 on kernel 6.9.2-arch Tried:
wwmm
commented
1 month ago issue still persists running easyeffects 7.1.8-2 on kernel 6.9.2-arch Tried:
* the aur package, the easyeffects-git package (that one ran on 7.1.9), and the flatpak all 3 faced the same issue, but the middle one also had core dumping issues which i resolved (missing dependency for the delay plugin) * deleting .local/state/wireplumber * using pavu; that worked "flawlessly" (my default audio output is bugged as of the last 2 weeks) * rebooting and/or reseting pipewire services
At least here on Arch Linux I still can't reproduce this issue. Which gtk4 version do you have installed @mickol-schiz ?
mickol-schiz
commented
1 month ago Running 1:4.16.3-1
wwmm
commented
1 month ago Running 1:4.16.3-1
Exactly the same I have. Are you also using Arch Linux?
mickol-schiz
commented
1 month ago EndeavourOS to be particular, as mentioned running the 6.9.2 kernel gtk demos run just fune
wwmm
commented
1 month ago EndeavourOS to be particular, as mentioned running the 6.9.2 kernel gtk demos run just fune
Does the one from libadwaita-demos also runs fine?
My kernel is 6.11.3. But I do not see how the kernel could be involved in this. Either something changed in gtk4/libadwaita and we have to adjust accordingly, something like this happened in the past, or there is a bug in these libraries.
Do you see any warning or error message when EasyEffects is executed in debug mode? https://github.com/wwmm/easyeffects/wiki/Reporting-Bugs#basic-logs
mickol-schiz
commented
1 month ago yes adwaita is also working as expected Nothing suspicious; the gtk warning is just an IME
wwmm
commented
1 month ago yes adwaita is also working as expected Nothing suspicious; the gtk warning is just an IME
Yes, the logs seem fine. I wonder what is going on. The last time something changed in gtk4 and some controls stopped working when a value was typed I was able to reproduce the issue. But now I can't. Typing works as well as using the up/down buttons or the mouse wheel.
mickol-schiz
commented
1 month ago Probably should have mentioned that but typing doesn't really work in the input box - the second I click enter it autogically goes back to 0% as if I left the screen boundry. The + button only allows me to go up to 1%, unless I hold it.
wwmm
commented
1 month ago Probably should have mentioned that but typing doesn't really work in the input box - the second I click enter it autogically goes back to 0% as if I left the screen boundry. The + button only allows me to go up to 1%, unless I hold it.
Does it work on the other input boxes? For example the ones in the limiter or the bass enchancer.
mickol-schiz
commented
1 month ago yes, everything else works as intended. At this point I'm starting to consider whether some random thing is misconfigured in pipewire that somehow only affects easyeffects
wwmm
commented
1 month ago yes, everything else works as intended. At this point I'm starting to consider whether some random thing is misconfigured in pipewire that somehow only affects easyeffects
If only the streams volume control is affected then some kind of bad interaction with PipeWire or WirePlumber is happening. The fact that the issue was fixed for some users after they deleted wireplumber's state folder always felt strange to me.
As a reference for the future this is the code we use to set volumes https://github.com/wwmm/easyeffects/blob/2ef8d2c976fa437bacf3f9046497a28d0d70367a/src/pipe_manager.cpp#L1777. I wonder if wireplumber is expecting something different there. But in this case this control should be broken for everybody...
EasyEffects Version
7.17
What package are you using?
Fedora
Distribution
Fedora 40
Describe the bug
I have set the volume to 0 for discord and cannot increase it. When I try to increase the volume and then click the mouse elsewhere in the program or press enter, the volume is reset to zero.
Expected Behavior
Expectation: I have successfully set the volume to 100% for discord.
Debug Log
Debug Log
``` Paste your log here ```
Additional Information
No response