In the voice editor, choose Effective sound / Where settings came from. It uses the attached source item captured through the entry route or voice list. If none is attached, choose an ordinary buffer at its current point. The item must provide inspectable facts or valid retained feedback. Choose another source context deliberately selects a replacement.
This simulates captured facts and rules, showing the selected voice, matching rules, requested fields, and their sources. One rule can set pitch and another richness. A stronger pitch rule can mask a base edit; a rule choosing a different named voice can make the open entry irrelevant. Competing relative rates also replace, not add.
P previews the edited voice in context and B compares original/edited with the same facts, rules, and text. These voice-only previews omit cues and spatial placement. Family remains a portable fallback outside full preview. Per-choice support applies the actual fallback’s tuning before context, and an explicit context value overrides even when numerically equal to shared tuning. Requested values remain distinct from confirmed starts, accepted audio, and unsupported adjustments. Changed/deleted sources are rejected. After saving a rule, refresh facts and rules from the source to capture its contribution. q returns to the base editor.
Adjust for this context presents matching criteria and personal, session, or buffer lifetime. Choose one adjustment and value to prepare the ordinary rule editor. A richness-only change does not select a different voice. Review criteria with RET, use V for another voice field, and save the chosen scope with w. The palette is unchanged. Finish existing rule-editor work before preparing another contextual rule.
Inherit removes a field so weaker contributions can supply it; removing the last voice field removes the patch. Existing explicit defaults are shown and preserved when another field is edited. Zero is not inheritance. Some older default forms cannot reset underlying tuning on every backend; inspect preview and explanation. Context changes are saved as rules, not as a palette entry containing the combined result. The Developer Guide describes representation and compatibility.