You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No, they didn't exist when this extension was written so using alternate text encoders was never a consideration. Using the Forge functions to handle the text encoding would be an interesting thing to try, but it would be a very low priority experiment: performance is fine, and any such changes wouldn't benefit A1111 or reForge or old Forge.
Is it possible to skip the hardcoded unquantized T5 and instead use the Forge UI vae/encoder dropdown to specify the gguf versions in https://huggingface.co/city96/t5-v1_1-xxl-encoder-gguf/ ?
The text was updated successfully, but these errors were encountered: