SIS hardware routing how-to · reviewed August 23, 2026
Mixer → Pikka → transmitter (keep existing receivers)
If a venue already owns a transmitter and receivers, you can keep the installed distribution and route selected Pikka language channels into an available compatible transmitter input. This page explains the functional signal path and the checks that prevent show-day surprises.
This is an engineered audio connection, not a universal “native integration.” Confirm connector, level, routing, and receiver performance for the exact transmitter model and rack design.
The functional signal path (step-by-step)
The goal is simple: the audience keeps using the distribution route that already works. Pikka changes language production upstream. The last metre remains the transmitter + receiver system.
1) Take a clean mixer feed
Use a dedicated floor or program mix that is stable and speech-forward. Confirm it includes every speaker path (podium mics, handheld Q&A mics, remote callers if relevant).
2) Run it into the Pikka production workstation
Use a controlled host workstation with known power settings and a tested browser environment. Confirm the internet route and backup plan; receivers don’t remove the need for dependable production connectivity.
3) Configure the event room and targets
Verify the exact source-to-target configuration you need (don’t rely on headline language counts). Use the test-session window to validate with real voices, names, numbers, and domain terminology.
4) Engineer independent professional outputs
For every simultaneous language you will send to the transmitter, assign one independent output you can monitor. Use a professional audio interface or approved digital routing; label each output consistently.
5) Patch into a compatible transmitter input/channel
Match connector type and level to the transmitter documentation. Confirm routing permissions, licensing, channel numbering, and that receiver users can reliably select the channel.
6) Rehearse end-to-end on real receivers
Listen on real receivers in every coverage zone. Test normal speech, fast speech, silence, cable movement, a brief network interruption, and the operator’s ability to identify the failing boundary.
The “don’t confuse distribution with translation” warning
A transmitter can distribute a technically clean channel whose meaning is wrong. Receiver engineering and interpreting quality are different problems. Use AI only where it passes rehearsal and consequence review, and keep qualified humans in the loop where required.
FAQ: mixer → Pikka → transmitter routing
These answers focus on what the hardware route does (and does not) guarantee.
Reminder: receivers remove attendee Wi‑Fi from the last metre, but they do not remove the need for a tested production internet route.