Ovvos Wasel 1.0The short version
Ovvos Wasel does not connect to any conferencing platform. It listens to the sound the room PC is playing — at the Windows audio layer, the same sound the loudspeakers carry — and interprets it for the people in the room.
Because of that, it works with every platform, needs no integration, and never appears in a meeting.
How it captures audio
The audio page in the application offers three sources. One is chosen per room.
| Mode | What it hears | When to use it |
|---|---|---|
| Everything this PC plays (system loopback — default) | Whatever the PC sends to its default speakers or headphones | The usual case: the call runs on the room PC |
| A microphone or line-in | A chosen input device | Lectern or ceiling microphones, or a feed from the room's audio mixer — including in-person events with no call at all |
| One app only (process loopback) | One application's audio, nothing else | When the room PC also plays other sounds that should not be interpreted |
Capture runs in its own process with real-time scheduling priority, so a busy PC does not cause gaps in the audio.
What it never does
- Install an app, add-in, plugin or bot in any conferencing platform
- Join the meeting, or appear in the participant list
- Need a platform account, API key, OAuth consent or tenant administrator approval
- Receive the meeting stream from the platform's cloud
- Change any of the platform's settings, recording or security controls
- Record the meeting
What that means in practice
- No integration project. Nothing to build, approve or re-certify when the platform updates.
- Any platform, any time. Microsoft Teams, Zoom, Cisco Webex, Google Meet, browser-based calls, telephone bridges played through the PC — and switching platforms needs no change at all.
- Platform security untouched. The conferencing platform's own encryption, lobby, recording and compliance settings stay exactly as the organisation set them.
- Works without a call. With a microphone or mixer feed it interprets an in-person meeting just as well.
Who benefits
Ovvos Wasel serves the people in the room. When remote participants speak — in any of the 15 languages it can hear — everyone in the room can follow in their own language on their own phone and headset.
It does not send interpretation back into the call. Remote participants keep their own arrangements. The right mental model: an interpreter sitting at your table, not one sitting in the platform.
Room setup patterns
1. Remote speakers, local audience (most common). The call runs on the room PC; the room hears it on the speakers. Mode: Everything this PC plays. Participants in the room choose their language on their phones.
2. Only the call, nothing else. The room PC also plays notification sounds or presentation audio. Mode: One app only, pointed at the conferencing application.
3. Both the call and the room. Some speakers are remote and some are in the room. Feed a mix of the call audio and the room microphones from the room's audio mixer into a line-in. Mode: A microphone or line-in. Everyone in the room hears every speaker interpreted.
4. In-person event, no call. A lectern or ceiling microphone into the PC. Mode: A microphone or line-in.
Practical notes
- Default output device. In the default mode, Ovvos Wasel listens to the PC's default playback device. The conferencing application must play to that same device. Plugging a headset into the room PC can change the Windows default, so check the Audio page — it names the device being heard and shows a live level.
- Silence is reported, not hidden. A muted call or the wrong device produces silence; the Home readiness row warns when no sound is reaching the interpreter.
- Courtesy. As with a human interpreter in the room, follow your organisation's policy on informing participants that interpretation is in use.