-
Notifications
You must be signed in to change notification settings - Fork 24
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
Prompt Editing is misconstrued. #50
Comments
[A:B:weight] is not supported currently. Since I have no idea if I should put the first one into TIPO prompt or second one or both, also I didn't find a better parser to parse it. (The parser in A1111 will directly split it into multiple prompt for different timestep which makes things worse) |
I see what you mean. |
On user side: no |
A possible workaround is to put the lora annotation into format instead of prompt |
When using Prompt Editing with TIPO, the prompt is unexpectedly converted into a string containing mysterious numbers.
To address this, I tried generating with "No formatting" enabled, but this resulted in LoRAs being applied twice.
I suspect this is due to misinterpretation of characters like [].
I have confirmed this behavior in both a1111 (ver 1.10) and EasyReforge environments with the same extensions.
A fix would be greatly appreciated.
The text was updated successfully, but these errors were encountered: