Oxo Sample records external audio on iPad only when its AUv3 effect version receives the source signal and routed MIDI. The instrument version can play and sequence, but it cannot record incoming audio. That small distinction decides whether the sampler actually has anything coming in to capture.
The setup feels unusual because the sampler still needs musical control while sitting in an effect slot. Your host has to do two jobs at once: pass audio through the channel carrying Oxo Sample and send MIDI to that same AUv3 effect. A host that cannot route both signals to an effect cannot provide the recording setup Oxo specifies.
Oxo Sample's iPad recording path depends on that split. The effect instance lets audio reach the sampler's input bus while MIDI keeps the playable side of Oxo Sample available. If one path is missing, the red record controls are not the first thing to blame.
AUM is one host Oxo supports, but the important capability is broader than one app. The host must send audio and MIDI to an AUv3 effect; otherwise Oxo can open normally while its playable side seems dead.
Microphone sampling adds another dependency. The iPad microphone has to be available to the host, and the host still has to pass that input through the channel containing Oxo Sample.
Once the signal reaches the effect instance, Oxo can capture incoming audio into a slot using its 12-bit, 32 kHz mono sampling path. If the microphone never reaches that host channel, changing record controls inside Oxo cannot create an input that is not there.
That is different from loading an existing sample file. File loading does not depend on a live input route because the audio is already being supplied directly to the sampler. Live capture does, so a setup that loads files perfectly can still fail when you switch to recording a microphone or another app.
You are dealing with a two-path AUv3 routing setup, not a simple audio insert. Audio should flow through the channel holding the effect, while your keyboard, pad controller, sequencer, or host MIDI source targets that same Oxo instance. Keep those destinations matched.
Sending MIDI to a separate instrument instance can make sound elsewhere, but it does not restore control to the effect receiving the audio. That split setup is especially misleading because both instances can look healthy on screen. One is hearing your notes while the other is hearing the source you wanted to sample.
Reinstalling can be a red herring here. If the interface opens, presets load, and existing samples play, Oxo Sample itself may be fine even when live recording appears broken. Check the instance type and the host's audio and MIDI routes before assuming its sampling engine has failed.
Use the same route you intend to keep. Feed the real source into the effect instance, send MIDI to it, record into the available slot, and confirm that the captured audio can be played back. If that chain works, the basic iPad routing is already in place before extra slots become relevant.
When capture still fails, trace the signal rather than guessing. The wrong AUv3 instance, an unassigned MIDI destination, a source routed around the effect, or unavailable microphone input can all break the route. Oxo Sample currently requires iPadOS 17 or later, so the device also has to meet that baseline before the routing details matter.
The setup feels unusual because the sampler still needs musical control while sitting in an effect slot. Your host has to do two jobs at once: pass audio through the channel carrying Oxo Sample and send MIDI to that same AUv3 effect. A host that cannot route both signals to an effect cannot provide the recording setup Oxo specifies.
Oxo Sample's iPad recording path depends on that split. The effect instance lets audio reach the sampler's input bus while MIDI keeps the playable side of Oxo Sample available. If one path is missing, the red record controls are not the first thing to blame.
The effect slot is the recording path
Start with the channel that carries the sound you want to sample. That might be an iPad microphone input, another instrument, or another audio channel exposed by the host. Insert the AUv3 effect version of Oxo Sample there instead of opening its instrument version elsewhere and expecting it to hear the source.AUM is one host Oxo supports, but the important capability is broader than one app. The host must send audio and MIDI to an AUv3 effect; otherwise Oxo can open normally while its playable side seems dead.
Microphone sampling adds another dependency. The iPad microphone has to be available to the host, and the host still has to pass that input through the channel containing Oxo Sample.
Once the signal reaches the effect instance, Oxo can capture incoming audio into a slot using its 12-bit, 32 kHz mono sampling path. If the microphone never reaches that host channel, changing record controls inside Oxo cannot create an input that is not there.
That is different from loading an existing sample file. File loading does not depend on a live input route because the audio is already being supplied directly to the sampler. Live capture does, so a setup that loads files perfectly can still fail when you switch to recording a microphone or another app.
MIDI still matters inside the audio effect
Putting Oxo Sample in an effect slot does not turn it into a passive processor. Sample slots, MIDI Learn, and the sequencer still respond to musical control. Oxo specifically tells iPad users to route MIDI to the effect used for external recording.You are dealing with a two-path AUv3 routing setup, not a simple audio insert. Audio should flow through the channel holding the effect, while your keyboard, pad controller, sequencer, or host MIDI source targets that same Oxo instance. Keep those destinations matched.
Sending MIDI to a separate instrument instance can make sound elsewhere, but it does not restore control to the effect receiving the audio. That split setup is especially misleading because both instances can look healthy on screen. One is hearing your notes while the other is hearing the source you wanted to sample.
Reinstalling can be a red herring here. If the interface opens, presets load, and existing samples play, Oxo Sample itself may be fine even when live recording appears broken. Check the instance type and the host's audio and MIDI routes before assuming its sampling engine has failed.
The free slot can test the whole route
Oxo Sample's free version includes one fully functional slot, which is enough to test external capture before unlocking all six slots. Oxo recommends trying the free version first on iPad because the host must support audio and MIDI routing into AUv3 effects. That test tells you more than simply confirming that the plug-in appears in the host's browser.Use the same route you intend to keep. Feed the real source into the effect instance, send MIDI to it, record into the available slot, and confirm that the captured audio can be played back. If that chain works, the basic iPad routing is already in place before extra slots become relevant.
When capture still fails, trace the signal rather than guessing. The wrong AUv3 instance, an unassigned MIDI destination, a source routed around the effect, or unavailable microphone input can all break the route. Oxo Sample currently requires iPadOS 17 or later, so the device also has to meet that baseline before the routing details matter.
