8.9.6 Set Shared Engine Preferences

Engine preference is global, not buffer-local. In C-e H v, e chooses a session preference, S chooses and saves one, and r restores saved or initial order. Availability and unsaved-policy checks remain. The speech-settings scope does not change these saving rules.

  1. Edit Saved Engine Configuration

    From engine details choose Engine configuration, or run M-x omnivox-engine-configuration. This needs an updated local Omnivox host. Files belong to the speech host, including Windows under WSL; entered paths must make sense there.

    RET edits a row: enabled engines, preferred/backup order, or automatic-selection permission for a helper. Advanced startup settings exposes literal arguments and wait limits. l changes engines while retaining drafts. Add installed helper registers a compatible program disabled; it neither downloads nor executes it. Enable, Save, then Apply to check runtime support.

    s saves without changing speech. A file conflict retains the draft for fresh review. g rereads saved settings, asking before discarding. q returns while retaining the draft. Saved/draft states are distinct from worker availability, and explicit environment overrides remain visible.

    A reviews and applies saved engine/library settings to both workers through preflight and rollback. Save all edits first. Check saved settings validates files only. P opens live voices in Workbench, so saved changes are audible there only after successful Apply.

  2. Choose The Shared Preferred Engine

    C-e d e chooses an available engine for this session; C-u C-e d e saves the preference. With no saved policy, an ordinary first invocation uses live Omnivox policy as an in-memory baseline without writing. The prefix saves that baseline and preference. Explicit named-voice physical choices outrank it.

    Workbench policy is shared across palettes. O toggles preferred engines and [~/~] reorders them; f toggles fallbacks and {~/}~ reorders them. D enables/disables and K requests a recovery probe. These are staged changes; w saves and applies. Physical choices for an individual entry are saved in its voice editor.

    Names appear first in tables; x details capabilities, native IDs, and registration. Availability, failure, predicted selection, and observed playback are distinct. Saving engine policy is separate from voice or profile saving. For unconfirmed application, see Recovering Unfinished Changes. Installation belongs to Optional Omnivox Engines.