-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
Toolbox not working with python3.8 #401
Comments
@brcisna As you note, the code will not be compatible with python 3.8 until we can use tensorflow 2.x. There is an issue for this: #370 . If you want to hack at it, you are welcome to pull my tensorflow 2.x branch and try to figure out the error messages. Start here for more info. #370 (comment) Edit: If you're able to make my tensorflow2 fork run on Python 3.8 (that is, get through demo_cli.py without an error, regardless of output quality), I will take on the task of converting the pretrained model and getting it merged upstream with the latest updates. |
Hi blue-fish, Thank You for the information. Am showing my stupidity. I see the #370 comment but don't know how to install the fork of your tensorflow_v2 to my existing virtualenv? I see several commits,but have never dealt with this type of files,,i guess. Would like to hack around on this if i can figure out how to patch your files in? Thanks again |
No worries @brcisna ! Happy you are taking an interest to this. You need another copy of the Real-Time-Voice-Cloning toolbox, but it will work with your existing python3.8 + tensorflow2 virtualenv. Here are two ways to do it: 1. Quick (harder to share code changes)This clones the branch from my fork but you will not be able to push anything back without doing a bit of setup.
2. Fork method (very easy to share code changes)If you are willing to spend just a little more time on the setup, I suggest you make a fork so we can easily collaborate on this:
As you make fixes, push your changes back to your fork. Then I will be able to pull them into mine, and push them upstream when everything is working. Post-setup (after either method)
|
Hi blue-fish, Done the #1 routine here just to see what happens. I believe i am correct ,,cloning your branch simply dumps your patched files into my existing Real-Time-Voice-Cloning dir? I am still ending up with identical ' tensorflow.contrib not found'. I did also deactivate and activate the virtualenv one time also after cloning your branch to my dir. Thought i may end up with a slightly different error after cloning your branch? line 3, in Adding: Thanks |
Cloning makes a copy of the files with version control enabled. I think the way you ran it placed another Real-Time-Voice-Cloning directory inside the existing Real-Time-Voice-Cloning dir. Then when you tried it out, it was still running the old code. To help keep things straight, you should either remove the existing copy before cloning, or perform the clone in a different location entirely. |
OK, I apologize. I was thinking your dir branch patched my existing directory, from tensor2tensor.utils.hparam import HParams EDIT: Opps I did not run the requirements.txt,,,, Let me do this and report back. Thanks |
Let's start on demo_cli.py, I find it easier to troubleshoot. After updating the requirements do you get the same error message as me?
I recall working around it by changing this line to |
blue-fish, Arguments: Running a test of your configuration... Your PyTorch installation is not configured. If you have a GPU ready for deep learning, ensure that the drivers are properly installed, and that your CUDA version matches your PyTorch installation. If you're trying to use a cpu, please use the option --cpu. I do NOT have a CUDA capable GPU ,,Just want to use cpu if possible with this setup. Goes without saying,,I am very green at this. Thanks |
Try enabling CPU support: |
Thank You,,I wasnt sure how to enable --cpu even after googling,,, Getting closer,,,This is running demo_cli.py Thanks |
OK I tried changing the line you suggested to this: return tf.TensorShape([]).with_rank(1) Thanks. |
I should have mentioned at the start that the most direct way for you to get the toolbox working is to reinstall python3.7 (or run it inside a virtual machine). While I would greatly appreciate your help figuring out tensorflow_v2 compatibility, getting the toolbox to run on python3.8 is likely much harder than getting python3.7 back. I'll understand if you want to try restoring python3.7 instead. |
I did spend quite a bit of time trying to get python3.7 installed back onto here. python3.7 is simply not in the debian bullseye repositories now,,,nada . tried setting up backports and all sorts of stuff,, i would guess there was a cutoff date and the maintainers are full on python3.8 for their new dsitro release. I thought i got python3.7 installed through source with the --altinstall switch but cant see it anywhere,,?i never found any decent howtos on installing for a local user in an virtualenv either?.If i can get 3.7 back on,it will work as it did before,, i never realized when i done the autoremove of python3.7 as suggested a couple weeks ago it would kill this virtualenv setup,,never thought about it at the time until i tried using the toolbox again. |
Can you run a virtual machine with Ubuntu 18.04 and install python3.7 on that? |
That may be what ill have to do. i was really hoping to try and get this setup back to 3.7 Thanks for helping out too. |
blue-fish, finally with much wrangling used deb. snapshots repositories to get python3.7 reinstalled on this system and appears to be back to were it should be,,,,but,, when i use this command on my original (was working) virtualenv The UPSIDE is the toolbox.py opens fine and i can do recordings! Not sure if the synthesizer or other stuff works. Kinda burned out right now,,Would really like to get this back to working as i would like to use this again for some race history voices ( of now deceased people to narrate) of some videos,i do as a hobby. Thank You |
Try installing virtualenv for your python3.7 and then try the above command again.
|
will do thanks
…On Mon, Jul 6, 2020 at 8:04 PM blue-fish ***@***.***> wrote:
@brcisna <https://github.com/brcisna> Based on #404
<#404> can I
conclude that the toolbox is working for you now? If so can you please go
ahead and close this issue?
(Resolution: Use python 3.7)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#401 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALJUC6UQMIFCKMORLBZL6V3R2JYABANCNFSM4OQ6HYKQ>
.
|
Hello All,
Debian 11 Bullseye.
Started with python3.7.x and python3.8.x and recently updated to python3.8.xx along with deprecation python3.7. Tried installing python3.7 from source but for some reason python3.7 is never seen as an alternative and did install with the altinstall switch or whatever that is. From a LOT of reading python3.8 will only accept tensorflow2.x This is the major downfall for python3.8 and realtimevoicecloning. Had the realtimevoicecloning working great in virtualenv until debian suggested & done an autoremove of pyton3.7. ,, 'no longer needed'.
Have spent quite a bit of time trying to figure this out,and still no joy.
Thank You
The text was updated successfully, but these errors were encountered: