Why does the SC220 not appear in Windows?

Check the data cable, USB port, power, Device Manager, Windows Sound, and test without a hub. Endpoint names may differ by revision.

Why is the microphone only on the left?

A single microphone normally uses one mono channel. Select a mono input or enable mono handling in the destination application.

Why do I hear echo or doubled audio?

Direct monitoring and software monitoring may both be active, or the same source may be captured twice.

Should I download a driver from an unofficial website?

Do not install an unofficial driver unless its vendor, model, and source can be verified. First record how Windows identifies the device.

SC220 MKII SUPPORT

Good diagnosis starts with complete evidence.

Use this page before opening an issue about SC220, SC220 MKII, SC220 Live, OBS, TikTok Live Studio, VB-CABLE, or a karaoke processor. The goal is to separate hardware, Windows, routing, software, and gain-staging problems.

Start diagnosis Open bug report

Checklist before declaring the device faulty.

Change one variable at a time. Record the result of every step so one change does not hide another.

1. Identity and connection

Photo of the model label: SC220, SC220 MKII, or another name.
Front and rear panel photos with port labels visible.
USB cable type and whether it supports data.
Direct USB port or hub/dock.
Source type: dynamic mic, condenser mic, guitar, mixer, or karaoke processor.
Complete wiring from source to headphones, speakers, and applications.

2. Windows and driver

Windows 10/11 edition, version, and OS build.
Device name in Device Manager and Windows Sound.
Visible input/output count.
Selected sample rate and bit depth.
Actual audio API or driver type: Windows audio, WASAPI, or ASIO when available.
Whether the device disappears after sleep, reconnect, or a port change.

3. Hardware controls

Input 1 and input 2 gain positions.
+48 V status and why it is enabled.
PAD and Line/Instrument status.
Whether the hardware meter moves.
Whether headphones/direct monitor produce sound.
Whether the problem remains with DSP and other applications closed.

4. Software and routing

SC220 Live, OBS, TikTok Live Studio, DAW, or other application versions.
Selected input, playback source, and stream output names.
Meter screenshots at every stage.
Whether the same source is captured twice.
Whether exclusive mode or another application is holding the device.
Whether the problem starts before or after GO LIVE/stream output.

A diagnostic order that avoids guessing.

Start with the simplest path and add one component only after the basic result is stable.

Hardware only

Test the microphone or source into the SC220 and listen through direct monitoring/headphones when available.

Windows input

Check the endpoint, Windows meter, sample rate, and microphone permissions.

One application

Use a single capture application without DSP, virtual cables, or extra monitoring.

SC220 Live

Add routing, faders, meters, and stream output only after the base input is proven.

Broadcast chain

Add OBS or TikTok, make a test recording, and compare meters with playback.

Issue report template.

Copy this into a GitHub issue. Enter “not tested” instead of guessing.

## Problem summary
Describe the problem in 1–3 sentences.

## Hardware model
- Model printed on label:
- Front/rear panel photos:
- USB cable type:
- Direct port / hub:

## Source and wiring
- Microphone/instrument/processor type:
- Input used:
- Mic/Line/Instrument mode:
- +48 V:
- PAD:
- Wiring diagram:

## Windows
- Edition/version/build:
- Device Manager name:
- Windows Sound input/output names:
- Sample rate / bit depth:
- Audio driver/API:

## Software
- SC220 Live version:
- OBS/TikTok/DAW version:
- Selected input:
- Playback source:
- Stream output:

## Reproduction steps
1.
2.
3.

## Expected result

## Actual result

## Meters and evidence
- Hardware meter:
- SC220 Live meter:
- OBS/application meter:
- Screenshot/log with private data removed:

## Tests already completed
- Another cable/port:
- Without hub:
- Restart/reconnect:
- DSP disabled:
- Direct monitor only:
- Other applications closed:

Common first-line diagnostic questions.

These are starting points. Control labels and driver support must still be checked against the physical unit.

The SC220 does not appear in Windows. What should I check?

Use a proven data cable, try a direct USB port, temporarily avoid hubs, check Device Manager and Windows Sound, then retest after a restart. Record whether it appears as an unknown device or not at all.

The microphone is only on the left or right.

A microphone connected to one input is a mono source. Select a mono channel or enable mono handling in the destination application.

A condenser microphone has no signal.

Confirm that the microphone requires phantom power, the XLR cable is correct, gain is not at minimum, and +48 V is enabled after the cable is connected. Phantom power is not a universal fix for every microphone.

The audio is echoed or doubled.

Disable either direct monitoring or software monitoring. Confirm that the source is not captured directly and again through SC220 Live or a virtual cable.

The audio clips even when the OBS fader is low.

Clipping is probably earlier in the chain. Lower source output or hardware gain, check PAD/line mode, disable extra processing, and inspect meters from input to output.

Should I install a driver from an unofficial website?

Not recommended. Do not install a driver binary that cannot be clearly tied to the vendor and model. Save screenshots of the device identity first and use an official source when one becomes available.

PUBLIC SUPPORT

Complete, reproducible issues receive higher priority.

This repository provides best-effort support for the installer, landing page, documentation, device detection, routing, and reproducible SC220 Live behavior.

Open structured bug report Security policy