Skip to content

Add Sebas Microphone (1209:5EBA) - #1357

Open
Sebaszip wants to merge 1 commit into
pidcodes:masterfrom
Sebaszip:sebas-microphone
Open

Sebaszip wants to merge 1 commit into
pidcodes:masterfrom
Sebaszip:sebas-microphone

Conversation

@Sebaszip

@Sebaszip Sebaszip commented Nov 6, 2026

Copy link
Copy Markdown

Requesting PID 0x5EBA under VID 0x1209 for Sebas Microphone, plus the organisation page for Sebas.

Source (MIT OR Apache-2.0, LICENSE files included): https://github.com/sebas-dot-zip/sebas-virtual-usb-device

Why a software project needs its own PID: this is a software-only virtual USB device. Every Sebas installation emulates it over USB/IP when a remote user shares their microphone, so end users can't request their own PID, and Windows keeps one device instance and its endpoint settings across sessions by VID/PID.

Sebas Microphone is a USB Audio Class 1.0 microphone (48 kHz 16-bit PCM,
mono or stereo, one asynchronous isochronous IN endpoint) that the Sebas
desktop app emulates on a Windows computer during a remote session, so that
every app on that computer can record the remote viewer's microphone. The
device is served over USB/IP to the usbip-win2 host controller driver, and
Windows binds its in-box USB audio driver (usbaudio.sys) to it; no custom
driver is involved. Its source (USB descriptors, control and isochronous
request handling, the jitter buffer and the USB/IP framing) is a Rust crate
licensed under MIT OR Apache-2.0.

This is a software-only virtual USB device with no hardware of its own.
Every Sebas installation emulates this same device over USB/IP whenever a
viewer shares a microphone, so its end users cannot request their own PID:
the PID has to identify the one device that all installations present.
Sebas also recognises its own microphone by these IDs (to turn Windows'
voice processing off on its recording endpoint), and a fixed VID/PID lets
Windows keep one device instance and its endpoint settings across sessions.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant