Hey vMix Community & Team,
I've been using vMix intensively for quite a while now, both as a stress-tester pushing it to its limits and as an active Twitch streamer. And I have to say — vMix's stability is on another level compared to OBS. Where OBS drops frames, stutters under load, or randomly crashes mid-stream, vMix just keeps going. That alone is a massive advantage for any serious broadcaster.
But here's the thing: Twitch has been rolling out 2K (1440p) streaming and HEVC (H.265) support for eligible streamers, and right now vMix is missing out on this entirely. If vMix were to implement these features, it would be a genuine game-changer — and honestly, a compelling reason for a lot of streamers to finally make the switch from OBS.
What I'd love to see:

HEVC / H.265 encoding output for Twitch streaming (hardware-accelerated via NVENC / AMD VCE / Apple VideoToolbox)
2K / 1440p streaming resolution support via the Twitch ingest (not just as a local recording option)
Proper integration with Twitch's Enhanced Broadcasting pipeline

The efficiency gains from HEVC are enormous — better image quality at lower bitrates, which matters a lot for streamers with bandwidth constraints. Combined with vMix's rock-solid stability, this would be an unbeatable combination.
I'd love to hear if this is on the roadmap at all — or if other community members share this interest. The more voices, the better the chances of seeing it happen.
Thanks for the incredible software either way. Keep it up! 🙌

Hi
My post was translated in english with some enrichment, because my native language is German...

Your answer is not fully correct according to Twitch. At the moment it's not possible to stream 2K to Twitch. Twitch is expecting multi-coding headers:

Twitch Enhanced Broadcasting is based on the RTMP Multi-Track Video standard (also known as "Multicode").This standard requires specific metadata headers within the streaming protocol to correctly signal the different quality levels (renditions) to the server. As of 2024/2025, vMix does not yet natively support this specific multi-track protocol header for Twitch.

Lack of Bundling: Twitch recognizes these as separate, individual streams rather than a single, unified "Multi-Encode" package.

That it what I have tested and failed. At the moment a workaround is over NDI --> Obs Enhanced broadcasting --> Twitch
But that is not reasonable hardware saving.

Cheers from Switzerland
Manuel