・実験的VAE
・エンコーダーは調整していません
・画像にRefinerは使用していません
・NansException
Description
・ピンク減らしました
・青(緑)くなる
・F2より彩度が低い
・コントラストが高い
FAQ
Comments (14)
Thank you for the amazing work! Would it be possible to also provide FP16 versions of these VAEs, similar to this one: https://huggingface.co/madebyollin/sdxl-vae-fp16-fix
After switching from NV cards to Macs, I’ve been encountering NaN exceptions and can now only use FP16 models like the SDXL VAE mentioned above. I’d greatly appreciate it if you could consider releasing FP16 versions. Thank you!
XL_VAE_C is all FP16.
Sorry, I don't know about NaN.
Bro, the output is always black no matter what VAE or sampling method
maybe you dont have clip skip at 2
@AlIs_115 gives no changes to me. Anyway, why should it be tied to clip skip
Yeah, same is true here. It shouldn't be tied to clip skip, it seems to be a problem with the vae itself.
我也一样,所以这个问题解决了吗……
@Hakuri_Yuki yeah solved. Do --no-half-vae at argument line on launch. I guess half-vae breaks non-mature models or sorta
Vae works great. A lot of default model checkpoint's built-in Vaes are too bright all across the images. This vae appears to raise contrast for darker colors and background objects which reduces the fuzzy feelings of a lot of images.
there is a small problem for g9
skew to blue tint due to increased contrast, or something else
yes, I started adding blue hair to the negative to deal with this
Hello, the VAE colors you've created are truly excellent. However, when I try to generate larger resolutions (e.g., 832*1216) and then perform a 2x high-definition redraw upscale, I consistently encounter VRAM overflow issues resulting in black images. Do you have any solution to fix this problem? Based on my tests, when using the official VAE at the same resolution, this issue doesn't occur - it seems VAEs around 300MB in size don't have this problem.
您好,您制作的vae颜色真的非常棒,不过我在生成较大分辨率,如:832*1216再高清重绘放大两倍的情况下都会爆显存生成黑图,您有办法修复这个问题吗?根据我的测试,使用官方的vae在生成同样大小分辨率的图片就不会有这个问题,貌似容量在300多mb的vae都不会出现这个问题
@atw44qb Thank you for your reply. After using Forge, the problem was resolved.









