Eros 2pass Workflow.

Can't recommend Lokken's workflow enough. It is faster and better than the one you're using. Unless you're already using that one.

beta 7:

"Fix1" version is for doing high MP outputs without flickering or single pass ones. It also will have some visual difference since the base was changed and the mix wasn't adjusted because I'm working on v1.0 instead. It can't be run mixed precision it needs to be loaded out of a normal Load Diffusion Model node, if you have Final Layer tensor size issues you need to change the loader and update comfy.

More like what beta6 probably should've been in most expectations. The premix was all redone and seated inside MLP. Generalizing loras were given full blocks 0-49, some were pushed further out to block 4,8,10-49. This method courtesy of alcaitiff's mysticV5 notes, but taken a lot further. All were boosted strength MLP extracts CWB combined and merged to the base with the same per-tensor magnitude cap limit strategy as 6, except that MLP protects attn and the base H3 model's visual sampling styles, reinforced paths, and reference system. The b6 mix blew those out which is why it's a bit untamed, but this is a more refined experience. This should have base level reference accuracy.

The base and turbos give the most character besides the mix. It's a skeleton of Fast Omni with Omni's trained reference timestep transplanted to base fl2va then folded again, and the VSA gates (which suck) were left out. The base is still meant to run 90% sparse with the same 0 start as omni, or else it can cause flickering, the same flicker issue in the full Fast Omni, I'm not sure what the issue with that is. Sol, SLA, VSA can all be used for sparsity. The turbo is a folded version of Silver's newer reference turbo v2 fused with DMAD and it's put on top of the remnant turbo delta from Omni with their cumulative v-band magnitude capped to prevent turbo-related contrast and audio issues. It can still produce reference noise and motion noise on 8 steps, but sampling is varied and can be configured around it and will just have to be. The whole omni-fl2va hybrid base is essential to this version and it's issues need to just be mitigated with 2 pass sampling or upscales. Lokken's WF will be the easiest high quality results and already mitigate all of them already, but you can take his 2 pass setup and put it into other workflows. The mix itself does not work on other normal bases or the base model. I still need to update lora credits, but at this point their individual contributions are a negligible part of a whole shift that is custom and targeted.

The other selling point on this is the ability to use Loras on top. The only one's you would really not need is generalizing ones like dre4mlay, nsfw, sexgods, or mystic. This has basically already nsfw-ified the model like those already by shared-signal merging a select mix and group of extracts into MLP layers. You can still run those kinds of Loras and go crazy though since they have no actual individual representation in the mix and no presence in attn layers.

Loras you'd use are concept detailers, style loras, unique anatomy loras or anatomy interaction loras like the coachbate gay loras for anal details, and such. Realism slider and Motion speed controls are the most useful.

beta 6:

Post mortem: rough implementation, but was experimental. More in-line with beta3/4 than 5. It does not replace b5, it does just does everything it couldn't do well and trades off generation speed to do it. It is not good to run on smaller cards and is a heavily modified reference model more than the normal hybrids. Uses 10/3 shift and higher sampling targets of 8-12 steps across multiple sampling combinations. Either full dense or VSA sparsity, the correct sampling setup can be found in the "FastH3" comfyui templates, just add more steps. VSA will work better over SLA or Sol. That is the result coming from a different turbo mix that avoids the 4-step issues (audio, plastic skin, lack of motion detail). It is not a rapidly quick-gen model like beta 5, it is designed more for professional level and higher quality use with references and higher end systems that can churn higher steps quicker and optionally run an upscale pass to clean up reference noise and details. It is also designed to be unique since it actually shifts the H3 model significantly and is not like any of the dozens of fully base-aligned models, including previous beta5 - prompt outputs will be different and may require adjustment to align to it's behavior.

If you want the max quality possible the full unpruned bf16 is here.

Everything was done differently and from scratch on the release full bf16 fl2va model as a base. Reference timestep, viggle deltas, turbo deltas, and Lora mix were integrated and then pruned. The Lora mix uses a unique application with a shared strength cap and a contribution 'noise floor'. It prevents H3’s self-guided architecture from decaying as is experienced with multi-Lora stacks. Each Lora’s character comes through while model coherence mostly stays intact under stacks that would normally destabilize the output. They bring in their data without the full level of disruption that 20+ Loras would do and instead homogenizes them into a shared capped strength per-tensor. This is as far as you can really push the model without visual and prompt degradation, so far. It already does sacrifice some visual quality in the form of some higher levels of noise and noised edges on objects, especially in the background common with the initial release Reference deltas. That is more or less the reality of H3 Loras and reference model right now. Half model H3 hybrids sacrifice that quality for much much lesser reference ability, and the typical late-block hybrid format was abandoned on this one. This is essentially a true hybrid, i.e. just a Reference model with T2V ability. If I2V is having issues it should be transferred to reference generation since it still has issues with starting image style first-frame continuity that reference mode does not have.

Full credits to these lora makers for having data involved, even in possibly miniscule contributions, in the merge of beta_6 version:

alcaitiff, MisticRain69, diogod, FourBunny, HearmemanAI, tazmannner, simonishere, QualityControl, blo01, ComfyTinker, kermitfrog1202, qdr1en, coachbate, salttaro, alternative_penguin, misterxrex, freek22, definitelynotadog, The Midnight Lab.

beta 5:

Use TURBO-hybrid_int8 by default. Other options are for experimenting. Full versions here.

beta_5 is built with a different normalization technique. It's also built off 7 different concept-grouped grafts and consensus merges from over 20 Loras, no full direct lora merges. It allows for a non-turbo version which is available. The files with TURBO have a hybrid turbo-delta fusion baked in saving 4.2 gigabytes of memory instead of having to load both ref/fl turbos. Other concept Loras will also load on top more readily, usually needing lower strength 0.2-0.6. For t2v and even some i2v you should 100% be loading mystic_v4, anatomy enhancer, or a related concept lora on top.

Also consider using the non-turbo with PDD, 6 warmup and 4 PDD turbo steps.

Prompt is the entire key to quality and success. Any issues you'd want to blame on a model or workflow, you can go ahead and take a look at the prompt instead. Describe things cleanly and literally:

❌ ~~He puts his penis in her pussy, make hot sex~~

✅ Live-action pornographic explicit sexual and sensual intimate POV recording: The man slowly moves his lower body forward with his finger on the base of his penis shaft. The tip of the penis slowly disappears into her pussy hole and her wet labia open allowing it entry. He keeps swinging his pelvis forward until his crotch touches hers. Then he backstrokes and starts a repeated thrusting sex motion. The sex act makes her whole body recoil into the couch, bouncing her breasts wildly. She stares lustfully into the camera.

Prompt in temporal sequence on a linear time flow. The longer and more embellished the prompt, the better the output will be usually. 100% use some kind of LLM enhancer; Grok is the one I use since he has a skill preset for reference prompting.

The version just labeled 'hybrid' is non-turbo. Non-turbo full step audio will always be better than audio on turbo versions.

Some working sampling setups:

er_sde/beta57 4-6 steps (seems to be best preservation of style and reduced drift)
res_multistep/simple 6-9 steps (good motion quality, beta will be the sharpest fast motion at 8-9 steps but will give a plastic/burned look)
LCM/simple 6-8 steps (best turbo audio)
Euler/simple 4-8 steps

Next version should be mainly powered by the first round of Sulphur training. From what I've seen it will fix most missing audio and missing concept issues.

Updated - Full credits to these lora makers for having deltas involved in a consensus merge in beta_5 version:

alcaitiff, MisticRain69, diogod, FourBunny, HearmemanAI, tazmannner, simonishere, QualityControl, blo01, ComfyTinker, kermitfrog1202, qdr1en, coachbate, salttaro, alternative_penguin, misterxrex, freek22, definitelynotadog

beta 4:

rebuilt on beta3 config with some loras changed out for newer versions. Turbo was consensus merged to construct a ref/t2va hybrid turbo lora. That's the key element to the merge, there is no non-turbo version. The non-turbo version is bad and doesn't work since the turbo weight is normalizing the merge by it's strength. That custom turbo merge will need further improvement. This one preforms video, reference, and motion well in 6-8 steps without the issues from beta3, but audio needs shift configuration.

Use sampling like Euler/simple 8 steps with sampling shift - 12 video/ 7+ audio. LCM/simple or beta with 6-8 steps and no shift can also be better for audio and drawn styles.

Audio is lackluster and it's becoming somewhat apparent that H3's integrated audio is not good, like terrible actually. Any future multimodal models should avoid integrated audio if they intend to open source. I have almost no control over how the audio works inside the model. Don't post about it. I focused on motion and prompt response and of course when I get those working well, the audio ends up bad, go figure. I'll look at what kind of different turbo configs can enable more audio crispness to come back or likely will have to wait for Sulphur to replace MysticXXX which is contributing to the audio quality drop.

beta 3:

Rebuilt on the delta1024 reference hybrid model. Does t2va and reference. Treat i2v as a single image reference, don't do i2v prompting. Silver's merged turbo is integrated and tuned for 6 steps with simple schedule with the extra _emb layers tacked on to the model, not sure if they're needed.

Samplers like er_sde or multires or other turbo sampling setups work. Best imo is just er_sde/simple 6 steps, no shift, no spectrum, no cache, only a comfy_kitchen backend selection node. 3 video references in a 15+ second outputs can be done in under 10-15 minutes now on larger cards with no extra cache or quality hit needed.

Many (like a lot, all the good ones) on-site loras were fully combined into a consensus weighted merge with ranked drop-out to form an initial part. That merge is put against new, more powerful Wan and LTX grafts as a blend/reshape that uses the loras to consensus shape the grafts, but it also allowed some of the better loras clean pass-through. This is not a linear list of loras just merged. The main element that can present most is probably MysticXXX which was given the most pass-through weight since it's just good--and all 3 release steps of that are inside it. However, they're all-combined with a ton of other loras with agreement and consensus of shape and then it's only reshaping the grafts parts. The results of that are the actual weighted loras that are used to make the model.

Due to drop-out and consensus merge, pretty much all of the loras can all still be used easily on top if needed, and might work better even. All of this was only done to create a large rank dummy lora similar to what sulphur data will look like as a lora or extracted lora so I can start looking at how to apply it cleanly.

It's definitely not a few on-site loras that are linear merged, uncredited, and then renamed with some emojis. I'll only do this until sulphur tuning steps are in my hands and I can work with more targeted and shifted stuff, plus I was tired of waiting and I wanted fast easy i2v.

There is one quirk of the hybrid h3 usage: don't use it i2v. It should either be always used in reference prompting mode, or t2va prompting mode. Even if there is just one single image input it needs to be used as reference and prompted in the ref2va format. If you run an underdeveloped or manually written prompt you will get odd outputs, random camera changes, and blue lighting color shifts when you use the i2v prompt style.

Full credits to these lora makers for being involved somewhat in beta3 version:

alcaitiff, MisticRain69, diogod, FourBunny, HearmemanAI, tazmannner, simonishere, QualityControl, blo01, ComfyTinker, kermitfrog1202

Beta2 and previous:

This started a finetune-by-graft. Or maybe a GST - grafted shift of transformer (cross-architecture). I made both up, because there aren't any projects that have done it that I know, except one reddit post that made me look into it. I experimented with Wan and LTX on the side which led to the initial LTX Eros scripts that became what powered this, all before H3 ever came out. It seems like unified unbiased models like MMH3 can technically take attention influence from any other DiT without breaking if done correctly. Anima, Krea2, LTX, Wan2.2, Flux1 were all tried out, configs tested, about ~40 hours maybe of working in the dark without any paper or technical documents from Minimax. Eventually I developed linear-magnitude blend application and specific block and head gate targets allowing for a smoother graft on an attn-triplet-unfused version of H3 output as a patch file. That sent to lora extraction, then merged to checkpoint at taste. This is a merge but a merge of LoRas I extracted that interact to produce this current shift. I saved 5 ponds of water by recycling data in a few minutes on a single card instead of toasting a server up.

Turbo not recommended yet for i2v, especially when used with other LoRas. T2V use with turbo is better. Use 20-25 steps normal sampling with no dialogue, 25 steps with dialogue along with cache nodes and attn modes. More steps over 25 are not neccessarily better, and can be worse. Use full int8: int8 model, int8 VAE (if it doesn't crash comfy), int8 qwen3vl along with current cache or attn mode nodes. For smaller cards: quants, macOS ports, and Wan2gp support will likely appear on huggingface but not from me.

Known quirks:

Audio difference v.s. Base - This model's audio changes come from attention shifts seeking alternate audio pairing. Attn triplets were unfused before graft, both standard and triplet q_attn was grafted holding about maybe 10-15% audio influence, attn_k was frozen and MLP fc2 layers were untouched resulting in minimal audio interference. This was the main issue with the entire transformer graft and protecting audio. However this version is slightly louder overall than the base model.
Low resolution detail smearing - Some finger digits and fine motion will smear more at low resolution, also a problem in base model. As memory use gets more efficient increase resolution or work on the composition to get around it.
Odd outputs - This can attempt certain concepts more liberally than base model, but that can lead to some undesirable outputs in bad prompting and certain contexts. Data shift comes from completely different transformers and architecture. This shouldn't even work, so it is what it is.

This model is not dedicated to NSFW as that would violate community license agreement. Sure it can do it, just like base. Any NSFW generations are purely the result of advanced reasoning and tokenization resulting from experimental changes. All terms from the H3 community license also still apply to the users of this version. Don't be a dumbass.

H3 usage still requires very intense prompting for maximum effect. Every motion, every interaction, every sound plainly and fully described. Not with slang terms; with proper actionable words that can be tokenized. Refer to the h3 developer prompting guide, hand that .md file to an LLM or Chat agent and have them enhance or refine prompts along the released H3 developer prompt guide styles using the model's tag system. Certain concepts can be made from pure token reasoning. Consult the prompts in my previews to see certain physical descriptions that I use for some things. When using enhancement give the agent feedback about any issues in the generation and get them to describe motions in alternate fashion, or manually edit it yourself adding a negative like "no X, no Y". Still requires prompt refinement and trial/error for best outcomes.

Sulphur Project has 10k banked to attempt actual tuning. Right now training pipelines are sub-optimal. As always Eros is my personal side project, and this beta was also essentially a speed-run of finetuning, figuring out exactly in what configurations and target areas do you get helpful/harmful changes in the model. This is also a proof-of-concept of what and where to target while leaving the reinforcement quality of base unharmed by being additive.

https://huggingface.co/TenStrip/10Eros-Max

https://ko-fi.com/10strip

Files with SHA256: ea0df6670a84dfe594fe12c1202dfd82a497dbf2a75d6f06279a6b6993ab64b2