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
Hello. I'm using the google colab version. I was able to run with the default input output files provided. I then tried to use my own files and the input file is read correctly, but then I get the following:
The tensorboard extension is already loaded. To reload it, use:
%reload_ext tensorboard
Metadata will be skipped
Reusing TensorBoard on port 6006 (pid 936), started 0:16:07 ago. (Use '!kill 936' to kill it.)
Checking that we have all of the required audio files...
Found input.wav, version 3.0.0
No response activated the trigger in response to input spikes. Is something wrong with the reamp?
SHARE THIS PLOT IF YOU ASK FOR HELP
So, I checked the file format is indeed with 48kHz and 24 bit mono, for both the input and output files. Any ideas?
The text was updated successfully, but these errors were encountered:
The Colab shouldn't let you use your own files like this. This part of what you shared (thanks!):
Found input.wav, version 3.0.0
Shouldn't have happened. Instead, it should have thrown an exception and said that the input file you provided couldn't be recognized as any of the standardized inputs.
I'll look into it and we should be able to improve the input validation on Colab, but in the meantime if you want to do this you'll want to use the full trainer locally ("nam-full").
sdatkinson
changed the title
No response activated the trigger in response to input spikes
[BUG] [Colab] Non-standard input file isn't detected correctly
Dec 19, 2024
Hello. I'm using the google colab version. I was able to run with the default input output files provided. I then tried to use my own files and the input file is read correctly, but then I get the following:
So, I checked the file format is indeed with 48kHz and 24 bit mono, for both the input and output files. Any ideas?
The text was updated successfully, but these errors were encountered: