Identify the virtual inputs
An interface’s loopback channels are software-visible inputs rather than extra physical sockets. Focusrite describes them as a way to record software playback or a selected mix back into a recording application. Availability and channel numbering vary by interface model and generation, so use the exact product’s guide before selecting an input.
Write down what should be captured. You might want an instrument application, a remote conversation with the participants’ agreement, or a mix of microphone and computer playback. Also write down what should be excluded, such as notification sounds or the recording application’s own return. This defines the routing before you start moving faders.
Prevent the recorded return from re-entering
If the recording track plays back into the same mix being captured, it can create a feedback loop. Focusrite’s loopback instructions call for muting the recording channel or routing its output away from the loopback source as appropriate. Follow the model’s diagram and keep monitoring levels low while verifying the setup.
Create a short test with a recognizable sound from each intended source, one at a time. Stop recording and play the file back through a normal listening route. Confirm that each source appears once and that excluded audio is absent. If the result doubles or grows unexpectedly, stop and inspect the routing instead of trying to balance the problem with lower faders.
Keep separate tracks when they are useful
If later editing requires independent control of voice and computer audio, record them on separate suitable inputs or tracks where the system supports it. A single loopback mix may be convenient, but its components cannot automatically be separated afterward. Decide this before the session rather than discovering it while trying to remove a loud notification from a combined recording.
Save the working routing preset and give it a clear name. Restore the ordinary monitoring arrangement after the session if loopback is no longer needed. Before the next use, check whether application output assignments have changed. A documented loopback route is repeatable; a collection of virtual inputs chosen by trial and error is much harder to troubleshoot when another program is added.
Exclude notifications during the test
A loopback source that captures the entire system output can include alert sounds as well as the intended application. Before a session, check whether the interface or software offers a dedicated playback route for the material you want. If it does, assign that route explicitly and test it. If it does not, silence avoidable notifications and understand that the captured mix is broader than one application.
Keep a short test file containing each intended source in sequence. Say or note what should be heard, then verify the saved recording. This catches a common ambiguity: hearing something in headphones does not prove it is included in loopback, and seeing a meter move does not prove the correct source is isolated. Test the saved file as the final evidence of the routing.
