<h1 id="info">Info</h1><h3 id="general-usegoal:">General Use/Goal:</h3><ul><li><p>Creates a blank slate background via Qwen 2511, dropping our person into a blank white void and outputting the resulting image</p></li><li><p>Takes the above output, creates a Wan 2.2 360 orbit video, outputting the video and an image batch of each frame</p></li><li><p>Final Output</p><ul><li><p>A clean base image with no background for future use</p></li><li><p>A 360 orbit video that can be leveraged in other works</p></li><li><p>An image frame batch of the 360 video for use in character creation, reference images, lora training, or whatever else you have in mind (I've found multiple uses for the "slightly turned" variation of an image I just couldn't get a previous t2i prompt to behave on)</p></li></ul></li></ul><h3 id="what-lead-here:">What Lead Here:</h3><p>I've been looking to get more into automating runs through ComfyUI to serve multiple purposes in one go, while also bumping up against the desire to start training my first character LORAs with as little friction as possible to make prompting and output more consistent. That path merged on and lead me to <span class="MentionNode_mention__q78sK" data-type="mention" data-id="mention:2677512" data-label="KelevraQuakenstein">@KelevraQuakenstein</span>'s <a target="_blank" rel="ugc" href="https://civarchive.com/models/2053449/360-degree-i2v-video-creator-image-extractor">360 degree i2v video creator / image extractor</a> which is in large part the basis of this workflow, but I was running into issues with Wan 2.2 generating weirdness with unique poses, positions, etc. which I started to diagnose largely down to background artifacts. Not to mention the generations for the far side of an image being kind of insane from time to time (as to be expected) as context is lost in the turn (and honestly never existed to begin with).</p><p>While playing with ideas that could help simplify and allow for reused prompts in bulk, I decided why not remove the background from a ton of images, then queue them up in my modified version of Kelevra's workflow, and call it good?</p><p>So I fired up the ComfyUI template I'd modified for Qwen 2511 image edit and started removing backgrounds. After some settings and prompt tweaking, I got it down to a decent beat with 95% plus success for what I was looking for. The issue was, with Qwen being less than instant on my hardware, I was stockpiling images and not seeing quick enough feedback on the 360 rotation and image batch to know if where I was headed was the right direction.</p><p>Then it clicked, why not clean them both up and combine them?</p><p>Enter my <strong>i2i2v - QWEN 2511 Background Remove to WAN 2.2 360 Spin (Lightning v1)</strong> workflow which allows us to remove the background to a blank slate (for use in other i2i setups), save our output image, then fire that image directly into the WAN 2.2 360 Spin workflow and save our output video and image batch, labeled, all simultaneously.</p><p>In the end, we should get an image with an edited subject, paired against a solid white background for future use/character creation/lora baseline generation. Immediately following this we get a 360 spin output video, and a batch of images that match on a per frame basis for training a lora or whatever else you feel is useful.</p><h1 id="overview">Overview</h1><p>The process itself works off a modified combination of the ComfyUI Qwen Image Edit workflow and pairs that to a modification and cleanup of Kelevra's Wan 2.2 360 video creator and batch image extractor. The two workflows essentially pair, with the second awaiting the output of the first. This means you can fire multiple runs off with multiple images loaded up and walk away, the workflow should take care of the rest.</p><h3 id="full-workflow-overview:"><strong>Full Workflow Overview:</strong></h3><h3><img src="https://image.civitai.com/xG1nkqKTMzGDvpLrqFT7WA/434ffc88-4687-4e85-98b0-6ff5d06627de/width=525/434ffc88-4687-4e85-98b0-6ff5d06627de.jpeg" /></h3><h3 id="qwen-2511-portion:">Qwen 2511 Portion:</h3><p><img src="https://image.civitai.com/xG1nkqKTMzGDvpLrqFT7WA/812f52f5-4136-4fb8-9876-c3766653aadc/width=525/812f52f5-4136-4fb8-9876-c3766653aadc.jpeg" /></p><h3 id="wan-2.2-video-portion:">WAN 2.2 Video Portion:</h3><p><img src="https://image.civitai.com/xG1nkqKTMzGDvpLrqFT7WA/48ab1b65-7b86-44b0-a7e3-5845920b4f8e/width=525/48ab1b65-7b86-44b0-a7e3-5845920b4f8e.jpeg" /></p><h3 id="final-output:">Final Output:</h3><p><img src="https://image.civitai.com/xG1nkqKTMzGDvpLrqFT7WA/d452bfd2-4385-42e4-bd62-e4e4526eec5b/width=525/d452bfd2-4385-42e4-bd62-e4e4526eec5b.jpeg" /></p><p>Use the appropriate models for your VRAM/RAM/CPU needs, but this should be fairly plug and play to whatever hardware you're running on as long as you can get an appropriate model to run on it. Speed and clarity may vary, but overall the process should be smooth.</p><h1 id="prompting-guide-(wip)">Prompting Guide (WIP)</h1><h2 id="single-subject-background-removal-360-orbit">Single Subject - Background Removal - 360 Orbit</h2><p>The default prompt was tested over the course of 50+ generations to give solid results, more often than not, which was one of the main points of combining this into a single workflow (being able to batch this on one image after another) after coming back to a bunch of images that Qwen took liberties with I didn't account for with proper prompting in my first iteration of this across two workflows. This was on me, but partially defeated the purpose of the shotgun/automate approach I was looking for.</p><h3 id="qwen-portion-(workflow-default)"><strong>Qwen Portion (Workflow Default)</strong></h3><p><strong>Positive:</strong></p><pre><code>Remove the background from the image and replace with a blank white backdrop, leaving only the same original human subjects in the same position, same pose, and same placement within the image.</code></pre><p><strong>Negative:</strong></p><pre><code>NULL</code></pre><h3 id="wan-2.2-portion-(workflow-default)"><strong>Wan 2.2 Portion (Workflow Default)</strong></h3><p><strong>Positive:</strong></p><pre><code>ultra realistic, super high detail, modeling, steady camera. orbit 360</code></pre><p><strong>Negative:</strong></p><pre><code>Vibrant colors, overexposed, static, blurry details, subtitles, style, artwork, painting, image, still, overall grayish tone, worst quality, low quality, JPEG compression artifacts, ugly, incomplete, extra fingers, poorly drawn hands, poorly drawn face, deformed, disfigured, malformed limbs, fused fingers, motionless image, cluttered background, three legs, many people in the background, walking backwards</code></pre><h2 id="multiple-subject-background-removal-360-orbit">Multiple Subject - Background Removal - 360 Orbit</h2><p>Multiple subjects tend to work fantastically in the Qwen image edit with the prompt I settled on (previous iterations would cause subject removal, over editing, or general AI nightmare generation). Success rate using the default is upwards of 90% for a clean cut, with success dropping the more "primary" subjects that are in the photo. Background subject it does well at cutting out. The Wan portion needs work, and will be updated. Usually you'll get a handful of good images out of it, but a large portion will be trash/have ghosting or artifacts/create AI limbs. Not ideal for lora use, may have some good character use.</p><h3 id="qwen-portion"><strong>Qwen Portion</strong></h3><p><strong>Positive:</strong></p><pre><code>Remove the background from the image and replace with a blank white backdrop, leaving only the same original human subjects in the same position, same pose, and same placement within the image.</code></pre><p><strong>Negative:</strong></p><pre><code>NULL</code></pre><h3 id="wan-2.2-portion"><strong>Wan 2.2 Portion</strong></h3><p><strong>Positive:</strong></p><pre><code>WIP (to come after further testing/verification)</code></pre><p><strong>Negative:</strong></p><pre><code>WIP (to come after further testing/verification)</code></pre><h2 id="objectitem-background-removal-360-orbit">Object/Item - Background Removal - 360 Orbit</h2><p>Further testing on the horizon, but will be updated after this is done. It worked on my cat flawlessly with the default, but I'd like to get a broader range here.</p><h3 id="qwen-portion"><strong>Qwen Portion</strong></h3><p><strong>Positive:</strong></p><pre><code>WIP (to come after further testing/verification)</code></pre><p><strong>Negative:</strong></p><pre><code>WIP (to come after further testing/verification)</code></pre><h3 id="wan-2.2-portion"><strong>Wan 2.2 Portion</strong></h3><p><strong>Positive:</strong></p><pre><code>WIP (to come after further testing/verification)</code></pre><p><strong>Negative:</strong></p><pre><code>WIP (to come after further testing/verification)</code></pre><h1 id="tips">Tips</h1><ul><li><p>General use should be pretty simple as far as plug and play as long as you have the required nodes, and the correct models. I referenced by exact (searchable at your place of choosing) name in the workflow each of the diffusion models, loras, vae, and text encoders used in the workflow</p></li><li><p>I would, unless required, not change the prompts built in to the current workflow. You may have specific need to do so (in which case have at it) for specific poses, angles, or use cases, but for a single subject looking to create a character output what I have in place has worked for me with greater than 95% success on both ends</p></li><li><p>Sometimes the seed it picks just sucks for your subject, even if it isn't overly complicated/multiple people. I'd run a second round with a different seed before editing prompts heavily if this is the case</p></li><li><p>There is an optional rgthree lora node in the image edit portion which can be leveraged if your version of Qwen requires unlocking NSFW (if that's what you're looking to generate), or you want to edit an image in transit which may require the use of a lora</p></li><li><p>I've also left the default 2nd and 3rd image nodes from the ComfyUI template that can be leveraged as reference images should your prompt require it. My recommendation, though, would be that if you're going to get really crazy with image editing beforehand this batch workflow might not be the right solution for you, and a split set of workflows may work better for your situation (or an update/edit to mine with a custom pause/review node)</p></li><li><p>That said, you can go crazy with it and queue up multiple runs of this just to see what happens, which was the point to begin with (kick off ten runs, go do something else, see what you got - no need to babysit or wait for all the image edits and then queue up all the video outputs)</p></li><li><p>You're free to remove the Lightning lora in the image edit and use what I was calling the "full fat" version in testing, however I found that aside from adding 1-10 minutes (depending on the image complexity and size) to the Qwen portion, nearly no other benefit was gained. After extensive testing here I just scrapped that version entirely. If you're getting crazier with image editing in workflow, though, you may see benefit from it</p></li></ul><h1 id="known-issues-next-to-come">Known Issues / Next to Come</h1><h3 id="future-enhancements:">Future Enhancements:</h3><ul><li><p>For version two my plan is to add enhanced throughput to image property identification and use, passing those down appropriately to later steps. Currently you still have to set the WAN 2.2 video output resolution and framerate to your desired needs, but I'm planning on enhancements here that update and variablize this data for future use and correct aspect ratio identification</p></li><li><p>Cleanup and general tightening of the workflow, visually. I'm on a Samsung G9 with plenty of side to side screen real estate, but I've also recently dropped from a four monitor setup to this and am a sucker for having too many things and references open at one time. In the next version if I don't need to see it (and you don't need to ever edit it) it'll likely be condensed and collapsed</p></li><li><p>Optional Upscale (image and video) in workflow will likely come with the update that allows for better handling of predetermined image sizing and cropping settings. Still trying to get better at this on my own and understand the math behind it before I worked it into something with this many moving pieces. There will likely be an add-on to this flow that is optional that adds frames and upscale, especially for when it's being used for things outside of character studies/lora data generation.</p></li><li><p>Variations of this workflow branching off for background replacement and related prompting, replacing the video stage two with a dedicated image edit prompt based on having a clean background slate to work with</p></li></ul><h3 id="known-issues:">Known Issues:</h3><ul><li><p>The WAN 2.2 portion can struggle with multiple subjects or weird rotational axis requirements (especially very elaborate poses) still. Editing the prompt to account for this specifically can help, but it hasn't solved everything (and somewhat defeated the purpose of being able to batch out a bunch of these) - long story short, the more complex your image/subject, the more tweaking you may have to do in that portion</p></li><li><p>If your model isn't spinning you're likely not using the Orbit lora. I wasn't, so mine weren't. Make sure you snag a version of that and you should be good to go.</p></li><li><p>Extremely large images plus Qwen on even decent hardware can add a ton of time to this, even with the lightning setup. I found that by cropping or resizing my images down it massively helped. You may have better hardware than my testing specs (5080, 64GB RAM, Ryzen 7 9800X3D) which may make that trivial, but you also might be using heavier models as a result. Smaller images will help with time frames massively.</p></li><li><p>Generation of off screen limbs if a subject is really out of center can still be a bit wonky. I've had it work, I've had it create nightmares. YMMV</p></li><li><p>Held objects can get a bit wonky as it spins/creates the third dimension there. Sometimes it works absolutely fine, other times not so much. The most awkwardness I've seen in testing is on cell phones held awkwardly for selfies. If you're cropping after for a face lora this is essentially a non-issue, but if you're doing this for a character/full body use you may want to crop those portions out (or tag accordingly)</p></li><li><p>While cleaning up to publish today something I did stopped the clear VRAM node from posting to console, will look into and fix with the first update</p></li></ul><h3 id="general-notes:">General Notes:</h3><ul><li><p>Theoretically this works with Qwen 2512 or Qwen 2509, or whatever similar version you choose, as long as you use the correct VAE, Clip, and Diffusion Models</p></li><li><p>If you want to use something like <a target="_blank" rel="ugc" href="https://civarchive.com/models/1648982/wan-nsfw-posing-nude">Wan NSFW Posing Nude</a> for your batch image generation you absolutely can, just swap the Orbit Lora for that (or bypass and and a lora node to the Wan portion), the goal of the batch is to get character output/multiple angles, other non 360 rotation loras would serve this purpose well, just edit and prompt accordingly</p></li><li><p>When the more complex version happens I'll likely fork this one leaving it as light weight as possible, and branch from there</p></li><li><p>I'm working on a prompt guide to add to the top of this that has more success for multiple subjects/different subjects/more unique poses. Update to come (in progress above)</p></li></ul><p></p>

Files with SHA256: 632b512bd9b1d5109b1546676e600af618ba9b900934d939f541b41bc3541807