Immuch360 desktop build 3

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 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.
• 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.
• 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.
• 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.
• What the graphics chip decodes
• 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.
• 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 %.
• 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.
• 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 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.
• 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.
• 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.
• 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).
• Decoders: the list takes a fraction of a second to read (75 to 165 ms).
• 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.
• 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).
• 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.
• The libmpv in the ZIP: see BUILD-INFO.txt in the ZIP.
• 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.
• 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".
• X4 files with one lens per track: are not stacked on this 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.