<h1 id="0.9:">0.9:</h1>This is still i2v trained, but I have noticed with 0.9 that T2V works? Some motions seem like they are coming through on some t2v tests I did and they didn't seem like horror or anything. Slightly improved nudity and motion if you prompt for it. It shouldn't interrupt character loras as it's very weak on upper body and face data and is more of an amalgamation of body movements from many angles. Previews use <a target="_blank" rel="ugc" href="https://civarchive.com/models/2320262/ltx-2-i2v-14?modelVersionId=2610302">this workflow. </a>Modified it a bit <a target="_blank" rel="ugc" href="https://huggingface.co/TenStrip/Workflows/blob/main/bnzarev-LTX2i2v%2Baudio-modified.json">here</a>, use res_2s sampler from RES4LYFE on first pass, LCM on upscale pass, and my sigma changes and an optional audio latent load to track the output with custom sound voice or music.Problems already identified: Undertrained, under ranked (should probably be rank 64 for these nsfw concepts) and some tagging changes with angle set ups and pruning of the dataset can be done for 1.0.I also keep getting a visual bug with the upscaler in to larger vertical formats, if the image goes beyond 1536 vertically sometimes you get color noise at the top and bottom, not related to the lora. Anyone with a fix for that lemme know. Another quirk, or probably advantage, is that this lora has so much motion impact you can occasionally lower the compression on the PreProcess node and get some better adherence to start image, or in some cases turn it off completely and isolate the motion to only the lora. That's not usually plausible without loras, results just zoom in or freeze.I tried to reform the dataset tagging to bind the base concept under:<h2 id="doing-a-sexy-move">doing a sexy move</h2>The model seems to actually pick it's base concept up in context the way I wanted it. If you start a prompt with "a naked woman standing in front of the camera while doing a sexy move" it should start out with it. But you can do things like another action and dialogue, then later on in the prompt: "blah blah blah. Then she starts doing a sexy move." You can bring it in later on in context. At least that's the idea and I gave it clips to lead into that.You can set these other keywords up in-context with something like:"she is doing a sexy move with side to side hip movement and butt grinding."Won't always work, depends on start image and the usual LTX2 finding a good seed and refining prompt until it works. You don't want to just have a short prompt using only these tags, you should still prompt the base model correctly and mesh the data from this into it with a normal long and descriptive prompt. All these tags do is just give a hint to what kind of motion and scene it's trying to do, but this is pretty strongly trained and rigid and if the image is complicit it knows what to do, but also may just start mixing different motions together regardless of prompt. That's the biggest issue to try to iron out. The entire set if mostly static camera as well, obviously for better data clarity.<h3 id="angle-description:">Angle Description:</h3>Seen from behindLow angle static camera (crotch focus)Facing awayFrom above(all else is assumed to be front facing camera, probably don't prompt anything)<h3 id="motions:">Motions:</h3>grindingbouncingfeelingtouchingrubbingsqueezingdancingFront:a naked woman, a semi-naked woman, a girlvagina and anussex, the penis goes inside the vagina, two people having sexgrindingbreast squeeze, grabs her breasts, rubbing, rubs, feels, playing with her breastsbreast bounce, breast jigglesexy dance, dancing in-place, bouncy danceside to side hip movementgyration, gyrationsBouncing up and downBack:Seen from behind, facing awayTurns to face away from the cameraLooking back over her shoulderButtButt jigglein a doggystyle position/posebutt grindingtwerkingshaking her buttfeeling her buttspreading her butt showing her anus and vagina with her hand/handsSex: (don't expect much, needs targeted lora motion to partner with for a real output. This is almost just noise to make it aware of concepts. Also is a lot more riding on-top focused.)explicit motionshe reaches down and spreads her vagina with her fingersbouncing up and down while having sexthe penis goes inside the vaginaPOVman has sex with the naked womanvery long hard and stiff penisAnalStrength: 0.2-0.91, 0.75-0.8 seems the best zone. High strength has adverse effects. Always try it turned off to see if it's even helping, its not magic.This one is actually still kind of a test of course. It is overfit, but also not? I thought the first one was, but it isn't, just the audio. The 768 bucket seemed like it was going to overfit first, but the 512 long bucket seems to still work to extend and smooth things out. Idk like most others I also find this model has a lot of quirks to training it. The wan2.2 one was trained like this and works fine, but it's all aligned with the same frame count, I never did a split frame count but I don't see any kind of interruptions happening on long generations. I have seen bad outputs and good outputs, but then when it's a very explicit image and I turn the lora off: nothing happens at all, lol. So at minimum you can just use this at half strength to give nude characters in erotic positions movement at least, and it will still have a lot of impact.This is also mainly a motion support lora, if this was Overwatch or LoL, this lora is Mercy or Lulu. On it's own it will do a few subtle unique motions, but mainly just hone the model in on a single female subject. If you use it with more targeted NSFW loras, make sure you balance this lower, it has sex and NSFW data, but only enough to mesh in with more targeted loras. Do as I say, not as I do. This dataset is borderline untrainable with too much variance, but just enough to transfer a pretty large variety of motions and lifelike quality through scraping on overfitting. You're way better off training if you focus on one thing and one motion with a dataset of that thing in slightly different shapes and settings with very similar composition.After testing base model more, I changed tagging for this back to the Wan2.2 lora + less vulgar terms for body parts. LTX2 with the default Text Encoder seems to understands anatomy in less vulgar terms. So butt, vagina, breasts, penis, testicles; it knows what parts of the body they are, just not how to fully depict or animate on them. Pussy, ass, cock, dick seem a lot less reliable.As far as the loss of the sexier voice from the test: I'm trying to put together JOI data, ASMR, and dirty talking during sex clips to make that it's own Sexy Voice package.V0.9 is expanded with 768 data at 121 frames, audio removed, since the audio training is way too impactful and can conflict with loras that actually need dedicated audio data tied to their concept.<hr /><h3 id="test-0.5:-first-rough-version-with-less-unique-motions-and-motion-clarity-but-it-has-a-way-sexier-voice-lines.">Test 0.5: first rough version with less unique motions and motion clarity, but it has a way sexier voice lines.</h3>Test 0.5 keywords:Style: realistic - sexy.Style: realistic - explicit.Pussy, ass.The rest of the motion same as 0.9, but use pussy and ass instead (weaker tokens).<h3></h3>

LTX2 i2v - Sexy Move

-512x 241f 24fps-768x 121f 24fpsNo audio.

Files with SHA256: cc1a783baa5caf067401138c57374636b49ef1aa3f437d24c1e523c8418c5fc0