My plan is to keep LoadWithTorchaudio in the klay_beam package, so that any jobs that benefit from audio in torch.Tensors don't have to re-implement it. This will also make it easier to migrate existing jobs to klay_beam 1.0, because they won't have to all switch to LoadWithLibrosa simultaneously.
There will be breaking name changes to other methods that depend on torchaudio. klay_beam methods that depends on torchaudio should indicate this with thier function name (ex ResampleWithTorchaudio)
Closes #31
My plan is to keep LoadWithTorchaudio in the
klay_beam
package, so that any jobs that benefit from audio in torch.Tensors don't have to re-implement it. This will also make it easier to migrate existing jobs to klay_beam 1.0, because they won't have to all switch toLoadWithLibrosa
simultaneously.There will be breaking name changes to other methods that depend on
torchaudio
.klay_beam
methods that depends ontorchaudio
should indicate this with thier function name (exResampleWithTorchaudio
)