Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it possible to use T5 gguf versions? #5

Open
schen18 opened this issue Oct 5, 2024 · 1 comment
Open

Is it possible to use T5 gguf versions? #5

schen18 opened this issue Oct 5, 2024 · 1 comment

Comments

@schen18
Copy link

schen18 commented Oct 5, 2024

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/ ?

@DenOfEquity
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants