-
Notifications
You must be signed in to change notification settings - Fork 6.7k
Flux2 klein #12982
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
Flux2 klein #12982
Conversation
Co-authored-by: Sayak Paul <spsayakpaul@gmail.com>
* tests * up * tests * up
Co-authored-by: dg845 <58458699+dg845@users.noreply.github.com>
Co-authored-by: dg845 <58458699+dg845@users.noreply.github.com>
* initial commit * initial commit * remove remote text encoder * initial commit * initial commit * initial commit * revert * img2img fix * text encoder + tokenizer * text encoder + tokenizer * update readme * guidance * guidance * guidance * test * test * revert changes not needed for the non klein model * Update examples/dreambooth/train_dreambooth_lora_flux2_klein.py Co-authored-by: Sayak Paul <spsayakpaul@gmail.com> * fix guidance * fix validation * fix validation * fix validation * fix path * space --------- Co-authored-by: Sayak Paul <spsayakpaul@gmail.com>
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
|
D:\pinokio\api\flux-2-klein-pinokio.git>conda_hook & conda deactivate & conda deactivate & conda deactivate & conda activate base & D:\pinokio\api\flux-2-klein-pinokio.git\env\Scripts\activate D:\pinokio\api\flux-2-klein-pinokio.git\env && python app.py |
Use this branch for building diffusers |
|
@bot /style |
|
Style bot fixed some files and pushed the changes. |
cjkindel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there guidance/enforcement that Diffusers can provide to prevent the confusion that comes from initial pipelines being generic (ex: Flux2Pipeline) instead of specific (ex: Flux2DevPipeline) so that subsequent pipeline naming matches the pattern?
Griptape's customers experience some confusion on this, they see pipelines like Flux2Pipeline and it is not obvious that the pipeline is for [dev] models only, not [klein].
(Not specific to Flux.2, seeing this anti-pattern across pipelines)
|
|
||
| model_description = f""" | ||
| # Flux DreamBooth LoRA - {repo_id} | ||
| # Flux.2 DreamBooth LoRA - {repo_id} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Should this clarify [dev]?
|
hey @cjkindel thanks for your feedback, however we don't really know these release plans ahead of time and it's hard to plan around that You can use or they don't need to know the specific pipeline name at all. |
|
@Bili-Sakura can you please open a new issue with this feature request? |
|
Does Flux2 Klein actually use Qwen 3 VL? The readme says Flux2 Klein uses "Qwen VL" as text encoder, but the pipeline code imports: from transformers import Qwen2TokenizerFast, Qwen3ForCausalLMwhich is text only i guess? am I missing something? |
testing script