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

Cannot predict some files #14

Open
akashicMarga opened this issue May 15, 2019 · 3 comments
Open

Cannot predict some files #14

akashicMarga opened this issue May 15, 2019 · 3 comments

Comments

@akashicMarga
Copy link

while predicting some audio file I am getting the following error

Using TensorFlow backend.

Traceback (most recent call last):

  File "predict.py", line 41, in <module>

    predict(cli_args)

  File "predict.py", line 16, in predict

    data = np.stack(data)

  File "/home/gamut/anaconda2/envs/xyz/li/lib/python2.7/site-packages/numpy/core/shape_base.py", line 335, in stack

    raise ValueError('need at least one array to stack')

ValueError: need at least one array to stack
@ibro45
Copy link

ibro45 commented May 15, 2019

Hi Aki58, I think the problem is in the dimensionality of the data, it sometimes happens that the generated spectogram images are a bit shorter than supposed. Check this issue that I had and see if you can get something with the Spectrogram generator's small x parameter (the total width of the spectrogram image). Basically what I think is happening to you is that you're trying to predict on an audio file which is converted to a spectrogram but not to the expected dimension and therefore the prediction fails.
I unfortunately hadn't had time to make a pull request to this repo, but this change has been applied in the version that I forked

@akashicMarga
Copy link
Author

Hi ibro45,
Thanks for your help, I also thought that this might be the case as I was providing 2-3 seconds of the audio file to predict. I will make the appropriate changes as suggested by you.

@completelyboofyblitzed
Copy link

Hi @ibro45 ,
Your decision didn't work for me, still getting the same error on some files, some work out fine with both yours and the original code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants