-
Notifications
You must be signed in to change notification settings - Fork 661
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
torchaudio.compliance.kaldi.spectrogram is very different from torchaudio.transforms.spectrogram #157
Comments
Code to generate the two figures below. Sound file here.
|
The error appears unrelated to multiple channels, since I get similar results with
Note also that I had to pass the tensor with shape |
The main issue is that the result from kaldi looks like noise, and the fact that the train pattern is not visible in the spectrogram is unexpected. |
Try smaller inputs, zeros, ones, arange, etc. ; but in general we want to standardize on kaldi and whatever they produce is what we produce. |
@vincentqb I could investigate the flags more kaldi.spectrogram to get a more closer result but is this more similar to what you would expect?
|
Great, that's good enough. Thanks! |
@vincentqb |
The file can still be accessed here. |
For reference, this is enough to produce reasonable spectrogram.
EDIT: no log needed here. |
Does
torchaudio.compliance.kaldi.spectrogram
only currently support vectors?When feeding a tensor of shape
torch.Size([2, 276858])
the result is not what's expected, yet there is no error. I would expect a "train pattern" to be visible, as in the second figure below.This is what kaldi gives
This is what
torchaudio.transforms.spectrogram
givesThe "train pattern" is also visible on academo.org.
The text was updated successfully, but these errors were encountered: