Just a useful tip, which was oddly hard to locate ...
Was trying to re-stream a mjpeg stream from a security
camera based on a Pi + webcam + motion.
The "netcam_url" param needs to begin with "mjpeg://" as
in "netcam_url=mjpeg://111.222.111.222:5678" and then
it works. "
http://" does not work.
If there's a login, provide it with the "netcam_userpass"
param.
Of note, have seven cams all using one Pi-4 as the central
server to create mjpeg streams. A few are attached, others
are via wireless, one is the Pi+cam+Motion. Uses only 40%
CPU according to 'top', and I suspect that's only 40% of
one core. Very efficient !
"Motion" can be very useful. However I tend to use very
low frame-rates ... 1 or 2 FPS ... which is good enough
for most security purposes. However if you demand 30fps
then I doubt a Pi could cope nearly as well. "Motion"
is oriented towards mjpeg streams also, so if you must
have SOUND then an rtsp:// capable utility is going
to fit your needs better. Motion can (sometimes) monitor
rtsp, but it outputs a sound-free mjpeg stream.
Note that starting a couple of years ago the RHEL-derived
distros started using a STUPID version of ffmpeg that hasn't
nearly as many capabilities. Try to replace it with the smart
version and you'll run into the "dependencies wall", the
greatest curse of Linux. I see why why more and more stuff
comes as app-images.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)