Wellington Wallace

>Below is information about the autostart file that was generated when I natively installed Easyeffects on the Raspberry pi5. As expected the desktop file is fine. The issue is the...

> Yes, after analyzing this code it is clear that it doesn't work as I expected. This is the current situation of it. > It would be nice if I...

So much has changed that is probably better to close this issue

>Input volume/preamp on equalizer doesn't correctly apply to equalizer gain values, resulting in clipping when positive gain values are applied in the equalizer regardless of negative input gain. Please show...

>Negative gain on input volume should allow for positive gain in equalizer offsets without introducing artifacts. And they do if the appropriate value is chosen. Like I said before it...

>Lowering input by 20 and increasing gain on a bell curve by 7 results in the same clipping as lowering input by 0 and increasing gain on a bell curve...

> The overall levels are fine, the issue is that positive gain on the equalizer produces the artifacts of clipping, as though the input is clipping the output post-equalization, resulting...

>While the former, i'm guessing is because there is no target.object for the Google Chrome node, the latter seems like a bug? Clients are not forced to set a target...

> it seems like there's really no way to actually achieve the desired result of only intercepting things that are known to go to the specific output Unfortunately I am...

>where should_ignore_streams_with_unknown_output_devices is the boolean from the new config option. I do not see how this is going to work. The variable `pm->output_device.name` is the device EasyEffects should be outputting...