Is it possible to install nvidia toolkit and use gpu accelerated tts training without using windows insider builds

[JRMeyer]

>>> cesm23
[February 16, 2021, 10:45am]

So far i have been forced to use CPU only tacotron2 training (which
obviously it's very slow) because even tough i DO have a nvida card
(NVIDIA GEFORCE GTX 1060 SUPER 6GB), i am unable to setup up the nvidia
tookit simply because it requires we to be part of the windows insider
program AND install insider builds! I really didn't want to do this
because i have heared of so many bugs with windows updates, and i have
been lucky so far with windows updates (without using insider builds),
and now this means i am FORCED to use a windows insider build to be able
to take advantage of my gpu in training, which might be quite unstable
and full of bugs and risking having to reinstall windows in case of
getting a bad build without knowing? The ONLY alternative to this is
using cpu training??

I really wonder what most people here that use gpu acceleration in
training for TTS do, is everyone here running insider builds? No one had
problems with this, at least not more than those that already exist with
updates for normal builds of windows?? That's quite unusual, since so
far i haven't seen a single person complaining about this!

Sure i am aware that we could use dual boot, but this is really not
practical to me since i DO want to use the computer in the normal
non-insider build i am using currently as the main OS WHILE doing the
training, it would be a hugle hassle to install everything i need to use
on a daily basis on the second boot with the insider build os...

Also using a virtual machine for this i think it's out of the question
too, since we have to use WSL2 and ubuntuu to run the text to speech
engines and training, so i think this isn't viable too.

Regarding google colab i never used this before, but i am not sure if i
am able to use it too extensively because i need to train from scratch
quite a few custom new datasets for new voices, so i will need to use
this really a LOT (even though i am afraid my graphics card isn't
powerfull enough, altough i have seen people online having average
training speed with this card so it might be okay to me)

Unless... there is a way to run gpu accerelated training for TTS without
installing insider builds, that i haven't found anywhere on google... so
tell me guys what you advise about this? Unless perhaps there is a
'safe' specific build number that is stable to use? But won't they
expire?

[JRMeyer]

>>> erogol
[February 16, 2021, 11:39am]

To my knowledge, you can only either use WSL2 on win10 or install a
separate Linux Distro.

[Archived Post]

[JRMeyer]

>>> rdh
[February 18, 2021, 2:26pm]

I'm not sure what causes you to force to use inside builds, but I have
had no such issues. Could you clarify this? Tacotron2 trains fine for me
on Windows 10 without using WSL2. The only fixes I ever had to apply are
the occasional explicit UTF-8 file encodings to open files.

[Archived Post]

[JRMeyer]

>>> cesm23
[February 19, 2021, 8:14am]

Ok, in the meantime i was able to get other repository working with cuda
(DeepLearningExamples/Fastpitch), for example the fastpitch model which
in fact i prefer over just tacotron2 itself, and all inside windows
command prompt without using no ubuntu, no insider builds, no nvidia
developer drivers and no docker!! That's amazing! Regarding this
repository (mozilla tts), even that one now recognizes cuda finally,
even being fully run inside a windows command prompt without ubuntu.

> I'm not sure what causes you to force to use inside builds, but I have
> had no such issues. Could you clarify this? Tacotron2 trains fine for
> me on Windows 10 without using WSL2. The only fixes I ever had to
> apply are the occasional explicit UTF-8 file encodings to open files.

Yeah!! Exactly i finally figured out how to do it without wsl too,
thanks to a person from the other repository, and yeah indeed i run by
the UTF-8 file encoding problems, but i just had to had to open the
slash TTS slash TTS slash utils slash io.py file and replace all instances of : slash
'r' slash
with : slash
'r', encoding = 'utf-8'

And doing the same with 'w', and now it works, that's how you did it
too? Or is there an easier way?

But wait a minute, how the heck were you able to solve the problem of
the espeak dependency?? It's the only thing now that i wasn't able to
fix yet, what is the windows command prompt command to do this ? (using
PIP) Just using pip install espeak doesnt work, and installing espeak
for windows has no effect either, unless it has a different name to use
in pip, so tell me how you installed espeak in a way to this repository
recognize it.

[Archived Post]

[JRMeyer]

>>> nmstoker
[February 19, 2021, 3:09pm]

Good to hear you're making progress

FYI pip won't help you with espeak as it's for installing python
packages and what you need for espeak is the local executable. You
probably want to look at espeak-ng rather than straight espeak as the
latter hasn't been updated in a long while. slash
I haven't installed either on Windows before but I believe espeak-ng
have assets (eg an .MSI installer) on their GitHub release page (their
releases are very sporadic too but it's in a better state than espeak!)

BTW, when you're in a good position, how would you feel about writing up
some of the windows specific stuff? It might help to add to the
documentation / questions sections and save others from struggling too,
sharing your hard won expertise back with the community!

[Archived Post]