STREAMIX
English

Media server · Players for every platform

Original quality,played natively on your device

STREAMIX has two parts: STREAMIX Server, which only streams and never transcodes, and STREAMIX Player for eight platforms. Every playback is DirectPlay. Decoding, HDR compositing and Dolby Vision all happen on your device.

See development progressContact us

Both products are in development. Downloads and purchases are not open yet.

STREAMIX ServerStreams only · no transcoding
STREAMIX PlayerLocal decoding · HDR · Dolby Vision
  • Windows
  • macOS
  • Linux
  • iOS
  • iPadOS
  • tvOS
  • Android
  • Android TV

Principles

Four principles behind both products

  1. The server only streams

    Server sends the original file and serves byte ranges on request. It never transcodes audio or video and never repackages it. What you see and hear is the source itself.

  2. Playback happens on your device

    Hardware decoding, HDR compositing, audio output and Dolby Vision use each platform’s native capabilities. If the device cannot play a format, the app says why instead of spinning forever.

  3. Our own core, consistent everywhere

    All eight platforms share one in-house playback core and engine, so playback and picture handling behave the same everywhere. libmpv and ExoPlayer are fallbacks you can switch to in settings.

  4. Honest labels

    The interface shows which engine is playing and which format is actually being output. A downgraded picture is never presented as the original.

Products

One server, one family of players

Use them together or on their own: STREAMIX Player also connects to your existing Emby and Jellyfin servers.

STREAMIX Server

A media server built around DirectPlay

0.9 release candidate in testingRust server · web admin
  • Streams original files with range requests; the server never transcodes
  • Syncs files from Google Drive and updates the library incrementally
  • Movie and TV libraries, with several versions of the same title
  • Metadata from TMDB and other sources
  • Accounts, roles, library visibility and session management
  • Compatible with part of the Emby client API, plus a dedicated STREAMIX protocol
Learn more · STREAMIX Server

STREAMIX Player

Our own core and engine, with native shells on eight platforms

In developmentWindows · macOS · Linux · iOS · iPadOS · tvOS · Android · Android TV
  • A native interface on every platform: Qt, SwiftUI, Kotlin
  • Connects to Emby and Jellyfin servers and plays local files
  • Continue watching, next episode, audio and subtitle selection
  • Own engine as the main path, with libmpv and ExoPlayer as switchable fallbacks
  • HDR and Dolby Vision follow device and OS support, and the actual output is shown
  • A dedicated protocol for STREAMIX Server is planned
Coming soonApp StoreGoogle PlayMicrosoft StoreLearn more · STREAMIX Player

STREAMIX Player architecture

Our own core, native shells

To give users on all eight platforms the same playback experience, we built our own playback core and engine from scratch and share it across every platform. Around it, each platform gets a native app shell: Qt on Windows and Linux, SwiftUI on Apple, Kotlin on Android. The experience is the same everywhere, and every app still feels at home on its platform.

After you press play

Every playback is a round trip through all seven layers: first the request travels from the screen to the server, then the original file travels back to the screen. Decoding, HDR and audio-video sync all happen on the device.

① Request: from screen to server

  1. L1Native shell

    You press play in the native interface.

  2. L2Interaction

    Playback controls take the action, the same on all eight platforms.

  3. L3Facade

    Cross-language bindings or a C interface hand the request to the core.

  4. L4Core

    The core shared by all eight platforms picks the playback route.

  5. L7Protocol

    Gets the playback address over the Emby, Jellyfin or STREAMIX protocol; credentials stay in request headers.

  6. ServerMedia server

    STREAMIX Server, Emby or Jellyfin starts streaming, without transcoding.

② Playback: the original file back to the screen

  1. ServerMedia server

    Sends the original file, read on demand.

  2. L7Protocol

    Reads the bytes of the original file as needed.

  3. L4Core

    The byte source and cache hand the data to the engine.

  4. L5Engine

    Our own engine splits the file into video, audio and subtitles; libmpv and ExoPlayer are fallbacks.

  5. L6Platform pipeline

    Native capabilities decode in hardware, composite HDR and output sound, with audio as the clock that keeps the picture in sync.

  6. L1Screen

    Shows the picture and labels the engine and output format actually in use.

What each layer doesFrom screen to server

44 / 76 items mergedMerged 44In progress 19Planned 13

Read it like a player’s progress bar: the played part is code merged into the main line, the buffered part is in development, and the rest has not started. Merged work still goes through testing on real devices.

  1. L1Native shellsEach platform uses its own native UI framework: Qt on Windows and Linux, SwiftUI on Apple, Kotlin on Android.Merged 4 · In progress 3 · Planned 1
    • In progressWindows · Qt 6.12 Quick
    • PlannedLinux · Qt 6.12
    • MergediOS · SwiftUI
    • In progressiPadOS · SwiftUI
    • MergedtvOS · SwiftUI
    • In progressmacOS · SwiftUI
    • MergedAndroid · Kotlin
    • MergedAndroid TV · Kotlin
  2. L2InteractionLibrary, playback controls, track selection, subtitles, engine choice and error labels behave the same on every client.Merged 6 · In progress 2 · Planned 0
    • MergedServers and sign-in
    • MergedLibrary
    • In progressItem details
    • MergedPlayback controls
    • In progressSubtitle display
    • MergedEngine selection
    • MergedHonest labels
    • MergedDiagnostics and reporting
  3. L3FacadesOnly two kinds of interface sit between the UI and the core: generated cross-language bindings on Apple and Android, and a C interface on Windows.Merged 3 · In progress 2 · Planned 0
    • MergedCross-language bindings for Apple and Android
    • MergedWindows interface: Storage and settings
    • MergedWindows interface: Device capabilities
    • In progressWindows interface: Sign-in and library
    • In progressWindows interface: Playback session
  4. L4Player core · Core servicesOne Rust core shared by all eight platforms: media source connections, byte sources, routing, accounts, storage and stable error codes.Merged 8 · In progress 0 · Planned 2
    • MergedRouting core
    • MergedMedia source connections
    • MergedByte sources and caching
    • MergedAccounts and devices
    • MergedStorage and settings
    • MergedDolby semantics
    • MergedMedia and capability model
    • PlannedSubtitles
    • PlannedDiagnostics and metrics
    • MergedStable error codes
  5. L5EnginesThe shared STREAMIX Engine with four platform ports is the main path; libmpv and ExoPlayer are the fallbacks.Merged 4 · In progress 6 · Planned 3
    • MergedShared engine: Contracts and skeleton
    • In progressShared engine: First landing on Windows
    • PlannedShared engine: Seeking and subtitles
    • PlannedShared engine: Apple port
    • In progressShared engine: Android port
    • In progressWindows port
    • PlannedApple port
    • In progressAndroid port
    • In progressLinux port
    • MergedAutomated conformance tests
    • In progresslibmpv fallback (Windows, Apple, Linux)
    • MergedExoPlayer fallback (Android)
    • MergedEngine selection
  6. L6Platform pipelinesHardware decoding, HDR compositing, audio output, clocks and Dolby Vision use only native platform APIs; every third-party library is an LGPL dynamic library.Merged 16 · In progress 5 · Planned 4
    • MergedWindows · Video decoding
    • MergedWindows · Color and HDR
    • In progressWindows · Presentation
    • MergedWindows · Audio
    • MergedWindows · Clock
    • PlannedWindows · Dolby Vision
    • MergedApple · Video decoding
    • MergedApple · Pipeline
    • MergedApple · Presentation
    • MergedApple · Audio
    • MergedApple · Clock
    • In progressApple · Dolby Vision
    • MergedAndroid · Video decoding
    • MergedAndroid · Capability detection
    • MergedAndroid · Presentation
    • In progressAndroid · Audio
    • MergedAndroid · Clock
    • MergedAndroid · Dolby Vision
    • In progressLinux · Video decoding
    • In progressLinux · Color and HDR
    • PlannedLinux · Presentation
    • PlannedLinux · Audio
    • MergedLinux · Clock
    • PlannedLinux · Dolby Vision
    • MergedAll third-party libraries are replaceable LGPL dynamic libraries
  7. L7API / ProtocolsThe server only streams and everything is DirectPlay over the Emby / Jellyfin protocols; credentials stay in HTTP headers.Merged 3 · In progress 1 · Planned 3
    • MergedEmby · Jellyfin protocols
    • MergedContinue watching · Next episode
    • In progressRuntime, versions and tracks
    • PlannedSTREAMIX’s own server protocol
    • MergedLocal files
    • PlannedWebDAV · SMB
    • PlannedDirect HTTP(S) links

Development progress

Where each client stands

Every client is scored on the same nine milestones, totalling 100%. Merged into the main line counts in full, in progress counts half, planned counts nothing. Open a client to see each milestone.

Data updated

  1. AndroidKotlin73%
    1. Shell and navigationWeight 10%Merged10 / 10
    2. Sign-in and libraryWeight 15%Merged15 / 15
    3. Item details and tracksWeight 10%Planned0 / 10
    4. Player screen and controlsWeight 15%Merged15 / 15
    5. Own playback pipelineWeight 20%In progress10 / 20
    6. Fallback playerWeight 10%Merged10 / 10
    7. Engine choice and settingsWeight 5%Merged5 / 5
    8. HDR and Dolby VisionWeight 10%In progress5 / 10
    9. Real-device acceptanceWeight 5%In progress2.5 / 5
  2. Android TVKotlin73%
    1. Shell and navigationWeight 10%Merged10 / 10
    2. Sign-in and libraryWeight 15%Merged15 / 15
    3. Item details and tracksWeight 10%Planned0 / 10
    4. Player screen and controlsWeight 15%Merged15 / 15
    5. Own playback pipelineWeight 20%In progress10 / 20
    6. Fallback playerWeight 10%Merged10 / 10
    7. Engine choice and settingsWeight 5%Merged5 / 5
    8. HDR and Dolby VisionWeight 10%In progress5 / 10
    9. Real-device acceptanceWeight 5%In progress2.5 / 5
  3. iOSSwiftUI60%
    1. Shell and navigationWeight 10%Merged10 / 10
    2. Sign-in and libraryWeight 15%Merged15 / 15
    3. Item details and tracksWeight 10%Planned0 / 10
    4. Player screen and controlsWeight 15%Merged15 / 15
    5. Own playback pipelineWeight 20%In progress10 / 20
    6. Fallback playerWeight 10%In progress5 / 10
    7. Engine choice and settingsWeight 5%Planned0 / 5
    8. HDR and Dolby VisionWeight 10%In progress5 / 10
    9. Real-device acceptanceWeight 5%Planned0 / 5
  4. WindowsQt 6.12 Quick55%
    1. Shell and navigationWeight 10%Merged10 / 10
    2. Sign-in and libraryWeight 15%In progress7.5 / 15
    3. Item details and tracksWeight 10%In progress5 / 10
    4. Player screen and controlsWeight 15%In progress7.5 / 15
    5. Own playback pipelineWeight 20%In progress10 / 20
    6. Fallback playerWeight 10%In progress5 / 10
    7. Engine choice and settingsWeight 5%Merged5 / 5
    8. HDR and Dolby VisionWeight 10%In progress5 / 10
    9. Real-device acceptanceWeight 5%Planned0 / 5
  5. iPadOSSwiftUI55%
    1. Shell and navigationWeight 10%In progress5 / 10
    2. Sign-in and libraryWeight 15%Merged15 / 15
    3. Item details and tracksWeight 10%Planned0 / 10
    4. Player screen and controlsWeight 15%Merged15 / 15
    5. Own playback pipelineWeight 20%In progress10 / 20
    6. Fallback playerWeight 10%In progress5 / 10
    7. Engine choice and settingsWeight 5%Planned0 / 5
    8. HDR and Dolby VisionWeight 10%In progress5 / 10
    9. Real-device acceptanceWeight 5%Planned0 / 5
  6. tvOSSwiftUI55%
    1. Shell and navigationWeight 10%Merged10 / 10
    2. Sign-in and libraryWeight 15%Merged15 / 15
    3. Item details and tracksWeight 10%Planned0 / 10
    4. Player screen and controlsWeight 15%Merged15 / 15
    5. Own playback pipelineWeight 20%In progress10 / 20
    6. Fallback playerWeight 10%Planned0 / 10
    7. Engine choice and settingsWeight 5%Planned0 / 5
    8. HDR and Dolby VisionWeight 10%In progress5 / 10
    9. Real-device acceptanceWeight 5%Planned0 / 5
  7. macOSSwiftUI25%
    1. Shell and navigationWeight 10%In progress5 / 10
    2. Sign-in and libraryWeight 15%In progress7.5 / 15
    3. Item details and tracksWeight 10%Planned0 / 10
    4. Player screen and controlsWeight 15%In progress7.5 / 15
    5. Own playback pipelineWeight 20%Planned0 / 20
    6. Fallback playerWeight 10%In progress5 / 10
    7. Engine choice and settingsWeight 5%Planned0 / 5
    8. HDR and Dolby VisionWeight 10%Planned0 / 10
    9. Real-device acceptanceWeight 5%Planned0 / 5
  8. LinuxQt · Flatpak15%
    1. Shell and navigationWeight 10%Planned0 / 10
    2. Sign-in and libraryWeight 15%Planned0 / 15
    3. Item details and tracksWeight 10%Planned0 / 10
    4. Player screen and controlsWeight 15%Planned0 / 15
    5. Own playback pipelineWeight 20%In progress10 / 20
    6. Fallback playerWeight 10%Planned0 / 10
    7. Engine choice and settingsWeight 5%Planned0 / 5
    8. HDR and Dolby VisionWeight 10%In progress5 / 10
    9. Real-device acceptanceWeight 5%Planned0 / 5

Plans

Buy for the devices you use

Prices and sales channels have not been announced. These options will be available at launch.

  • Single platform

    STREAMIX Player on one platform of your choice

    For example, only Windows or only Android TV

    Coming soon

  • Apple bundle

    iOS, iPadOS, tvOS, macOS

    Every STREAMIX Player in the Apple family

    Coming soon

  • Android bundle

    Android phones and tablets, Android TV

    Every STREAMIX Player in the Android family

    Coming soon

  • All clients

    STREAMIX Player on every platform

    Windows, Linux, Apple and Android

    Coming soon

  • STREAMIX Server

    A license for one server

    Includes several client licenses; the number will be announced at launch

    Coming soon

  • Client add-on

    Extends an existing license

    Add devices or platforms

    Coming soon

About

STREAMIX began on November 18, 2025

We wanted a private media setup without compromises: the server only sends the original file, and every device plays it back the best way it can, so every screen in your home gives you the best private viewing experience.

  1. Design of STREAMIX begins
  2. Development of STREAMIX Player begins
  3. STREAMIX Server releases its first version, 0.3
  4. Server enters 0.9 release-candidate testing; Player moves forward on all eight platforms

Contact

Partnerships, feedback or anything else

Product suggestions, problems you run into, business enquiries: write to this address.

Email

[email protected]
Write an email