-
Notifications
You must be signed in to change notification settings - Fork 283
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
Error in training #9
Comments
Generally this error arises when your training directory is wrong or the tfrecords are actually empty files. Check your command line argument for the directory of your tfrecords. If the directory is correct, try previewing one: |
I had the same issue and in my case, I was using the actual tf.record file as the input instead of the folder where the files are. Hope this helps. Btw, why are you creating several tf.records instead of a big one? |
I am facing the same problem with a dataset I created, how did you solve this? I don't think it's empty my file because I had that issue and I solved it installing ffmpeg (as suggested in some issue here). And I'm using the folder not the actual file. Thanks for the help. |
If you are facing this issue still, I would strongly recommend pulling in the latest v2 update that we just released. This allows you to train a WaveGAN directly on a folder from MP3s/WAVs/OGGs/etc. Requires librosa (for MP3s/OGGs) or scipy (for WAVs). |
Hi! Then I tried with gpu using python 3.6 This is the error I obtain: |
I'm not sure. It sounds like you might not have the latest version of TF installed. Try pip install --upgrade tensorflow-gpu. Otherwise I would Google around for that specific error because it doesn't seem related to the WaveGAN code itself. |
Hi
![screenshot from 2018-07-04 22 46 30](https://user-images.githubusercontent.com/25304603/42289358-97714dd6-7fdc-11e8-979a-eb04e0303258.png)
I am having trouble training with my data
I sucessfully created tfrecord file
but when i use this data to train the GAN it has this problem
The text was updated successfully, but these errors were encountered: