🎯 Learning objectives

• Set iD14 gains so meters are healthy without clipping
• Configure the iD mixer for stream-critical inputs
• Choose buffer sizes that avoid dropouts on stream day
• Verify macOS/Windows sound settings won't hijack your stream

💻 What the iD14 is doing in your world

The Wing builds the room. The X32 builds the stream mix from AES50 splits. The iD14 is the bridge into the computer that runs Vimeo (or OBS/encoder feeding Vimeo). Treat it like a precision on-ramp — not a third FOH console.

• Stereo (or dual mono) from X32 stream outs → iD14 line inputs
• iD14 USB → computer becomes the audio device for your streaming software
• Optional: headphones on iD14 to audition exactly what the computer can hear

⚙️ Setup checklist that prevents Sunday fires

1. Install current Audient drivers / iD app for your OS. Reboot once after install.
2. Sample rate 48 kHz everywhere if possible (console card/interface/OS/stream). Mismatches cause pitch/glitches.
3. Buffer — streaming computer: start 128–256 samples. Lower latency is less critical than stability for church stream.
4. Clock — one master clock. Don’t let devices fight.
5. OS sound panel — set iD14 as input for the streaming app. Disable fancy “audio enhancements.”
6. Levels — X32 stream outs healthy; iD14 input meters show solid level without red.

🧪 Lab — prove the path with tone

• Send a tone or pink noise from X32 stream bus at a known level. Confirm meters on iD14 and in the streaming app move together.
• Intentionally clip iD14 once in rehearsal (then fix) so you recognize the sound/look of interface clipping.
• Put on iD14 headphones and compare to the room — stream mix should be intentional, not a copy of Wing FOH energy.
• Write the exact app input settings (device, channels, sample rate) on your run sheet.

🎬 Video tutorials

Curated watch-list. If an embed is unavailable, use the YouTube link — then come back and do the lab. Watching without the lab is only half-training.

📝 Prove it