Papers › DiffusionRig: Learning Personalized Priors for Facial Appearance Editing

DiffusionRig: Learning Personalized Priors for Facial Appearance Editing

13 Apr 2023CVPR 2023 1arXiv:2304.06711archive 2025-07-28

Zheng Ding, Xuaner Zhang, Zhihao Xia, Lars Jebe, Zhuowen Tu, Xiuming Zhang

We address the problem of learning person-specific facial priors from a small number (e.g., 20) of portrait photos of the same person. This enables us to edit this specific person's facial appearance, such as expression and lighting, while preserving their identity and high-frequency facial details. Key to our approach, which we dub DiffusionRig, is a diffusion model conditioned on, or "rigged by," crude 3D face models estimated from single in-the-wild images by an off-the-shelf estimator. On a high level, DiffusionRig learns to map simplistic renderings of 3D face models to realistic photos of a given person. Specifically, DiffusionRig is trained in two stages: It first learns generic facial priors from a large-scale face dataset and then person-specific priors from a small portrait photo collection of the person of interest. By learning the CGI-to-photo mapping with such personalized priors, DiffusionRig can "rig" the lighting, facial expression, head pose, etc. of a portrait photo, conditioned only on coarse 3D models while preserving this person's identity and other high-frequency characteristics. Qualitative and quantitative experiments show that DiffusionRig outperforms existing approaches in both identity preservation and photorealism. Please see the project website: https://diffusionrig.github.io for the supplemental material, video, code, and data.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 7 code samples harvested from 1 repository linked to this paper: 0 ran · 7 unverified.

By repository: official repository: 7 samples from 1 repository, 0 ran (0 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

adobe-research/diffusion-rig officialmentioned on GitHubpytorchSyntology: 7 samples, 0 ran · 7 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

7 samples harvested: 0 ran · 7 unverified. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

7unverified

Licence: 7 of the 7 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from adobe-research/diffusion-rig. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

adobe-research/diffusion-rig official repository 7 samples, 0 ran · 7 unverified
AttentionBlock in 69 papers diffusion/model.py unverified licence not identified · pointer only · 22ef91aa500af651 · report
DiffusionRig diffusion/model.py unverified licence not identified · pointer only · 04ee3c96077eb137 · report
TimestepBlock in 11 papers diffusion/model.py unverified licence not identified · pointer only · 482a63d7f1598ed8 · report
TimestepEmbedSequential in 28 papers diffusion/model.py unverified licence not identified · pointer only · fedcf75fd2b2ca46 · report
UNetModel in 23 papers diffusion/model.py unverified licence not identified · pointer only · 62664a62d891810b · report
create_model in 163 papers diffusion/model.py unverified licence not identified · pointer only · fb8a7a13dcb8c76d · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for DiffusionRig (graph method: DiffusionRig). 19 bricks; individually on a fixture: 9 ran (of which 4 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 4 where Syntology's instrument failed) · 10 unverified. The assembly has not been run end-to-end.

  1. DiffusionRig entry · level 0 · unverified · 04ee3c96077eb137
  2. create_model helper · level 0 · unverified · fb8a7a13dcb8c76d
  3. UNetModel model · level 0 · unverified · 62664a62d891810b
  4. AttentionBlock model · level 0 · unverified · 22ef91aa500af651
  5. Downsample helper · level 1 · ran · 8c5676227adb2492
  6. ResBlock model · level 0 · unverified · a74a21eb500c2979
  7. TimestepEmbedSequential model · level 0 · unverified · fedcf75fd2b2ca46
  8. Upsample helper · level 1 · ran · 6998a3677700ee6c
  9. conv_nd helper · level 0 · unverified · fe4eb545bbb728e0
  10. linear helper · level 1 · ran · our draft was wrong · 0e30585f04efffbe
  11. normalization helper · level 1 · ran · our draft was wrong · 5b31715a9b105926
  12. timestep_embedding helper · level 1 · ran · our draft was wrong · b0aa348a2f95ef0f
  13. zero_module helper · level 1 · ran · our draft was wrong · 129b804760b3115f
  14. QKVAttention helper · level 1 · ran · 5ebe00ac9e392f07
  15. QKVAttentionLegacy helper · level 1 · ran · c21412aa89ed28a7
  16. avg_pool_nd helper · level 0 · unverified · ecd0fc28815b65ae
  17. TimestepBlock helper · level 0 · unverified · 482a63d7f1598ed8
  18. GroupNorm32 helper · level 1 · ran · 426c2385fa431d9a
  19. count_flops_attn helper · level 0 · unverified · 0c49097ae6ff37ef

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2304.06711") returns these assemblies with each brick's role and wiring (how to connect).

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Diffusion

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections