uncannyuse
github

Development note

Audio Mix Groups is a mixer-driven component: the inspector launches the editor, but the authored state lives outside a normal inline parameter block.

by elkraneo · 2026-03-13

Fixture diffs show the inspector card is only a launcher. Real state lands in child `RealityKitAudioMixGroup` prims (`gain`, `mute`, `speed`) plus external `RealityKitAudioFile` prims routed with `rel mixGroup`.

Metadata

  • Component: audio-mix-groups-component
  • Status: confirmed
  • Confidence: high
  • Evidence type: direct-diff
  • Scope: USDA authored
  • Author: elkraneo
  • Date: 2026-03-13
  • RCP version: 26.3
  • Xcode build: Xcode 26.3 (17C529)

Reproduction

  1. Open the Audio Mix Groups component in Reality Composer Pro.
  2. Use Open Audio Mixer from the inspector card.
  3. Add a mix group, assign one or more audio files, then change gain, mute, or speed.
  4. Save fixture variants and diff USDA against the clean BASE.
  5. Verify the component prim stays structural while authored values land in mix-group and audio-file prims.

Evidence

  • Verified field matrix
    local-only evidence path (not publicly exposed)

    Documents Audio Mix Groups as mixer-driven with group children and external audio file routing.

  • Component research log
    local-only evidence path (not publicly exposed)

    Tracks Audio Mix Groups fixture coverage and revised missing-fixture count.

  • Audio Mix Groups fixture set
    local-only evidence path (not publicly exposed)

    Includes BASE, AddMixGroup, assignment, and gain/mute/speed variants.

Details

Audio Mix Groups behaves differently from the usual Reality Composer Pro component pattern. The inspector does not expose an inline field list to edit. Instead, it hands off authoring to the Audio Mixer.

The clean fixture diffs show a two-part authored shape:

  • The component prim itself is mostly structural: RealityKit.AudioMixGroups.
  • Group controls are authored as child RealityKitAudioMixGroup prims with gain, mute, and speed.
  • File routing is authored separately as top-level RealityKitAudioFile prims that point back to a mix group through rel mixGroup.

That means the interesting authored state is split across child mixer-group prims and external audio-file prims, not stored as a flat set of component attributes in the inspector card.