vesper_player_external_playback 0.4.1

Optional external playback integration for Vesper Player Flutter hosts.

vesper_player_external_playback

Optional external playback plugin for Vesper Player Flutter hosts.

The Android implementation provides:

• Google Cast control for an already selected Cast route.
• DLNA / UPnP AV device discovery and playback control.
• Local HTTP relay for local media, content URIs, and sources that require request headers.
• Optional relay FFmpeg adaptation through the Android vesper-player-kit-external-playback facade and shared vesper-player-kit-ffmpeg-runtime AAR.

Cast route selection still uses the system Cast route button. DLNA devices are reported through VesperExternalPlaybackController.routes, which delegates to the Kotlin facade at io.github.umbrella22.vesper.player.android.external.VesperExternalPlaybackController.

The Flutter plugin registers io.github.umbrella22.vesper_player_external_playback plus /routes and /events EventChannel suffixes. These names and the Android plugin package are a breaking pre-release rename from io.github.ikaros; no old handlers are registered.

Use VesperExternalRouteIconButton inside a player-stage action slot on Android to surface the system Cast route picker through a Flutter icon button. The Android method channel opens the SDK-owned MediaRouter button with an opaque light or dark theme so route button and dialog contrast calculation never depends on a transparent host background. Route picker startup failures are handled as best-effort diagnostics instead of user-visible playback errors. VesperExternalRouteButton remains available for existing integrations.

Android Host Requirements

The Android plugin manifest contributes internet, network-state, Wi-Fi, nearby Wi-Fi devices, multicast, and Cast options-provider declarations. It does not enable cleartext traffic globally.

DLNA discovery and relay playback can require app-owned cleartext HTTP access for local-network device descriptions and tokenized relay URLs. Apps that use those features must opt in from the host app manifest or an Android network security configuration:

<application
    android:usesCleartextTraffic="true">
</application>

Hosts with stricter policy should use a network security configuration that only allows the local hosts required by their discovery and relay flows.