AV ComfyUI Manual
49 / 64
Files
49
PEOPLE / PPL · WORKFLOW 01

Generate & Place New People by Mask — generate the person separately, solve placement separately

Workflow 01 is used when the required person does not yet exist in the base render. The character is generated independently, segmentation turns it into a clean compositing element, and a scene placement mask defines where it enters the architectural frame.

CONFIRMEDGeneration, segmentation, preparation, first composite and return topology are confirmed by source documentation for Epspoziciya_archviz_ph_sdxlflux_v001. A standalone JSON is intentionally not published as “ready” until the raw source workflow with complete serialized schemas is available for safe extraction.
COMPOSITING

Two routes converge at selector 459

MODE 1FLUX person
477 Color → 449 Cut → 429 Paste → 672
459PPL Switchcurrent: image1
MODE 2Input / 3D inpaint
503/504 Cut → 494–496 Inpaint → 509 → 685
459Selected PPL
573Detail transferblend 0.09
67VAE Encode
57Main FLUX
53Decode
730LQ Saveactive output
01 · ROLE

When to use Workflow 01

Use this mode when the required person does not exist in the original 3D/Corona scene and stock or 3D assets cannot provide the required period, clothing, pose or character type. AI creates the person asset separately from the architecture.

Architecture should not be regenerated together with the character. Generate the person as a separate image asset first, isolate and prepare it, then insert it into the approved scene canvas.

CONFIRMED

Core principle

PPL FLUX generation node 829 exists as a separate decoded image before composite; the main architectural scene enters later at the paste stage.

INFERRED

Production value

Separating person generation from the architectural canvas reduces the risk of unintended changes to facade, perspective and composition.

02 · WORKFLOW 01 VS 02

The key difference between the two PEOPLE workflows

CONFIRMED

Keep them separate

Workflow 01 and Workflow 02 use similar generation / segmentation / preparation tools but operate under different spatial contracts.

WorkflowWhat defines placementAI responsibility
01 · Generate & PlaceScene placement mask / target regionCreate a new person, isolate them and place them
02 · Replace ExistingExisting 3D / rendered personImprove or replace the person in the same spatial slot
03 · FULL ROUTE

Complete production route for Workflow 01

04 · GENERATE PERSON

The person is generated first as an independent FLUX image

  • If the person is already wrong at Preview 409, do not continue to mask/composite.
  • The prompt should describe full body, scale, action, clothing and lighting context.
  • Placement in the architectural scene is not solved at this stage.
StageNodesFunction
Prompt825 + 408 + 799 + 800 + 822Person + environment/light/style context
Assembly823 → 824 → 820Assemble the final PPL text
Encode831 → 830CLIP conditioning + FluxGuidance 2.1
Sample826 + 819 + 827 + 61 + 58 → 828Independent person generation
Decode829Person image before segmentation
Checkpoint409Verify the person before mask / composite
05 · ISOLATE PERSON

Florence2 answers WHERE; SAM2 answers WHAT EXACTLY

The generated person passes through People source selector 552 and is normalized to detection canvas 780. Florence2 550 performs phrase grounding, 114 converts detection into coordinates, and SAM2 115 builds the pixel mask.

The mask is then expanded and softened by nodes 144 / 146, after which 420/781 create the crop used to prepare the compositing element.

  • Florence2 and SAM2 must operate in the same coordinate space.
  • Person Mask should describe the figure, not its future position in the scene.
  • Image / bbox / mask batch cardinality must be consistent before downstream processing.

06 · TWO-MASK PRINCIPLE

Person Mask ≠ Placement Mask

This is the central idea of Workflow 01. The mask used to cut out the person and the mask/placement input used to position the person in the scene serve different roles and should never be treated as one conceptual object.

CONFIRMED

First composite topology

Paste By Mask 429 receives separate upstream inputs from 451, prepared person 449 and base scene 779.

NOT CONFIRMED

Exact semantic source of 451

Source documentation confirms incoming topology 451 → 429, but without the raw workflow export in the current assets we do not publish a standalone JSON with unverified serialization of this placement input.

MaskQuestionResponsibility
Person MaskWHAT TO TAKE?Isolate the generated person for crop / alpha / cutout
Placement Mask / placement inputWHERE TO PUT?Define the target region / spatial placement in the base scene
07 · PREPARE CUTOUT

The generated image becomes a compositing element

Color Match helps integration but does not replace a correct lighting prompt. A wrong light direction cannot be fixed by color correction alone.

NodeRoleQC
420 / 781Crop by person maskEntire figure stays inside the crop
422Remove Background / InspyrenetNo halo or residual generated background
477Color MatchTone/contrast closer to the base scene
449Cut By MaskRGB and alpha/mask remain aligned
08 · PLACE LOCALLY

Node 429 is the boundary between the person asset and the architectural scene

Paste By Mask 429 receives prepared person 449, base scene 779 and a separate placement-related input 451. Stored mode keep_ratio_fit shows that scale/fit is part of composite behavior.

After 429, the output passes through 672 and reaches image1 of selector 459. At this point the independent person asset becomes part of the master scene data plane again.

09 · REFINE GLOBALLY

After PPL return, the person enters shared master refinement

Selector 459 returns the composited scene to the main pipeline. Node 573 then performs detail transfer, 67 encodes the result to latent, 57 runs main FLUX sampling and 53 decodes the result.

This stage helps seamless integration, but methodologically it belongs outside the standalone PPL module: the person should already be correctly placed before entering main FLUX.

CONFIRMED

Active return

459 → 573 → 67 → 57 → 53; node 53 has an active LQ save route to 730.

10 · CHECKPOINTS

Five checkpoints where we stop and prove the result

CheckpointWhat must be proven
A · 409 / after 829The person generation itself is correct
B · after 115 / 146Person Mask is clean and matches the intended figure
C · after 422 / 449Cutout is clean, halo-free and alpha is aligned
D · after 429 / 672Scale, position and scene composite are correct
E · 53 / 730Main FLUX refinement preserved both the person and the architecture
11 · ARCHVIZ VALUE

Why this workflow is especially valuable for historical and unusual scenes

  • Create a period-specific person unavailable in a stock library.
  • Match clothing, action and visual language to the architecture.
  • Keep the approved architectural base as a separate source.
  • Correct person-generation errors independently from the main scene.
  • Control placement locally instead of regenerating the full frame.
12 · PRODUCTION CHECKLIST

Workflow 01 is ready for the Master only after these checks

  • The generated person reads as full body and matches the required role.
  • Person Mask and Placement Mask are not confused.
  • Florence2 / SAM2 use a consistent source size / coordinate space.
  • The crop does not cut off limbs or accessories.
  • Remove BG leaves no halo.
  • Color Match is not being used to hide an incorrect light direction.
  • Paste preserves a believable scale relative to horizon and architecture.
  • Feet have credible ground contact; no floating.
  • Occlusion relative to architecture is physically plausible.
  • Main FLUX refinement does not alter approved scene geometry.
13 · STANDALONE JSON CONTRACT

What belongs in the independent training JSON and where it should end

NOT CONFIRMED

Why the JSON is not published yet

The current repository / Library assets do not include raw Epspoziciya_archviz_ph_sdxlflux_v001.json with complete custom-node serialization. Under our rules, a reconstructed pseudo-JSON cannot be presented as an importable workflow.

14 · PASS CRITERIA

Workflow 01 is understood when you can explain it in one sentence

CONFIRMED

Spatial rule

Workflow 01: placement is defined by a target region / placement input. Workflow 02: placement is defined by an existing person.