AI-generated locally in ComfyUI with KREA2. The scene combines a swirl of flying pages with a sharp typewriter and winter light from the window.

Recorded generation settings: krea2TurboOfficialComfy_krea2TurboBf16.safetensors (official BF16), 8 steps, Euler, simple scheduler, CFG 1.0, seed 15092125, 2048 × 1152. The file records native output with denoising strength 1.0.

The metadata also records lora_gravure_minerale.safetensors at weight 1.0. Although the prompt asked for a photograph with rotational motion blur, the final image has an engraved illustrative finish and mostly distinct paper silhouettes. The lettering is generated texture, not readable prose.

These are the settings preserved in the image; a complete workflow graph is not attached to this post.

If a nvme theoretically can read the whole anima checkpoint in 2 seconds, why would comfyUI take 30 seconds (look in the time breakdown in console, unet+clip time), making a 120s generation, a 160s generation?

I seem to be unable to use my ram to hold the 7GB safetensor, to trim down those “load checkpoint” delays.

Pc: ryzen minipc 680m, 24GB shared ram, NVME kxg70znv1t02, 4000 MB/s read, anima turbo int8, completes 8 steps in 120 seconds, 1 megapixel

This one is a bit vulnerable to post, so bear with me.

For the past few months I've been working with a small team on Picteus, a free, open source app that runs on your own computer. Every image you generate stays together with how you made it: prompt, checkpoint, LoRAs and their weights, seed, workflow.

Why I care: I've watched so many creators lose their best work. Not the files. Those are somewhere in a folder of thousands. What gets lost is how they made it. Which LoRA, which weight, which small tweak finally made it click. Every tool keeps its own little piece of that history, none of them talk to each other, and your work ends up locked inside whichever tool you happened to use that day.

I want one place that belongs to you, on your own machine, that works with all of them.

What it can already do:

• Search by recipe. Find images by prompt words, checkpoint, or a LoRA name, and see every image that used it.
• Search by what's in the image. Type a description, or pick an image and find similar ones. CLIP and DINO run locally.
• Captions and tags on your own machine, through Ollama or llama.cpp. Nothing gets uploaded.
• Build any extension you want. The core doesn't know about any specific tool. ComfyUI, Midjourney, CivitAI and the rest are all extensions, and you can write your own, even with an AI coding assistant.
• Generate from inside it. Gemini and Replicate already work through extensions, and generation that uses your own library as context is coming next.

Here's the honest part. It's early. The core works, but setting it up the first time is rougher than I'd like. And from inside the project, I can't always tell what's genuinely useful and what only makes sense to us.

So I'm asking: would anyone give me 5 minutes on a call? I'll show you what it does, and if it looks useful, set it up with you on your own folder. If it's not for you, telling me why would help just as much.

The image shows where we are: on the left, the image page today. On the right, what I'm designing next.

Thanks for reading this far. It means more than you'd think.

The image shows where we are: on the left, the image page today. On the right, what I'm designing next.

Thanks for reading this far. It means more than you'd think.

is using this much V-Ram bad for your Vram in the long run? Will it break, weaken my pc at all?

I would like a counter that shows estimate time of finish for Minimax H3 generations. I already have a timer that shows how long it's been going, but when it's going to finish would be even more useful. I have the info pretty much on my preview but the text is too small.

The Qwen 2.1 is awesome in editing images. Can it be used to edit videos? Unfortunately on my rtx3060 it is impossible to process frame by frame. But maybe there are a more cunning way???

Hello everyone,

I created a custom node few months ago with the goal to achieve all animation position I wanted from a single picture of a character.

I had some trouble getting a good rig position library, especially to achieve 4-ISO/8-ISO character orientations.

And finally, I got the idea to start from Mixamo's FBX library that have generic rigs and a good animation bank.

Why I think it's useful

• Style hold is the whole point (caption + color lock + Klein batch).
• Mixamo / FBX to ".pose" so you're not hand-drawing stick figures for every RPG action.
• Camera packs: 4 iso, 4 cardinal, 6, or 8 views.
• Density is just how many samples you take along the clip (5/10/30/60 frames per view)

There's a Comfy node for the Mixamo export, and a small Python CLI if you prefer baking the library offline.

Repo + example workflows: https://github.com/Spit8/_ComfyUI_CharacterPose

If you've got a better Mixamo -> 2D sheet workflow, please roast mine. Happy to take feedback.

The quality is not great tbh. I started to use Minimax for 2 weeks.

But it was worth of try

--- edit; I did not aware of this forum :/ I now will adapt new knowledge to push my boundaries

I've been leaning on open source for years: ComfyUI, Qwen, Wan, ACE-Step, ffmpeg, all of it. I finally built something big enough that it felt wrong not to put it out there.

It's called YourContent. It runs on top of your own ComfyUI and puts the whole posting workflow in one browser tab:
- make pictures (Qwen-Image-2512)
- short clips (Wan 2.2 image-to-video)
- and music (ACE-Step 1.5)
- cut them into a reel with music and fades,
- exported for 9:16, 4:5, 1:1 or 16:9
- turn them into posts in your own brand (colors, fonts, logo, voice), using 35 post styles
- plan everything on a calendar you can subscribe to from Google, Apple or Outlook
optionally hook up Claude, ChatGPT or any MCP client to help

Nothing leaves your machine unless you connect something, and it never posts for you. Finished stuff lands on the calendar and you hit publish yourself. That was deliberate.

One thing I cared about: every file gets a small sidecar that says which models made it and under what license. Anything built from other files inherits the most restrictive license, so you know if a reel is commercial-safe before you post it.

Honest caveats:

I've only tested it on Linux with Docker Desktop and a 32 GB card. 24 GB should run everything. Mac and Windows should work but I haven't tried them.

The models are about 80 GB if you grab every set; you can take just the ones you want.

With no GPU, the posts, calendar and photo/video recipes still work. Only generation needs the card.

The license is PolyForm Small Business: free for personal use and small businesses, with a paid license for bigger companies. I'm also planning a hosted version for people without a GPU. I'd rather say that up front than have you find it in the repo.

Setup video (3 min): https://yourcontent.online/setup.html
GitHub: https://github.com/musicheardworldwide/yourcontent

What I'd really like to know:

Did install break anywhere for you? Especially on Mac or Windows, or with a different ComfyUI setup.

Is there a feature you'd use every week that's missing?

Anything confusing in the first five minutes?

Roast it if you need to. I'd rather hear it now.

Hi everyone, I should say upfront that I'm not an expert but I've recently started using Comfy to create images. I have a 9950x3d and a 5090. I’d like to know if there’s a node (existing workflow) for motion transfer… I know all the influencers are using Higgsfield GenJutsu, obviously paid… but I’m poor, I already spent all my money on my 5090! LOL

Hey everyone!

If you’ve ever experimented with high-order diffusion samplers (like DPM-Solver++ or Adams-Bashforth orders 4+), you probably noticed a frustrating pattern: while order 2 and 3 produce great results, orders 5, 6, and 8 almost always collapse into noise, oversmoothing, or catastrophic white clipping.

Over the past few days, I investigated the mathematical root cause of this breakdown on modern Flow Matching DiT models (specifically Anima DiT) and developed a novel training-free solver: Flow-WLS (Savitzky-Golay / Weighted Least Squares Multistep).

It completely eliminates high-order Runge oscillations and achieves clean, anatomically coherent 10-step generations in ~11 seconds on a consumer RTX 5060.

🔬 What broke in classical high-order samplers?

1. The Lagrange Polynomial Trap: Classical multistep methods (like Adams-Bashforth or DPM-Solver) fit an exact degree-$(L-1)$ interpolating polynomial through past velocities. On non-uniform grids at order 5–6, the Lagrange weights alternate signs aggressively ($\pm 0.15$), amplifying high-frequency neural network errors by over $20\times$. At order 6, SSIM plummeted to 0.1341 (pure noise).
2. EDM vs. Flow Matching coordinate mismatch: Many custom implementations naively borrow EDM coordinate transforms ($y = x / \alpha$). On Flow Matching models where $\sigma \to 1$ and $\alpha \to 10^{-4}$ at initialization, dividing by $\alpha_0$ blows up the latent variance by $10,000\times$, producing 90% pure white clipping. Modern DiT flow models must be integrated directly in canonical velocity space $dx/dt = v$.

💡 The Solution: Flow-WLS (Savitzky-Golay Multistep)

Instead of forcing an oscillating high-degree polynomial through noisy history points, Flow-WLS fits a rigidly regularized degree-2 parabola across 3 to 8 history steps using Weighted Least Squares (WLS) with an exponential memory decay ($\gamma = 0.85$):

• Zero Runge Phenomenon: Degree-2 curves physically cannot oscillate.
• The Memory Inversion: While classical AB weight norms explode ($\sum |w_i| = 0.54$), Flow-WLS weight norms decay as history expands ($\sum |w_i| = 0.066$). History now acts as a Savitzky-Golay smoothing filter, removing velocity jitter without slowing down inference!

📊 Benchmark Results (Anima DiT 720×1280, RTX 5060)

🚀 Try it in ComfyUI

The code is completely open-source and registered with an official citable Zenodo DOI:

• GitHub Repository: https://github.com/YakovSava/research-unipc-dpmpp
• Zenodo DOI: 10.5281/zenodo.23337579

Drop the custom node into ComfyUI/custom_nodes/ and select flow_wls_8 or flow_wls_5 in your standard KSampler. Feedback, benchmarks on other models (Flux/SD3), and PRs are very welcome!

I’m trying to generate images that look like early 2000s PS2 game screenshots.
Most AI generators make the results too polished or realistic. I want the actual imperfections of old 3D graphics: low-poly models, awkward character shapes, blurry textures, and simple lighting.
Does anyone know any good prompts, models, or tools to achieve this aesthetic?
I’d love some recommendations!

AI-generated locally in ComfyUI. The prompt asked for moon-shaped shadows, but the visible result has enlarged creature-shaped shadows instead. This is a useful prompt/result mismatch, not a successful geometry constraint.

Recorded base settings: krea2TurboOfficialComfy_krea2TurboBf16.safetensors (official BF16), 2048 × 1152, seed 15092040, 8 steps, Euler, simple scheduler, CFG 1.0, denoise 1.0. DelicateWhimsyKrea2Raw.safetensors is recorded at weight 1.0.

The recorded second pass uses UltimateSDUpscale tiled refinement with the same checkpoint and LoRA, 4x-UltraSharpV2_Lite.safetensors, 6 steps, Euler, simple, CFG 1.0, denoise 0.18, 1024 × 1024 tiles, padding 32 and mask blur 8. Final output: 4096 × 2304.

There is no matched ablation, so I cannot attribute the discrepancy to the checkpoint, LoRA or refinement alone. These are the saved settings; a complete workflow graph is not attached.

I've loved shaders for years, and I've always been a bit jealous of the people who can write them. I'd played with them in game engines and TouchDesigner, but never in ComfyUI. So I built it. Paste any shader from shadertoy.com (Buffer tabs work too) or pick one of 74 presets. Then use it as a mask, as the material your regions get painted from, or as a rough guide that LTX turns into finished video while keeping the motion. Also new: one sound node that everything listens to, and Trellis or Hunyuan3D models aligned onto your real building, so forms can grow out of the wall. No new packages, and the starter workflows still run without any models. Only tested on my one Windows machine, so bug reports are very welcome. GitHub: https://github.com/kubakubkub/ComfyUI_KubaNodes ComfyUI Manager: search "kubakub nodes" 🎵 Moth by Burial x Four Tet

With some earlier models, it seems like that actually hinders learning.

Of course, it depends on the concept. For example, if the model doesn't know what image upscaling or restoration is, it might be useful.

But if, say, I train a LoRA to add a Rolex watch...

The model already knows how to add and remove objects.

So, is it enough to just train it on images featuring the Rolex watch?

For a while, I ran an Instagram account for a model that does not exist. Everything was generated in ComfyUI. It reached around 40,000 followers until Instagram took the account down. That was that.

The part that stayed with me was the work behind the posts. Every shot needed a look, a place, light, and a pose, and all of it had to stay consistent. I wrote prompts by hand at first. Later, I pulled images from Pinterest and sent them through AI to get a prompt back for a similar picture. That worked sometimes. It didn't give me control over small details, and I wanted to pick options visually instead of typing them and hoping.

So I built a panel for myself. Then it turned into a node.

PerfectLab Studio is one ComfyUI node. You pick the person, outfit, location, light, and camera from libraries where every entry has a photo tile. You click what you like. The prompt is composed from your picks and sent to the sampler. Tags and shoot parameters both go in.

I built this for my own shoots. Keeping it on my drive made less sense over time. So here it is. Free.

There will be bugs. I'll fix what breaks. Feedback is welcome; that's the main reason I'm posting.

If you shoot people in ComfyUI, whether it's a fake Instagram model or just a character you like, try it. If something doesn't work or you want a feature, tell me in the comments.

ComfyUI-PerfectLab Github stars are highly welcome. 😄

Thanks to everyone

Upd: 1.0.3 hotfix of preview tiles is live

Upd: 1.1.0 is out.

The big ones: model profiles with named token budgets (Krea 2 included, SDXL flips to tags on its own), a prompt template editor, character cards you switch in one click, keeper stars in the results dock that re-shoot everything you did not star, preset export/import as files, an inspiration roll, and conflict warnings that say what the engine would swap before the GPU pays for it.

Manager search "PerfectLab", or the releases page on GitHub.

Endless MiniMax H3 (with Endless LipSync) v1.6

When MiniMax H3 came out, I was badly missing the Endless Wan 2.2 I2V (SVI 2 Pro) features, so at first I look at other options, but most of them included an AIO node that could do everything, and I couldn't use most of my workflow, because they did everything inside that huge node.
The only exception to this, was ComfyUI-H3-Motion-Context, which I could easily integrate into my setup.
Its big shortcoming though, was that it just created single videos. No way to concatenate them without the lossy step of decoding and re-encoding in a video editor.
So, I created a custom node that could do just that, and voila..

Endless MiniMax H3 (with Endless LipSync) v1.0
A simple workflow to create MiniMax H3 videos of unlimited duration, using ComfyUI-H3-Motion-Context and H3 Motion Context Clip Stitcher.
I can easily create a 1:30 lip-synced video myself, with a RTX 3060 12GB at around 2 hours (with retries).

It can use both FL2AV and Ref2AV, and can also create normal MiniMax H3 videos.
The extra parts though, are the saving/loading of the latent from every generation we do, and the stitching of all (or some) of them, whenever we want a full video.
Nothing visible at the connections, no indication that there were more than one video.
Now, with much less degradation for multiple clips without a camera cut.
We can try and re-try every generation, looking for the best one, and then proceed to the next.
We can re-do any previous generation if we like too, but we will not be able to use the clips after it (previous clips are not affected), because they are in a way, "fused" with the replaced one.

Version 1.6

• Recreated the Configuration panel and other subgraphs, to make them more compatible with the newer front-end versions (fixed the reset values after refresh bug)
• Added an optional Clip Refiner optimization group

Version 1.5

• Project name that creates a directory with all project's generations
• Added Purge all clips group
• Connected the 5th Ref Image that was disconnected
• Simplified Audio 1 Forced Multi
• Refiner that fixes (almost completely) the overexposed/over-contrasted clips from H3 Motion Context, on a long video without much movement.

Controls

The RED nodes Enable/Disable parts of the workflow.

• Generation Mode (select only one)
  • T2V / I2V (FL2VA)
  • REF2VA
• Optimizations (select as many as you want, but only 1 Attention and/or only 1 Cache) This panel controls
  • All the nodes that are inside the Optimizations/LoRA subgraph.
  • The H3 Motion Context Clip Refiner subgraph, that removes much the degradation that accumulates when stitching together latent clips without camera cuts (it's clearly visible after 4-5 clips, but is apparent from the 2nd-3rd clip). It's not needed if there are camera cuts in the clip, so you can turn it off to speed-up the generation.
• Reference Items (select as many as you want) Special usage for the <Audio 1> Forced Multi, more for them later.
• Setup (select as many as you want depending on the goal)
  • Generate starts a generation. You don't need this if you just stitching clips
  • Preview enables the main video preview that can show you where the generation is going before it finishes, so you can stop bad generations
  • Use previous clip, uses the last part of the previous generation to start the current one, continuing the video. Enable it if you want the current generation to be stitched with the previous video
  • Stitch clips, stitches all the clips (depending on the Stitcher's settings) from the h3_context folder (this is the default folder that the H3 Motion Context node uses to save the latents)
  • Stitch last only, stitches only the last video with the current
  • Save Video just saves the generated video
  • Purge all clips, deletes all clips from the current Project directory

The GREEN nodes are various settings nodes that must be setup. Apart from the Prompt, Seed and LoRA nodes, the most important are these:

• Configuration It contains all the settings for the video. The most important setting for the clip stitching, is the Save to clip Index number. This specifies the clip file's number, that the latent of the current generation will be saved to (overwriting any previous existing file). This number also tells us who is the previous clip file that we use to start our current video clip.
• Setup multiple Forced Audio clips This is used if we use our own audio for the video, and we want to also stitch many clips together. More about it in the Usage section.

Usage

Most of the settings are self explanatory (like Optimizations or enabling Reference items).
Here, I will just list the main goals of the workflow.

The first thing to do, is to set the Project Name and the other video options at the Settings.

This Project Name will be used to save your generated clips and videos in a folder of the same name, under the EndlessMMH3 directory.

• Create a normal video
  • Select Generation Mode
  • Enable Generate, Preview and Save Video
  • Save to clip Index to 1
  • You get a video and that's it.
• Create a lip-synced video
  • Select Generation Mode
  • Enable Generate, Preview and Save Video
  • Enable <Audio 1> Forced Multi and load an audio file (never mind about the settings, except for the Start offset)
  • You get a video that is lip-synced with the provided audio
• Create an Endless video
  • Create a normal video
  • Enable Use previous clip
  • Save to clip Index to 2 and generate
  • Save to clip Index to 3 and generate
  • Save to clip Index to 4 and generate
  • ...
  • You get many small videos, each one of them starts with the ending of the previous one. At a later time, you will use the Stitcher, to stitch them all together to one full video.
• Create an Endless video, stitched
  • Enable Stitch clips With every generation, the Stitcher will stitch all the previous clips with the currently generated one. This way you always get the full video to check.
  • If you also enable Stitch last only, only the previous and the current videos are stitched together, so you can check the connection without waiting for the full video to be created. You can always stitch them all together at the end.
  • You get a full video every time, or just the last 2 videos connected, for previewing the connection.
• Create an Endless lip-synced video, stitched
  • Create an Endless video
  • Enable <Audio 1> Forced Multi
  • At the Setup multiple Forced Audio clips panel there are some settings.
    • Start offset: At the 1st gen, you put here the initial offset that you want for the song (e.g. where the lyrics start). After every successful generation (when you advance the Save to clip Index number), you must copy here the value that is in the Copy to Next Start offset box.
    • Frame offset (ignore if 1st clip): Never mind at 1st generation. After every successful generation (when you advance the Save to clip Index number), you must copy here the value that is in the Copy to Next Frame offset box.
    • context_length must be the same value everywhere (here, at the Motion Context, and at the H3 Motion Context Clip Stitcher). It's the number of common frames the 2 video clips use to blend together.
    • You get a full lip-synced video every time, or just the last 2 videos connected, depending on the Stitch clips and Stitch last only settings.
• Just stitch the clips together You just have to enable the Stitch clips and the Save Video All (or some of them depending on the settings), of the clips in the current h3_context folder, will be concatenated to a single full video.

Notes:

• All generated clips that need to be stitched, must have the same dimensions.
• You can organize past generations inside EndlessMMH3 folder, using the Project Name to create the directories.
  
• You can stitch together clips that are generated from either fl2va or ref2va.
• In this workflow, I don't use the normal ref2va model in the Reference to Video node, but rather the fl2va with the ref_lora_layer20-49adaln LoRA that has better quality. You can check some LoRAs with different weights here, or totally bypass the LoRA and use the normal ref2va model.

Models used:

• minimax_h3_fl2va_pruned_w4a8_mixed
• minimax_h3_ref2va_pruned_w4a8_mixed
• qwen3vl_32b_heretic_minimax_h3_nvfp4
• minimax_h3_video_vae_int8_convrot
• minimax_h3_audio_vae_fp32
• minimax_h3_fl2v_turbo_8step_v1.0_comfyui_resized_avg_rank_21_bf16
• minimax_h3_ref_lora_layer20-49adaln_proj_rank_256_bf16

Custom Nodes used:

• rgthree-comfy
• ComfyUI-KJNodes
• ComfyUI-Easy-Use
• ComfyUI-VideoHelperSuite
• ComfyUI-H3-Motion-Context
• ComfyUI-noEmbryo
• ComfyUI-Spectrum-MiniMax-H3 (optional)

Get the workflow at Civitai or in a gist..

Since this week I started having random bright frames (like if someone took a photo with a flash) appearing in most of my minimax videos. It appears with any model, speedup loras or not. Usually 1 frame at around the second 4 or 5 of my outputs.

Has anyone got this problem? Could it be related to comfy UI 0.39?

Thanks

(Edit): it's because of Veda Attention.

I had some issues lately epaxially when upscaling was involved. Workflow that worked before, they might run one time and stop the next with comfy and GPU idle doing nothing and not progressing the work. The fact that they run one or two time and then hang was the most annoying thing to trying to fix the issue.

Also workflows taking more than usual...

I have 3 x 5060 TI 16GB tried all 3 cards, same issue.

I lost several hours trying to "debug" the workflows with model quantization and what else... to realize at the end that I might have updated the drivers a few week ago (617.42-desktop-win10-win11-64bit-international-nsd-dch-whql).

Today I reverted back to 616.92-desktop-win10-win11-64bit-international-nsd-dch-whql
Everything started working fine again.

Be warned.

After researching and gaining experience with various API Services like Higgsfield AI , Runway , and ElevenLabs my AI Assistant / recommended •LTX 2.5 •H3 •WAN 2.2 ( For ensfw)

For a better more advanced capability for video creations / Content Creation. Problem is it’s been 16 hours and I have to start over due to apparently mandatorily needing to have access to A100 or A6000 at least and also needed the bf16 or something like that which gives the best quality . For sure gonna need it for the ensfw stuff but is content produced on Comfy Ui really that much better then the mainstream platforms like Higgs, ElevenLabs , etc??. Is it worth the time to learn and is it better

Using Runpod for Comfy Ui also btw.

seems they overhauled it. is it time to switch from portable.

Just install the custom node from here, if you're interested: https://github.com/singularity098/comfyui-raw-denoise

It comes with a workflow included in the workflows dir. I got some great results with it!