-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hundreds of errors in ffmpeg 4 on rpi 4? #6
Comments
Switching my raspberry pi to use ethernet while the wyzecam's continue using the wifi they were seems to have resolved many if not all the errors/issues. I had planned to use the pi as a hotspot directly for the camera's so a router reboot would not affect them but that may be an issue if they have issues with the pi wifi. 2021-01-05T00:15:12.338Z [1] [Garage_Cam][stats] stream delay: 96s, segments in queue: 25, latest file: 20210104/19/13.mp4, errors: 3, warnings: 0 |
wyzecam-hls and shinobi both are not auto restarting on reboot....I'm having to do a pm2 resurrect to get them going. |
I'd like to know what pi and version of ffmpeg you are using because although the nfs shares and files are stable the hls stream generated is NOT. It gets hundreds of errors in the error log with multi minute gaps resulting in a jerky mess within shinobi. This is probably why motioneye wouldn't even accept the stream. It mentions Possible bad wifi but the nfs share has each minute mp4 and the hls is being generated on the same rpi that owns the share.
I'm on a rpi 4 8Gb running dietpi 64bit based on debian buster. ffmpeg version 4.1.6-1
deb10u1+rpt1 Copyright (c) 2000-2020 the FFmpeg developersdeb10u1+rpt1' --toolchain=hardened --incdir=/usr/include/aarch64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opengl --enable-sdl2 --libdir=/usr/lib/aarch64-linux-gnu --arch=arm64 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-sharedbuilt with gcc 8 (Debian 8.3.0-6)
configuration: --prefix=/usr --extra-version='1
wyzecam-hls-error__2021-01-04_00-00-00.log
wyzecam-hls-error.log
wyzecam-hls-out__2021-01-04_00-00-00.log
wyzecam-hls-out.log
The text was updated successfully, but these errors were encountered: