Skip to content

v0.1.63 — diagnostic logging for Emby/Jellyfin playback

Choose a tag to compare

@NebulaSleuth NebulaSleuth released this 24 May 01:04
· 197 commits to main since this release

Diagnostic-only release

User reports subtitle / quality controls broken across all clients (web, mobile, Roku) for both Emby and Jellyfin sources — subtitle picks invert, quality changes no-op, Jellyfin breaks entirely. Cross-platform symptom = backend issue.

This release adds deep logging to embyLike.getPlaybackInfo so we can diagnose:

  • Received PlaybackOpts (the actual subtitle/audio/bitrate ids the client sent)
  • Full PlaybackInfo request body we POST to Emby/Jellyfin
  • Full response: PlaySessionId, MediaSource[0] (Id, Container, Direct{Play,Stream} flags, SupportsTranscoding, default stream indices, bitrate)
  • Emby's own TranscodingUrl (was truncated to 80 chars, now full)
  • Every MediaStream (Index, Type, Codec, Language, Title, IsDefault, IsForced, IsExternal, DeliveryMethod, IsTextSubtitleStream) — to test the stream-index drift theory
  • Final constructed streamUrl (api_key redacted) for replay
  • streamParams summary

All lines tagged [<label>.dbg] (e.g. [Emby.dbg], [Jellyfin.dbg]) — filter via:

GET /api/logs?lines=500&filter=.dbg

How to use

  1. Auto-update lands at ~192.168.1.181:3001 within a few minutes.
  2. Start playback against an Emby source (web is easiest).
  3. Change subtitle, then change quality.
  4. Pull the log; the diff between request 1, 2, and 3 will tell us what's happening.