Radar Telegram alerts Open Radar

MiniMAX H3 Image in ComfaceUI: three settings against compressed textures on r / StableDiffusion Figured out how to remove the "crunchy" effect - on dry, grainy and rough skin and small details when created in Minimax H3 Image. The problem was solved by three editors in Pipeline ComfiUI without changing the model itself. MiniMAX H3 Image is a polished diffusion inverter based on a 6-step program (pd sigmas) with constant CFG 1.0 and no negative effect. The model is initially designed for ultra-high resolutions up to 16 MP and uses large predecessors of the Qwen family: if so, it works comfortably at 16-24 GB of VRAM and above, and on cards with 8-12 GB runs through GGUF Quantia (Q2 K3 K3, Q4 K) with load. When it is activated on default templates in small resolutions (4 MP and below) or with standard samples, high noise coding is dropped into a characteristic network "groony" on turns and textures. As a working solution, there are three parameters: First, raise the native resolution closer to the target (8-16 MP+, for example 3552x4736) followed by 2x down instead of compressing parts at 4 MP. It's still as fast as Rex. Second, go to DaggerLCM Node with the simple schedule in 6 steps and adjust the noise parameter s (from 1.10 to 00 or below 1.0 parts out micronoise). Third, abandon the tag set in favor of a coherent description and connect community patches: the MiniMaxH3PromptWeight node from ComfiUI-KJ Nodes and a one-frame decoder such as minimax h3 single frame 500k compatible. Secures in place of the basic VAE video. Discussion on Reddit @cgevent.

תרגם לעברית

Метаверсище и ИИще · · Source

MiniMAX H3 Image in ComfaceUI: three settings against compressed textures on r / StableDiffusion Figured out how to remove the "crunchy" effect - on dry, grainy and rough skin and small details when created in Minimax H3 Image. The problem was solved by three editors in Pipeline ComfiUI without changing the model itself. MiniMAX H3 Image is a polished diffusion inverter based on a 6-step program (pd sigmas) with constant CFG 1.0 and no negative effect. The model is initially designed for ultra-high resolutions up to 16 MP and uses large predecessors of the Qwen family: if so, it works comfortably at 16-24 GB of VRAM and above, and on cards with 8-12 GB runs through GGUF Quantia (Q2 K3 K3, Q4 K) with load. When it is activated on default templates in small resolutions (4 MP and below) or with standard samples, high noise coding is dropped into a characteristic network "groony" on turns and textures. As a working solution, there are three parameters: First, raise the native resolution closer to the target (8-16 MP+, for example 3552x4736) followed by 2x down instead of compressing parts at 4 MP. It's still as fast as Rex. Second, go to DaggerLCM Node with the simple schedule in 6 steps and adjust the noise parameter s (from 1.10 to 00 or below 1.0 parts out micronoise). Third, abandon the tag set in favor of a coherent description and connect community patches: the MiniMaxH3PromptWeight node from ComfiUI-KJ Nodes and a one-frame decoder such as minimax h3 single frame 500k compatible. Secures in place of the basic VAE video. Discussion on Reddit @cgevent.

More on Radar

Want to see every report in real time?

Hundreds of sources worldwide, translated into your language, with alerts for what matters to you.

Sign up free
Share on WhatsApp Get alerts on Telegram