Ashley Cipher is a person who doesn't exist. You can use her if you need a consistent character.
Please have a look at other Nobody models for contributions by other folks including those created with the LastName and NBDY tags.
Follow me if you'd like to be notified of future models!
Installation
To install, download the .bin file and then place in the stable-diffusion-webui/embeddings/ folder. Then you'll either need to restart WebUI or tap the Refresh button in the Textual Inversions tab in the Extra Networks tab.
To Use
The trigger word is AshleyCipher which you can use in your prompt. See the gallery below for some examples.
A note about what I use to generate images
My main go-to photorealistic model is Avalon TRUVision V2 but I also might use RealisticVision 2.0, Protogen Infinity, or HARDBlend
Many of the images in the gallery use TRUVision for the initial txt2img and then RealisticVision/Protogen for a quick img2img pass with denoising set to .10 - .15 to add some additional skin texture. Unfortunately that first generation information isn't embedded into the PNG.
I always use the vae-ft-mse-840000 as my VAE. You can find it at HuggingFace. You can enable the VAE dropdown menu in WebUI by going to Settings -> User Interface -> Quicksettings list and adding "sd_vae"
When I use Hires Fix to upscale I usually use 4x-UltraSharp for the Upscaler and enable Tiled VAE which is part of the Multidiffusion Upscaler package
If I upscale even further in
img2imgI'll use a combination of ControlNet 1.1'stile_resample/tile model and Ultimate SD Upscaler
Description
First version!
FAQ
Comments (6)
InvokeAI requires you to use "<ashleycipher>" as the trigger word, in lower case, with the < and >
@ian146 Thanks for the info. How did you figure that out? I'm pretty sure that's the placeholder token I used when I trained the TI which would make sense. I haven't used InvokeAI in many months (they didn't have TI/LoRA support back then I think) but I wouldn't mind listing the trigger token I used for each of my embeddings for Invoke folks.
@Scottymac yeh looks like InvokeAI uses a value that's stored inside the TI rather than the filename. I've seen this on a lot of other TI's too. It's most confusing.
@ian146 Ah ok so Invoke can see what the token is; I'll try to figure it out for each of mine and add it for InvokeAI folks.
@Scottymac Seems InvokeAI v3 is going to revert to using the name of the TI rather than the internal name
@ian146 Fantastic -- thanks for the update!
Details
Available On (1 platform)
Same model published on other platforms. May have additional downloads or version variants.