Long story short, for the first ever I needed a turbo lora (extracted as diff) to be used on the base Klein 9B model and I was not satisfied with the ones I found so I tried making my own with twice the rank (256).Thus, I'll be using this one and I'm uploading it even though its quite late to do so since Klein is pretty much a very old model by AI community standards. Its still the best open source image editing model - which is why I'm still using it.You can see in the comparison image - the output of the rank 256 BF16 turbo lora is closer to the original output of the Turbo model itself VS the rank 128 FP32 one.<h1 id="recommended-settings">Recommended Settings</h1><ul><li>0.25 Strength ➔ CFG: 3.0 | Steps: 16</li><li>0.50 Strength ➔ CFG: 2.0 | Steps: 12</li><li>0.75 Strength ➔ CFG: 1.3 | Steps: 8</li></ul>(check the included workflow in 'Optional Files' which shows how you can set a workflow to automatically handle those settings - and the ConditioningZeroOut node - for you, from a single subgraph widget input. Requires: <a target="_blank" rel="ugc" href="https://github.com/bananasss00/ComfyUI-SP-Nodes">https://github.com/bananasss00/ComfyUI-SP-Nodes</a>)<h3 id="about-the-negative-prompt:">ABOUT THE NEGATIVE PROMPT:</h3>when using turbo strength &gt;= 1.0: 'ConditioningZeroOut' node must be used - which means your negative_prompt is completely ignored.when using turbo strength &lt; 1.0:<ul><li>'ConditioningZeroOut' node CANNOT be used.</li><li>negative_prompt should be completely EMPTY for regular text-to-image tasks because otherwise your output quality drops dramatically. This is a flaw with the Base model itself - nothing to do with the turbo lora.</li><li>short, non-empty negative_prompt is only useful in some edge-cases in Image Editing mode</li></ul>

Files with SHA256: 8516f1f83fdec0af51262b00486ec27eba49dea2879cf61cf2d38a7d818a2031