🗡️💀 DaSiWa-WAN 2.2 I2V 14B Lightspeed | FP8 Safetensors💀🗡️
My new flagship model for WAN 2.2 I2V generation - This is the best of the best!
This is a WAN 2.2 Model: You will need one pair of High + Low.
Version overview: https://civarchive.com/articles/23495/dasiwa-model-versions-and-timeline
🔮 Key Features:
🔥 LoRA-Free Generations
Generate high-quality videos without stacking Wan 2.2 LoRAs (unless you want adding spacial styles/concepts).☄️Fast: 4 step generation
Extreme versatile (more build in concepts)
Quality motions (less slowdowns)
🔞 NSFW + SFW:
Enhanced anatomy + poses + framing
Better understanding of sexual concepts
🪄 Better Prompt Responsiveness
🥺👉👈Better understanding of anime/manga style composition
🪡 FP8/FP8+ precision
⚠️ Read "About this version" details for the version you are using for more information!
🚫 Do not use any extra speed-up (low step) LoRAs, this is baked in already
🍒Workflow
Make sure to checkout my easy to use Workflows!
🍄LoRA's
Try first without additional LoRAs!
But: This checkpoint is not meant to replace all LoRAs, it is meant to:
Perform better overall at his own
As easy as possible to use
With LoRAs to be absolutely awesome
⚠️ Read the corresponding announcements.
📢 Make sure to check it out for in-depth information and a complex comparison!
🛠️ Recommended Settings
Steps: 4
CFG: 1
Sampler/Scheduler: Euler/Simple or Euler/linear_quadratic
Resolution up to 720p (native quality).
My go to settings:
0.52 - 0.83 MP
CFG 1
Euler/linear_quadratic
4 steps
16 fps
Sigma Shift: 5
Add other LoRAs with 0.3-1
16 fps, 81 frames ~ 5s
Dependencies
🩻 Known issues
Tell me 🫵🫢
🩺 Fixes & Feedback
If you use LoRAs, try to respect the LoRA training triggers and try some versatile descriptions, most LoRAs will work with 0.3-1.2 (start with 0.3)
Do not mass add LoRAs, just add 1 or 2 (x2 High+Low)
Negative prompting do not work with cfg 1, thats a limitation of speed-ups with cfg 1
Low resolution (e.g. 480p) are only for fast samples and will blur fine details, do a higher resolution if you want clear details
Before posting any questions I suggest reading my guide.
Update your ComfyUI ❗
🪧❗ Test your comfyui-backend with this absolute basic test-workflow before asking about errors.
🖤 Why I Made This
I was tired of using all these massive list of LoRAs, just to get a remotely good result after 10 generations, consuming hours of time.
So I can just make my videos with 1 or 2 concept LoRAs without pushing 6 till 10 LoRAs (Low/High) into a generation.
This checkpoint is also my personal playground.
Closing words
🤩 I want to thank all the fantastic other creators who made super nice LoRAs and concepts to play with! Support that awesome creators by using their LoRAs and post to their gallery and share the meta-data!
⚠️ I made all this with permissions or open-source resources (the time it is incorporated).
I share as much insights as I can without compromising my work. I'm doing this for fun as my hobby and just do not want my hobby to be destroyed.
More details can be obtained in the corresponding announcements!
If you would like to contribute in my awesome (😉) checkpoint or willing to share resources I'll gladly give credit! Just contact me!
✅ All credits / resources are mentioned inside the announcements! - Since different versions may have different resources.
YOU are responsible for outputs as always! If you make ToS violating content and I get aware I WILL report this.
Disclaimer
This models are shared without warranties and with the condition that it is used in a lawful and responsible way. I do not support or take responsibility for illegal, harmful, or harassing uses. By downloading or using it, you accept that you are solely responsible for how it is used.
Custom License Addendum: Distribution Restriction
Notice: Notwithstanding the base license selected for this model, the following restrictive terms apply:
No Redistribution: You are not permitted to host, mirror, or redistribute this model (checkpoint, LoRA, or Safetensors files) on any other platform, website, or service (including but not limited to Hugging Face, Tensor.art, or SeaArt) without explicit written permission from the creator.
Attribution & Source: This model is officially maintained only on Civitai or other platforms where I explicitly own the repository. To ensure users receive the correct version, updates, and safety metadata, please point users to the original URL.
Usage: All other rights regarding the use of the model for image generation remain as per the terms and the restrictions provided per model.
Description
See high description
FAQ
Comments (221)
Man I must say. Your work are top-tier. The best I've seen so far. I truly congratulate you
Thank you :)
Are some of these Lightspeed fp16 or all of them just fp8?
I do not release the fp16 versions. All fp8 from fp16 base.
@darksidewalker Why not release the fp16?
Any tips on how to get smooth transitions on FLF2V?
Luck! - color match and images with same composition :)
I give 2 start images, 2 frames from the previous video segment. Doesn't have to be the last frames, works even better if you truncate the previous video mid-action, to continue motion
@catsama Thanks for the reply! I'll give it a shot
@Kazuki_kun just found this, did you try? https://civitai.com/models/2024299/wan-vace-clip-joiner-smooth-ai-video-transitions-for-wan-ltx-2-hunyuan-and-any-other-video-source
@catsama I will try soon, thanks!
Welcome back king ! I'm gonna test this new version now :)
Nice to be back! I wish you the best awesome results! And fun!
I just found it and test it. Amazing model!
Extremely fast with your simple workflow.
Congrats!
That BoundBite version felt a bit underwhelming at first, but after some adjustments it turned out to be really good. I liked how SynthSeduction handled anime character faces, but BoundBite might actually be even better in that regard.
Even though it feels softer, prompts seem to be better understood, which gives more control over the outputs. I made plenty of clips to compare, and the overall quality is also slightly better.
Amazing work, thank you for all your effort!
Can you share your settings? I'm trying Boundbite as well, and there seems to be a lot less motion compared to Synth.
@BenkyouDekinAI Hello, i'm just using higher cfg 1.5 instead of 1 and using loras to help him giving motions. His power is actually the fact that he's "softer" which can make it easier to do soft motion, for something mor lewd such as the clips i shared, u might need loras and play with the strengths. i shared loras/prompts on the clips. for the sampler im using euler/normal 8steps and cfg 1-2
welp, looks like im waiting 2 weeks to try these since civit only allows buying buzz with crypto now, looking forward to it xD
ngl i'm quite excited for next version
I'm counting the days as well xD
SynthSeduction seems to make my asian women into latino/white women where TastySin did not. Is there a way to avoid this?
Don't know, never had this happen, are you sure this is not caused by a Lora? Besides that BoundBite v10 is more consistent to details.
@darksidewalker Thanks for letting me know it was user error. I got more specific in my prompt and it fixed it! Amateur move :(
I really enjoy this! I've been using 7 steps for a bit more style and hot dang!
When you mean 7 steps are you doing something like 4 high 3 low or some other combination?
@serpentine18 exacty!
somehow its not understanding basic prompts.... it take 3 seconds before they start moving, looks like they are very shy to do anything ....
Well that can not be true, since after 3 seconds the video is almost over XD I assume you doing something crazy or trying to do things it can not do O.o
Maybe you mixed the checkpoints up.
Share your prompt.
I really like version V10. In V9, when generating anime-style videos, the eyes often have issues, such as style inconsistencies, forced eye opening, or unnatural eye contact with the camera. In contrast, these problems rarely occur in V10, and it also seems better at understanding and accurately rendering prompt descriptions.
I was facing the exact same problem. I can't wait for the day when access is unlocked.
hello friends, I'm a beginner and my internet speed is very slow, so I'm asking: Do these models only produce anime-style cartoon videos? Can they also produce realistic i2v videos?
You can read up inside the announcement, it can produce whatever you insert as i2v.
Do not use this guy's model, kidney failure warning!
Is this person here to stir things up, or did you just not read the other comments?
I have no clue what this should be about, maybe I don't get the reference
@darksidewalker It means that using your models is addictive, whether it's the Wan series or the Illustrious series. The generated pornographic videos/images are so stunning that it makes you want to masturbate,if you do it too frequently, you'll suffer kidney failure (of course, this is an exaggeration). So, people with poor self-control should use it with caution (I will strongly recommend your series of models to my good buddies). I'm not trying to stir up trouble, hahaha.
@stom72569752 Ah okay, thank you for the explanation! Maybe that's why I'm so drained lately :P
Ok this is gonna sound so stupid, has anyone had this issue where the genitals turn out awful? like there is no anus, most of all, the vulva droops like its a melting scrotum, literally have no idea why this keeps happening but unless i use a lora like dreamlay, vaginal lips (anime or realistic) just come out looking like testicles hanging and swinging. Its been happening to me so consistently that i might be making a common mistake or something, any clues?
@g1263495582 i've tried using this before but it fucks up my gens for some reason, especially anime ones, i've been using dreamlay as a workaround but genitals always look half-baked, almost like forced, idfk what im doing so wrong, everyone's gens look amazing, with every bend and fold and texture so clearly defined, they all look so nicely detailed. beats me man.
@redlucario1735 Weird, mine works fine with no issues. What LoRAs are you using when you gen? Both high/low weight ones. Also if you're comfortable, send over your results + prompt (upload to Jumpshare/etc). And what text encoder are you using?
@g1263495582 https://www.redgifs.com/watch/obviouspinktarsier - https://www.redgifs.com/watch/understatedpropertigershark
These are two examples of this issue happening, although it seems to happen also when im using no loras whatsoever
First one on the left - ONLY smoothXXXanims low noise @ 1.0
second one - smoothXXXanims high+low noise @ 1.0 AND doggy high anal cut high+low @ 0.3
4 steps, euler/simple Dasiwa v9 Q6
nsfw_wan_umt5-xxl_fp8_scaled
Wan2_1_VAE_bf16
Prompt: "A high quality anime 2d video, SmoothMixAnime. A woman with long dark blue hair and cat ears sits on a red bed, wearing only a thin red thong and a black lace mask covering her face | Jumpcut to a new scene seen from the side diagonally where the same woman is on her knees on a bed, her face and chest pressed flat against the bed, head turned sideways facing the camera with a happy aroused look, Her bare feet are spread wide apart across the bed flat with soles looking up, thighs vertical with hips lifted high into an exaggerated arch that elevates her buttocks prominently upwards. A man with his back turned to the camera stands on the bed behind her fucking her asshole in a deep squat position, his legs bent and spread very wide out of frame; he leans forward slightly while gripping her glutes as he thrusts vertically downward from above with full length of his large penis inserted into her anus. His large erect penis is fully embedded within her stretched anal opening — balls-deep at the bottom of each powerful motion, which causes visible skin stretching and glistening fluids around both bodies. The camera angle is low, capturing the scene from the side at a 45 degrees angle. her face and breasts remain visible without obstruction."
@redlucario1735 Add the pussy asshole LoRA at a low model strength of around 0.5–0.8.
[Edit] Also, the other thing — you can ignore it if you want. Have you tried changing the word 'asshole' to 'anus' yet?
Thanks you, I've already used V10. The V10 high model's latent output is noticeably cleaner than the older V, and it keeps the eye/lip details from shifting into something different like the older V used to after coming out of the low model.
I have some questions, how many distillations lora did you mix, and could you share the names? If not, that's totally fine.
I use the LightX2Vid distillation loras in a mixture that I invented myself, but I would like to keep the mix and weights a secret. There are so many people who just steal the work of others.
@darksidewalker I feel that V10 has 2 issues I've encountered:
The model tends to be somewhat like slow motion. If prompt with a good description of the motion, it can be fixed to some degree.
The second issue — honestly, you can ignore this one — is that the Low model V10 feels like the nipple detail is not as good as V9 (in cases where the nipple is not visible in the image)."
What aspects of performance do you think should be compared against LTX-2.3?
@g1263495582
It has sound. I tried it and it's fantastic. You can see my work in my profile. I just need a good LTX 2.3 model (NSFW).
@Renessance OK
This is the best model I've ever used!
Thank you! Enjoy :)
Awesome Igm2Vid Model, does a great job maintaining the style of the original image. Would Recommend. 👍
Can't it be recognized by the Wan GP? I put it in the ckpts folder, but my Wan GP couldn't find it
No clue, I don't use WanGP, maybe you should ask the WanGP creators?
I normally put it under "unet" not "checkpoints".
@darksidewalker Thank you. I'll check it again
Did you create a json file to put into the finetunes folder?
https://github.com/deepbeepmeep/Wan2GP/blob/main/docs/FINETUNES.md
@technocratnumber 不,我没有。我该如何创建或者哪里能够下载json文件?
Yeah gotta have a JSON file in the finetunes so it can find the models and open it
Put the models files in Wan2GP\ckpts
Create a .txt file in Wan2GP\finetunes and paste the code below code into the .txt file save and rename to DaSiWa-WAN_22_I2V_14B_BoundBite_v10__Lightspeed__GGUF.json (the name does not matter but make sure to rename the .txt extension to .json.
Code:
Thank you, boss, for allowing me to try this. I don't know if I can do it.
@ernestb83414 Thank you, boss, for allowing me to try this. I don't know if I can do it.
@ernestb83414 Thank you, boss. I have found it in Wan GP and it successfully turned my picture into a video. But I don't know why, the video is very blurry, as if it were covered with a layer of snowflakes. However, I can clearly see the movements of the characters. I set CFG to 1 and Steps to 4, without using any Lora
@simarkatarezzy193475 https://pastebin.com/R9rXKdKs I have uploaded the code to pastebin as the formatting gets lost in this chat
So i dont know of anyone mentioned this before but in my testing and playing around with this model i found out you get a TON more motion and dynamism if you actually use lightning loras, i accidentally left my lightx2v 480p loras on at 3 and 1.5 strengths for high and low respectively, and i get far more motion, i haven't done much more testing like simply increasing the amount of steps beyond 8 in total but i thought this was worth mentioning to you guys.
You’re right. I compared V9 and V10 using the same prompts and parameters, and I found that without any Lora, V10’s motion effects are very weak—in NSFW scenes, it’s practically static—whereas V9 doesn’t have this issue...
@Tieasc actually im getting some really interesting results by using speed loras on the v9 model as well, i dont mean to say that it doesnt work without it, its just that adding speed loras suprisingly makes these models even better. I'm trying jumpcut types of scenes without using any loras and just by adding speed loras im getting much better "transformative" generations that actually change the scene significantly instead of just morphing the character into position according to the prompt. this is definitely worth looking into i think.
Just to clarify:
Adding distillation on distillation always add more motion, but also will introduce artifacts, camera distortions and detail shifts. Be aware of this.
The model is made to preserve as many details as possible, so the amount of distillation is already finetuned on that.
@Tieasc V10 is more sensitive to prompts, the same prompts will not make the same results, but adding prompting like "fast, slow, rapid, swift, strong ..." will change the outcome significantly.
For V10 you may have to be more clear how the motion should be, instead of just writing the motion.
V9 added overall significant amounts of motion, that would also lead to unwanted motions and camera movent. What was fixed for v10.
I do not found the images to be static in V10 if the prompt is clear what to do. Static videos may occur if a concept can not be done without lora, but that's normal for all checkpoints.
@darksidewalker can you give a rundown on what prompts the checkpoint will adhere to (especially camera movements) and prompts that work as we don't know what exactly was merged with the checkpoint? I used your guidelines as broke down the prompts with the scene type structure you described, but it provides very little change.
@unknowngreatone I can not provide that, because this is not a lora, trained on specific type of wording. You have to figure out what works best for your input and scene, a full checkpoint has no fixed trigger words.
I tested many camera movements and all worked: "pan, zoom, strife, hover, orbit, ..." - It may depend on the complete sentence and initial image, how good one or the other worked.
For version 10 just a general question, the retainment of details and characters is very good. But whenever there is any kind of s*x scene there will be some sort of bloom effect where the clear colors shift into this lighter smear relatively quickly. Any ideas?
using er_sde/beta
I would suggest using a other sampler+scheduler, I never faced that
Thank you for always creating such wonderful models. I would like to purchase the model as soon as it is released in Early Access, but I have had to give up on the purchase due to CIVITAI's coin payment method. I was wondering if you happen to trade the model on other platforms that accept card payments.
I've noticed there seems to be a slight drift to the left while using v9 which gets amplified when using SVI.
Based on the previews this seems to not be an issue on v10?
Should not appear with BoundBite, as far as I tested
Is this model compatible with a Mac Studio with M4 Max chip and 64GB of RAM? Looking forward to your reply, thank you!
No clue
@darksidewalker Could you let me know if this model is compatible with Mac devices at all? I’d really appreciate any insight you might have.
@darksidewalker I’m running this model on a Mac Studio (M4 Max, 64GB RAM), and I found that Mac’s MPS backend doesn’t support FP8 data types, which causes errors. Could you please provide the FP16 version of the model? I’d really appreciate it!
@s_songjiafeng01 sorry, won't provide it. I also have no clue what models are supported on Mac.
How can I stop the videos from playing in slow motion? Even though I use many positive prompts with words like "fast" and "quick," or negative ones like "slow motion," they always play in slow motion... Is there a setting I need to change?
Did you open up a previous generation made on an older workflow and just change the model? I had the same experience, rebuilding it in the most recent workflow didn't show any signs of slowdown.
use lower resolution and change fps, my resolution is THD and 16 fps (interpolated) and get slowmo/static movement too
When interpolating, ensure that you're using a workflow that multiplies the framerate when saving the video. If you generate at 16fps and then interpolate to double the frames but don't change the fps, you're gonna have half-speed videos (IE: it's showing 32 frames at 16fps). Current DaSiWa workflows will multiply it automatically if you've got interpolation selected - if you're using a workflow where you added interpolation yourself, you need to up the rates yourself.
I also am getting slow motion videos with v10. I didn't have this issue with previous versions. I just use the default Comfy Wan 2.2 I2V workflow and I would prefer to not need to download a more complex one.
same issue, also any one getting "get image" issue, every thing is loaded works for a few runs then that bug comes up, and have to restart comfy
Christmas in March.... whatever you did to the v10 model was wonderful; it has much better facial and detail consistency that Synth Seduction did when running certain styles.
Yeah that was the number 1 goal for me :)
is there anyway to fix the pause at the start of each of the videos? even the showcase ones show the pause
Just to provide insight im using workflow as well from the creator posts and trying smoothmix, dr3amy, and fused motion and I cant get aggressive movement even using quick, fast strong, etc as the creator suggested. i tried a mix of none, all etc but overall compared to v9 the movement inst quite there at least im stumped at this point
I also want to know how to get rid of pause at the start
Happens to me as well, I've been using the creator's models since LureNoir with a very simple workflow that I practically never had to edit and I never had an issue every time I switched to any of the creator's newest models, always worked seamlessly, but then I switched from SynthSeduction to this and suddenly my animations barely have any movement now, I tried to tweak everything and simply nothing works, the weird pause at the start along with the static robotic movements is almost every result I get. I had to switch back to SynthSeduction after messing for a couple of hours with no results
I thought I was going crazy or doing something wrong after updating from v9 to v10 and getting this.
应该是VBVR lora混进了模型导致的,可以搜搜PainterI2V这个动作加速节点
I've found that using smoothmix v2 on high with lightx2v=3 and boundbite on low works very well. Sigma/shift 6 or 7. There were certain i2v generations that had the pause no matter the seed, sampler, prompt... One thing I noticed is that if wan thought the subject should be looking somewhere else, or that something else should be moved in a specific place, it would do that before anything else. Even prompting to not move where they are looking didn't help...
V10 is really, really cooool. working perfect. To be honest, I felt some parts were a bit lacking up until V9, but V10 reflects my intentions with surprising accuracy. I can really feel the effort put into balancing detail and dynamism. The level of detail is incredibly satisfying. While the dynamic aspect still has a tiny bit of room for improvement, I believe this is a masterpiece that finds the perfect sweet spot—maintaining maximum detail while still capturing the right amount of movement. Thank you for this amazing work.
Great checkpoint (V10), quality wise the best...
And you know what... when rendering on 0.6mp with perfect looping F2LF with the same image (8-10 seconds) along with the 1.05mp I2V for a stage to change you can create really long consistent quality video's since the chance of getting a high quality last frame is pretty high and consistent.
Also this version compared to V9 adds a lot less balls to female vagina's lmao.
I was so confused at first getting low quality results...
User issue lmao, after I noticed one of the switches was bugged in GGUF instead of Safetensors I finally was able to get good results on this one (the switch safetensor was on, but it actually wasn't and I was getting the GGUF results).
How do you do F2LF with out flickering on the last frames?
@granz33 enable perfect loop in DaSiWa's workflow.
Depending on the light on the scene its sometimes better to keep the color correction off
I never get flickering in my results, but don't expect a 100% looping result. The chances of those are rare depending on how fast and detailed the video is.
I have a looping video in my showcase, its X rated so beware (I believe that one is 8s).
let's do this.
Great work, I've been really enjoying your models for awhile now and happy to see you push and further improve results (v10 has some of the best motion I didn't even know wan could achieve) I have noticed since v9 and v10 that theres a bit of a "warm up" in the beginning frames before the animation is full swing in my generations (I've been using SVI 2.0 pro to chain them together for a longer generation) but is still evident in most generations I've seen. do you know if theres a reason for that?
I noticed that this sometimes is happening, it's also on some examples, but on others not. I don't really know why this could be, maybe just a prompting thing. Describing the initial situation seem to prevent this for me, maybe it's an "analysis" thing till it understands the situation. But it is only sometimes, so maybe just bad luck.
@darksidewalker good suggestion, I'll try to prompt in a way where it has kinda whats going on to start
@CubeyAI Any luck? I tried a lot of prompting techniques, then also some loras and even some speed loras. The most success I was able to get was maybe around 20-25% decrease in pause with the speed loras. With the length of the pause, it's not enough.
I really like this release, it looks good, but this is a killer for me.
I'm facing the same issue.
I was able to achieve satisfactory results by trimming the first few frames using FFmpeg.
AWESOME ! now i'll see myself building workflows
Good 🤞
releasing it on april 1st is quite something lol
For me it was 31.03.😄
Do you guys have a discord channel where I can follow your projects?
I get better cum details and motion from the old ass Radiant Crush version than v10 lol I don't get it..
There is an obvious reason mentioned inside the announcement 😉
@darksidewalker Ah! interesting, thanks for the response. What would you say the trade-offs are? Also I should have specified even when using a lora like DREAMLY the controls and detail of this aspect is much worse than I could get before. Would v8 or v9 be a better option for me maybe?
@SolidBold Tradeoff is quality degeneration and detail shift. What is not happen with BoundBite v10.
If another checkpoint suites you more, well, that's on your side to decide ;)
I always admire your wonderful creations as I use this. You are like a beacon of light for the wan users. However, this v10 version is quite difficult for me to handle with my current capabilities. I took a day off to experiment, but it was extremely difficult to create the motions I wanted, and I couldn't get a handle on motion consistency at all. Since you mentioned that this was a different approach than before, I will try again this weekend.
So far I'm finding v9 is quite a bit more "active" with its motion than v10 - sometimes even too much where some things move and jiggle that shouldn't - while v10 is more subdued which can be nice but also I'm struggling to get more motion out of it when I want to.
(Though I am using Wan2gp, not Comfy, and I'm not that in-tune with what my generation parameters are that may be affecting the amount of motion apart from the prompt.)
Not intended as criticism or asking for help, just an observation!
That's an inherit thing, because v9 had so much motion values that it introduced camera shifts sometimes. So v10 got this tunes down a bit to stabilize details and camera shift.
Therefore v10 has to be less motion than v9, exaggerated motion values lead to unwanted jiggling, drifts, distorted details.
What helps (for me) is using motion descriptors like fast, rapidly, swift, ... depending on the scene.
Like this, on other checkpoints were exaggerated motion is baked: https://civitai.com/articles/27986/
This can be good in some situations, it is not in many others. Choose your poison 😁
This is true. Workflows running on V9 produce far more satisfactory results in camera movement and motion than V10 running the same workflow almost to debilitating limits, but the facial consistency of V10 is unparalleled. So I tried the hybrid model, using V9 for High Noise and V10 for Low noise, and that output gave better results.
@vredbat02664 I assume you just refer to overextended fast hyper thrusting motions... Since the motions are fine with v10🙄 camera movement is worlds better with v10, v9 is not even close there.
You can always add more distillation with lighx2v loras and extend the speed, sacrificing details, understanding and prompt adherence for the repetitive motion 😏
The model is not made for 1 simple task, it is made to overall perform (also on SFW!) and many styles.
@darksidewalker To be honest, ComfyUI changed its calculation methods for certain parts of the model. Because of this change from the older version, the outputs might look different or have minor bugs—something some people may or may not encounter.
@g1263495582 Any source? I'm not aware that comfyui is doing the calculations of the tensors itself and alter them...
@darksidewalker https://github.com/Comfy-Org/ComfyUI/issues/13106
@g1263495582 Thank you, very interesting O.o
But there is a mention that the issue exists if your dependencies are outdated and the problem get solved with:
2.10.0+cu130 and xformers to 0.0.35
Also it was said v9 vs v10, so if it would be comfy it would effect both.
@darksidewalker As for v9 vs v10, hmm... was v1022 mixed into the v10 mix distillation?
@g1263495582 it is partly included in both versions
@darksidewalker for example a workflow that worked well with V9 said (excerpt from the prompt) "The girl has a green emerald pendant around her neck, the girl lifts the red-wine glass from the table and walks towards the fridge. The camera zooms out to reveal full body shot of the girl walking towards the fridge with the wine glass in her hand". -- The output of this is exactly as expected, all items and parts visible and well produced.
Now to V10, the output is crystal clear with great facial consistency, but there is absolutely no zoom action, the girl's pendant is present but the camera angle is such that its not visible, the wine glass is present but is only partially visible and there is no camera motion for the full body shot to show the girl walk. The view is fixed while the girl walks to the fridge.
This output happens with no change to the prompt, only removing V9 and loading V10 and running the workflow.
Again, I will iterate V10 is an insanely good model, but perhaps for a different use case such as multiple short subjective situational prompts stitched together for long videos.
@darksidewalker Hmm, regarding Motion V10, I think the 1022 that was mixed in might have been overshadowed by other distilled models. Personally, I feel like 1022 is the distilled LoRA that makes videos look the most 'active' compared to the others. That’s probably why V9, which used 1022 directly, performed better in terms of motion.
@vredbat02664 Regarding the camera, I feel like using 'camera pulls back' yields better results. However, you need to format it something like: 'camera pulls back, [describe the background/what is visible in the scene], [followed by what you want to see, e.g., full body, etc.]'.
Like I said before I love V10 so far, amazing quality and motion consistency.
I'm only struggling with one thing: Camera position and movement...
This is probably more of a WAN limitation but are there effective ways to increase the change for the camera to move?
Sometimes it works, but for some scenes with the same prompt it doesn't, some even move the opposite direction of my prompt lol.
Best results so far for me was adding the camera movements in the last sentence of the prompt.
Any help or advice is much appreciated!
Regarding the camera, it depends on the input image plus the camera commands. From what I've shown in this official guide under the camera section, I feel like there's a specific pattern to it. If the format is wrong or incorrect, there's a chance that Wan will either follow it or just ignore it.
Currently, I’m noticing a significant reduction in movement in v10 compared to v9. Maybe it’s because I generate horizontal videos rather than vertical ones like most people here? In v9, the whole body moves - there’s twitching and blinking - while in v10, the person looks almost frozen, without natural human-like motion.
V10 needs promoting for the motions you want. The reasoning needs details. The benefit is it will not add unwanted motions out of the blue.
quality is unparalleled, amazing quite frankly but has massive issues with movement. thank you
There is no movement problem, the reasoning needs a bit more detailed descriptions.
@darksidewalker gotcha thanks
v10 definitely feels harder to use than previous versions (I started with v7), but put in a good prompt, and the result is an absolute banger. After a few days, I've finally decided to delete v9. Good stuff.
Were You be able to get rid of initial freeze and robotic movement and lack of subtle body motions? If so I'd very much like to hear how. So far v10 is collecting dust, while v9 bangers, although half is scrapped because of camera drift.
@Kolt93: You have to describe the initial state of the image, or you'll have a bad time, like I first did. Without that description, you're animating an image instead of generating the rest of the video, if that makes sense.
@SamuraiJack109 Thanks, I'll look into that!
I previously made somewhat harsh remarks about v10. However, after spending the entire Saturday researching it, I have come to understand your intentions and the model's performance. While v8 and v9 were models that performed reasonably well based on learned data and simple instructions, v10 seems to have the potential to produce the results I truly desire by moving each individual joint, assuming it adheres strictly to the mechanisms of human movement. Thank you for creating such a great model. It is a small token, but I sent you the cost of a cup of coffee.
Thank you for your support and tha kind words, I hope everyone can crate awesome art with the model🖤
@darksidewalker You've got the best model for stylized stuff (I use v9 for nearly all my videos :D). I'm still figuring out V10, and it's great to have variety in how the models perform; different tools for different jobs!
I'd say it is a strict downgrade artistic-wise: initial 1 second freeze, robotic, lazy movements, lack of live subtle body motion. The only things good I found about the model is stricter prompt adherence and (Oh my god!) steady camera. I'd say V9+steady camera would have been near perfect. V9 already produces insane things, that are 50% time destroyed by camera zoom/drift/pan and maybe overenthusiastic head/body bobbing.
I would say you are using it wrong. Considering the hundred examples proofing otherwise. 🤷
The reasoning will need more description, if you do not describe anything, it will not do anything ... it is more prompt sensitive. What is a good thing.
@darksidewalker I will try working with it more, I just dont understand how to describe every subtle motion that V9 did on it's own.
What about freezing? What causes it?
@Kolt93 Nobody said you need to describe every single bit, but description matters with the reasoning build in.
The good thing is it will not add unwanted motion, clam faces, you got the power, slight smirk, go for it. ~
I never noticed any freezing, so I do not know what that should be.
@darksidewalker Literally every video from v10 starts from around 1 second freeze. I didnt notice it right away too, but after looking through other's comments about it, I rewatched my generations - and there it is, every 5 second clip is basically 4 second with ~1 sec freeze at the start.
@Kolt93 Looking at my latest vid here (https://civitai.com/images/126424971) there is no freeze.
@darksidewalker I double checked - first 7 pixel frames are static initial image (I2V). Thank god it doesn't affect SVI workflow.
@darksidewalker I can only add that I'm not alone with this problem.
@Kolt93 7 frames would not even a second. Even if this is happening to you and as I said it is more likely a prompting problem. There is no proof to tell there4 are others that prompt your way and get that same behavior. I could also say there are 100 examples with no problem, so this must be a setting or usage problem.
Even IF this problem occurs and would exists, there is nothing I could change now, since the checkpoint is released this way. I do not get what you want from me.
If the problem is real and reproduce able constantly I could only try to fix it with the next checkpoint.
So if the v10 is not your cup of tea and do not produce the wanted results for you, there is no reason to use it, you can just use any other out there.
@darksidewalker I wanted to report a problem (freezing), that you would either confirm (and maybe patch) or not, thats all. 7 frames is half a second at 16 fps and less than a third at 24, so may be not that noticeable at 24, but either way - if it exists, you will know about it and remove it from V11. Peace, man <3
@Kolt93 Okay, now I understand. I can confirm this happen occasionally. But I can also say, that this is not in general, since I made a lot of video.
My clue is this is the deeper reasoning from vbvr.
I can just give you a heads up, that this is somehow connected to the input and prompt used.
could this be used for T2V? just curious
It is a I2V model, so this is not intended for T2V and will not reliably work as T2V.
Haha, I don't know how many works I've created using V7 through V10.
I'm only commenting now. With V10, I've noticed that while the dynamic range isn't as strong as previous versions, it still produces pleasing effects after appropriate cue words.
Especially when using FLF2V, its stability is incredibly strong; previous versions would have flickering noise.
I've created many works with V10. It seems to have a greater understanding of human anatomy.
In short, it's awesome!
Thank you! Yes, I tuned down the motion a slight bit, to eliminate unwanted motions and camera shifts.
I've been having some technical issues running the low model (v9 and 10), where it tends to shift colors to a desaturated olive green hue when either video is too big, or too long. any insights?
You have to run both high+low
i notice that in SVI workflows, its often have blurring issue. try to fix it with prompting but it's still there. any help?
beside that it works great with AIO workflows
Running on 1x H200 SXM5, when NAG is enabled it shows this error, does anyone know why?
ValueError: Query/Key/Value should either all have the same dtype, or (in the quantized case) Key/Value should have dtype torch.int32
query.dtype: torch.float16
key.dtype : torch.bfloat16
value.dtype: torch.bfloat16
File "/root/ComfyUI/execution.py", line 534, in execute
output_data, output_ui, has_subgraph, has_pending_tasks = await get_output_data(prompt_id, unique_id, obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb, v3_data=v3_data)
File "/root/ComfyUI/execution.py", line 334, in get_output_data
return_values = await asyncmap_node_over_list(prompt_id, unique_id, obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb, v3_data=v3_data)
File "/root/ComfyUI/execution.py", line 308, in asyncmap_node_over_list
await process_inputs(input_dict, i)
File "/root/ComfyUI/execution.py", line 296, in process_inputs
result = f(**inputs)
File "/root/ComfyUI/nodes.py", line 1625, in sample
return common_ksampler(model, noise_seed, steps, cfg, sampler_name, scheduler, positive, negative, latent_image, denoise=denoise, disable_noise=disable_noise, start_step=start_at_step, last_step=end_at_step, force_full_denoise=force_full_denoise)
File "/root/ComfyUI/nodes.py", line 1556, in common_ksampler
samples = comfy.sample.sample(model, noise, steps, cfg, sampler_name, scheduler, positive, negative, latent_image,
File "/root/ComfyUI/comfy/sample.py", line 66, in sample
samples = sampler.sample(noise, positive, negative, cfg=cfg, latent_image=latent_image, start_step=start_step, last_step=last_step, force_full_denoise=force_full_denoise, denoise_mask=noise_mask, sigmas=sigmas, callback=callback, disable_pbar=disable_pbar, seed=seed)
File "/root/ComfyUI/comfy/samplers.py", line 1180, in sample
return sample(self.model, noise, positive, negative, cfg, self.device, sampler, sigmas, self.model_options, latent_image=latent_image, denoise_mask=denoise_mask, callback=callback, disable_pbar=disable_pbar, seed=seed)
File "/root/ComfyUI/comfy/samplers.py", line 1070, in sample
return cfg_guider.sample(noise, latent_image, sampler, sigmas, denoise_mask, callback, disable_pbar, seed)
File "/root/ComfyUI/comfy/samplers.py", line 1052, in sample
output = executor.execute(noise, latent_image, sampler, sigmas, denoise_mask, callback, disable_pbar, seed, latent_shapes=latent_shapes)
File "/root/ComfyUI/comfy/patcher_extension.py", line 112, in execute
return self.original(*args, **kwargs)
File "/root/ComfyUI/comfy/samplers.py", line 995, in outer_sample
output = self.inner_sample(noise, latent_image, device, sampler, sigmas, denoise_mask, callback, disable_pbar, seed, latent_shapes=latent_shapes)
File "/root/ComfyUI/comfy/samplers.py", line 981, in inner_sample
samples = executor.execute(self, sigmas, extra_args, callback, noise, latent_image, denoise_mask, disable_pbar)
File "/root/ComfyUI/comfy/patcher_extension.py", line 112, in execute
return self.original(*args, **kwargs)
File "/root/ComfyUI/comfy/samplers.py", line 751, in sample
samples = self.sampler_function(model_k, noise, sigmas, extra_args=extra_args, callback=k_callback, disable=disable_pbar, **self.extra_options)
File "/root/ComfyUI/venv/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 124, in decorate_context
return func(*args, **kwargs)
File "/root/ComfyUI/comfy/k_diffusion/sampling.py", line 205, in sample_euler
denoised = model(x, sigma_hat s_in, *extra_args)
File "/root/ComfyUI/comfy/samplers.py", line 400, in call
out = self.inner_model(x, sigma, model_options=model_options, seed=seed)
File "/root/ComfyUI/comfy/samplers.py", line 954, in call
return self.outer_predict_noise(*args, **kwargs)
File "/root/ComfyUI/comfy/samplers.py", line 961, in outer_predict_noise
).execute(x, timestep, model_options, seed)
File "/root/ComfyUI/comfy/patcher_extension.py", line 112, in execute
return self.original(*args, **kwargs)
File "/root/ComfyUI/comfy/samplers.py", line 964, in predict_noise
return sampling_function(self.inner_model, x, timestep, self.conds.get("negative", None), self.conds.get("positive", None), self.cfg, model_options=model_options, seed=seed)
File "/root/ComfyUI/comfy/samplers.py", line 380, in sampling_function
out = calc_cond_batch(model, conds, x, timestep, model_options)
File "/root/ComfyUI/comfy/samplers.py", line 205, in calc_cond_batch
return calccond_batch_outer(model, conds, x_in, timestep, model_options)
File "/root/ComfyUI/comfy/samplers.py", line 213, in calccond_batch_outer
return executor.execute(model, conds, x_in, timestep, model_options)
File "/root/ComfyUI/comfy/patcher_extension.py", line 112, in execute
return self.original(*args, **kwargs)
File "/root/ComfyUI/comfy/samplers.py", line 325, in calccond_batch
output = model.apply_model(input_x, timestep_, **c).chunk(batch_chunks)
File "/root/ComfyUI/comfy/model_base.py", line 172, in apply_model
return comfy.patcher_extension.WrapperExecutor.new_class_executor(
File "/root/ComfyUI/comfy/patcher_extension.py", line 112, in execute
return self.original(*args, **kwargs)
File "/root/ComfyUI/comfy/model_base.py", line 211, in applymodel
model_output = self.diffusion_model(xc, t, context=context, control=control, transformer_options=transformer_options, **extra_conds)
File "/root/ComfyUI/venv/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1779, in wrappedcall_impl
return self._call_impl(*args, **kwargs)
File "/root/ComfyUI/venv/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1790, in callimpl
return forward_call(*args, **kwargs)
File "/root/ComfyUI/comfy/ldm/wan/model.py", line 644, in forward
return comfy.patcher_extension.WrapperExecutor.new_class_executor(
File "/root/ComfyUI/comfy/patcher_extension.py", line 112, in execute
return self.original(*args, **kwargs)
File "/root/ComfyUI/comfy/ldm/wan/model.py", line 664, in _forward
return self.forward_orig(x, timestep, context, clip_fea=clip_fea, freqs=freqs, transformer_options=transformer_options, **kwargs)[:, :, :t, :h, :w]
File "/root/ComfyUI/comfy/ldm/wan/model.py", line 597, in forward_orig
x = block(x, e=e0, freqs=freqs, context=context, context_img_len=context_img_len, transformer_options=transformer_options)
File "/root/ComfyUI/venv/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1779, in wrappedcall_impl
return self._call_impl(*args, **kwargs)
File "/root/ComfyUI/venv/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1790, in callimpl
return forward_call(*args, **kwargs)
File "/root/ComfyUI/comfy/ldm/wan/model.py", line 252, in forward
x = x + self.cross_attn(self.norm3(x), context, context_img_len=context_img_len, transformer_options=transformer_options)
File "/root/ComfyUI/venv/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1779, in wrappedcall_impl
return self._call_impl(*args, **kwargs)
File "/root/ComfyUI/venv/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1790, in callimpl
return forward_call(*args, **kwargs)
File "/root/ComfyUI/custom_nodes/comfyui-kjnodes/nodes/model_optimization_nodes.py", line 1382, in wrapped_attention
return wan_crossattn_forward_nag(self_module, args, *kwargs)
File "/root/ComfyUI/custom_nodes/comfyui-kjnodes/nodes/model_optimization_nodes.py", line 1302, in wan_crossattn_forward_nag
x_pos_out = normalized_attention_guidance(self, q_pos, context_pos, nag_context)
File "/root/ComfyUI/custom_nodes/comfyui-kjnodes/nodes/model_optimization_nodes.py", line 1255, in normalized_attention_guidance
x_negative = comfy.ldm.modules.attention.optimized_attention(query, k_negative, v_negative, heads=self.num_heads).flatten(2)
File "/root/ComfyUI/comfy/ldm/modules/attention.py", line 137, in wrapper
return func(*args, **kwargs)
File "/root/ComfyUI/comfy/ldm/modules/attention.py", line 466, in attention_xformers
out = xformers.ops.memory_efficient_attention(q, k, v, attn_bias=mask)
File "/root/ComfyUI/venv/lib/python3.10/site-packages/xformers/ops/fmha/__init__.py", line 311, in memory_efficient_attention
return memoryefficient_attention(
File "/root/ComfyUI/venv/lib/python3.10/site-packages/xformers/ops/fmha/__init__.py", line 472, in memoryefficient_attention
return memoryefficient_attention_forward(
File "/root/ComfyUI/venv/lib/python3.10/site-packages/xformers/ops/fmha/__init__.py", line 488, in memoryefficient_attention_forward
inp.validate_inputs()
File "/root/ComfyUI/venv/lib/python3.10/site-packages/xformers/ops/fmha/common.py", line 242, in validate_inputs
where do i paste these bro
Almost all the generated videos by V10 have a delayed motion. The characters have minimal movement in the first 1 sec. The previous V9 doesn't have this problem.
BTW I am a loyal fan of this work. Best Wan2.2 ckpt ever!
@lillblues78249 Seem to happen on some inputs and prompt types. Best use a brief description of the setting as first 2-3 sentences.
@darksidewalker Thanks for the tips. How come V9 doesn't have such a problem?
I'm having the exact same issue. tried simplifying the prompt to 2-3 sentences, tried ensuring all the sentences describe motion rather than the image, etc. but seems to be the issue with the model.
@penguin235 as I said, it can happen, but most of the time it is an prompting issue. V9 is different and the motion vectors where too much resulting in camerashift and some detail shift. V10 has build in reasoning and needs more prompting, but responds better.
How do one go about merging in loras? I like your merges, but I'd like to mix in some of my own loras to keep generation times low.
I tried using the comfyui nodes to load up model +loras and then using the save model node, but keeps failing
You can not effectively merge loras into quantized models.
V10版本在二次元人物的一致性方面令人赞叹,但我发现想要保持完美的一致性需要牺牲人物的肉体的柔软感,抱歉如果冒犯到您,您的视频展现的很多女人的肉体是没有弹性的。但我喜欢使用诸如slop bounce或者slop twerk这两种使女人身体柔软,动起来时更具冲击力与美感的lora,而使用这些lora会导致女人长出真人嘴唇或者使用效果不及预期,达不到那种柔软的肉体效果,但调高lora的数值比如到1~1.3又会导致女人脸部真人化等等问题。看到别人做的视频展现的柔软的肌肤臀部这些羡慕得要死,希望早日能找打解决办法
i have v7 and v8 i use v7 more then any other can someone update me is v9 or v10 worth my time or is it wasted space ?
Hi! I have start with you v10 since few day now, but for understand the prompting can you list the lora inside the checkpoint plz ? i need to know what i can do with no lora plz
All information I want to share is inside the corresponding article. Anything above this will not be shared to protect my work from stealing :)
@darksidewalker ok but how to know what we can do with no lora ? you don't list prompt word or exemple ? for blowjob exemple, i use sensual_teasing lora or Deepthroat/Face Fuck- Wan2.2 I2V lora, but i see problem with this Lora, then if you already use this one in your check point i use its two time for nothing :/ Do you use your own blowjob lora ? Thank you very much for your answer and your work
@djoedjoe15454845 You are right and also not. Since it is NOT a lora and not trained on triggers or specific sentences and be a full checkpoint, it will listen and understand complex settings and natural language. There is no way to fully provide a list of working sentences, since it always is depended of the context, attentions, encoders, seeds and inputs.
To check if a lora will add any benefit you can just run the same seed and setting and see if this lora will add anything you want or the model already understands that on its own. that's why I recommend to try without first.
To know what you can do without lora is trying out, that's how it works with ALL models out there. Nobody can tell you all capabilities of an checkpoint and there is no way to test every possible setting.
I have kind of casual question, but can someone tell me whats the difference between this lineup of models and TastySin? fp8 and fp16 only?
You can find detailed descriptions under 'About this version' on the right side of the model page. Additionally, NVFP4 and GGUF versions are available for v10.
Also there are detailed articles and announcements on my page to explain everything.
V10 is great. very smooth, intuitive, good prompt adherence, plays nicely with loras. fast and reasonable quality output even at 4 steps, excellent quality at 8 to 10 steps. obviously works great inside DaSiWa's I2V AiO workflow.
Thank you:)
What is your workflow? Using a regular (default) WAN2.2 workflow v10 is broken for me. The result is unpredictable.
@deepz hey sorry late reply but i use darksidewalker's FastFidelity all in one I2V workflow with just the I2V, upscale x2, NAG, and interpolation turned on. it can do lots of other stuff too check out the description. link: https://civitai.red/models/1823089/dasiwa-wan22-workflows-or-i2v-or-svi-20-or-s2v-or-flf2v-or-audio-or-combine
Is there a workflow were you have section for longer vids 20sec+, like kenpechi wf? i tried kenpechi wf with dasiwa model but its not nearly the same quality and takes longer.
This is my SVI WF: https://civitai.com/models/1823089?modelVersionId=2580650
Awesome model, the best out there for NSFW for wan 2.2, do you have a recommended final pass detailer + upscaling workflow? I tried to work one out myself but i couldn't get it working right, plus 1080p OOMs needing another 1.6gb of vram to work.
DaSiWa (the same account that posted this model) has a great all in one video workflow that I highly recommend. Its very modular so you can set it up however you like!
@Nk0GGry the fastfidelity workflow? That's just a straight resize upscale, not a full final pass upscale.
where am i going wrong the pussy if fingered or played with looks like bubble gum and the ass mix's in with the pussy is it my prompting ot not prompting something ?
I am having issues with v10, v9 works fine even without any loras.
@deepz Whatever you issue is, please read the announcement and front-page to the model. There are in depth explanation how the model works and that it is not meant for replacing all loras.
@darksidewalker I mean v10 doesn't work. It is broken for me. It doesn't do simple SFW prompts what v9 used to do well
@deepz I doubt that, v10 has much more reasoning and prompt adherence. I have no clue what you are doing, but v10 is much more capable of doing things, even more for sfw.
You need more prompting as for v9, because of VBVR - Just use a bit more detailed prompts. And a brief start (as always) describing the situation. There are plenty of examples already in the gallery.
@darksidewalker understood, I will double-check with more test cases assuming the parameters stay the same as in v9
@darksidewalker i like how there this big talk in side my question but my question never got answered lol
@crafted101 Oh, yeah, I assume this is prompting or the situation needs a lora.
I did test it again. v10 is better at preserving identity but movement is stale or non-existent
@deepz Sight... How can you say that? Look on the gallery. It is just not true.
But well, if you do not like it or its not how you want it, there is nothing I can do, you may just use another checkpoint. There is no point in telling me that over and over in the comments and other comments. I can not just rewrite the checkpoint to your needs.
@darksidewalker maybe I have a broken model I will re-download it. But I did test in more than 4-5 repeatable cases where are got excellent results with v9. Could be the prompting or the settings.
@darksidewalker You are right! I might have had a broken model the first time. It seems to be much better when I re-downloaded it! Good Job!
@deepz Glad it now works for you :)
@darksidewalker maybe give some prompts example?
@junyung99_tan302 99% of my uploads are with prompts, also from others... So there are enough examples already.👍
Having a ton of fun with this excellent model. Only one question, it seems like a lot of my generations have a tendency to return to the init image/pose at the end of the video. For example I'll have a character with long hair in front of their chest, and tell the prompt to move the hair behind her shoulders, which works, but then in the last 1-2 seconds of the video they will move the hair back in front of the character so it looks like the init image again instead of it staying behind their shoulders. Almost like there is looping behavior except I'm not doing any looping. Is there some other setting I can use so generations don't return to their init image at the end?
After 5s WAN 2.2 will gradually start looping back.
@darksidewalker Thanks. I suppose it's not that big of a deal, just need to stick to 5 seconds to avoid undesired looping behavior and go longer if I DO want the looping, since it is actually helpful in some instances like creating extended clips via end frames
Trying to use MMAudio but it only lasts 2s then cuts out. I tried 24fps like the workflow says and tried 30fps some else recommended but no luck. Any ideas?
Hey buddy, can we have gguf version?
There is, just look on my profile/collection 👍
I am a newbie, why is the quality of the video I generated with your recommended settings so poor and blurry? I need to set something to improve the picture quality.
Oh,I found that Video-Reason has released the official lora of VBVR.Since I spent more time adjusting the prompts and so on to avoid a slower motions than using V9.I guess can official version VBVR performs butter than optimized version?
I have no clue what your talking about can you specify?
@darksidewalker Sorry about express not clearly.I don't know much about backing models,but I realize that VBVR don’t has a lora format released until a few days ago,so V10‘s VBVR originates from the whole VBVR Diffusers format model as base model?Since V10’s
generation often has a slower motion than V9 when using same input and promots especially with SVI Pro,I wonder if it's VBVR Diffusers model‘s influence?Now VBVR has official WAN2.2 lora released,could backing VBVR lora in V9 provide better results since lora is more concise,conducive to a balance between dynamics and reasoning?
I will be very sorry if I am wrong with how V10 implements VBVR,but anyway you did a great job,your model is consided as one of the best WAN2.2 models in our community.
Thanks for your great work!
@ql_weepingwind036 VBVR also has general Wan 2.2 checkpoints with it built in. One person I read claimed the lora can't work as well as the checkpoints because it's a lora but I don't know if that's the case. One video tester claimed the KJ lora works better than the checkpoint but he only tested the "surgically" compressed version rather than the full-fat VBVR checkpoint. I have found that the full-fat VBVR checkpoint has better quality than the allegedly "surgically" compressed one. It is slower, though. I am not sure VBVR is always an improvement. Sometimes it seems to improve things and sometimes it seems to be a hindrance, whether it's the lora or the checkpoint. I have not tested any lora other than the unofficial KJ one.
@ss9999 I see....So the most important thing is still to use more detailed prompts.Oh.I hate constantly adjusting the prompts and generating them repeatedly....sad....
@ql_weepingwind036 There are a lot of variables (which loras to use and at what strength, how many steps, what sampler/scheduler, how much shift, which checkpoints to use, whether or not to use accelerator loras and which ones, whether or not to use things like NAG and VBVR, etc.) and unfortunately there is a lot of trial and error.
Well BoundBite is more prompt related than SynthSeduction.
I took a lot of time to test it and found BoundBite way more "precise" than SynthSeduction in understanding the prompts and also is more versatile by keeping the input image without too much changing it. I'd say, darksidewalker made it's own VBVR in his models without using the actual LoRa in it.
To be clear, i always test without any LoRa. This is the best method to get the boundaries of the checkpoint, it's capabilities and what it can or cannot do.
I noticed that BoundBite react better with "strong", "repeat", "fast", "wide" trigger words. Also specifying physics helps a lot like: "velocity", "friction", "gravity", "weight"; specifying material "type", "state" and also motion "type", "state", "direction", "placements" (which are not necessarily needed in SynthSeduction).
I found that BoundBite react way better to science than SynthSeduction and is way more stable. Yes, motion is fast almost everytime in SynthSeduction, but it lose a lot of the prompt's detailed explantation and for what i've tested is too much doing whatever he wants.
The workaround for BoundBite: If it's slow at 16fps (81 frames) that means it will be okay at 24fps (121 frames). If it's too fast at 24fps it will be okay at 16fps. If the motion takes too much time to start (like early frames taking time to start the motion), that means your subject's description trigger some motion informations from the model. In that case put the subject's description AFTER the motion explantations and make sure to weight what you really want to see like (motion:1.2).
Also don't push the number of frames (number of seconds) too much expect if you wish for a loop/repeat result. For example: "A man walking from left to the right" > Result: going from right to the left in last frames (like backward) means the time is too long for what you asked according to motion description.
Details
Files
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
Mirrors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
DSW14BLightspeed_V10.safetensors
dasiwaWAN22I2V14B_boundbiteLow.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
wb_dasiwaWAN22I2V14BLightspeed_boundbite_low_V10.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
Wan22_Dasiwa_Latest_LOW.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
BoundBite-Low.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
loww.safetensors
DasiwaWAN22I2V14BLightspeed_BoundBiteLowV10.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors
dasiwaWan22I2V14B.Io2V.safetensors
DasiwaWAN22I2V14BLightspeed_boundbiteLowV10.safetensors