Closed justinsalamon closed 7 years ago
This would be pretty easy to do if we just tweak PitchShift
to accept a float-or-array
instead of a single float. Should be a minor hack, if you want to take a crack at it.
Cool, I'll try and squeeze in a PR sometime before the end of this week
Check background for an example of this kind of logic. All you need to do is then make this part iterate over the list of pitch values, instead of yielding a single value.
Cool, I'll try and squeeze in a PR sometime before the end of this week
Actually, I wound up on a spree of muda hacking last night, so I don't mind taking this one over today.
The
PitchShift
deformer only takes a single semitone parameter (n_semitones
), which makes it a little awkward to work with when you want to perform multiple pitch shifts.LinearPitchShift
can perform multiple shifts, but they have to be linearly spaced, which might not be the desired functionality (e.g. I may wantn_semitones = [ -2, -1, 1, 2]
).It would be nice if
PitchShift
would accept (in addition to a single value) a list for then_semitones
parameter, in which case it would generate an output audio/jams for every pitch shift value in the list (timesn_samples
). This would make the behavior more consistent with other deformers (e.g.DynamicRangeCompression
), and would allow (what I'm really after) writing more generic code that can apply a deformer agnostically of which deformer it actually is because the deformer is fully defined during initialization.