LoginSign Up
← Back to all sparks
E

Element Call

MEETINGS
Velocity5.0

Open-source end-to-end encrypted group video calling built on Matrix

element.io/call ↗

Element Call starts moving to new LiveKit transports and falls back to remote SFUs when needed.

video callsmatrixlivekitwebrtcopen source
◆Current state
Element Call ships a release candidate roughly every two to three weeks. v0.28.1-rc.1 adds a breaking change that falls back to publishing media on a remote SFU when possible, supports migrating to new LiveKit transport types and endpoints, and fixes room v12 power-level compatibility. It also brings in a MatrixRTC SDK and patches several dependency security advisories. The previous rc added a quick audio menu and redacted analytics IDs from rageshakes.
◆Where it's heading
With the MatrixRTC protocol cutover finished in August, the team is now working on the media transport layer itself: how calls find and publish to SFUs and how LiveKit endpoints change underneath them. Packaging the RTC logic as an SDK suggests it is meant to be reused beyond the Element Call app.
◆Prediction
Expect a 0.28.1 final and follow-ups to the LiveKit transport migration; whether the MatrixRTC SDK gets its own release isn't clear from the entries.

◆Recent moves

  1. 2d ago

    Element Call 0.28.1 rc adds remote-SFU fallback and LiveKit migration

    Calls can now fall back to publishing on a remote SFU, and the client supports migrating to new LiveKit transport types and endpoints, with room v12 power-level fixes. After August's protocol cutover, this moves the work down to the media transport layer.

    View source ↗
  2. 23d ago

    Quick audio menu, bell reaction sound and redacted analytics IDs

    A quick audio menu and a bell reaction sound make in-call controls faster to reach, and analytics IDs are now redacted from rageshake reports. The release also fixes tooltips in embedded mode, a sign the Element Web integration is getting attention.

    View source ↗
  3. 1mo ago

    v0.26.1-rc.1

    Falls back to the browser's default audio output when none is chosen and ties member IDs to the MatrixRTC mode. Small cleanup after the protocol transition.

    View source ↗
  4. 1mo ago

    v0.26.0-rc.2

    Delayed-leave timings now adapt when delegation is available, so departures register more reliably on the new protocol. It is marked breaking because it changes behavior that deployments depend on.

    View source ↗
  5. 1mo ago

    v0.26.0-rc.1

    Screen-share failures now surface instead of failing silently, and per-connection LiveKit logging lands. These are debuggability gains for the multi-SFU stack the project now depends on.

    View source ↗
  6. 2mo ago

    MatrixRTC legacy mode removed — all calls now run on the new protocol

    ⚡ SPARK

    Removing MatrixRTC legacy mode closed out the protocol transition that began with multi-SFU in v0.21, and it shipped with a batch of large-call performance fixes. Everything since has been built on the single remaining protocol.

    View source ↗