On 2015/10/16 11:29, Aleksander Trofimowicz <[email protected]> wrote: > My aim is to create facilities for a basic filter management: list all > available filters (or filter sets) and select the current one. I think > it makes sense to include these to MPD protocol as digital filters > affect how sound is perceived by users no less than volume levels > (which are handled by MPD protocol already). And such extensions will > enable music players to simplify user experience.
MPD has an infrastructure to write filter plugins, and these can be configured in mpd.conf. However, the filter plugins you're thinking of don't exist in MPD currently. If I understand you correctly, what you're about to propose is NOT writing new filter plugins, but provide a protocol interface to configure/select filter plugins at runtime? I can't comprehend that proposal. Your reason for this dynamic filter interface is that you wish to have those digital filters, but your proposal will NOT make those filters available in MPD. All it does is make existing filters dynamic at runtime. There is a mismatch between your proposal and your stated reason. If you want those filters, write filter plugins. I understood that you want those filters, even though I never felt I need them. That's ok - write a plugin, send it to me, and I'll merge it. What you did NOT say is why you want to make them available on the MPD protocol. Which, however, is the only thing you were going to implement. Max _______________________________________________ mpd-devel mailing list [email protected] http://mailman.blarg.de/listinfo/mpd-devel
