SDXL Natural Skintone (FP32)
Will reduce saturation across all images, and can provide a more natural look for over saturated models with minor quality loss compared to BASE FP32 SDXL VAE
Without setting the FP32 VAE command, the VAE is downcast to FP16
This VAE works by introducing more green values in the encoder/decoder and does have more artifacting compared to SDXL FP32 Base VAE
Description
FAQ
Comments (14)
There is only one real VAE test
1) Encode HD photo with VAE
2) Decode output with same VAE
You will be surprised how popular VAE checkpoints distort image and degrade quality.
I Checked all existing SD1.5 vae and official ones (from SD devs account) which are biggest in size (32bit) produce the most accurate results. Probably with SDXL will be same results.
You need to do 0.5 latent upscale and 2x latent upscale to test scaling, admittedly my VAE produces some odd green coloration by itself. Nether model preformed well down-scaling and in a one to one comparsion the base SDXL FP32 vae is more color accurate but the green coloration acts to de-saturate over saturated reds
Fuckin good, doesnt work with highres fix(forge, fp16, green pic with artifacts)
Yes it works by green corruption, unfortunately unlike comfy ui you can not switch back to base fp32 sdxl during upscale in forge
@Felldude Allright, i switched VAE for highres. It takes longer, but your VAE is too good to not use.
just diving into this vae and clip stuff you have been working on, very interesting. Where does one find the base vae in fp32?
It would be great if this worked with Invoke in the fp32 form. Sadly it doesn't. great colors, terribly blurry details.
It is a corruption so that is not necessarily surprising. I wonder what invoke is doing that comfy is not.
@Felldude What is a corruption? I'm gonna try bf16 one later and see what happens
I see something about enabling fp64 on the HDR one, which I wished worked too. That doesn't work in Invoke for sure. For some reason Invoke only seems to work with the fp16fixed one for clean outputs for now, but I'll post results about the bf16 version.
@Crowyote I do not recommend FP64 it is possible in comfy or standalone but the improvement if any in data compression accuracy was negligible - So regarding the corruption it is truly corrupting the data from a reconstruction standpoint with green values that where non existent, terrible from a data science end beneficial from a art end
@Felldude First tests with bf16, just as blurry as the fp32. It must not be compatible with the Invoke code. Perhaps I'll try Comfy again someday.
I really like this model. It's become my go-to VAE. My current work ends up being a pseudo-realistic visual style coming by way of more anime-centric checkpoints. I find that this VAE adds a much appreciated push towards realistic skin textures.
Thank you.