Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: RockJamm on June 06, 2020, 06:41:51 AM
-
In order to use FFmpeg as a server the listen option needs to be used but the version I get from tce-load -I ffmpeg when I run this (and yes there may be other issues with the script but it's a work in progress):
#!/bin/sh
raspividyuv -fps 40 -o - -md 7 -w 1920 -h 1080 -n -t 0 -awb greyworld | ffmpeg -f flv -listen 1 -i - -c copy rtsp://localhost:9998
complains:
ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers
built with gcc 9.2.0 (piCore)
configuration: --prefix=/usr/local --disable-static --enable-gpl --enable-version3 --enable-shared --disable-debug --disable-doc --enable-bzlib --enable-fontconfig --enable-libass --enable-libfreetype --enable-libpulse --enable-libspeex --enable-libtheora --enable-libvorbis --enable-zlib --enable-libmp3lame --enable-libv4l2 --enable-libvpx --enable-libx264 --enable-libx265 --enable-libwebp --enable-libpulse --enable-libspeex --enable-libopus --enable-librsvg --enable-gnutls --enable-sdl2
libavutil 56. 31.100 / 56. 31.100
libavcodec 58. 54.100 / 58. 54.100
libavformat 58. 29.100 / 58. 29.100
libavdevice 58. 8.100 / 58. 8.100
libavfilter 7. 57.100 / 7. 57.100
libswscale 5. 5.100 / 5. 5.100
libswresample 3. 5.100 / 3. 5.100
libpostproc 55. 5.100 / 55. 5.100
Option listen not found.
Could this be because it's missing from the extension?
-
It's difficult to tell with ffmpeg as it has changed so much over the years - ffserver has been depreciated for several years and (afaik) not replaced. It is possible that the listen option only worked with earlier versions of ffmpeg...
-
Ah ok. Thanks. I think I may try the GStreamer route. Thanks for your suggestion of Motion. I’ve used it before, I’ll have another look at it. My aim is multiple pi cameras monitoring wildlife from a central much more powerful machine with the highest possible stream quality/reliability. PiCore will be hard to beat from a reliability perspective I imagine.
-
https://ffmpeg.org/ffmpeg-protocols.html (https://ffmpeg.org/ffmpeg-protocols.html)
It is still documented for http and rtmp as an experimental server.
-
Thanks for your suggestion of Motion. I’ve used it before, I’ll have another look at it. My aim is multiple pi cameras monitoring wildlife from a central much more powerful machine with the highest possible stream quality/reliability. PiCore will be hard to beat from a reliability perspective I imagine.
You could run motion on each RPi and watch them on the more powerful machine using ffmpeg (ffplay) or a browser as I mentioned in the other thread.