Default atlas layout #4

Closed
opened 2026-10-06 03:55:51 +00:00 by crowmaki · 1 comment
Owner

Part of #1

Question

What is the default Atlas layout for up to three Looks × 4 Tiles (face close-up, front, side, back A-pose)? Settle grid vs stack geometry, burned-in labels or none, minimum face-tile resolution, and the output image size. The owner's hands-on H3 experience drives this.

Part of #1 ## Question What is the default Atlas layout for up to three Looks × 4 Tiles (face close-up, front, side, back A-pose)? Settle grid vs stack geometry, burned-in labels or none, minimum face-tile resolution, and the output image size. The owner's hands-on H3 experience drives this.
Author
Owner

Resolution

  1. Geometry: one row per Look, stacked top to bottom. Columns go in template order: face → front → side → back. The prompt refers to subjects by row ("top / middle / bottom row of Image N").
  2. No burned-in text. Only positional phrasing maps subjects to rows.
  3. Cells: a uniform 4:9 portrait cell for every Tile, matching sheet Tiles of about 480×1080 (a 1920×1080 sheet split into about 4 columns). Each Tile is scaled to fit and padded, never cropped.
  4. Size: a megapixel budget, 1.0 MP by default (the owner has seen H3 handle 1.0 MP), that keeps the aspect ratio and never scales up, so fewer Looks get bigger Tiles. A native size toggle turns the budget off. Both are set per Project with a per-Setup override (e.g. for close-up-heavy shots), and both are part of the Atlas's content identity.
  5. Fewer than 3 Looks: the canvas shrinks to N rows. A single Look still gets a 1-row Atlas.
  6. Padding and gutters: neutral mid-grey. The gap between rows is wider than the gap between Tiles in a row.
  7. Wardrobe items go in their own image slot, outside the Atlas. The Look's row still shows the full default-wardrobe turnaround, and partial preservation in the prompt tells H3 to ignore its clothing.
  8. Grouping: by default, Looks fill Atlases in the Setup's subject order, 3 per Atlas. The user can regroup per Setup (e.g. to split Looks with similar clothing against attribute bleed). The regrouped order is part of the content identity.
  9. Missing Tiles: the empty cell collapses. An Atlas only combines Looks with exactly the same Tile set (same parity), so every column shows the same view in every row. Default grouping and user regrouping both stay within a parity group. The layout is fixed for the slice, and a layout id in the content identity leaves room for others later.

Downstream:

  • Prompt composer phrasing (#9): row phrasing and the column meaning per parity.
  • Reference slot budget (#10): extra slots from parity splits and user regroups, plus a slot for each Wardrobe item.
  • .studio schema (#11): the budget and native toggle (Project plus Setup override) and the per-Setup grouping.
## Resolution 1. **Geometry:** one row per Look, stacked top to bottom. Columns go in template order: face → front → side → back. The prompt refers to subjects by row ("top / middle / bottom row of Image N"). 2. **No burned-in text.** Only positional phrasing maps subjects to rows. 3. **Cells:** a uniform 4:9 portrait cell for every Tile, matching sheet Tiles of about 480×1080 (a 1920×1080 sheet split into about 4 columns). Each Tile is scaled to fit and padded, never cropped. 4. **Size:** a megapixel budget, **1.0 MP by default** (the owner has seen H3 handle 1.0 MP), that keeps the aspect ratio and never scales up, so fewer Looks get bigger Tiles. A **native size** toggle turns the budget off. Both are set **per Project with a per-Setup override** (e.g. for close-up-heavy shots), and both are part of the Atlas's content identity. 5. **Fewer than 3 Looks:** the canvas shrinks to N rows. A single Look still gets a 1-row Atlas. 6. **Padding and gutters:** neutral mid-grey. The gap between rows is wider than the gap between Tiles in a row. 7. **Wardrobe items** go in their own image slot, outside the Atlas. The Look's row still shows the full default-wardrobe turnaround, and partial preservation in the prompt tells H3 to ignore its clothing. 8. **Grouping:** by default, Looks fill Atlases in the Setup's subject order, 3 per Atlas. The user can regroup per Setup (e.g. to split Looks with similar clothing against attribute bleed). The regrouped order is part of the content identity. 9. **Missing Tiles:** the empty cell collapses. An Atlas only combines Looks with exactly the same Tile set (same **parity**), so every column shows the same view in every row. Default grouping and user regrouping both stay within a parity group. The layout is fixed for the slice, and a layout id in the content identity leaves room for others later. **Downstream:** - **Prompt composer phrasing** (#9): row phrasing and the column meaning per parity. - **Reference slot budget** (#10): extra slots from parity splits and user regroups, plus a slot for each Wardrobe item. - **.studio schema** (#11): the budget and native toggle (Project plus Setup override) and the per-Setup grouping.
Sign in to join this conversation.
No description provided.