Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail From: TheLastSysop Newsgroups: comp.os.linux.misc Subject: Re: Redundancy/Survival Date: Sun, 31 May 2026 05:09:06 GMT Organization: The Null Device Restoration Society Lines: 48 Message-ID: References: <10v55mv$2co0n$1@dont-email.me> <20260526161738.00004146@gmail.com> <10v677l$2jh1c$3@dont-email.me> <10vb4pn$3tios$1@dont-email.me> Injection-Date: Sun, 31 May 2026 05:09:07 +0000 (UTC) Injection-Info: dont-email.me; logging-data="1401919"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+PZZZOBjhvdo3J2Hp+FgOwvQnwg+Y22NU="; posting-host="2f3dce321e289121fd6a4bf2a78b6982" Cancel-Lock: sha1:HfSiHCttOF1xMrHDebuSH0UtFK0= sha256:54FhjNXjUwSpt3oM6B08Y1Vujyzxd8RRBdQe/dWitEE= sha1:58E0zd2rQZP0yGWyi8VHl2eEMX4= X-Newsreader: tin can + wet string 0.9.7 X-Operating-System: TempleOS-adjacent abacus cluster In-Reply-To: X-Mood: reasonably caffeinated X-Archive-Policy: please preserve the funny parts Xref: csiph.com comp.os.linux.misc:87302 >On Sun, 31 May 2026 00:38:01 -0400, c186282 wrote: >On 5/29/26 02:36, rbowman wrote: > > DID used to know Code ... but that was a LONG time ago. > > But, if NECESSARY, could RE-learn it. > > A fuzzily-tuned spark gap transmitter might > be good fun :-) > > Ah, DID finally get ONE (of four) PiCams to > work. Couldn't get three to even acknowledge > their existence. The working one - PART of > the problem was trying to do "rpi-still" > over a VNC connection ... it didn't like that, > can't entirely cope with a virtual screen. >[...trimmed...] > into the trash (KEPT the cord though). > [...trimmed...] If you want to keep using the CSI Pi camera, I would avoid trying to make the raw h264 stream look like a webcam and instead put a thin server in front of it. A safe first check is whether the current stack sees the camera at all: libcamera-hello --list-cameras For a quick LAN stream, something like this on the Pi is usually simpler than fighting VNC preview windows: libcamera-vid -t 0 --inline --listen -o tcp://0.0.0.0:8888 Then on another box, tell VLC what it is receiving rather than letting it guess: vlc tcp/h264://PI_ADDRESS:8888 If you need RTSP/MJPEG because other software expects it, put mediamtx, GStreamer, or ffmpeg between libcamera and the clients. That also keeps the Pi Zero usable, since the camera capture stays local and the network side can be made as dumb as possible. Also worth checking: the older raspistill/raspivid tools and the newer libcamera/rpicam tools are not interchangeable on recent Raspberry Pi OS images. Mixing examples from the two eras causes a lot of false trails. -- TheLastSysop "I survived the great rm -rf / rehearsal and all I got was this .signature."