Wicaby 0.14.2

Desktop only. The Android apps stay at 0.13.0 (versionCode 41 and 38): their update.json entries are unchanged.

Fixed

• Desktop: IPTV TV channels (the Freebox TV playlist among them) show their picture again. Every IPTV channel was taken
  for a radio channel, so a black "Radio" screen covered the video (only the sound played, and the picture showed
  for a moment when leaving with Escape), and the display could go to sleep. Channels marked radio="true" keep the
  radio screen.

Wicaby 0.14.1

Desktop only. The Android apps stay at 0.13.0 (versionCode 41 and 38): their update.json entries are unchanged.

Added

• Desktop: IPTV lists with rtsp:// channels play in mpv, among them the Freebox TV playlist
  (http://mafreebox.freebox.fr/freeboxtv/playlist.m3u, from the Freebox network). A list whose streams are all in
  formats Wicaby cannot play (udp, rtp, rtmp) now says so instead of "No playable channel", and IPTV channels open
  in mpv even when the built-in player is the default.

Changed

• Desktop (Windows and Linux X11): mpv plays in the Wicaby window as you left it (same screen, size and position,
  maximized or snapped), and Wicaby comes back the same way afterwards; moving, resizing or maximizing the player
  carries over. Full screen only when you ask (F, double-click, the button), and leaving it returns to that window.
• Linux (native Wayland): the player opens at the size of the Wicaby window, maximized if it was (the compositor
  decides where it goes).
• Desktop: Start in Full Screen (Settings → Playback) is off by default (it was on up to 0.14.0, and is turned off
  once on update); turn it on again there.
• Linux: when mpv uses its own window (native Wayland when video cannot play inside Wicaby), it opens at the
  size of the Wicaby window, maximized if it was, not in full screen.

Wicaby 0.14.0

Desktop only. The Android apps stay at 0.13.0 (versionCode 41 and 38): their update.json entries are unchanged.

Added

• Desktop: the Home featured banner can be set up in Settings > Home and libraries (#19): its source (Automatic, the default and the banner as before, or Random, Recently added, Continue watching, Favorites, Top rated, Unwatched), movies, shows or both, which libraries or collections feed it, excluded genres, 5 to 20 titles, the time per title, and hiding watched titles. Random draws a new set on each visit and has a New Titles button; the banner also gets previous and next arrows.
• Desktop: a Shuffle screen, opened from Home or the sidebar, that picks five films or series for you at random, from
  all your libraries, one library or one genre (genres with the same name in other languages count as one), with
  unwatched, Continue Watching, decade and rating filters; Play starts one directly and R shuffles again (#18).
• Desktop: Administration → Analytics (Emby and Jellyfin): items, media types, video and audio codecs, containers,
  resolutions, HDR formats, subtitles and audio languages for every library or one, with the items behind each
  figure, a cached scan you can refresh, and CSV or JSON export (#17).

Wicaby 0.13.2

Desktop only. The Android apps stay at 0.13.0 (versionCode 41 and 38): their update.json entries are unchanged.

Added

• Desktop: a message at start when Chromium cannot use the GPU (the app then draws without it).

Fixed

• Desktop (Linux): when Chromium starts without GPU compositing, Wicaby clears Chromium's GPU caches and relaunches
  once with more conservative GPU switches (no zero-copy, GPU rasterization or hardware video decode; then no GPU
  sandbox; then ANGLE on GLES under Wayland, on Vulkan under X11), and keeps the first set that works for later
  starts of that version. A GPU process that is only slow to start is no longer mistaken for a failure.
• Desktop (Linux): with WICABY_OZONE or outside a Wayland session, Wicaby could run its windows on X11 and its GPU
  process on Wayland, which left it without any GPU. It now relaunches once on the right display backend, and only
  picks Wayland when the Wayland socket exists.
• Desktop (Linux, in-window video on Wayland): Chromium and libmpv now use the same GPU, chosen before Chromium
  starts (the GPU the computer booted on, NVIDIA only with nvidia_drm.modeset=1). WICABY_RENDER_NODE still
  overrides the choice.
• Desktop (Linux, in-window video): Wicaby now checks that the player window shows the frames libmpv renders. When
  it does not (a black or garbled picture), when Chromium's GPU process fails during playback, or when frames cannot
  be drawn, playback moves to mpv's own window, and later starts on that computer go straight there until Wicaby,
  the graphics driver or the GPU changes (WICABY_MPV_RENDER=texture tries again).
• Desktop (Linux, in-window video): video buffers are now allocated with an explicit layout (linear first, else one
  the driver lists as renderable). Without it, AMD (radeonsi) gave buffers Chromium could not import: its GPU process
  crashed and restarted (black and white flashes), then fell back to software for the session (a black picture).
• Desktop (Linux, in-window video): mpv no longer stalls and drops frames while the player window holds every
  buffer (6 instead of 4), and a buffer Chromium never gives back is reclaimed after 5 s.
• Desktop (Linux): the tar.gz has a wicaby.sh launcher that adds --no-sandbox only where the system blocks
  Chromium's sandbox (Ubuntu 24.04 and later); the AppImage no longer needs libfuse2; the in-window video addon is
  built against Ubuntu 22.04, so it also loads on older distributions; mpv started from the AppImage no longer loads
  the AppImage's own old libraries. WICABY_LIBMPV names the libmpv to load (NixOS).
• Desktop (Linux, Wayland): when Chromium composites in software (its GPU process failed to start, seen with a
  Radeon on CachyOS), video now opens in mpv's own window instead of a black in-window picture. The log line
  chromium gpu: ... gpu_compositing ... shows that state.

Wicaby 0.13.1

Desktop only. The Android apps stay at 0.13.0 (versionCode 41 and 38): their update.json entries are unchanged.

Added

• Desktop: Settings > Home and libraries > Show in the sidebar hides the sidebar groups you do not use (Live TV and
  IPTV, for example).
• Desktop (Linux): Settings > Playback > Video inside Wicaby's window. Turning it off keeps mpv in its own window,
  as before 0.13.0, from the next start: the way out when the picture stays black.

Fixed

• Desktop (Linux, in-window video on Wayland): on a computer with two GPUs (Intel and NVIDIA laptops), libmpv now
  renders on the GPU Chromium draws with, instead of the first one found. On the other GPU the picture stayed black
  with no error. WICABY_RENDER_NODE still overrides the choice.
• Desktop (Linux, in-window video): when the player window cannot draw the frames, playback now moves to mpv's own
  window, as when they cannot be sent, rather than staying black.
• Desktop: library and music pages animate their first 30 cards in, not 12.
• Desktop (Linux): the log names Chromium's GPUs and whether it composites and draws canvases on the GPU, for
  black-picture reports.

Wicaby 0.13.0

Android TV 0.13.0 (versionCode 41), Android mobile 0.13.0 (versionCode 38); no Android change.

Added

• Desktop (Linux): in a native Wayland session, video plays inside Wicaby's player window again, under its own
  controls, as on Windows and X11. libmpv renders into GPU buffers that the player window draws (new
  apps/desktop/native/mpv-render addon, built by npm run build on Linux). It needs libmpv (libmpv2, which
  the .deb now depends on, with libgbm1, libegl1 and libgles2); without it, mpv keeps its own window as in
  0.11.1, and also with GPU acceleration off or no usable GPU render node. Video in this mode does not need the
  mpv command. If in-window rendering fails at run time, the item is retried once in mpv's own window, which is
  kept for the rest of the session. WICABY_MPV_RENDER=detached keeps mpv's own window and process. Known limits:
  SDR only (HDR is tone-mapped), a decoder crash closes Wicaby, and picture-in-picture is placed by the compositor
  (on Hyprland a title rule does not fire when the title changes on the toggle; docs/desktop.md suggests a
  float-and-pin key). Music still plays through the mpv process.
• Desktop (Linux): Hyprland theme. It reads the current Omarchy theme's colors.toml
  (~/.local/state/omarchy/current, or ~/.config/omarchy/current on older Omarchy) and paints every window
  with it, light or dark, accent included; without Omarchy it uses Hyprland's active border color as the accent
  over Graphite. Changing the Omarchy theme repaints Wicaby within a second. The card only shows when one of the
  two is found; on Windows, or when neither is there any more, a saved Hyprland theme shows as Graphite.

Fixed

• Desktop (Linux): sign-ins are kept again on Hyprland, Sway and other desktops Chromium does not recognise. It
  picked its "basic_text" store there even with gnome-keyring or KeePassXC running, so Wicaby kept the accounts in
  memory only and asked for them again at every start. Wicaby now asks for the Secret Service (libsecret) on these
  desktops; a --password-store switch given by hand still wins.
• Desktop: the system media controls (MPRIS on Linux, so shell and bar widgets, and the Windows media flyout) show the
  album art, the film poster or the channel logo again. Chromium refuses artwork from Wicaby's own image scheme;
  the art is now handed over as a data URL.
• Desktop music: the full-screen player's "Similar" tab no longer flickers and reloads a new mix on every position
  update; it loads once per track.
• Desktop (Linux, in-window video): audio goes through PulseAudio (pipewire-pulse) rather than mpv's native PipeWire
  output, whose realtime thread could get the whole app killed on systems with rtkit.

Wicaby 0.12.0

Added

• New TV web app for Samsung and LG TVs (#15, thanks @SEC844). It is the Android TV app rebuilt for TVs that only run web apps, from 2018 models on (Samsung Tizen 4+, LG webOS 4+). It replaces the previous web TV app and updates it in place: your servers, your accounts and your device carry over.
  • On Samsung, playback goes through the TV's own hardware player (AVPlay, with HDR10 and HDR10+).
  • The app has Home, search, libraries, music with lyrics, Live TV with the guide, photos, comics and several servers.
  • Test builds only: the .wgt and .ipk below are unsigned. docs/tv-web.md explains how to install them.
• Android TV: a "Next Episode" button in the player's control bar whenever there is a next episode or queue item.
• Desktop music: a Stop button beside Play/Pause. It ends playback and hides the music bar.
• Desktop comics: a Folders view. A books library now opens on its folder tree, with breadcrumbs and folder covers. "All Books" keeps the flat list, and the choice is remembered per library.
• Community timestamps (every app): Settings > Playback. It fills in the intro, recap, credits and preview that your server has no markers for, from TheIntroDB and IntroDB, ahead of AniSkip.
  • Each kind follows its usual Ask / Auto / Off setting.
  • It is off by default, because it sends the watched title's TMDB, TVDB or IMDb id to these services.
  • The TV web app uses TheIntroDB only.

Android TV 0.12.0 (versionCode 40), Android mobile 0.12.0 (versionCode 37).

Wicaby 0.11.2

Desktop fix release.

Fixed

• Resume in the same session (#14): playing the same title again without restarting Wicaby started from the position it had before the last viewing. Pages now reload the position as soon as the server has the stop report.

Android: no change (Android TV 0.11.2, versionCode 39; mobile 0.11.2, versionCode 36).

Wicaby 0.11.1

Linux fix release.

Fixed

• Linux (Wayland): in a Wayland session Wicaby now runs as a native Wayland app by default. Under XWayland, the window never showed on hybrid Intel + NVIDIA setups (#14). Video plays in mpv's own window there, with mpv's on-screen controls and keys (Space, arrows, f fullscreen, q to close), and Wicaby comes back when it closes. WICABY_OZONE=x11 brings back the embedded player.

Windows, X11 and Android: no change (Android TV 0.11.1, versionCode 38; mobile 0.11.1, versionCode 35).

Wicaby 0.11.0

Nouveautés

• Connexion par code (Quick Connect, Jellyfin) : un code à 6 chiffres à valider depuis un appareil déjà connecté, plus besoin de taper un mot de passe à la télécommande. Réglages › Comptes › Autoriser un appareil.
• Regarder ensemble (SyncPlay, Jellyfin) : créer ou rejoindre un groupe ; lecture, pause et avance sont partagées.
• « C'est quoi cette musique ? » : reconnaît la musique d'un film ou d'une série via Shazam (desktop avec mpv, touche W ; Android en lecture directe).
• Notes IMDb, Rotten Tomatoes, Metacritic, Letterboxd, TMDb sur les fiches, avec une clé MDBList gratuite.
• AniSkip pour les animés : opening, ending et récap sautables quand le serveur n'a pas les repères (désactivé par défaut).
• Sous-titres SDH et audiodescription : badges SDH/AD, préférence SDH, et l'audiodescription n'est plus choisie d'office quand une piste normale existe.
• Scrobbling ListenBrainz et Last.fm pour toute la musique, avec file d'attente hors ligne.

Corrections

• Linux / Wayland (#14) : icône, fenêtre qui n'apparaissait pas, WICABY_OZONE=x11|wayland|auto, WICABY_DISABLE_GPU=1, et lecteur intégré en Wayland natif (mpv ne peut pas s'y intégrer).
• Android TV : l'onglet sélectionné garde ses bords arrondis (#12, merci SEC844).

---

What's new

• Quick Connect sign-in (Jellyfin), Watch together (SyncPlay), "What's this song?" (Shazam), external ratings (MDBList key), AniSkip for anime, SDH and audio description preferences, ListenBrainz and Last.fm scrobbling.
• Fixes: Linux Wayland (#14), Android TV tab pill (#12).