Understand UAD REC and MON Before Mixing

Avoid confusing a performer’s monitored sound with the audio captured in the DAW.

Where Universal Audio and MixingMusic fit

Apollo and UAD Console support low-latency monitoring and let the user record either processed or unprocessed input, depending on insert mode. MixingMusic begins after recording: upload the committed files or aligned stems you intentionally exported.

This guide describes a complementary workflow. MixingMusic.AI is independent from Universal Audio; the trademark belongs to its owner, and no partnership or endorsement is implied.

The audio problem to solve

UAD REC routes post-insert audio to the DAW, while UAD MON routes the pre-insert input even when monitoring through effects.

Practical workflow

1. Check the Console indicator before every take.
2. Record a short test and inspect the DAW file.
3. Name committed tracks with a wet marker.
4. Keep a dry alternative for settings that may need revision.

File handoff to MixingMusic

Know whether each performance was recorded wet or dry. Keep dry safety tracks when the sound is still undecided, then export an intentional set of stems or a clean premaster for MixingMusic.

Quality-control checklist

• Recorded tone matches expectation
• Track names state commitment
• Safety version is available

What MixingMusic cannot repair

Mixing and mastering can improve balance, dynamics, tone and delivery level, but they cannot restore audio information removed by lossy encoding, reverse a committed effect perfectly, guarantee rights, or turn a poor separation into the original multitrack recording. Keep source files and make reversible decisions whenever possible.

Official references

• Universal Audio — UAD Console overview
• Universal Audio — UAD plug-in inserts
• Universal Audio — Console layout and insert modes

Product features, plans and export options can change. Confirm the current documentation of the original platform before starting a release-critical project.