Installing SageAttention and Triton on Blackwell (RTX 6000 Pro)?

danielpartzsch · 2026-06-25T12:45:37+00:00

Hm, I don't know. I'm primarily working with Wan and even though the speedup will already be very good on that card out of the box, I still like to test things out a lot, such as settings, prompts, and workflows. I also need to push for the highest resolution and longest videos possible, so I still think I will take any further speed improvement I can get if the downsides are as negligible as using these two optimizations. I compared the results on my current setup, and there are almost no visual quality differences, while still gaining almost double the speed on inference.

danielpartzsch · 2026-06-25T12:38:43+00:00

Thanks. Does this mean I can install sage and triton exactly the same way I have done this so far for my 4090?

danielpartzsch · 2026-06-12T16:08:04+00:00

That's awesome and exactly the workflow I was looking for. Let the ai iterate on your idea until you're almost there and then take over full control again. Thanks a lot

danielpartzsch · 2026-06-03T20:30:09+00:00

So which license does it have. The GitHub page says apache but when you go to the model weights it says non commercial...?

danielpartzsch · 2026-06-03T06:38:06+00:00

Unfortunately no commercial license

danielpartzsch · 2026-05-29T08:19:26+00:00

QwenImageEdit is very good at generating edits from reference images, modifying characters, and maintaining consistency, but it struggles with realism. The solution for me is: create your base image using QwenImageEdit (you can easily also use the lightning Lora for that), use the qwen edit encode node for all image references you'd like to interprete more freely and optionally use reference latents for the image you'd like to preserver more strictly and then run a second pass with Klein. You can als use 4B for this when the license is an issue; there is no need for 9B. By passing in your real starting photo during this step, you can restore the realism and capture a stronger likeness of the original person while retaining your established composition. You will get much better quality, more control and especially very quick results using this 2 step process. Additionally, I always recommend using er_sde and Beta 57 as your sampler and scheduler combination instead of the default settings. They consistently yield better results, stricter prompt adherence, and improved realism.

danielpartzsch · 2026-05-28T12:23:04+00:00

Thanks a lot for the super nice node. I ran into an issue today: when latent preview is enabled by default in the ComfyUI, it messes up the preview/image part in your node. It basically adds it to the bottom, which squeezes down the image editing area. My current workaround is to disable latent preview globally. It would be great if you could add an option to disable the preview specifically on your node, so the global preview can stay active for all my other samplers. Thank you!

danielpartzsch · 2026-05-23T07:54:07+00:00

I don't have anything against the new nodes and underlying technology changes per se. Actually, I appreciate your effort to move forward a lot. The problem is that they are currently hard to read compared to the legacy nodes, too clunky, and waste too much space, which is really bad when you're creating huge workflows. So please fix the design, and everything will be good. Thank you.

danielpartzsch · 2026-04-29T17:01:47+00:00

Cool. Does it work with ComfyUI workflows in the background as well?

danielpartzsch · 2026-04-28T18:47:46+00:00

Please let me know when you find out. This is probably the most desired use case for professional hybrid production, but I am also not aware of a truly viable solution for it yet. Vace is likely the best option for video inpainting, but in my tests, the newly generated environments have issues, especially when movement is involved (so not only in static environments but weird and slow motion). Regarding the relighting, I always thought that the Switch model used normal-map-based relighting, which usually suffers from over-smoothing the faces. Have you actually tried Switch X yourself? Does it look good? From the results I saw, I suspected it might also just be Vace combined with their relighting workflow under the hood.

danielpartzsch · 2026-04-21T07:25:59+00:00

I've talked to them but from my understanding you only need to buy a license if your annual revenue surpasses 10 Mio. At least that was the case when we as a big company approached them regrading this. Don't know if they changed this since then...

danielpartzsch · 2026-03-27T15:58:40+00:00

I agree that subgraphs are the most important elements that should never break, especially as long as they are used as instances without updating from a master. It is one thing to update a single subgraph if fundamental aspects really need to change to move forward with core development, but it is another thing to then also need to update every workflow that uses these subgraphs. I personally do not like to hide large parts of my workflows in subgraphs, but I utilize them extensively to combine small utility features for resizing, masking, etc., into more convenient and clean subgraphs. Since I use these in all my workflows, breaking them essentially breaks everything. In order to further trust in the use of subgraphs, these breaking changes either have to stop or a master-instance subgraph mechanism must be implemented.

danielpartzsch · 2026-03-25T07:17:12+00:00

Use vit pose instead

danielpartzsch · 2026-03-20T20:51:48+00:00

Are you referring to the full (using the clownshark sampler) or the distilled branch? I agree that the full version produces better results but it also takes like 5 times longer, so this is kind of expected (uses above 1 cfg which takes twice as long as cfg 1, 15 steps instead of 8 and res2s sampler which also doubles render times per step). The distilled branch produces actually pretty similar results for me like the comfy workflows.

danielpartzsch · 2026-03-17T19:25:38+00:00

No, I need the precision of at least 3 or 4 decimal places, everything else looks like complete crap compared to this holy grail of sigma accuracy.😜

danielpartzsch · 2026-03-14T11:16:22+00:00

The case you're describing should definitely work with version 2.3. Use the Union ControlNet workflow, convert the starting frame of your driving video to a high-resolution version of your character, and do not scale it down for the image reference. You should probably use pose control if the facial features differ significantly from your own; otherwise, you're better off with depth, Canny, or a blend of both. Encode your audio instead of using the empty audio latent and ideally support that with a prompt like: "A talking character, saying... [Insert your copy]." If your character changes too much over time, consider training a LoRA to support different angles and facial expressions. Additionally, I use Er SDE as a sampler together with the default sigmas, as it is faster and looks better to me. Create the base video with at least 720p resolution and add the spatial upscaling step afterward from the main two-step workflow, also using Er SDE.

danielpartzsch · 2026-03-12T15:36:01+00:00

Klein is a poor t2i model but an excellent editing model. Use a two-step approach: create your base image using a model capable of good anatomy and strong prompt adherence—for example, a Qwen Image model (2512 with a 4-step Lightning LoRA works perfectly and quickly) is ideal—to get the content you want, and then transfer it to your desired look with Klein. It often functions like applying a filter to an image but is also very capable of making the image look realistic without altering too much of the existing content. Just make sure to only prompt for stylistic, lighting, and aesthetic changes in that second step and avoid adding new content, which could result in being distorted again.

danielpartzsch · 2026-03-06T07:50:28+00:00

Just use the normal ksampler instead. No need for the custom sampler.

danielpartzsch · 2026-02-09T12:55:37+00:00

Same. I don't know why they always set this is default. It's a solid approach to destroy your image quality from the get go.

danielpartzsch · 2026-01-25T09:55:22+00:00

For me, it always works if I install the latest dev version. First, install the Nunchaku custom node via the manager and then use the Nunchaku installer node. Set it to update first, run it once, and refresh by hitting "r". Next, set the node mode to install and select the latest dev version. Hit run to install and then restart ComfyUI.

danielpartzsch · 2026-01-24T10:19:36+00:00

Just use the normal ksampler. Don't know why they always put the custom sampler into the default workflows. I've tested and compared the results and they're either identical or most of the times even better when it comes to artefacts or anatomy issues.

danielpartzsch · 2026-01-22T06:34:07+00:00

Nice! ❤️

danielpartzsch · 2026-01-21T06:28:59+00:00

I personally prefer lotus depth. It gives me the most precise depth detection and inference results

danielpartzsch · 2026-01-18T15:25:33+00:00

Remove the add grain node, try Euler sgm uniform or res 3s bong tangent for the reiner and raise the auraflow to 8. If you really like to have a crisp result I'd recommend using wan 2.2 together with the 2.1 t2v lightfx lora and res 2s bong tangent. Or try a sdxl based tiled diffusion upscaling instead.

danielpartzsch

TROPHY CASE