register_pydub_effect design about pydub HOT 3 CLOSED

The decorator just provides an official interface for adding processing methods to the AudioSegment object.

Eventually it could be the entry-point for a plugin system

Assigning the functions directly onto the AudioSegment object would get the same effect, but providing an official interface protects us from future problems (like if we rename or move the AudioSegment class, or if we want to make performance tweaks, it's hard to think of everything ahead of time).

from pydub.

It also allows us to break the code into multiple files based on functionality instead of having one giant class.

you could also just provide functions, but personally I like to use libraries that just have one main object you need to know about and then you can just use autocomplete to find the methods (like requests)

from pydub.

Ah I see now,
I work on a project that handles a plugin architecture. Using packages and some init magic.
For example, if pydub used this architecture, to add a new "plugin" you have to drop a class/function somewhere into the package directory(say: "pydub/effects") a convention name like NormalizeEffect().

Anyway. So to add a new effect we just have to write the effect function in the effects module and apply the decorator, isn't it?

Thank you.

from pydub.