Receive-side processing
Cleaning audio that arrives at your app from elsewhere, before it reaches the listener.
Receive-side processing runs Rapidly on the audio coming into your app from the outside: a network stream, a decoded media file, a remote participant. The engine sits between the source and the playback path (speakers, headphones, recorder). The listener hears clean audio regardless of how noisy the source was.
Where the engine sits in the pipeline
Audio source
A buffer of PCM audio arrives from the outside: a network stream, a decoded media file, or a remote participant.
Rapidly engine
You hand the buffer to a RapidlyEngine instance. The engine cleans noise, reverb, and unwanted sounds, then returns a cleaned buffer of the same shape.
Speakers, output, or recorder
You play the cleaned buffer to the listener, or write it to a recording. The audio they hear is clean regardless of how noisy the source was.
When receive-side is the right choice
Communications apps
Cleaning incoming voice so the listener hears it well even when the sender is in a noisy environment.
Streaming and content playback
Cleaning podcast audio, video calls, or other prerecorded or live media for the listener.
Premium audio features
Offering cleaner playback as a paid-tier feature that improves the listening experience for paying users.
Accessibility and neurodiversity
Cleaner audio supports hearing-impaired listeners and neurodivergent users for whom background noise interferes with comprehension.
Personalised settings
On-device processing lets each end-user tune the cleaning to their own preferences without ever sharing their audio.
Multi-guest recording
Cleaning each guest's downlinked stream on the recording end.
Together with capture-side
Many apps clean both directions. See Capture-side processing for the input path, and One vs multiple engines for how to set up two engines when both directions matter.