OBS scenes and microphone with CYPAD

Before you start

This guide assumes a working connection. If you do not have one yet, start by connecting CYPAD to OBS. Before creating keys, gather these details:

• An active OBS connection in the CYPAD OBS card
• The exact name of each scene, as shown in the Scenes panel
• The exact audio input name, Mic/Aux by default
• A Pro licence, required for OBS actions

How a scene key behaves

Each scene key targets one scene by name. When you press it, CYPAD asks OBS to put that scene in program, exactly as if you selected it in OBS. If the scene is already active, the key stays lit and pressing it again changes nothing.

Scene keys work with whole scenes, not individual sources. If you need a specific look with one element hidden, the reliable way is to keep a scene prepared for that state.

Step by step: one key per scene

Every scene you use during a stream deserves its own button. The process is the same for all of them:

• 1. In CYPAD, click New → Button.
• 2. Under actions, choose OBS and then Switch scene.
• 3. In Scene name, type the name copied from OBS, with spaces and capitals.
• 4. Label the key with something recognisable, such as "Camera" or "Gameplay".
• 5. Save the button, duplicate it and change the scene name for the rest.
• 6. Press each key and confirm in OBS that the scene changes.

Step by step: mute the microphone

The mute action targets one specific OBS audio input. The default is Mic/Aux, the name OBS gives to the main microphone.

• 1. Create a button with the OBS action and choose Mute input.
• 2. In Audio input, type the exact name of the input.
• 3. Save the key and test it: the mic should mute in OBS.
• 4. The key lights up while the input is muted, not while you speak.

What lights up and what does not

The pad mirrors what OBS reports: streaming active, recording active, scene in program and muted input. That poll runs about once a second, so a state change can take up to that long to appear.

Windows system volume and media keys are separate actions and do not depend on OBS. The deck does not move OBS source faders: it only exposes mute per input.

If something does not work

When a key does not react, the cause is usually the name or the connection. Check these in order:

• The key does not change scene: the name does not match OBS exactly.
• The mic does not mute: the input is not called that; check the name in the OBS mixer.
• No key responds: the connection dropped; open the OBS card and use Test connection.
• The key does not light up although the state is correct: without an active connection no OBS state arrives.
• The button looks locked: OBS actions require Pro.
• State is only read for OBS keys that exist in your profiles.

Combine scene, mic and sound in one routine

If changing scene should also mute an input or fire a sound, build a routine: one action with several steps, including OBS actions, with waits between them. A single button runs the whole sequence.