Support structured custom location entries
This commit is contained in:
@@ -64,10 +64,14 @@ node. For cleaner workflows, use the split nodes:
|
||||
`men_weights=0.5,0.3` means 50% no man and 30% one man.
|
||||
- `SxCP Location Pool` outputs `location_config`. `replace` uses only the
|
||||
selected/custom location pool; `add` keeps the category's own locations and
|
||||
adds yours. Custom lines can be plain location text, or `slug: location text`.
|
||||
adds yours. Custom lines can be plain location text, `slug: location text`, or
|
||||
one-line JSON objects/arrays. JSON location entries preserve metadata such as
|
||||
inline `camera_profile` / `scene_camera_profile`.
|
||||
- `SxCP Composition Pool` outputs `composition_config` to control framing
|
||||
separately from location. Use it when category framing mentions unrelated
|
||||
outfit-check details such as shoes, bags, or mirror poses.
|
||||
outfit-check details such as shoes, bags, or mirror poses. Custom composition
|
||||
lines can also be one-line JSON objects/arrays when metadata needs to travel
|
||||
with the selected composition.
|
||||
- `SxCP Location Theme` outputs matched `location_config` and
|
||||
`composition_config`. Themes such as `classical_library`,
|
||||
`semi_public_affair`, `hotel_corridor`, `parking_garage`, and
|
||||
|
||||
Reference in New Issue
Block a user