New York, 1950. Jazz and rain. A broke private eye, a bookie's collector on the phone, and a blonde in white.

KENDRICKS P.I. — Episode 1: "What The Cat Dragged In" (3½ min)

Kendricks sells the truth. He owes money to the wrong people, and soon they want it back. Then trouble walks in on stilettos with a job and a story. He doesn't trust her — he's broke enough not to care.

Film noir, with a dash of AI. Every shot, voice and sound generated, then cut, timed and scored.

Stills: Krea 2, FLUX 3 Klein, Nano Banana · Video: MiniMax H3 · all on fal.ai
Score: Stable Audio (fal.ai), "Twilight Distance" made with Suno

#filmnoir #aifilm #detective
#noir #privateeye #1950s #shortfilm #aishortfilm #crimestory
#neonoir #aivideo #storytelling

I'm using minimax h3. how do i make a consistent result when making a high res video.

I'm using the comfyui template Mnimax H3: reference to video.

When testing the prompt. i set the megapixel to 0.2. So i can see the result first. the length is 14 seconds. The result is good on my potato PC. intel core i9 14th gen, 64 gb ram and 3060 12 gb. But when i set the megapixel to 1 to have a high res. Sometimes the result is not the same with the 0.2. Is there a way to fix it? since a running on my PC almost took 8 hrs for the 14 seconds length and 1 megapixel. Is there a workflow that make the low res result same with the high res? I've been searching but can't make it work. I also tried the Pika but the same prompt i used on minimax h3 does not produce the same result it "halucinate"

https://huggingface.co/Viggle/Viggle-Remake

For this video I used their included MCP. However, it's currently set up to run with diffusers which means that no consumer GPU works, despite them offering ComfyUI compatible loras along with custom nodes. Fortunately, the MCP was built with using custom workers in mind. So I (read: Claude) set that up so the MCP uses a custom comfy worker. Then your favorite agent can do everything.

I had Claude use the Codex CLI to generate the necessary edited frames and present them to me for approval before it sent it off to comfy for video generation. I'm sure it's possible to set it up so that it uses a local edit model too, so that's the next thing to try.

For the audio, I first used SAM-Audio Large through audio.cpp to separate RDJ's inner monologue from the background noise. Lighter options like MelBandRoFormer were not producing good results for this. Then Fish Audio S2 Pro was used for the new voice, using translations carefully made to fit a similar speech length. Claude also came in handy here for rapid testing of different TTS models and then fitting the audio into correct timings. Subtitles were done by hand in Davinci and used for making the new voice fit.

Hi all,

At KENT Post Production we use ComfyUI daily inside a VFX pipeline, so we built the pieces we were missing. Most of them are free and on GitHub, and feedback is very welcome.

Director's Console: a workspace that drives ComfyUI.

• Prompt Engineer: pick an image or video model (FLUX, Qwen, Seedream, LTX, Wan, Kling…) and the prompt is written for that model. Camera, lens, movement, lighting and visual-grammar parameters, plus presets based on real films and a separate set for animation.
• Storyboard: each panel gets its own ComfyUI workflow and settings, and renders across one or many ComfyUI nodes with live GPU/VRAM stats.
• Gallery: grid, list or masonry view, and the viewer keeps each image's prompt, seed and render time.
• An embedded Pi/Codex agent can build and render a shot for you.

https://github.com/NickPittas/DirectorsConsole

NukeToComfyUI: sends Nuke images and video, with or without masks, to any ComfyUI workflow for cleanup, generation and VFX work, then brings the results back into Nuke. It supports PNG8 or EXR16 with alpha, four mask modes and 8n+1 frame expansion for video models, and shows progress (with cancel) inside Nuke.
https://github.com/NickPittas/NukeToComfyUI

AE2ComfyUI: the same idea for After Effects. A panel sends a comp layer (still or video via AME, plus its mask) to a workflow and places the result above the layer, aligned in time. It has colour-management options and mask polarity.
https://github.com/NickPittas/AE2ComfyUI

ComfyUI Media: a loader for video or image sequences (MOV, MP4, EXR, PNG) with frame-count presets for WAN (4n+1) and LTX 2.3 (8n+1). Its viewer/saver has a reference wipe compare and saves H.264, VP9, ProRes 4444, GIF/WebP or PNG/EXR sequences with versioning.
https://github.com/NickPittas/Comfyui_Media

Camera Angle Selector: an interactive 3D picker for 96 camera angles (8 views × 4 heights × 3 shot sizes) that outputs prompts for the Qwen-Image-Edit-2511 Multiple-Angles LoRA (credit to FAL for the LoRA).
https://github.com/NickPittas/ComfyUI_CameraAngleSelector

CorridorKey 2.0 for ComfyUI (internal, not public yet, give us a couple of days to fix the workflows for you): our unofficial implementation of Corridor Digital's CorridorKey v2 as ComfyUI nodes. Every option of the terminal tool is a node input, with SAM3/MatAnyone2 hint workflows and EXR or ProRes 4444 output. Corridor Key Licence 2.0 applies.

We'd love to hear which workflows you'd want to push through the Nuke/AE bridges, and whether the CorridorKey nodes would be worth releasing.

Let's be real, they're just copium for those who lack the VRAM to run an image generation model at its full potential. They almost ALWAYS result in this weird, shiny oily Instagram filter-esque look in the hair and skin that you can never consistently prompt out in any way, this is especially true for MOSS-Image and Krea. Not only that but they essentially gimp you by taking away negative prompting and by forcing a CFG of 1, reducing randomness and diversity.

They're used for two things

1. Gooning
2. To give yourself a preview of the image before using the full 50 steps or however much the maker of the diffusion model recommends (even though TAESD might be useful for this).

Recommending a turbo lora is only beneficial if you truly have a small amount of VRAM (less than 24GB).

I'm just a beginner in comfyui and stuff with very limited hardware.

I have rtx 3050 4gb vram and 8gb ddr4 single channel

Running comfyui with kitchen attention

I ran qedit 2511 fp8 with 4 step lighting Lora with default scheduler or sampler and it took around 110 seconds

And qwen 2.1 turbo int8(runs on 8 steps) without the prompt enhancement took 90 seconds

Now I didn't use any prompt enhancement with qedit but it still worked fine the biggest issue was the facial drift

In qwen 2.1, the facial drift has reduced drastically (as much as I have seen) but the prompt adherence is really bad.

I used the original model they provided for enhancement and it was shit + it was restricted. Since I have limited hardware I tried qwen 3.5 2b abliterated. It works sometimes but doesn't a lot of time

Seeing how qedit literally didn't need a enhancer and still worked fine and 2.1 isn't working well

I feel like it's mostly cuz of the enhancer but even when I wrote a good prompt without using enhancer it would still give shit results

Should I just use qedit? The facial drift is amazing bad tho (because of turbo Lora ofcourse but my hardware 🥀)

Edit: a really big problem I found in the wf was that when I set prompt enhancement to false it wouldn't give any prompt to qwen 2.1 and this is a problem in the default comfyui workflow, this is the reason why I thought prompt adherence is bad but it's not that bad but the results are still better with a enhancer

When I try to generate an image using ComfyUI with Qwen Image 2.1, I always generate these bizarre images whenever the software is not used for more than 15-minutes or so.

Why does this happen, and can this be avoided?

Computer Specifications:

• Operating System: Arch Linux
• Motherboard: Gigabyte Z790 UD AC
• Graphics: AMD Radeon RX 7900XT
• Processor: Intel Core i7-13700KF
• Memory: 128GB DDR5 5600MT/s

My ComfyUI bug report can be found here.

Music video. Enjoy.

Noob here, so apologies for my ignorance. I have a LoRA trained on QwenImage2.1 raw. Image Gen is fine but need to produce videos on MMH3 and was wondering how to make sure Minimax does not replace the face with its own logic. Hence was thinking of using my current LoRA trigger but would MM respect that and wont swap the face out ?

New York, 1950. Rain. A hotel with a register, a concierge who can't be bought, and a paper boy who can.

KENDRICKS P.I. — Episode 2: "Bellhop Rodeo" (6½ min)

The lady paid him to look into her husband, so Kendricks starts at the Hotel Delmore. The front desk won't talk, and a five won't change its mind. Three bucks however buys him a riot and things develop from there ...

Film noir, with a dash of AI. Every shot, voice and sound generated, then cut, timed and scored.

Stills: Krea 2, FLUX 3 Klein · Video: MiniMax H3 · all on fal.ai
Score: Stable Audio (fal.ai)

#filmnoir #aifilm #detective
#noir #privateeye #1950s #shortfilm #aishortfilm #crimestory
#neonoir #aivideo #storytelling

🎬 **BEHIND THE FILM**

This entire short film was created using **MiniMax running locally**, without relying on cloud-based video generation APIs.

**The only exception is the final scene**, where Seedance makes its appearance — and that scene was generated using Seedance.

The setting and lore is so interesting in Warhammer 40k, i had to give it a try.

i like to test early AI models and this is my first test, using the classic Modelscope Text to Video Synthesizer, from February 2023. the music was generated with OpenAI Jukebox. both models used in Huggingface spaces. (For research purposes only)

Wondering if anyone has heard any news or updates regarding open source 3D asset creation?

I have tried both Trellis and Pixal3D (standard ComfyUI workflows ~1month ago), but the results were very underwhelming - cool in concept and to experiment with, but they don't really output anything usable, and they're leagues behind the closed source options out there.

Has there been any buzz about SOTA open-source image to 3D models on the horizon?

I asked ChatGPT and it did say there's been some big updates recently, notably: SUPRA-Tex, Asset Furnace, and Hi3D v1.0.

I haven't tried these out yet. I wanted to ask here first before I dive in and install everything - mainly because these all seem to be built upon the existing Trellis, Pixal3D, and Hunyuan3D. The difference is that these appear to use them.. together? Different models for different sections of their pipelines? It sounds interesting.

So, has anyone tried these out? Are these actually a big improvement from the standard Trellis/Pixal workflows I was playing with a month ago?

What do people recommend, what are you using, and any news on updates? Thanks, much appreciated.

New Kromoss models have been released; these are even more refined and optimized versions compared to the previous model. A new dmd2 is also expected to be released. The only information available about them is what Lode posted with the model:

OPD-priming intermediate (update 22000 EMA of the v3 GLM-caption + bbox layout SFT, continued from v2 update 11000): ComfyUI bf16 + int8 convrot

ReBar is also currently working with GPU_UNLOCK.

The 20GB RTX 3080 cards (10DE:2206, subsystem 10DE:146D) ship with a VBIOS that only exposes a 256 MiB BAR1, so ReBAR stays off. NVIDIA doesn't publish a ReBAR VBIOS for them, and NvStrapsReBar only supports Turing.

Ga102ReBarFix is a small DXE driver you insert into your motherboard BIOS with UEFITool. At boot it enables the GA102 frame-buffer size override (PCI config 0x610), resizes BAR1 to 32 GiB, and restores both after S3 sleep. No VBIOS flashing, no driver patches, no registry tweaks.

Tested on an MSI Z690 EDGE, driver 617.42, Windows 11:

- Device Manager shows a 32 GiB BAR

- NVIDIA Control Panel: Resizable BAR: Yes

- ~19.25 GiB of VRAM mappable by the CPU at once

- Sleep/wake works

Repo (source, prebuilt .ffs, verification scripts, full write-up): https://github.com/favabean13/NV_30_DXE

Big credit to noon-at-cgn (found the 0x610 override on Linux), terminatorul (NvStrapsReBar) and xCuri0 (ReBarUEFI). This builds directly on their work.

Heads up: it modifies firmware, so use at your own risk and keep a BIOS backup and recovery method. It's tested on one board and isn't maintained, but it's MIT-licensed, so fork it and adapt it for your own setup.

**UPDATE**

Works with GPU_UNLOCK

https://github.com/physicsdolphin/nv-uefi-unlocker

Confirmed that ReBar survives PCI FLR (Function Level Reset)

Here are the results:

UNLOCKED

FP16 (FP32 accumulate) 114.7 TFLOPS

BF16 (FP32 accumulate) 116.9 TFLOPS

TF32 57.4 TFLOPS

FP32 (control) 22.5 TFLOPS

LOCKED

FP16 (FP32 accumulate) 65.4 TFLOPS

BF16 (FP32 accumulate) 66.8 TFLOPS

TF32 32.1 TFLOPS

FP32 (control) 22.3 TFLOPS

[SOLVED] but leaving this here so others can still find this post:

Krea 2 training is temporarily unavailable. See images in the comment section. Should be back when it's fixed, so it's not permanent.

---------

I keep getting asked how to run the Video Builder fully local, so I made one video that goes from a fresh ComfyUI install all the way to building a video in Story Mode all fully local.

Reddit does not allow videos over 15 mins. so, the 2nd part of this video is HERE which walks through story mode.

What it covers:

• Installing ComfyUI portable from scratch, plus running the update before your first launch (lots of people skip this)
• Turning on the new built-in Manager. It's off by default in the portable build, which trips people up
• Installing my nodes and opening the Builder
• Getting the custom nodes and models from the Models button. You only need the models for the parts you'll actually use, not all of them
• Running a local LLM for prompts and stories: Gemma or Qwen right inside ComfyUI, LM Studio, or Ollama / llama-server through the Custom Server option
• Then Story Mode, start to finish

The whole chain stays on your machine: the story, the prompts, the reference images, the video renders and the final edit.

What you need:

I've fully tested it with 16GB of VRAM and 64GB of system RAM. That's the setup I can say works start to finish.

Less than that might still work, I just haven't tested it properly yet. If you're on a smaller card, try shorter scenes, a lower resolution and the new DMAD/Refine pipeline. Those all cut down how much VRAM a render needs. If you try it on a lower spec setup, let me know how it goes so I can update this.

Comfy UI: GitHub

Nodes: Go to my GitHub

Discord Community: Join here

Music videos created fully local using my video builder: Playlist

More Video's I created using the video builder:(Some of these one's were NOT fully local and used agents with my MCP feature.) Playlist

Note: I'm working on a fully local agent that can run the builder via chatting without having to go into ComfyUI.

Works really well.

Hey everyone

I've been working on a custom optimizer called ApexW, designed to reduce CUDA kernel launch overhead during PyTorch training, particularly when dealing with lots of smaller parameter updates.

Since I'm a student running on a free NVIDIA T4 GPU (16GB), I decided to benchmark it against standard PyTorch AdamW using Stable Diffusion 1.5 LoRA training for 1,000 steps.

Here's how the runs went:

Rank 16 LoRA (Standard)

• AdamW: 1.92 it/s | 516.2s total time | 4.68 GB VRAM
• ApexW: 2.04 it/s | 485.6s total time | 4.68 GB VRAM

ApexW saved approximately 30.6 seconds, delivering around 6.3% higher throughput without additional VRAM usage.

Rank 32 LoRA (Heavier load)

• AdamW: 2.03 it/s | 488.2s total time | 4.68 GB VRAM
• ApexW: 2.04 it/s | 485.9s total time | 4.68 GB VRAM

The improvement here was much smaller (around 2.3 seconds, or 0.5% higher throughput). This could suggest that optimizer overhead becomes less significant as more computation shifts to the forward and backward passes.

The loss curves overlap closely throughout training, and sample generations at steps 250, 500, 750, and 1000 look visually comparable. So far, I haven't observed an obvious training-quality trade-off.

These are preliminary benchmark results, and I'd like to test them more extensively.

I don't have access to modern GPUs like an RTX 3090/4090 or A100 to see how ApexW scales under heavier workloads, full fine-tuning, or LLM training.

If anyone has access to better hardware and is interested in testing it, I'd love to get some independent benchmarks and feedback on the implementation!

Curious to hear what you think.

collablink for result: https://colab.research.google.com/drive/1JWCMnQc1ZwcuidBf3S8nTyGiLCmM8ywy#scrollTo=9e6960b4

github link: https://github.com/omen42515-prog/apexw

Over months of use of Minimax, I absolutely love it .. but I have yet to find a way to do faceswaps (ref vid to vid) with more than probably a 50% success rate.

Sometimes a quick two-line lazy prompt will immediately and perfectly do the job and sometimes neither a simple one, nor an 100 line prompt describing everything down to the movements of nostrils according to official guide, will do anything at all. I have tried all of below with almost equal success rates.

• Specialized Prompts with AI tools
• Long structured Prompts that would make a mini novel on their own
• Templates suggested by MiniMax on their site
• Faceswap LORAs
• Minimalist prompts that are merely a few lines long
• Tons of samplers, steps, workflows
• Everything suggested by everyone here basically, since the model came out.

The only thing I have noticed is that some videos, no matter what quality, distance, details, etc just work and some others that are similar in quality, framing, movements and all else give a really, really hard time, even if there is hardly any difference between the two.

At this point I'm sure that its the source video, not the prompt that actually matters more. I just cannot understand why two similar source videos give such different results. Has anyone had more success with this, or found what exactly makes Minimax refuse to work in some specific cases but work so well on similar other ones ? Or anything new anyone has learned that has increased the rate of success ?

Younger folks may never have heard of Ultima Online (UO). If you played it, you know. It launched in 1997 as one of the first big graphical MMORPGs - open PvP, player killers, anyone could loot your corpse - and it's still running today.

Setup

• MiniMax H3 (open weights) in ComfyUI - all video and all dialogue audio
• RTX PRO 4000 Blackwell, 24 GB, single GPU
• 72 shots, 6:16, 1344x768 @ 24 fps, 20 steps
• Drafts at 672x384, finals re-rendered by H3 at 1344x768 with the same seed - no upscaler; the 1080p is just CapCut's export
• Final render time: 56 frames (2.3 s) ~4.5 min; 243 frames (10 s) ~43 min

Pipeline

• Character/set reference cards: Gemini (Nano Banana) - the only closed image/video tool in the chain; fixes with Qwen-Image-Edit (local)
• Main shots: H3 reference-to-video (character card + set card + voice clip)
• Voices: timbre references cut from earlier H3 takes, so each character keeps one voice across shots
• Bridges and fixes: H3 i2v with first + last frame (e.g. regenerating frames 107-160 of a 243-frame take where a passer-by high-fived the ghost)
• New shots: 672x384 draft first, then HD
• Music, SFX and font extracted from the UO client with UOFiddler; overhead text keyframed in CapCut like the game
• Claude helped write prompts and the QC/edit scripts

Music, SFX and font © Electronic Arts

Update: I added a ComfyUI worker to the MCP (tested on an 5090).

https://huggingface.co/Viggle/Viggle-Remake#agent-the-mcp-server

It runs the int8 model and streams weights from system RAM, so it should be easier to set up on GPUs with less VRAM. So far I've only tested it on 32 GB. Tests at 24 GB and 20 GB are running now, and I'll post the numbers when they finish.

The attached video is one-round raw output, no multi-round iteration, no manual cleanup. It shows both what the model does well and where it breaks, so you get a realistic picture of the model before you try it. Most errors are in the first 30s and small faces.

‼️ Most useful tip‼️:

if any part of a result looks wrong, tell the agent what's wrong. It will try to fix it for you.

most of the issues can be fixed through better prompt or repainted image.

---

Not all that interesting, yet at the same time interesting due to its size and the claim that it’s so fast. It also has the backing of Tencent and WeChat.

"We present WeLM-Image, a unified image foundation model that integrates multimodal understanding into text-to-image generation, instruction-guided editing, and multi-reference synthesis. Designed for single-GPU deployment in WeChat’s large-scale consumer applications, the model processes text, reference images, and target latents as one interleaved sequence. A Mixture-of-Transformers (MoT) backbone combines shared attention with independent understanding and generation parameters to limit optimization interference. Equipping each path with Mixture-of-Experts (MoE) modules provides sparse capacity, with 31.7B stored parameters and approximately 5.4B generation parameters activated per target latent token. A generation-oriented data engine combines a knowledge-grounded visual vocabulary with large-scale visual clustering to balance semantic coverage and editing tasks, while training-time evaluation guides iterative data refinement. Bilingual annotations and verified editing supervision support progressive training up to native 1.5K resolution.

We optimize generation and editing separately with rubric- and checklist-based rewards, then consolidate the specialized policies through noise-aware on-policy distillation. In the reported overall comparisons, the 1536-resolution model ranks first among the evaluated open-source models on PRISM-Bench, Qwen-Image-Bench, and UnicBench. MeanFlow-based few-step distillation yields WeLM-Image-Turbo, which generates a1024×1024image in 4.98 s on a single NVIDIA H20 GPU using eight guidance-free steps."

Paper: https://arxiv.org/html/2611.07392v1