This release plays field-coded 1080i channels on Windows, keeps remuxed streams running through bursty provider pauses, and retries failed media probes during scans.
Playback
- Windows WebView2 cannot decode field-coded (PAFF) interlaced H.264 through MSE, so such channels failed with "Decode error" after the AAC audio route started. When an MPEG-TS route ends in a decode error, the player now falls back to a proxy route that deinterlaces with
bwdifand re-encodes with libx264. Frame-coded interlaced and progressive H.264 are unaffected (#291). - Converted 1080i keeps its full 50 fps motion: each field becomes a frame. Video is encoded at CRF 15, since the stream only travels over loopback. Only interlaced frames are deinterlaced, and only app-built proxy requests can start an encode (#292).
- Channels that needed conversion go straight to it on reconnect or reopen for the rest of the session (#291).
- Routing keeps the media element's decode error instead of mpegts.js's generic MSE append error, so the real failure reason is shown and acted on (#291).
- Remuxed streams use a 15-second inactivity timeout instead of the 6-second direct-stream one. Providers that deliver in bursts pause for 7-9 seconds; the proxy previously killed a healthy ffmpeg mid-stream, interrupting playback every couple of minutes (#291).
Scanning
- Failed media probes are retried in both the single-connection and mixed-provider paths, using the scan's retry count and backoff. Single-connection providers often had not yet released the liveness check's connection, leaving alive rows with blank Res, Codec, FPS and Audio (#290).
- When every probe attempt finds no track, the reason is kept on the result and in the scan log, and the Resolution cell shows an amber
?with the reason on hover (#290). - Mixed-provider probes run beside media capture and retry after it, avoiding capture races. Recovered probe warnings are cleared (#290).
Full changelog: v2.2.0...v2.2.1