8.13.1 A saved voice change is not audible ¶
Use one representative item and repeat the same navigation or reading action
for each comparison. A preview and a different action may use different
context, so changing several things at once makes the result harder to explain.
- Read the editor’s save and application status first. A retained draft has
not been saved; a partial or unconfirmed application needs
its own recovery, not another speculative voice edit.
- Open Voice Palettes with C-e H v p and check which palette is active.
Saving to the collection does not select its destination. Activate that
palette only if you intend to use it now; otherwise its unchanged live
sound is expected. Return through the manager and menu to the source.
- Explain the item with C-e E. Check that it resolves to the named entry
you edited. A rule may choose a different entry, or this kind of text may
have an explicit voice rather than using
default.
- Inspect the physical choice and last sample result. An explicit choice
outranks the shared preferred-engine policy, and that choice’s individual
tuning can mask a shared adjustment. Then check availability, disablement
and failures rather than repeatedly changing the engine order.
- In the voice editor, inspect Effective sound / Where settings came from.
A contextual rule may override the edited value. Compare samples and
reported unsupported fields to distinguish an override from an engine
that cannot express the adjustment.
After correcting the identified cause, return to the original item and repeat
the same action. Confirm both the explanation and what you hear. If the cause
remains unclear, keep the working settings and prepare a problem report
instead of removing unrelated rules or voices.