You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like the transform chaining for complex effects; it's a really smart way of optimizing how sox is controlled. However, I don't like how verbose it is for simple one-off operations.
added benefit, any future changes to the Transformer base class / interface would be hidden, insulating users / code upstream... because change is inevitable.
@ejhumphrey good idea. I've been thinking about creating a utils or cookbook module for a while now for this kind of thing. The challenge is in deciding which simple operations are common enough to get a standalone function. convert seems like a reasonable one, but what else? Maybe more "complex" things like crossfade that are clunky to do as is?
so here's a idea for discussion...
I like the transform chaining for complex effects; it's a really smart way of optimizing how sox is controlled. However, I don't like how verbose it is for simple one-off operations.
For example, to convert a file currently:
For simple operations, this doesn't feel very pythonic. I'd be curious how folks feel about abstracting this away for trivial / common pipelines:
This could also roll-up try-catch logic, if one were so inclined (e.g.
strict=False
could return a non-zero status, etc).thoughts?
The text was updated successfully, but these errors were encountered: