Immuch360 3.3.0-rc.0 build 25

Immuch360 3.3.0-rc.0 build 25: the same app as build 24, rebuilt with its own Android version code (3030023), the one Google Play and the Meta Horizon Store need. Nothing else changed.

Build 24 brought the welcome page ("Use without a server" first, then the network shares and media servers, then an Immich server), files opened with the program on a computer, the desktop packages and the DJI Osmo 360 raw files in both players; see the notes of build 24 for the details.

Files: universal APK (phones, tablets and TVs), APKs per ABI (arm64-v8a, armeabi-v7a, x86_64), the Quest APK, and the app bundle sent to Google Play.

Immuch360 3.3.0-rc.0 build 24

Immuch360 3.3.0-rc.0, build 24: start without a server

Immuch360 is a free and open source app to find, browse, play and explore your photos and videos, flat, panoramic, 360°, 3D and VR180, with or without a server. Build 24 makes that the first screen: the app opens on a welcome page, where using it without a server comes first.

New in build 24

• Welcome page. While no server session exists, the app opens on a page with its icon, "Your media. Any screen. Every perspective." and three choices: "Use without a server" (the photos and videos of the device, with every viewer, the 360° list and the network shares), "Add a network share or a media server" (the Network shares page, without asking for the photos of the device) and "Connect to an Immich server" (the login page, whose Back returns to the welcome page). Signing out leads there too, and without a server the Library tab ends with "Connect to an Immich server". Up to build 23, the login page came first, with "Use without a server" under the form.
• Every input. Touch, the TV remote (the frame starts on "Use without a server"), the Quest controller and the keyboard. The choices sit side by side on a TV, a tablet and a phone held sideways, one above the other on a phone held upright. Five new texts, in the 88 languages of the app.
• DJI Osmo 360. The .osv files of a share are listed with the 360° badge. The Immich server still refuses .osv and .360 uploads, and Android does not count .insv, .insp, .360 and .osv files as media, so raw files copied onto a phone do not appear in its gallery: play them from a share or a computer.
• Immuch360 Desktop build 5 is built from the same sources (files opened with the program, an installer, DJI Osmo 360 files in two players): it changes nothing on phones, tablets, TVs and headsets.

Checked

With debug builds on the Android phone emulator (the three choices, Back from the login page, signing out, light and dark themes) and on the Google TV emulator with the remote (the first focus, the order, OK, Back, light and dark), and by the full test suite. Not checked yet: an iPhone, a Quest and a real TV. Reports are welcome in Issues.

Files

• Immuch360-v3.3.0-rc.0-24-release.apk: universal, for every phone and tablet, and for Android TV and Google TV (installed with adb, see the README).
• Immuch360-v3.3.0-rc.0-24-arm64-v8a-release.apk: for a recent phone. -armeabi-v7a is for older 32 bit phones, -x86_64 for the Android emulator.
• Immuch360-v3.3.0-rc.0-24-quest-release.apk: the Meta Quest build, sideloaded in developer mode.
• Immuch360-v3.3.0-rc.0-24.aab: the App Bundle for Google Play, not for sideloading.

The APKs do not update themselves. They and the store versions are signed with different keys: to switch from one to the other, uninstall the app first, which loses the login, the settings and the list of network shares. Which store has which build: the platform table of the README.

More: the user guide and the known issues.

Immuch360 is an unofficial fork of the Immich mobile app, under the GNU AGPL v3. Immuch360 is not affiliated with nor endorsed by Immich, FUTO, Plex, Meta, Apple, Google, Insta360, GoPro, DJI or TP-Link.

Full Changelog: v3.3.0-rc.0-23...v3.3.0-rc.0-24

Immuch360 Desktop 3.3.0-rc.0, desktop build 5

Immuch360 Desktop 3.3.0-rc.0, desktop build 5: an installer, files opened from Windows, Linux and macOS previews

Immuch360 Desktop is Immuch360 on a computer: your photos and videos, flat, panoramic, 360°, 3D and VR180, from the folders of the computer, a NAS, a Plex server or an Immich server, with the mouse and the keyboard. No account and no server required. It is a preview for Windows 10 and 11, 64 bit; the Linux and macOS packages are early previews.

What it does on Windows

• Your folders, without a server. Choose the folders of your photos and videos: nothing is read outside them, and without a server nothing leaves the computer.
• Shares and servers. SMB, WebDAV and DLNA shares, Plex Media Server without plex.tv, Tapo cameras live and recorded, and your Immich server: timeline, albums, people, memories, search, and the backup of your folders while the app is open.
• A video player of its own. libmpv plays the flat videos of every source, with the audio track menu. 360°, 3D and VR180 videos play in the app's 360° player, where the graphics chip draws the view from each decoded frame: dragging the view keeps the memory flat, and a paused video turns without decoding. The app measures the first seconds of each 360° video and picks a frame size the chip keeps up with. On the test laptop, the dedicated NVIDIA chip drew synthetic 4K, 5.7K and 8K 360° clips at full size and 30 frames a second while the view turned; the integrated Intel chip drew them at most 2880 pixels wide.
• Raw 360° camera files, stitched on the graphics chip as they play: Insta360 .insp and .insv, GoPro MAX .360, DJI Osmo 360 .osv.
• The mouse and the keyboard. Drag, wheel, double click, the arrows, Space, J and L, F or F11 for full screen.
• Share the computer with a headset at home. A Meta Quest reads the photos and videos of your folders over the Wi-Fi.

New in desktop build 5

• An installer. Immuch360-Desktop-3.3.0-rc.0-desktop.5-windows-x64-setup.exe installs for you only (no administrator rights) or for every user, in the language of Windows, with a Start menu entry, an uninstaller, and Immuch360 Desktop in "Open with" for photos and videos. It never makes itself their default program.
• Files opened from Windows. A photo, a video or a folder opened with the program ("Open with", the command line) or dropped on its window opens at once, a 360° one in its 360° view, and "View as 360°" works on the others. Several files open together on one page. A second start hands its files to the open window and brings it to the front.
• The welcome page of build 24. "Use without a server" opens the choice of your folders, "Add a network share or a media server" the Network shares page, and "Connect to an Immich server" the login page.
• DJI Osmo 360 .osv videos in two players, one per lens, each decoded by the graphics chip, both frames drawn together: a real file played at 25 of 25 frames a second on the NVIDIA chip of the test laptop. The integrated Intel chip was not checked in 360°.
• The probe of the GPU decoders is asked again when it fails at the first start of a build.
• Linux and macOS packages, early previews: see the files below.

Checked

On one Windows 11 laptop (Intel UHD and NVIDIA RTX 4060 Laptop) with CI builds of 13 October 2026 and CC0 media: the installer for the current user (the same files as the ZIP, "Open with" for 19 file types, no default program changed, a clean uninstall); files and folders given on the command line, by second starts and by drops sent to the window by a test script; a 360° video opened that way played at 30 of 30 frames a second on the Intel chip. Not checked by hand yet: the "Open with" menu and a drag with the mouse in File Explorer, and the installation for every user.

Files

• Immuch360-Desktop-3.3.0-rc.0-desktop.5-windows-x64-setup.exe: the Windows installer.
• Immuch360-Desktop-3.3.0-rc.0-desktop.5-windows-x64.zip: the same program as a folder, to unzip anywhere and start immuch360.exe from it.
• Immuch360-Desktop-3.3.0-rc.0-desktop.5-linux-amd64.deb (Ubuntu 22.04 or later, Debian 12 or later) and Immuch360-Desktop-3.3.0-rc.0-desktop.5-linux-x86_64.rpm (Fedora 40 or later): an early preview with the folders of the computer, photos and 360° photos as a sphere. Videos do not play yet, and SMB shares need Ubuntu 24.04, Debian 13 or Fedora 39 or later.
• Immuch360-Desktop-3.3.0-rc.0-desktop.5-macos.dmg and Immuch360-Desktop-3.3.0-rc.0-desktop.5-macos.zip: Apple silicon and Intel, macOS 12 or later. Nobody working on the project has a Mac: the app was only started on the project's CI, it plays no videos yet, and its network access has not been tried. Reports are welcome.
• SHA256SUMS.txt: the checksums of the files above.

The files are not signed yet. On Windows, SmartScreen may show "Windows protected your PC": choose "More info", then "Run anyway". On macOS, Control click the app and choose Open (macOS 14 and earlier), or "Open Anyway" in System Settings, Privacy & Security (macOS 15 and later). The first start of a new build can take up to a minute while Windows scans the new files.

Not there yet

Spatial 2.5D (later, with the webcam), the map, signing in with OAuth, Google Cast, notifications, a signed build and automatic updates. A 3D video shows its left eye on the screen; true 3D is for a headset. The new texts of the computer version are in English for now. More in the user guide and the known issues.

Immuch360 Desktop is part of Immuch360, an unofficial fork of the Immich mobile app under the GNU AGPL v3. The ZIP and the installer carry libmpv (mpv and FFmpeg, under the GNU LGPL), with its licences in the licenses folder. Immuch360 is not affiliated with nor endorsed by Immich, FUTO, Plex, Meta, Apple, Google, Microsoft, Insta360, GoPro, DJI or TP-Link.

Immuch360 3.3.0-rc.0 build 23

Immuch360 3.3.0-rc.0, build 23

Build 23 finishes the TV work of build 22, on the same Immich base (Immich main of 10 October 2026, version
3.3.0-rc.0). Phones, tablets and headsets get the same app as build 22 plus these TV fixes, which only change what a
TV shows.

On Android TV and Google TV

• Sharper thumbnails: the photos of the TV itself are asked at twice the size of their tile and drawn smoothly, so fine
  detail (branches, snow) no longer speckles; the photos of the server are asked in the server's preview size instead
  of its small thumbnail.
• The focus frame passes above the label of a text field (name, port, email, server address) instead of crossing it.
• The two panes of Settings keep the margins of the screen: the focus frame is no longer cut on the right or at the
  bottom, and the focused row scrolls inside the screen.
• From build 22, on the same TV: the focused row of the Photos tab stays inside the bottom margin of the screen.

Unchanged from build 22

The Immich changes of 10 October 2026 (birthday memories, faster timeline, fewer uploads of photos the server already
has, iOS background upload fixes), the TV fixes of build 22, and the servers tested: Immich 3.2.4 and Immich built from
main on 10 October 2026.

Files

Immuch360-v3.3.0-rc.0-23-release.apk (all phones), the ABI split APKs, the Quest APK and the Play bundle. Built by
the project's GitHub Actions from the branch immuch360 at commit 4dd65d3.

Immuch360 3.3.0-rc.0 build 22

Immuch360 3.3.0-rc.0, build 22

Build 22 is the first build after a synchronisation with the Immich project: it carries the 109 commits Immich made
on its main branch between 29 September and 10 October 2026 (Immich 2685234ed), on top of the features of
Immuch360. It stays on Immich 3.3.0-rc.0 and asks nothing new of the server.

From Immich (10 October 2026)

• Memories: birthday memories, the date of a memory shown in every app language, memories kept full screen while
  swiping, the bottom information follows the photo shown.
• Timeline: rows are loaded in a deferred way while scrolling fast, long images are no longer squished on Android,
  the selection of a month no longer leaks, the picture no longer jumps when the full resolution loads during a zoom.
• Uploads: a photo the server already has is not uploaded again; on iOS, a background batch waits for its remote
  sync, and the foreground backup cancels the background uploads.
• A link that opens the app starts the session properly.
• A native core in Rust now does the thumbhash decoding, the raw photo rotation, the 10 bit conversion and the
  Android byte buffer (previously Kotlin, Java, Swift and C).
• Shared person indicator, people page search and other server fixes (see the Immich changelog).

From Immuch360

• TV (Android TV and Google TV): the login page fits a 1080p screen with "Use without a server" in view and the
  focus on the Email field at the next step; the arrows move the focus out of a group of radio buttons and OK picks
  the choice (the share type, the share quality in Preferences); a filled form asks "Discard the changes?" before it
  closes; the connection test says "1 entry" and "N entries"; the 360° list gets a compact header, whole tiles six
  per row inside the screen margins, sharper thumbnails, the focus kept inside the margins, a first tile focused on
  arrival, and a row with the 360° files of the network shares; the result of a connection test scrolls into view;
  Right from a share goes to its Edit button; changing the "Remote control layout" keeps the open page.
• The computers keep their thumbhash decoder (Immich dropped the Dart package when the phones moved to the native
  core); local decodes on a computer are capped at 16384 pixels on the long side, as on Android.
• A script merges the translation files at each synchronisation with Immich, so the keys of Immuch360 and those of
  Immich never clash (.github/desktop/i18n_merge.py).

Servers tested

Build 22 was checked against two Immich servers with the same account flow: login, timeline, albums, flat photos,
360° photos in the sphere view, video playback, the 360° list and an upload from the app, with no API error in the
app's logs:

• Immich 3.2.4 (the published release).
• Immich built from main on 10 October 2026 (3.3.0-rc.0, commit d845426), the base of this build.

Files

Same files as build 21: Immuch360-v3.3.0-rc.0-22-release.apk (all phones), the ABI split APKs, the Quest APK and the
Play bundle. Built by the project's GitHub Actions from the branch immuch360 at commit 78bce08.

Immuch360 Desktop 3.3.0-rc.0, desktop build 4 (Windows preview)

Immuch360 Desktop 3.3.0-rc.0, desktop build 4 (Windows preview)

Desktop build 4 is the computer version of Immuch360 on the same sources as the phone build 22: the Immich app of 10 October 2026 with the features of Immuch360, and the fork's own build of the video player library.

What changed since desktop build 3

• The fork's own libmpv: the ZIP now carries libmpv-2.dll built by the project's GitHub Actions from pinned sources of 2026 (mpv 0b7ed67, FFmpeg 5b9a3ad), instead of media-kit's archive of 2024. Its corresponding sources are published with the release libmpv-windows-20261009-3, and BUILD-INFO.txt in the ZIP names it. With it, the two lenses of a raw video stored one per track or one per file can be stacked in one player, and the 360° player draws the decoded frames on the graphics chip without copying them back first.
• Up to date with Immich of 10 October 2026: birthday memories and the date of a memory in every language, faster scrolling of the timeline, fewer uploads of photos the server already has, the people and the timeline fixes of the Immich app. Tested against Immich servers 3.2.4 and 3.3.0 (built from Immich main).
• A native core: Immich moved some image work (the thumbhash decoder, the raw photo rotation, the 10 bit conversion) to a library written in Rust, which the computer build compiles too. The computers keep their own thumbhash decoder, and a local photo is decoded at most 16384 pixels on its long side, as on Android.
• The phone, headset and TV apps of build 22 come from the same commit; their changes (TV navigation, the 360° list on a TV, a filled form that asks before it closes) do not change the computer version.

Checked

• On the project's CI (Windows Server 2022): the desktop tests, the build and the ZIP with the new libmpv; the macOS and Linux builds compile; the whole test suite of the app passes.
• On the test PC (Windows 11, Intel UHD and RTX 4060 Laptop): the ZIP starts, a local 1080p video opened with the program plays (the picture changed every second for 15 seconds, libmpv-2.dll of the project loaded), and the window closes cleanly with no crash report. The 360° player with this libmpv is covered by the automated tests on Windows; it has not been checked by hand on the PC with real camera files yet.

Not there yet

• Spatial 2.5D (later with the webcam), the map, signing in with OAuth (use an email and a password), Google Cast, notifications.
• An installer, a signed build and automatic updates: this build is a folder with immuch360.exe.
• Linux and macOS: their projects are in the sources and build on the project's CI, but the app has not been started on those systems yet, and their video player is not in them yet.
• Translations: the texts of the computer version are in English for now.

Install

1. Download Immuch360-Desktop-3.3.0-rc.0-desktop.4-windows-x64.zip below (about 58 MB) and unzip it anywhere, for example in Documents. To replace build 3, delete its folder or unzip into a new one: your sign in, folders and settings stay in your Windows profile, not in that folder.
2. Start immuch360.exe from the unzipped folder (173 files), and keep the folder whole: the program needs the files next to it, among them libmpv-2.dll, the video player, immuch_desktop_video.dll, which reads the decoders of the graphics chip, and the licenses folder with its licences.
3. The files are not signed yet: Windows SmartScreen may show "Windows protected your PC", choose "More info" then "Run anyway". Where Smart App Control is on, it blocks unsigned programs.
4. Windows 10 or 11, 64 bit.

Known problems

• The first start of a new build can take from 10 seconds to a minute while Windows scans the new files: wait for the window rather than starting the app again. The next starts take a second or two.
• A file held while it is read: while a video of your folders plays in the app, or while a headset reads a file from the shared computer (a video it plays, a photo it downloads), Windows cannot rename, move or delete that file and says it is open in Immuch360 Desktop: close the video, or stop the playback in the headset, first.
• The 360° view on an integrated graphics chip works on a frame at most 2880 pixels wide, so a 5.7K or 8K video is softer than on a dedicated chip, and a 5.7K H.264 video is not smooth there (see above): from the server it switches to the transcoded stream, from a folder it plays on with the message "This graphics card cannot show the 360° view of this video smoothly". On a laptop with two chips, Windows runs the app on the integrated one unless told otherwise: in the Windows settings, System, Display, Graphics, add immuch360.exe and choose "High performance", then start the app again.
• X4 files with one lens per track are not stacked smoothly on the test PC (7 to 9 frames a second even on the RTX 4060): they show one lens, half of the sphere black, with the message of the phones, then if that fails the server's transcoded stream, the LRV copy, the video unstitched. An X3 pair is stacked on the dedicated chip only; on the Intel UHD it shows one lens too.

Files

• Immuch360-Desktop-3.3.0-rc.0-desktop.4-windows-x64.zip: Immuch360 Desktop for Windows x64 (about 58 MB, 173 files once unzipped).
• SHA256SUMS.txt: checksums of the files above.

Built by the project's GitHub Actions (run 38067366625, Windows Server 2022 with Visual Studio 2022) from the main branch immuch360 at commit 9911335. libmpv-2.dll is the project's build named in BUILD-INFO.txt; mpv and FFmpeg are under the GNU LGPL 2.1 or later, the DLL as built under the LGPL 3 or later, its sources are on the release named above, and the licence texts are in the licenses folder of the ZIP, with NOTICES.md.

Immuch360 Desktop 3.3.0-rc.0, desktop build 3 (Windows preview)

Immuch360 Desktop 3.3.0-rc.0, desktop build 3 (Windows preview)

The third preview of Immuch360 Desktop, the same application as the Android, iOS, Meta Quest and TV versions, built from the same sources for a Windows computer. 360°, 3D, VR180 and raw 360° videos now play in the app's own 360° player, and the live view of Tapo cameras comes to the computer. The 360° player is at its best on a dedicated graphics chip: see the figures below. Please report what goes wrong in the issues, with the log saved from the Logs page.

What changed since desktop build 2

• 360°, 3D and VR180 videos play in the app's own 360° player, from every source of flat videos: the folders of the PC, your Immich server, the shares, Plex and the Tapo recordings. Click 360° in the top bar, as on a phone (for a 360° file the server does not flag, "View as 360°" in the ⋮ menu first). Drag with the mouse to look around (the view keeps turning a little after a quick drag), zoom with the wheel, + and - or Page Up and Page Down, turn with the arrow keys. Space pauses and plays, J and L jump 10 seconds, M turns the sound off and on, F, F11 or a double click switches to full screen, and Escape leaves full screen, then the player. The controls of the phones (close, 360°/180°, 3D, audio track and full screen at the top; play, 10 seconds back and forward, the time bar and the sound at the bottom) hide after 3 seconds of play.
• 3D and VR180: the 3D button cycles "Mono (not 3D)", "3D, top and bottom" and "3D, side by side", and the 360°/180° button switches to the half sphere of VR180. A 3D video shows its left eye, as on phones; to watch in true 3D, share the computer with a Meta Quest.
• Raw 360° videos: Insta360 .insv files with both lenses in one track, GoPro .360 and DJI .osv files are stitched as they play, with the calibration of the file, as on phones. Files with one lens per track (X4 and later) or per file (X3 pairs, keep both files together) are stacked side by side in one player when the computer keeps up: the first seconds are measured and the result is kept for that graphics chip (a way found too slow is tried again after 14 days). Otherwise the player goes through the steps of the phones, with their messages: one lens, half of the sphere black; the server's transcoded stream; the low resolution LRV copy the camera recorded next to the file; the video unstitched.
• The view is drawn by the video plugin: libmpv draws each frame into a texture of the size of the video, then the app's own GLSL pass draws the part of the sphere you look at. Turning the view changes a value of that pass, not the player: dragging costs no memory, and a paused video turns without decoding anything.
• The graphics chip is measured: the first seconds of each 360° video tell how large a frame the chip works on, the whole frame on a dedicated chip, at most 2880 pixels wide on one built into the processor (Windows tells the app which kind it is, so the Intel Arc of a Core Ultra laptop counts as built in), one step smaller when it does not keep up. The verdict is kept per kind of video (codec, size, frame rate and decoder). When even the smallest step is not smooth, a server video switches to the server's transcoded stream from where it was, and a video with none plays on with the message "This graphics card cannot show the 360° view of this video smoothly". A driver that refuses the view (no OpenGL ES 3.0, a pass it does not compile) gets the flat player, and the player says why; the next video of that kind is measured again. In Settings, Advanced, with "Troubleshooting" on, "360° video renderer" lets you choose the size yourself or the flat player, and "Measured last" names what the last 360° video got: copy it into a bug report.
• What the graphics chip decodes: Settings, Advanced, "Video decoders of this device" lists what the chip in use decodes, as Direct3D 11 reports it (it follows the graphics preference Windows keeps for each app), corrected by what the app measured while playing. The Video source setting and the two lens check of raw videos follow it.
• The Tapo live view plays on the computer as on Android: the SD stream on the page and the HD one in full screen, the sound off at first, over RTSP in TCP. A stream that is lost (the camera restarts, the Wi-Fi drops) comes back by itself, tried again for about a minute and a half while the last picture stays on screen. A camera account the camera refuses is said so and not tried again, since failed sign ins count towards the camera's lockout. The account never shows in the logs.
• The phone, headset and TV apps do not change: the computer parts are wired in under a desktop check only, and the phone and Quest release APKs built from these sources hold the same files, at the same size within 0.001 %.

Measured on the test PC

• The PC and the clips: the same Windows 11 laptop as for build 2, with an Intel UHD integrated graphics chip and an NVIDIA GeForce RTX 4060 Laptop, 16 GB of memory, on its own screen. Synthetic 360° clips: 4K H.264 (3840x1920, 30 fps, a moving test pattern), and with noise in every frame 5.7K H.264 (5760x2880, 30 fps, 132 Mbit/s) and 8K HEVC (7680x3840, 30 fps, 215 Mbit/s); for raw videos, two synthetic two lens clips, a real X3 pair (two 2880x2880 H.264 files) and a real X4 file (two 3840x3840 HEVC tracks). Each video was played at rest, while the view turned during playback, and while the view turned with the video paused. Unless said otherwise the figures are with a 2026 build of libmpv (mpv v0.41.0-1109).
• Why the app draws the view itself: with mpv's own shader and the view handed to it as an option, every change of the view rebuilt mpv's drawing passes. On the Intel UHD a 5.7K video fell to 11 to 12.5 frames a second while dragging. On the RTX 4060 each change kept 100 to 200 MB of graphics memory on the 5.7K H.264 video, 1.2 to 1.6 GB after 6 to 14 changes, until the PC ran out of memory. With the app's own pass, nothing of mpv changes while the view turns: paused, mpv draws 0 frames while the view is redrawn up to 58 times a second.
• On the dedicated chip (RTX 4060), from the whole frame: 8K HEVC at 30 frames a second with 0 dropped frames while dragging, and its memory grew by only 8 MB over 30 seconds of dragging; 5.7K H.264 at 30 frames a second with 0 dropped frames. The 360° player kept the full size for the 4K (30 of 30 fps) and the 8K clip (29.8 of 30).
• On the integrated chip (Intel UHD), at most 2880 pixels wide: 4K H.264 at 30 frames a second at rest and while dragging (30.2 of 30 in the player's measure), 8K HEVC at 29.2 at rest and 28.7 while dragging. 5.7K H.264, which the processor decodes since neither chip takes H.264 wider than 4096 pixels, at 27 at rest and 19 while dragging, about 20 in the player's measure: that is where a server video switches to the transcoded stream.
• With media-kit's 2024 libmpv (mpv v0.39.0-179), the Intel UHD copies each frame back from its decoder: the 4K clip played at 23 to 27 of 30 frames a second in the 360° player, against 30 with the 2026 libmpv. The RTX 4060 kept 30 of 30 with both.
• Raw videos with two lenses: an X3 pair stacked in one player plays at 30 frames a second on the RTX 4060 (0 of 150 frames dropped). On the Intel UHD the stack dropped 45 to 61 of 150 frames, so the player went to one lens, which played at about 30. An X4 file stacked plays at 7 to 9 frames a second even on the RTX 4060, while one of its tracks alone plays at 30: X4 files go straight to one lens on this PC. With the 2024 libmpv, which cannot stack, the player went to one lens within 2.3 seconds.
• Decoders: the list takes a fraction of a second to read (75 to 165 ms). Both chips decode H.264 up to 4096x4096, the RTX 4060 HEVC and AV1 up to 8192. The Intel UHD's driver says yes up to 16384 for HEVC and AV1, more than it plays smoothly: that is what the measured correction is for (8K HEVC with the 2024 libmpv lost 95 of 150 frames there and is marked as not keeping up).
• The Tapo live view, against a test RTSP server on the same PC that signs in the way the cameras do (Digest): the SD picture after 2.3 to 2.9 seconds, the HD one 1.2 to 1.3 seconds after the switch; a cut stream shown as lost after 1.5 seconds and back by itself 9.4 seconds later; a refused account said so within 4 seconds and not tried again. Passwords with spaces, accents and signs such as : / % @ # sign in, and no password shows in any log line.
• Tests: 855 of the 863 desktop tests pass on Windows (8 skipped by design), and the whole test suite of the app passes (4425 tests, 0 failed). A release ZIP of these sources starts, plays a 1080p test clip given on its command line, and closes cleanly, with no crash report. The 360° player opened, played, turned while playing and paused, and closed the 4K clip on both chips, with no crash and no reset of the graphics driver.
• Still to check by hand: real 360° and 3D files from the cameras in the 360° player, the window moved between the laptop's screen and an external one, sleep and resume, and a real Tapo camera.

Not there yet

• Spatial 2.5D (later with the webcam), the map, signing in with OAuth (use an email and a password), Google Cast, notifications.
• An installer, a signed build and automatic updates: this build is a folder with immuch360.exe.
• Linux and macOS: their projects are in the sources but the app has not been started on those systems yet, and their video player is not in them yet.
• Translations: the texts of the computer version are in English for now.
• The libmpv in the ZIP: see BUILD-INFO.txt in the ZIP. When it says media-kit's archive of 2024, raw videos with one lens per track or per file always show one lens, half of the sphere black (that build lacks the filter that stacks them), and the integrated chip copies each frame back from its decoder, which slows the 360° player and 8K HEVC there (see above). The lib...

libmpv for Windows, libmpv-windows-20261009-3

libmpv-2.dll (mpv with FFmpeg) for Windows x64 and arm64, built by .github/workflows/immuch360-libmpv.yml for Immuch360 Desktop. Not an app release: the Windows build of the app downloads one of these archives and checks it by its SHA-256.

• mpv: 0b7ed670f7c353dd3dd4f8ae0fc788a181a15aa6; FFmpeg: 5b9a3ad71a4b54979e7afc3a1a4269763c4f41fc; recipe: Predidit/libmpv-win32-video-cmake at fdf75129fc694b5ca555ce73cffc43bb6943ae13. Every library and its commit: BUILDINFO-x86_64.txt, BUILDINFO-aarch64.txt.
• Licence: GNU LGPL version 3 or later for the DLL as a whole (mpv LGPL-2.1-or-later, FFmpeg configured with --enable-version3); the licence texts are in licenses/ inside each archive, the notices in mobile/packages/media_kit_video/windows/NOTICES.md.
• Corresponding source: libmpv-windows-20261009-3-sources.tar.xz.
• Run: https://github.com/freeKC/Immuch360/actions/runs/37951288479

SHA-256:

9a1a156553f0b004d89791eb39e5f6c61f4f87cb9711ff0ab978031ac9063f82  mpv-dev-x86_64-20261009-git-0b7ed67.7z
230eac0a94453456617f124636512abc7dc584998c1911f98cdd83aede96c33a  mpv-dev-aarch64-20261009-git-0b7ed67.7z
9f0b9ea3aa4c9d4272511d6d80c24ea1e50f38e4b3e9c7af7cd0322ac9c7eb28  libmpv-windows-20261009-3-sources.tar.xz

Immuch360 Desktop 3.3.0-rc.0, desktop build 2 (Windows preview)

Immuch360 Desktop 3.3.0-rc.0, desktop build 2 (Windows preview)

The second preview of Immuch360 Desktop, the same application as the Android, iOS, Meta Quest and TV versions, built from the same sources for a Windows computer. Flat videos now play, from every source the app reads; 360°, 3D and VR180 videos still play flat until the next desktop builds. Please report what goes wrong in the issues, with the log saved from the Logs page.

What changed since desktop build 1

• Flat videos play on Windows, with the controls of the phones, from every source: the folders of the PC, your Immich server (the original or the transcoded version), Samba (SMB), WebDAV and DLNA shares, Plex servers, and the recordings of the memory card of Tapo cameras. Server videos reach the player through the app, so the player never holds your session token.
• Video thumbnails: the videos of your folders and of the shares show a frame of the video instead of a film icon.
• Audio tracks: when a video has two audio tracks or more (languages, commentary), an Audio track button lets you pick one.
• A paused video stays paused when the window gets the focus back.
• A video cut before its end (a share or a server that stops answering) says so, and opening it again resumes where it stopped, paused.
• One decoder on a swipe: the next video takes over the player of the one you left, so going through 8K videos does not hold two decoders.
• A new player after the graphics device is lost (a driver update or a reset of the graphics chip): the video reopens where it was.
• Playlists in a share are not followed: a file of a folder or a share that is in fact a playlist or a stream description named like a video does not make the player connect anywhere else.
• Network search: already in build 1 and kept, the search for the servers of your network and the computer share go through Windows' own functions, without the plugin that crashed the app.
• One set of sources: the computer version is merged into the main branch, so phones, headsets, TVs and computers ship from the same sources. The phone, headset and TV apps do not change with it.

Measured on the test PC

• The PC and the clips: a Windows 11 laptop with an Intel UHD integrated graphics chip and an NVIDIA GeForce RTX 4060, 16 GB of memory. Two synthetic 30 second clips with noise in every frame, so that the encoder spends its whole rate: 5.7K H.264 (5760x2880, 30 fps, 132 Mbit/s) and 8K HEVC (7680x3840, 30 fps, 215 Mbit/s), played from a file in an optimised build as the app draws them (at most 1440 lines high), 300 frames per measure.
• On the dedicated chip (RTX 4060): 5.7K H.264 and 8K HEVC with 0 dropped frames, on the laptop screen and on an external screen, and the app stays smooth.
• On the integrated chip (Intel UHD), which Windows gives the app by default on this PC: 8K HEVC shows only half to three quarters of its frames (66 to 141 of 300 dropped) and the app slows down around it. 5.7K H.264 drops at most 27 of 300 frames, but in full screen the app redraws at about 30 frames a second while it plays.
• 5.7K H.264 is decoded by the processor on both chips, since their decoders refuse H.264 wider than 4096 pixels: about three cores. HEVC is decoded by the graphics chip. One 8K player takes 1.6 to 1.9 GB of graphics memory, which the Intel UHD takes from the computer's own memory.
• From a share and from a server: from a Samba share and from an Immich server, both running on the same PC (so the network itself is not in the measure), the app hands the player 719 to 2800 Mbit/s, 3 to 13 times the rate of these clips, with no stall while playing.
• 200 players in a row, opened and closed through the app's player pool: handles and memory stay flat after the first rounds, no leak.
• The player: libmpv, mpv v0.39.0-179-g0f78584518 with FFmpeg N-117622-g8d940a07d.
• Tests: 656 of the 663 desktop tests pass on Windows (7 skipped there by design), and the whole test suite of the app passes (4237 tests, 0 failed). The ZIP of this build starts, plays a 1080p test clip given on its command line, and closes cleanly, with no crash report.

Not there yet

• 360°, 3D, VR180 and raw 360° videos play flat for now, as the file holds them (the whole sphere unrolled, the two eyes side by side, or the round pictures of the lenses of a raw file), and the 360° button stays on photos. Their players come with the next desktop builds.
• Spatial 2.5D (later with the webcam), the Tapo live view, the map, signing in with OAuth (use an email and a password), Google Cast, notifications.
• An installer, a signed build and automatic updates: this build is a folder with immuch360.exe.
• Linux and macOS: their projects are in the sources but have not been built on those systems yet, and their video player is not in them yet (videos would show a placeholder).
• Translations: the texts of the computer version are in English for now.

Install

1. Download Immuch360-Desktop-3.3.0-rc.0-desktop.2-windows-x64.zip below (about 57 MB) and unzip it anywhere, for example in Documents. To replace build 1, delete its folder or unzip into a new one: your sign in, folders and settings stay in your Windows profile, not in that folder.
2. Start immuch360.exe from the unzipped folder (78 files), and keep the folder whole: the program needs the files next to it, among them libmpv-2.dll, the video player, and the licenses folder with its licences.
3. The files are not signed yet: Windows SmartScreen may show "Windows protected your PC", choose "More info" then "Run anyway". Where Smart App Control is on, it blocks unsigned programs.
4. Windows 10 or 11, 64 bit.

Known problems

• The first start of a new build can take from 10 seconds to a minute while Windows scans the new files: wait for the window rather than starting the app again. The next starts take a second or two.
• A file held while it is read: while a video of your folders plays in the app, or while a headset reads a file from the shared computer (a video it plays, a photo it downloads), Windows cannot rename, move or delete that file and says it is open in Immuch360 Desktop: close the video, or stop the playback in the headset, first.
• 8K HEVC needs the dedicated graphics chip: on a laptop with two chips, Windows runs the app on the integrated one unless told otherwise, and there an 8K HEVC video drops frames and slows the app (see above). In the Windows settings, System, Display, Graphics, add immuch360.exe and choose "High performance"; the picture stays right when the window moves to a screen driven by the other chip. A PC with only an integrated chip like the Intel UHD of the test PC does not play 8K HEVC smoothly yet.

Files

• Immuch360-Desktop-3.3.0-rc.0-desktop.2-windows-x64.zip: Immuch360 Desktop for Windows x64 (about 57 MB, 78 files once unzipped).
• SHA256SUMS.txt: checksums of the files above.

Built on the maintainer's computer from the main branch immuch360 at commit 5b723bd (phases 1 and 2a of the computer version merged). The ZIP carries libmpv-2.dll from media-kit's build of 2024-10-21 (mpv at commit 0f78584518, FFmpeg at commit 8d940a07d): mpv and FFmpeg are under the GNU LGPL 2.1 or later, the DLL as built under the LGPL 3 or later, and their licence texts are in the licenses folder of the ZIP, with NOTICES.md.

v3.3.0-rc.0-21

Full Changelog: v3.3.0-rc.0-20...v3.3.0-rc.0-21