Аудио
Въпросите от тип аудио позволяват на респондентите да записват и изпращат аудио файлове като част от анкетата.
The audio question type enables respondents to record audio or upload an existing audio file as part of their survey response. It is useful for capturing verbal accounts, environmental sounds, testimonials, or any information that is better conveyed through voice than text.
Basic XLSForm Specification
| type | name | label |
|---|---|---|
| audio | voice_note | Please record your comments |
For more details on the standard audio question type, see the XLSForm specification.
Uses
Audio questions are commonly used for:
- Capturing open-ended verbal responses to reduce enumerator typing burden
- Recording testimonials, personal stories, or oral histories
- Documenting environmental sounds (e.g., noise levels near infrastructure)
- Collecting voice samples for linguistic or health research
- Allowing respondents to add verbal clarifications to numeric or select answers
Data format
Audio files are stored as binary attachments alongside the form submission, typically:
- Format: MP3 or AAC (mobile recording); WAV (high-quality recording)
- Naming:
{instanceID}-{fieldname}.mp3(or equivalent) - Storage: Uploaded to the server media folder and linked to the submission record
- Access: Playable and downloadable from the submission management interface
rtSurvey extensions
Maximum duration
Use the parameters column to limit recording length:
| type | name | label | parameters |
|---|---|---|---|
| audio | interview | Record the interview | max-duration=120 |
max-duration is in seconds. The recorder stops automatically at the limit.
Quality settings
The recording quality can be set via parameters:
| type | name | label | parameters |
|---|---|---|---|
| audio | feedback | Record feedback | quality=normal |
Supported values: low, normal (default), voice-only. voice-only optimises for spoken audio with noise reduction.
Playback before submission
On mobile, the enumerator can play back the recorded clip before proceeding. This is enabled by default — there is no configuration needed.
Native recorder integration
On Android and iOS, audio launches the device’s native recording app. On web, it uses the browser’s built-in MediaRecorder API.
Example usage
With maximum duration and hint
| type | name | label | hint | parameters |
|---|---|---|---|---|
| audio | story | Tell us about the incident in your own words | Speak clearly. Recording stops after 3 minutes. | max-duration=180 |
Conditional audio — only if an issue was reported
| type | name | label | relevant | required |
|---|---|---|---|---|
| select_one yesno | issue_found | Was an issue found? | ||
| audio | issue_audio | Record a description of the issue | ${issue_found} = 'yes' | ${issue_found} = 'yes' |
Best Practices
- State clearly in the
labelorhintwhat the enumerator should say and for how long. - Use
max-durationto prevent excessively large files in areas with slow upload speeds. - Inform respondents before starting the recording — unexpected recording can raise privacy concerns.
- Test recording on the target device and network conditions before deployment.
- Set
quality=voice-onlyfor interview-style recordings to reduce file size without losing intelligibility.
Limitations
- Audio files can be large (a 2-minute recording at normal quality is ~2–4 MB) — factor this into your data plan and upload time estimates.
- Not all browsers support the MediaRecorder API — Chrome and Firefox work reliably; Safari on older iOS versions may have issues.
- Transcription of audio responses requires additional post-processing (manual or automated speech-to-text).
- Privacy regulations may restrict recording voices — verify local data protection requirements.