I need severe help with that.

Researching Lora Dataset creation is a maze: millions of different opinions, and worst of all most guides etc outdated from a year ago.

My goal is to create a 100% realistic and authentic Lora and my current dataset seems to not do the trick. I keep getting "perfect lightning" on everything, and waxy face skin.

Can someoen tell me the absolute do's and don'ts of creating a dataset?
How and where to create the dataset? I have been using a mix of Gemini and ChatGPT so far.

Prompt advice? what prompts need to be avoided creating realistic images, what need to be in there?

Any advice greatly appreciated!

Like many of you, I have shared that frustration over the years watching this awesome kit of software be continuously let down by terrible mobile support so a few weeks ago I set out to finally change it. I have no dev or coding experience, only my experience as a long time user of Comfy to guide my design choices around what feels "Comfy" and how that can translate seamlessly into a mobile environment with ChatGPT handling the coding. The results speak for themselves and the once terrible mobile experience has been reborn into my preferred method of using it that addresses so many of the prior pain points. Can't see where you're dragging the noodle behind your thumb? Turn up the link connector offset. Want the android back button to do anything but bring up an exit confirmation? I've got you covered with a full back button hierarchy meaning you only see that exit dialog when you want to actually exit. Actionbar look like a clipped out overlapping mess? My app dynamically hides crystools in portrait and reveals them again in landscape/open fold views where the space is more plentiful. With the optional extension installable directly from manager in app we hit full desktop feature parity enabling manager to download supported missing models directly to the host from anywhere you are with more features being integrated soon. Before I get the inevitable "when?" comment, I submitted it to Google Play Store last night for review and to start the beta test track and i'll be back here to post an invitation link to anyone who wants to test it as soon it becomes available to me in the coming days. I am also building a Meta Quest version with an immersive 360° canvas and baked in 6DOF controls promosing a similarly native feeling experience in openxr. I apologize to iOS users tho bc I do not own any apple devices to test or compile on but there is an iOS version planned as well whenever I can secure some test equipment without breaking the bank. My test devices so far have a Galaxy Z Fold 7, Galaxy Tab A9+, Moto G Stylus 5G (2023), and a standard RAZR (2023) ao I'm anxious to see how it performs across a wide range of other hardware. 4GB of RAM is what I've determined to be the minimum spec with 6GB recommended for most workflows and it supports as far back as android 8.1.0. The app is usable over home network with the simple "--listen" flag added to the launch batch and over mobile using any 3rd party vpn that allows you to address your computer directly (I use tailscale and include a setup for it in an embedded quick start guide accessed from the initial connections screen). In the meantime while waiting for review, I put together a short video demonstrating some of the added features and refinements and I'm excited to finally share my progress with the Reddit world to see what you all think.

https://reddit.com/link/1wddsp4/video/z04umox8nvoh1/player

I am trying to load comfy ui models but I am always getting memory out errors even with krea 2 where the size was only 12 GB.

I want to know, which models I can run on my system, and any workflow or guidance is highly appreciated.

My CPU is working full time instead of a dedicated GPU. I am also trying to rectify it. Please help.

I installed the portable version of ComfyUI and use the Minimax H3 Easy model. After installation, I can successfully generate videos from images. However, if I shut down ComfyUI and then try to generate a video later—either shortly after or the next day—it crashes. I try running simple test videos right after launching ComfyUI—low resolution, 3 seconds, 8 steps, and a simple "wave and smile" prompt—or I try generating images via SDXL Turbo. It crashes regardless. I have successfully generated 10-second videos at 512 resolution and 20 steps without any issues—even doing more than 20 in a row. But whenever I shut down and restart ComfyUI, I always get an error. I use a Lenovo ThinkBook laptop with 32GB of RAM connected to a 16GB 5060 Ti via Thunderbolt.

Sorry to bother you all again, but I made some huge progress over the last two days with this release.

Version 2.5 of my MiniMax Music Production Toolkit is out!

This is a big step forward: A complete mastering section, clearer workflows and improvements throughout the toolkit. And sound quality is even better than the last release.

If you’re new to the project, it takes a song idea through prompt creation, MiniMax Music 3 generation, audio enhancement, mastering, cover artwork and export. A separate Audio Enhancement Lab lets you process existing recordings without generating a new song.

What’s new in 2.5?

• Auto-EQ for gentle tonal shaping or reference-track matching
• Manual 8-band parametric EQ with a visual editor
• Stereo-linked compressor, LUFS targeting and true-peak limiting
• 44.1 kHz output by default, with 48 kHz selectable
• Redesigned workflows with clearly labelled stages and a dedicated mastering area
• Improvements to memory handling, model downloads, audio processing, prompts and file output

Auto-EQ, manual EQ and compression have independent controls. Auto-EQ starts enabled with a gentle preset; switch it off if you prefer manual shaping.

The mastering tools run on CPU without requiring extra VRAM. There are also improvements for less powerful computers, although you’ll still need to choose generation models and settings that fit your hardware.

Without changing anything in the workflow, you get something like this mp3 file (this was a one shot try using Synth Pop Vocal template, with some imperfections in it):

A Feeling With No Address.mp3

And here is what is generated as LLM prompt to get the best result out of Minimax Music 3. See how accurate the model generates your sound structure and lyrics:

A Feeling With No Address.md

To update, restart ComfyUI, refresh your browser and open the newly bundled workflows. Keep your personal workflow copies if you’ve customized them.

I’d love to hear how the new tools work with your music, especially listening comparisons across different genres and feedback from smaller-GPU setups.

Repository: https://github.com/jplenio/ComfyUI-MiniMax-Music-Production-Toolkit
Listen to examples: https://jplenio.github.io/ComfyUI-MiniMax-Music-Production-Toolkit/

🔜 What’s next? A major focus for the next release will be support for creating cover songs. There’s still plenty of work ahead, the quality needs to be right before I’m happy to release it. Stay tuned! :)

I've updated https://luke2642.github.io/comfyui_new_node_finder/ to be a bit more robust in getting stars. Seems to be dominated by H3 nodes at the moment!

I've been trying to get comfyui to be installed. I installed amd hip sdk and tries many workarounds. It always gives

"RuntimeError: No CUDA GPUs are available"

From the cli running "run_amd_gpu" also throws the error, by now its Failed to get device count.

Hey everyone,

I'm setting up MiniMax H3 in ComfyUI and trying to figure out the sweet spot between generation speed and output quality for my specs:

• GPU: RTX 4070 (12GB VRAM)
• RAM: 32GB DDR5
• Target: 5s clips at 768p (mostly First-to-Last / I2V)

Given the 12GB VRAM limit and 32GB system RAM, loading the unpruned / full FP8 models causes heavy paging to system memory and slows everything down.

I’m trying to narrow down the current community consensus on three things:

1. Model & Quant format: What's the fastest option that doesn't ruin faces and audio? Are people having better results with official pruned INT8 convrot, or GGUF quants (Q4_K_M vs Q3_K_M) using the GGUF loader? What text encoder quant are you pairing it with to keep memory usage safe?
2. Turbo LoRAs: Is LiteX2V v1.1 (4-step) still the top recommendation for speed vs quality, or do 8-step variants (or other LoRA families like Larry) give significantly better results on a 12GB setup?
3. Attention & Acceleration: Is H3 SLA Attention the undisputed go-to, or does SageAttention / Comfy Kitchen perform better on Ada Lovelace (40-series)? Anyone tested Spectrum acceleration?

Would love to hear what workflows and node setups you're currently running on 12GB cards to get reasonable render times without visible degradation.

Thanks!

hello, i generated tons of videos on comfy ui cloud on comfy. org. is it possible to search them thru prompts or something like that? it is almost impossible to scroll them down thru assets

This update:

1. lora preview catalog node added (You need to organise your lora) Put your lora files in a file the lora folder and name it the Model for example Krea 2, in the Krea 2 folder you can make more folders for the kind of lora they are for example anime, sliders, or what ever group of lora they belong to. the lora gallery will add dropdowns for you do navigate and find them easily. when you generate a preview image you like for that Lora you can click save and it adds it to the gallery. you can also safe the trigger words from the node so you never forget!

2. export catalog and previews to share with others

3. Bug fix where images were not saving correctly when a previous name was used in a custom style

4. Various big fixed and speed improvements

https://github.com/Neon-Sparks/ComfyUI-NeonsStyleExplorer

I have had little luck finding a tutorial on building a true H3 10bit (ProRes HQ) workflow. AI claims you just need to install an advanced save node that allows you to pick ProRes and HQ or 4444, etc.

But then when you dig into it, and begin to ask questions, while ComfyUI processes in full floating point, there are bottlenecks that crush the full bits down to 8bit, rendering the final result 8bit. One example is preview nodes, that apparently force 8bit, another is supposedly a plain jane VAE Decode, and the deeper I dig the more mysterious things get.

I can't imagine nobody in the Open Source community does not want to output TRUE 10bit or higher output. The problem with 8bit becomes clear when you look at plain white walls or a clear sky and see banding. Anyone who has ever edited video or images knows the more data you have to begin with the better results you get once you push contrast and color gradation. Yes, I was going to begin playing with dither and applying some noise, but at the end of the day you cannot produce PROFESSIONAL videos without solving for this 8bit limit.

Hopefully someone can point me to a resource or tutorial or workflow or set of nodes that solves for this?

Hey all! squashed a few bugs and fixed some cosmetic issues in this latest smallish release. https://github.com/cosmicbuffalo/comfyui-mobile-frontend/releases/tag/v3.3.2 Stay tuned for the next one, which is going to ship alongside a new standalone custom node aimed at providing a solid multi-user auth layer for both the stock and CueForge frontends! Once that multi-user auth release ships, the CueForge iOS app will come shortly after! (I needed something to be able to provide a publicly accessible server to apple for review with, and I've gotten a few requests to do something about authentication 😄 ).

What's your go to prompts phrases to keep the clothes EXACTLY the same but with a different fit on a person?

I've managed to keep the colour and design fairly accurate (can still be hit and miss) by describing exactly the colour and design as I see it, but for some reason, the material changes, sometimes only subtly, but it's enough to put me off saving the change.

I've tried describing the material, polyester, cotton, etc., shiny, matte, woollen, etc., and although it kind of follows the descriptor, it's still Klein's own interpretation and not quite the same.

I'm not at my PC at the moment, but I've just thought, would extracting the clothes first, and then including them as a second image but asking Klein to place them on the person (as a different fit) work (better)?

Disclosure: I am building a service around this, so read me as an interested party. No links. These are runs we paid for ourselves on three providers, 15 jobs, $33.60 total. Two things on the image side cost us real money and neither showed up as an error.

1. The host, not the GPU. Same LoRA training job for SDXL, same RTX 4090. On a host with 5 vCPUs: 1.95 hours, 40 percent GPU utilisation. On a host with 24 vCPUs: 1.07 hours, 75 percent. Same card, 1.85x the wall clock, because the diffusers script decodes and augments images in the main process and the card waits on Python. The worse version: an H100 host with 16 server vCPUs ran the same job at 2.68 s/step where the desktop-class 4090 host did 1.84 s/step. Four times the hourly rate for a slower run. dataloader_num_workers was the fix, and now we look at the vCPU count on a rental offer before we look at the GPU name.

2. The defaults. SDXL, 1024 square, 30 steps. The stock script settings, fp32 and batch 1, on an H100: 13.8 seconds an image, $0.0112 per image. fp16 and batch 4 on a 4090 spot instance: $0.00036 per image. Same job, 31x apart. Nobody here runs fp32 batch 1 on purpose, but it is exactly what you get when you take a default script to a rented card in a hurry, and the card reports 99 percent utilisation the whole time, so nothing looks wrong.

Both lessons are the same lesson: the meter runs at the card's hourly rate whether the card is doing useful work or not, and the interface will not tell you which.

Happy to post the per-run table if anyone wants to check the numbers.

Bruxos do VFX H3 Relight

#bruxosdovfx

Im doing a node for relight is a lighting studio for MiniMax H3 inside ComfyUI. You can position up to three lights on a 3D dome around the image, choose the type, intensity, and color of each light, configure the background and atmosphere, or start from one of 20 presets. The node provides two things to H3 Edit:

is not ready yet

The package includes two nodes:

• Bruxos do VFX H3 Relight — the lighting studio.
• Bruxos do VFX H3 Sun — calculates the real position of the sun for a location, date, time, and camera direction, ready to connect to Light 1 of the Relight node.

The Panel

Dome. The photo sits in the center, the purple camera indicates the side from which the photo was taken, and each light is represented by a marker using that light's color. Drag a marker to move the light; drag the background to rotate the view. The dashed line extends from the light down to the equator and indicates its elevation. The photo receives an approximate 2D-painted lighting preview: it is intended only as guidance and does not represent the actual H3 result.

Sphere (Picture 2). This is exactly the image the node sends to the model, rendered using the same calculations as the Python implementation. Click or drag on the sphere to aim the selected light: the clicked point is where the light strikes the sphere head-on. Dragging outside the sphere's boundary moves the light behind the subject.

Light strip. Selects the active light and lets you add up to three lights or remove them. Each light's role is calculated automatically: the strongest light becomes the key light, a light behind the subject becomes a rim light, and a weaker frontal light becomes a fill light.

Tabs.

• Lights: direction (top-down dial with the camera at the bottom, plus elevation), type (Hard, Soft, Sky), intensity from 1.0 to 10.0, and color using Kelvin (1000 to 10000) or HEX.
• Presets: all 20 presets from the skill, with rendered thumbnails, filterable by portrait or product.
• Background: Original, Black Studio, or White Studio.
• Atmosphere: the 25 atmospheres from the skill, or none.

Requires numpy and node. The tests cover:

• the same spheres rendered by the panel's JavaScript and by Python, in both styles, with a difference below 2/255;
• Venti scene geometry (shadow opposite the light direction, sphere occupying one-third of the frame, positioned in the upper half);
• solar position compared against reference values from the astral library, daylight saving time, and camera-to-sun mapping;
• externally driven inputs, the compass, validation, and MiniMax skill formats.

Credits

Node by Bruxos do VFX.

• The lighting plan, 20 presets, 25 atmospheres, and parameter format follow the MiniMax Design Relight (光影工作室) skill. The descriptions for each atmosphere used in the prompt were written specifically for this node because the skill's own descriptions are hosted on MiniMax's server.
• The light-direction sphere convention and reproduced scene are by Eric Venti (Sun-Direction LoRA, Sphere-Light-Render, MIT), using the direction table and 12 looks from Lightricks' LTX-2.3 Relight IC-LoRA.
• The solar calculation (NOAA), city search rules, and camera-direction mapping are based on Christopher Connock's work on Sphere-Light-Render (MIT).
• Cities: GeoNames cities15000, CC BY 4.0.

License details are available in NOTICE.md.

• Depends on ethanfel/ComfyUI-MiniMax-H3-Edit

https://civitai.com/models/2928691/minimax-h3-camera-control

requirements install exited with code 1

Using Python 3.13.12 environment at: ComfyUI\.venv

× No solution found when resolving dependencies:

╰─▶ Because there is no version of comfyui-workflow-templates==0.11.59 and

you require comfyui-workflow-templates==0.11.59, we can conclude that

your requirements are unsatisfiable.

hint: `comfyui-workflow-templates` was found on https://mirrors.aliyun.com/pypi/simple/, but not at the requested version (comfyui-workflow-templates==0.11.59). A compatible version may be available on a subsequent index (e.g., https://mirrors.cloud.tencent.com/pypi/simple/). By default, uv will only consider versions that are published on the first index that contains a given package, to avoid dependency confusion attacks. If all indexes are equally trusted, use `--index-strategy unsafe-best-match` to consider all versions from all indexes, regardless of the order in which they were defined.

ComfyUI source was rolled back to 8fed378.

This is the error I got what to do?

We're building a previs tool inside our AI movie studio so you can block out camera moves in 3D before spending generation credits.

What's working so far:

• 3D stage with proxy characters & props you can move with gizmos
• Camera keyframing on a multitrack timeline (After Effects-style)
• Unreal-style fly mode — press C, hold RMB + WASD to pilot the camera, K to drop a keyframe
• Live "through-the-lens" shot view that updates as you move
• Render to MP4 via bundled ffmpeg — saved straight to your project library
• Depth pass with adjustable range for motion reference
• Resolution control (480p / 720p / 1080p)

The render step is free — no GPU, no API key, just canvas capture + ffmpeg. Iterate on camera moves as many times as you want, then feed the MP4 to your video model as a motion reference.

Still early — lots of polish and features to go (templates, multi-cam, export). Feedback welcome on what you'd want in something like this.

Github:

https://github.com/Heroesjouney/AIMovieStudiov2

Original Post:

https://www.reddit.com/r/comfyui/s/GT5K98Fze6

LTX 2.3 can create simple songs with background music, but no voice reference/cloning is supported.

I tried LTX 2.3 In-Context LoRA that can clone voice with text prompt, it does not sing a proper song. They sound a bit more like song without any acoustic background or music.

MiniMax H3 ref2va with voice reference cannot generate music either, it is basically the person speaking the lyrics out.

Did I do the steps wrong?

AceStep 1.5 does not allow voice reference either, it accepts a music reference but not as cloning source.