-
Notifications
You must be signed in to change notification settings - Fork 117
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
Unable to load music_speech_audioset model #6
Comments
Hi. I just did the colab test. It works for me. Here are the expected logs: Some weights of the model checkpoint at roberta-base were not used when initializing RobertaModel: ['lm_head.decoder.weight', 'lm_head.dense.bias', 'lm_head.dense.weight', 'lm_head.bias', 'lm_head.layer_norm.bias', 'lm_head.layer_norm.weight']
Load AudioSep model from [checkpoint/audiosep_base_4M_steps.ckpt] Separate audio from [exp31_water drops_mixture.wav] with textual query [water drops] Write separated audio to [separated_audio.wav] The warning is NOT related to the KeyError. I didn't reproduce the error of "KeyError: 'pytorch-lightning_version', could you try it again? |
I see from your log that you are using |
I tried using the Colab notebook. The first model checkpoint loads without any issue, however, the second model checkpoint leads to an error during the model initialization. Below is the snippet of the code that downloads the model checkpoints and attempts to initialize the model:
Upon executing the model initialization, a KeyError related to pytorch-lightning_version is encountered, as shown below:
KeyError: 'pytorch-lightning_version'
Additionally, a warning concerning the initialization of RobertaModel with some weights not being used is thrown, although it's unclear if this warning is related to the KeyError.
The issue seems to arise specifically with the second model checkpoint music_speech_audioset_epoch_15_esc_89.98.pt. I would appreciate any guidance or suggestions on how to resolve this KeyError and successfully load the second model checkpoint for further use.
Thank you.
The text was updated successfully, but these errors were encountered: