Present locally
Show the selected content on the agreed display or both displays. Playback audio follows that source. Room volume changes what people hear locally. This mode does not start a call or enable microphone transmission.
Wirewolf / Commercial AV / Design examples
Original concepts / Control + DSP
A useful AV design connects the user's next action to a clear system response. Explore how we approach room workflows, audio routing and the checks needed before handover.
Illustrative concepts created by Wirewolf. These are not completed client projects or device-tested systems. No customer drawings or employer project materials are used.
One room, two displays, a conferencing endpoint, a camera and a DSP. The design separates presentation from calling while keeping room listening level, microphone privacy and device status understandable.
Present locally
Route the selected source to the agreed display layout.
Join a call
Prepare endpoint video, camera and conference audio.
Request display power and input, then show preparation status.
Apply the selected audio routing and retain the confirmed microphone mute state.
Display/input status, selected source, camera availability and microphone mute feedback.
Show unavailable or unknown status when feedback is missing.
Show the selected content on the agreed display or both displays. Playback audio follows that source. Room volume changes what people hear locally. This mode does not start a call or enable microphone transmission.
Use one display for the meeting and the second for shared content where the endpoint supports it. Camera presets and content sharing appear only when supported. Call connection status comes from the endpoint, not from selecting the room mode.
Label local playback level, incoming call level and microphone mute distinctly. A room volume adjustment must not change the outgoing microphone level. Synchronize microphone mute across the panel and supported endpoint controls, with a defined source of truth.
Keep the affected device visibly unavailable after a timeout. Bound retries and refresh status when communication returns. Confirm disruptive actions such as ending an active call. Never represent a sent command as a verified hardware state.
Acceptance focus: review both display layouts, source changes during a call, camera feedback, mute synchronization and loss of a device connection. Confirm the actual interfaces and supported feedback before implementation.
Explore the interface side in touch panel and GUI design, or scope the complete workflow through AV design and commissioning.
This base concept has one conferencing endpoint and no local speech reinforcement. It separates microphone transmission from room playback and makes the acoustic echo cancellation (AEC) reference explicit.
Reference follows the far-end and playback signals reproduced in the room. Room microphones are excluded from this base reference.
Use one agreed sharing path. Account for endpoint or application content-audio sharing to avoid sending it twice.
The outgoing mix contains local speech and any intentionally shared playback. It excludes that endpoint's own far-end return, preventing a direct electronic loop back to the caller. AEC separately addresses speaker sound picked up by room microphones.
The reference represents the far-end and playback audio heard through the speakers. Coordinate its source selection, level and mute with the speaker path. Choose the exact tap points and output processing for the DSP platform and room. Do not feed a microphone into its own AEC reference.
Acceptance focus: check near-end speech, far-end speech, simultaneous talk, shared playback and mute recovery with a remote participant. Inspect microphone, transmit, return and reference meters, then listen at both ends. Acoustic performance needs the installed room and cannot be confirmed from this diagram.
Technical basis: Q-SYS conferencing signal paths and AEC reference guidance and Biamp AEC reference guidance. The diagrams are original, platform-neutral concepts, not vendor design files.
For AV integrators and teams responsible for their own systems. Send the room requirements, equipment list, available source files, location and target schedule. We can agree the design scope, implementation responsibilities and acceptance checks.
Remote support by agreement. Site work in the GTA and Ontario scoped separately.