I came across this library for a implementing a certain use-case with PyDub and was wondering if it's being actively maintained vs not.
Also, I'd like to know if there's any specific reason for wrapping around pydub.AudioSegment as opposed to subclassing it and implementing / overriding additional functionality as needed ?
Most of the dunder methods (like __getattribute__, __mul__ etc., need not be re-implemented in the child class. Also, this conforms to the Open-Closed design (open for extension, closed for modification).
I came across this library for a implementing a certain use-case with PyDub and was wondering if it's being actively maintained vs not.
Also, I'd like to know if there's any specific reason for wrapping around
pydub.AudioSegmentas opposed to subclassing it and implementing / overriding additional functionality as needed ?Most of the dunder methods (like
__getattribute__, __mul__etc., need not be re-implemented in the child class. Also, this conforms to the Open-Closed design (open for extension, closed for modification).