Question 1

What hardware do I need to render two formats at once?

Accepted Answer

Any GPU from the last 4 years — NVIDIA GTX 1060, AMD RX 580, Apple M-series and up. Because the pipeline keeps frames on the GPU end-to-end, the second format costs a small fraction of what a second encoder pass would on the CPU.

Question 2

Which GPUs are supported?

Accepted Answer

NVIDIA (NVENC), AMD (AMF/VCN), Intel (Quick Sync), and Apple Silicon (VideoToolbox). The encoder is selected automatically based on what’s available; you can override it in advanced settings.

Question 3

Does it work with NDI, Spout2, or virtual cameras?

Accepted Answer

Yes. NDI inputs and outputs, Spout2 textures, and standard virtual camera output for Zoom / Meet / Teams are all first-class sources and destinations.

Question 4

Can I import scenes from my existing setup?

Accepted Answer

Yes. The one-click migration tool reads scene collections, source layouts, hotkeys, and audio routing from common streaming software setups and rebuilds them as a native DualStream project.

Question 5

What about macOS and Linux?

Accepted Answer

Both are in active testing with our pilot users. The engine itself is cross-platform from day one — we’re finalizing platform-specific capture and encoder paths before opening public builds.

Question 6

What does “patent pending” actually cover?

Accepted Answer

A patent application has been filed on the dual-output rendering method that lets a single composited GPU canvas yield two independently-formatted, independently-encoded streams without re-doing the composite work. We’ll publish the filing reference once it’s public.

하나의 워크플로.
두 개의 네이티브 스트림.

라이브 방송이 여전히 힘든 세 가지 이유.

포맷 세금

세팅 지옥

숨은 비용

모든 창작 분야는 직관적인 레이어를 얻었어요.
스트리밍만 명령줄에 멈춰 있었죠.

제로-카피

통합 파이프라인

제로 카피 처리

하나의 소스, 두 가지 포맷

GPU 네이티브 파이프라인

여러 소스 입력. 두 가지 포맷 출력.

Engine FAQ

차이를 직접 느껴볼 준비됐나요?

제품

회사

리소스

법적 고지

하나의 워크플로. 두 개의 네이티브 스트림.