In this article
In Audient’s interview with Joe Wakeford, he described keeping familiar physical controls while using an iD22 to monitor and route a recording session. The models available to a voice actor change. The practical test is doing the job in front of you without interrupting the read.
Listen from the actor’s position
Speak a few lines. Can you hear your own voice comfortably with the director’s return audible? If there’s a distracting delay, compare the monitoring options your setup supports. Do the check on headphones in your usual recording position.
Check the director’s return separately
Ask a colleague to join the call and say what reaches them. A cue or a reference they need to hear can go to the monitoring path while you save a clean voice track for the edit. Make the setup clear to the engineer before the director arrives. Our live remote session checklist covers the handoff in more detail.
Open the files from the test
Record a few seconds with both people speaking at different times. Listen to the track you intend to deliver and confirm it has the sources you agreed to capture. Check the export settings once, and keep the template for the next session.
Read Audient’s profile of Joe’s iD22 setup on VoicesUK for the original equipment and workflow.
Test a short changeover while someone is listening
In the Audient interview, Joe talked about keeping a physical monitor dial to hand and leaving an earlier control surface in the setup. One practical question behind those choices was whether a local audio path could keep recording while the engineer or director was talking. You can answer that for your interface without buying anything. Send a short voice feed to a colleague, start and stop the local recording, and have the colleague speak through the return. Compare the local file with what the colleague heard.
Then use the same test for a change in monitoring level. Ask what changes on the remote side when you adjust what you hear in the headphones. If you can hear the problem before a booking, you can write down which controls belong to that job and leave the rest alone. Keep the export and one note about the routing with your live-session preflight.
In the actual session, have the editor check a sample near the start. It should contain the mic signal you intended, and a note that identifies which person recorded the master.
Leave a Reply