LeanCast 0.3.0-beta
A compact Windows creator studio with saved scenes, window or display capture, optional camera, photo backgrounds, and one to four selected YouTube, Twitch, Kick and TikTok destinations. Landscape destinations share H.264 video; TikTok uses a separate portrait composition. All destinations share program audio.
This is a limited compatibility beta. Opening setup starts no physical capture or broadcast. It does not inject into games, supply platform access, run chat clients or browser overlays.
Compatibility
| Requirement | Supported scope |
|---|---|
| System | Windows 10/11 x64 with Windows Graphics Capture, .NET Framework 4.8, and the installed OBS runtime prerequisites. Use a supported Windows release and current graphics driver. |
| OBS | Independently installed OBS Studio 30.x x64. 30.1.2 is tested; other major versions are rejected. No OBS binaries are bundled. Choose its installation folder in Engine & help. |
| Encoder | NVIDIA NVENC H.264 is the tested hardware path. Explicit obs_x264 uses CPU and may materially increase load. No silent software fallback. AMD/Intel and multi-GPU configurations remain unvalidated. |
| Sources | Explicitly selected available window or display, optional camera, or local PNG/JPEG background. Protected or unavailable content may not capture. |
| Accounts | Authorized publishing server/key for each selected platform. Eligibility and credentials must come from that platform. |
OBS 30.1.2 is an older release, not the current OBS recommendation. Do not replace a maintained installation merely to try this beta. The official release record identifies the tested dependency. Supporting current OBS remains future work.
Install
Extract the complete archive into a writable folder. Run build\LeanCast.exe, or optionally run:
powershell -NoProfile -ExecutionPolicy Bypass -File .\install-desktop.ps1The installer uses %LOCALAPPDATA%\Programs\LeanCast\0.3.0-beta and creates versioned LeanCast Setup and LeanCast Go Live shortcuts. It refuses existing folders/shortcuts. It never starts the app, installs OBS, changes OBS settings, or modifies saved profiles. The executable is unsigned; no publisher identity or SmartScreen reputation is claimed.
First session
- In Scenes & sources, select Refresh sources, then choose a window or display. Display capture includes everything on that display. No other display/window is automatically substituted if a source disappears.
- Camera is off by default. Choose List cameras, select the exact device, and enable Camera on to use it. Listing does not activate a camera. Edit layout / photo changes widescreen and portrait positions independently using drag/resize or numeric controls. Photos remain local file references; keep them available.
- Name, create or copy scenes and choose a default. Use Make default, then Save setup to choose the scene loaded on future setup/Go Live launches. Switching scenes during a session does not change that saved default. Apply scene uses a draft immediately when local capture is active. Selecting another scene while capture is active applies it immediately. Publishing requires a separate Start action.
- Check only the desired destinations. Enter official server/key details. YouTube requires Auto-start on the intended broadcast bound to that key; Kick requires title/category in its dashboard. Confirm the setup acknowledgements only after doing this.
- Use Test microphone, choose intended audio devices, and adjust gain/mute. Disable unwanted inputs. Desktop audio captures the selected playback device, including other apps; it is not per-window audio isolation.
- Choose Capture selected, enable Preview if desired, then Record 8s test and Play test with headphones. Review picture, voice, desktop audio and sync.
- Save setup, then Start selected or use Go Live later. A three-second cancellation window appears. Each selected destination and the selected scene must pass preflight. You may save unfinished setup; saving alone never captures or publishes.
TikTok requires approved direct RTMP server/key access. LIVE Studio access or another application's keyless integration is not transferable to LeanCast. Without direct credentials, leave TikTok unchecked. Selecting it blocks launch until details are supplied. There is no eligibility bypass. See platform setup.
Connecting/Sending is local transport status, not proof that viewers see a public broadcast. Check every dashboard. A destination failure may leave other destinations sending.
Scenes, pause and hotkeys
Scenes retain source identities, camera selection, separate layouts and local photo paths. Missing sources/assets require explicit repair. Switches prepare replacement inputs before committing, without restarting output encoders.
Pause program keeps connections open while showing a break slate and silencing program audio. Resume restores the selected scene and logical gain/mute choices, including changes made while paused. Pause is not Stop: platforms may continue counting the broadcast as live.
Hotkeys are off by default. Enter chords such as Ctrl+Alt+M or Ctrl+1 (digits 0-9 are supported) for microphone mute, desktop mute, pause/resume, next or previous scene. Blank leaves an action unbound. Enable and Apply, then Save. A conflict leaves all LeanCast hotkeys off and names the unavailable combination. Hotkeys never start broadcasting. Saved enabled bindings register on normal launches and unregister on exit; diagnostics never register them.
Load and bandwidth
- Widescreen defaults: 1280x720, 30 FPS, 4,500 Kbps. Selected Kick caps this at 1920x1080 and 8,000 Kbps.
- TikTok portrait: 720x1280, initially 3,500 Kbps. Shared stereo AAC: 48 kHz, 160 Kbps.
- Preview starts off and stops on minimize. Minimize uses the tray. Small displays use a scrollable interface.
- Each destination uploads separately. Four outputs at defaults need about 17.64 Mbps before overhead. Shared encoding does not reduce upload per destination.
- Camera, capture resolution, photo decoding, preview and CPU x264 can add load. No universal faster-than-OBS or lag-free claim is made. See benchmark method and limitations.
Stop all outputs ends publishing/recording while local capture remains active. Stop capture also releases inputs and the engine. Driver/network cleanup may take time. A second instance does not start another broadcast.
Profiles and privacy
The full profile, including server URLs and keys, uses DPAPI CurrentUser encryption at %LOCALAPPDATA%\LeanCast\profile.dat. It is tied to the Windows account and is not portable. This does not protect against another process running as that user. There is no telemetry, phone-control server or automatic updater.
Version-1 profiles import into schema 2, preserving destinations, keys, selections and audio settings. Capture becomes unselected, camera off, and hotkeys off. Review and save before Go Live. The encrypted envelope is compatible, but older app versions cannot read saved schema 2. Installation alone never migrates/overwrites the file.
Keep the app folder writable for local recordings/caches. Do not share profiles, recordings or keys. An unreadable profile blocks automatic startup. Uncheck a destination to retain its details without connecting; clear its key and save to remove it.
Build and safe tests
Corresponding source, icon source, scripts and focused tests are included:
powershell -NoProfile -ExecutionPolicy Bypass -File .\build.ps1
powershell -NoProfile -ExecutionPolicy Bypass -File .\tests\run-safe-tests.ps1Safe tests use fake profiles under tests/profile-fixtures, synthetic data, and a noncapturing UI. They never read the actual profile or connect to platforms. DPAPI needs a loaded Windows user profile. --render-ui <png> renders idle UI without saved settings. --self-test <folder> records a synthetic slate without physical capture/network. --go-live is publishing intent and cannot be combined with diagnostics; never use it to test installation.
See release validation for executed checks and limits. Synthetic checks do not establish platform authentication, viewer delivery, camera compatibility or real application capture quality.
License
LeanCast is GPL-2.0-or-later. The complete LICENSE, corresponding source and build instructions accompany the executable. OBS/dependency binaries are not redistributed. See third-party notices and dependency source instructions. LeanCast is independent of OBS Project and the streaming platforms.