Not Found Model

[SyamsQ]

I have successfully downloaded the default Xtts model, but why is it still not found?

[erew123]

Hi @SyamsQ

Ive tested a fresh install and cant find any issues with downloads or loading models once they are downloaded.

Please confirm the folder location in RED has the files indicated in ORANGE and if you download them again, please confirm the console shows all files in BLUE being downloaded. You can hit the download button again to download any missing files.

Please also check that the file are of the correct size as shown in the screen shot. If not you may need to check your internet access or antivirus software to see if something strange is going on there.

You can manually download the files from here https://huggingface.co/coqui/XTTS-v2/tree/v2.0.3 if necessary and place them in the folder location show in the screenshot.

Thanks

[SyamsQ]

I've gone through all the processes you mentioned. Here is the Xtts folder. Still not available

Your help and guidance please.

[erew123]

@SyamsQ So I am assuming you re-downloaded the model file again... If when AT is loaded you click on the selection box where it says "No models available" nothing shows in there to select? Or if you click the "Swap TTS engine" with XTTS selected, the other dropdown still has no choices in when its re-loaded the engine?

[SyamsQ]

I have re-downloaded it. I even downloaded version 2.0.2. But it still doesn't work

[erew123]

and you have clicked on the "Swap TTS Engine" button AFTER downloading that model?

[erew123]

If so, it would seem to me its a permissions issue in some way or perhaps you ended up with a corrupted Coqui TTS package installation.

I assume you have an alltalk_tts\outputs folder, as that is the only outputs folder I know of, and I assume you have permission to access that folder (copy files in and out etc). Likewise the same for the XTTS model folders (otherwise it shouldnt have been able to download into them, though you can deny read access in Windows, but leave write access in place).

Assuming no strange permissions issue, I would propose reinstalling the coqui-tts engine. At a command prompt in the alltalk_tts folder:

start_environment.bat

pip uninstall coqui-tts

pip install coqui-tts==0.24.3

The actual AllTalk code just looks for the existence of the files in the folders:

https://github.com/erew123/alltalk_tts/blob/alltalkbeta/system/tts_engines/xtts/model_engine.py#L623C1-L684C37

This function checks if you have properly installed your XTTS models. For each model to work, it needs to be set up like this:

models/
└── xtts/                      # This is your main models folder
    └── your_model_folder/     # Your model goes in its own folder here
        ├── config.json        # Required file 1
        ├── model.pth          # Required file 2
        ├── mel_stats.pth      # Required file 3
        ├── speakers_xtts.pth  # Required file 4
        ├── vocab.json         # Required file 5
        └── dvae.pth          # Required file 6

The function does these simple steps:

1. Looks in your models/xtts folder
2. Checks each subfolder it finds
3. Makes sure all 6 required files are present
4. If it finds all the files, it marks that model as available to use
5. If files are missing, it warns you that something's not right

When it finds a valid model, it actually registers it twice:

• Once as "xtts - modelname" for local use
• Once as "apitts - modelname" for API use

If anything's missing, it will tell you:

• Which folder it checked
• That files are missing
• That you need to download or properly install your models

Clicking on the Swap TTS Engine button with XTTS selected will ensure that the specific check/block of code I reference is run and that the Load Different Model dropdown is populated with whatever available models there are, so you can select one and load it in.

So as mentioned, if it cannot find the files for some reason, something is causing a permission access issue e.g. Windows file permissions, Antivirus, something strange in the folder path that Python doesnt handle (though I cant see a path naming issue in your screenshots).

I suppose its also possible they are on a Mapped network drive, which can cause issues with Python, so that could be an issue. Also the files could be marked as System or Hidden, which may cause an issue.

Those are the only things I can suggest investigating, as testing a full factory fresh installation on a Windows 11 system here shows no issues.