> Current embedding manager terms: *, my-embed,, but that invoke is just going to use the filename (from the embeddings folder or supplied as option) as the placeholder value for a given embedding? Is it correct to say that for the purposes of using the embeddings in a prompt, it genuinely doesn't matter how they were created or what the placeholder given when they were created is. But like I said before, when I copy these pt files into an A1111 install, they do resemble the trained images when I use the prompts, so I know the trained files must be "working" in some sense. That is, when I have nothing in embeddings folder, I see only *, when I put files in the folder, or symlink files from the folder, or supply arg on command line, I do see the relevant file names added to that list (ie, adding a embed.pt file to the folder shows *, embed during load).Īll that said, the generated images are still not producing anything resembling my trained images when I attempt to use them from the invoke CLI (or web UI). Thanks, I tried various options and can confirm that I do see the expected list in the "Current embedding manager terms" output during load. I've tried lots of variations of "a photo of *", "a photo of * dog", "a photo of my_dog" (I used my_dog as the name during training). pt file generated by the invoke/main.py script, copy it into a separate a111 install, and get that to generate images of the dog (struggling to get it to make anything OTHER than the dog), which makes me think that the training did work correctly but it's just not loading correctly or I'm not prompting it correctly. but I cannot figure out how to get invoke to actually use the embedding from a prompt, despite running the CLI with the -embedding_path option on that page. I've been able to train an embedding (using that tiny dog that's in all the various online examples) using the script from that page in the invoke docs. Separately, I'd love to get a more detailed "how to successfully name and use your embedding after training it" sort of instruction on that page, and would be happy to document and PR that once I understand it. Yeah, I think on that page the big "WINDOWS" section should really just be a smaller note, and the instructions for running the script are the same across platforms.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |