Once installed, cvlc works for the self-compiled version, though also it just works fine with, say, vlc -I dummy --fullscreen --loop --no-mouse-events --no-keyboard-events --video-on-top --no-osd --mouse-hide-timeout=1 videos/some.mp4. But . . . it still visibly pauses. Arghh!

Reckoning that maybe I was just running things wrong, I've decided to install the possible-abomination I've compiled.

Running in a terminal session unfortunately doesn't seem to really benefit either very much, but VLC's CPU usage is maaaaybe even lower, and it seems entirely viable and so could bypass the need for even something like openbox (which I'm mostly using to avoid polluting the shell init for testing, but this means it could easily be a systemd service for the production approach).

Okay, actually I wayback machine'd it, which points in turn to https://code.videolan.org/videolan/vlc/-/issues/549 which in turn points to https://code.videolan.org/tguillem/vlc/-/tree/gapless-mr which was set to maybe be merged into VLC 4.0 . . . and maybe it still will be, but 4.0 isn't out yet anyways.

Got back at this, decided to try to run just direct invocations of video players that have hardware decode on the Pi.

Current status:

• OS: Ubuntu Server 24.04 (latest LTS, so good for at least another 4 years, and I keep it up to date entirely automatically)
• Nextcloud: Updated all the apps and updated the core to version 29.0.14, the latest non-.0 release of the second-latest Nextcloud version as of last I was touching this . . . but actually since then there's been a version 31. And looking now, I see at https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule that 29 is nearly EOL already: