Skip to content
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

[BUG] [Colab] Non-standard input file isn't detected correctly #503

Open
Rkiefe opened this issue Nov 4, 2024 · 3 comments
Open

[BUG] [Colab] Non-standard input file isn't detected correctly #503

Rkiefe opened this issue Nov 4, 2024 · 3 comments
Labels
bug Something isn't working priority:low Low-priority issues

Comments

@Rkiefe
Copy link

Rkiefe commented Nov 4, 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:

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

Sem título

So, I checked the file format is indeed with 48kHz and 24 bit mono, for both the input and output files. Any ideas?

@Rkiefe Rkiefe added bug Something isn't working priority:low Low-priority issues unread This issue is new and hasn't been seen by the maintainers yet labels Nov 4, 2024
@Rkiefe Rkiefe changed the title [BUG] No response activated the trigger in response to input spikes Nov 4, 2024
@sdatkinson sdatkinson transferred this issue from sdatkinson/NeuralAmpModelerPlugin Nov 5, 2024
@sdatkinson
Copy link
Owner

Can you share the files?

@sdatkinson sdatkinson removed the unread This issue is new and hasn't been seen by the maintainers yet label Nov 21, 2024
@Rkiefe
Copy link
Author

Rkiefe commented Nov 22, 2024

Definitely! The reply does not accept .wav files directly so I'll send them as a .zip.
rk_files.zip

@sdatkinson
Copy link
Owner

Thanks.

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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority:low Low-priority issues
Projects
None yet
Development

No branches or pull requests

2 participants