Open Laserology opened 4 hours ago
When using auto-applying presets for specific outputs, the program does not account for if the system is playing via the built-in speakers, or the headphone jack(s). This should be fixes as i have to open easyeffects and disable it every time my laptop gets slotted into it's dock, as this routes audio via the line out port.
Did you try to create independent autoloading profiles for both cases? This is not going to be handled automatically. If you want a different preset for the headphone an autoload profile has to be created for it. And if you want no effects for the headphone create preset file with no plugins and associate an autoloading profile to it.
When using auto-applying presets for specific outputs, the program does not account for if the system is playing via the built-in speakers, or the headphone jack(s). This should be fixes as i have to open easyeffects and disable it every time my laptop gets slotted into it's dock, as this routes audio via the line out port.
Did you try to create independent autoloading profiles for both cases? This is not going to be handled automatically. If you want a different preset for the headphone an autoload profile has to be created for it. And if you want no effects for the headphone create preset file with no plugins and associate an autoloading profile to it.
yes i have. It does not distinguish between headphone port and device speakers. When attempting to make separate profiles, it has the same device name for the profile
When attempting to make separate profiles, it has the same device name for the profile
I see. In many cases the driver/pipewire generates a different routing (hardware profile in Pavucontrol) and keeps the same device name when a headphone is plugged. In EasyEffects list this information is saved in a field named Profile
. Does it change when a headphone is plugged and a new autoloading is created?
For example this is the profile I've created for my bluetooth headphone Depending on how the bluetooth device is configured the "Profile" field changes.
And as usual getting seeing what is being printed in the logs when the headphone is plugged and then unplugged also helps https://github.com/wwmm/easyeffects/wiki/Reporting-Bugs#basic-logs.
When attempting to make separate profiles, it has the same device name for the profile
I see. In many cases the driver/pipewire generates a different routing (hardware profile in Pavucontrol) and keeps the same device name when a headphone is plugged. In EasyEffects list this information is saved in a field named
Profile
. Does it change when a headphone is plugged and a new autoloading is created?For example this is the profile I've created for my bluetooth headphone Depending on how the bluetooth device is configured the "Profile" field changes.
No, it stays the same. "Built-in audio analog stereo". However, the system (kde plasma) does recognize when a headphone is plugged in, and displays a different name. For me, bluetooth does indeed change, just not with a physical audio device using the audio jack.
As for logging, i had not included it because the issue template did not seem to say it was necessary for bugs like this. Either way, here are some logs:
pw-dump: Too long to post
I can see for myself in the logs that it changes some name to "analog-output-headphones", but that name isn't utilized anywhere in the program. Checking for this property when loading presets would probably fix this issue.
EasyEffects Version
7.1.9
What package are you using?
Flatpak (Flathub)
Distribution
Fedora
Describe the bug
When using auto-applying presets for specific outputs, the program does not account for if the system is playing via the built-in speakers, or the headphone jack(s). This should be fixes as i have to open easyeffects and disable it every time my laptop gets slotted into it's dock, as this routes audio via the line out port.
Expected Behavior
Application should detect if the headphone jack is being used, and apply a different preset for it instead of the default "main" preset used for built in speakers.
Debug Log
No response
Additional Information
No response