Reolink Year in Review 2023
How ColorX Technology Turn Night into Day
Reolink App v4.43 Released
I've had a long-running problem with videos saved from my 411S camera via FTP to a local Raspberry Pi server. The videos all play fine, but a large proportion (maybe 25%?) have errors in the video headers. It's not been too much of a problem in the past as my software has seemingly tolerated the errors, but a new version is more strict and just won't open the videos any more.If I try to open one of the videos in FFMPEG, I get [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7ff492000400] error reading header [path]: Operation not permitted.I've put an example video here: https://www.dropbox.com/s/tu4ddegh6yn05nu/ErrorReadingHeader.mp4?dl=0Grateful for any insight into what's going wrong - the file is unmodified (other than being renamed and uploaded to Dropbox) since being saved onto my computer using the FTP feature of the Reolink 411S.PS - I've just updated the firmware to the latest version, and reset all settings / configuration, but no improvement...Thanks!
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7ff492000400] error reading header [path]: Operation not permitted
I had no problems in playing your video using the VLC-player (https://www.videolan.org/vlc/).Since VLC is supported on quite a number of platforms, probably you might try this or search for someone who ported it to a Raspberry-Pi server (I don't own a Raspberry-Pi to try it for you unfortunately ).Another option might be to convert it using something like Handbrake (https://handbrake.fr and https://en.wikipedia.org/wiki/HandBrake).Although FFMPEG is used quite often by various (embedded)video-app developers you might end up using older versions which didn't fix the specific error you experienced.
So just as an update, I got an answer from another source (https://superuser.com/questions/1462076/25-of-my-mp4-have-error-reading-header-in-ffmpeg-opencv-but-videos-all-pl).Basically, it sounds like some of the metadata for the videos saved from my camera isn't quite standard. The answer at the link above explains better than I ever could, but would be grateful if someone from Reolink could take a look and see whether that can be fixed / changed in a firmware update. I've got a workaround for now, and sounds like there will be a patch to FFMPEG shortly to make it tolerate this type of metadata, but would be great if the camera produced "standard" .mp4 videos by default.
Sorry for any inconvenience caused to you. Could you please take the screenshot of this post and send an email to email@example.com? Our support team will check it for you soon. Thanks.
Hi there! Join the Commnunity to get all the latest news, tips and more!