[X] I have searched the existing issues and checked the recent builds/commits
What happened?
I'm not sure what the distinction is, but there seem to be some factor dividing my 133 textual embeddings into 2 distinct groups (perhaps some are based on SD 1.x and some are based on SD 2.x, because the newer ones seem to pretty consistently be the ones which fall into the second, smaller category that has emerged, or maybe it has to do with what fp precision I load the webUI with, though loading with "precision autocast" argument doesn't enable them all to load)?
It's not as if they're marked in any way that distinguishes them-- it's just that, consistently, when I start up the webUI, it will either say it successfully loaded 119 of them (the majority of older ones) but failed to load 14 of them, or it will say it successfully loaded the 14 newer ones but failed to load the 119 slightly older ones that I've been using for a while. I can't figure out what causes it to go one way or the other, but it never seems to load all of them.
Would love to see this fixed so I can use all of these wonderful embeddings freely. It's become a bigger issue for me since I started using IlluminatiDiffusion (one of the new models incorporating offset noise), which requires 3 negative embeddings among the 14 newer ones, so when it does allow me to use those embeddings, almost all of the others are inaccessible, whereas when the 119 majority of them are accessible, I can't use IlluminatiDiffusion at all because the Fixer embeddings it needs to work properly don't load.
Thanks.
Steps to reproduce the problem
Here's the list of Textual Embeddings which do vs those which don't load when the 119 successfully do load. If you have some from both lists in your embeddings folder then I suspect you'll encounter the same thing:
As you've noticed, textual inversion embeddings made for SD1.x can only be used with SD1.x based models, while those made for SD2.x can only be used with SD2.x based models.
Is there an existing issue for this?
What happened?
I'm not sure what the distinction is, but there seem to be some factor dividing my 133 textual embeddings into 2 distinct groups (perhaps some are based on SD 1.x and some are based on SD 2.x, because the newer ones seem to pretty consistently be the ones which fall into the second, smaller category that has emerged, or maybe it has to do with what fp precision I load the webUI with, though loading with "precision autocast" argument doesn't enable them all to load)?
It's not as if they're marked in any way that distinguishes them-- it's just that, consistently, when I start up the webUI, it will either say it successfully loaded 119 of them (the majority of older ones) but failed to load 14 of them, or it will say it successfully loaded the 14 newer ones but failed to load the 119 slightly older ones that I've been using for a while. I can't figure out what causes it to go one way or the other, but it never seems to load all of them.
Would love to see this fixed so I can use all of these wonderful embeddings freely. It's become a bigger issue for me since I started using IlluminatiDiffusion (one of the new models incorporating offset noise), which requires 3 negative embeddings among the 14 newer ones, so when it does allow me to use those embeddings, almost all of the others are inaccessible, whereas when the 119 majority of them are accessible, I can't use IlluminatiDiffusion at all because the Fixer embeddings it needs to work properly don't load.
Thanks.
Steps to reproduce the problem
Here's the list of Textual Embeddings which do vs those which don't load when the 119 successfully do load. If you have some from both lists in your embeddings folder then I suspect you'll encounter the same thing:
What should have happened?
They should all load.
Commit where the problem happens
0cc0ee1bcb4c24a8c9715f66cede06601bfc00c8
What platforms do you use to access the UI ?
Windows
What browsers do you use to access the UI ?
Mozilla Firefox
Command Line Arguments
List of extensions
aesthetic-gradients, depthmap2mask, DreamArtist, images-browser, prompt-fusion-extension, sd_smartprocess, sd-dynamic-thresholding, sd-infinity-grid-generator-script, sd-webui-controlnet, shift-attention, Anti-Burn, Auto-TLS-HTTPS, Embedding Editor, Prompt Travel, Sonar, and Stylepile (though Sonar and Prompt Travel don't work).
Console logs
Additional information
No response