@Monica

Thank you for your reply. I tried several times to do a hard reset, power off, reboot, etc. Finally I realized that changing the encode setting is not the problem, the problem is the reboot. So, for example, I can change any setting (OSD, network settings, etc), press save, and the camera works fine with the new settings. Then I reboot, and all of the changes are gone; the camera has reset to the default settings.

I will email the support group directly.

I am using motioneyeOS with reolink cameras.

motion (and hence motioneye) only supports certain image resolutions. The default encodings for the reolink cameras *are not* supported. So the first thing is to set the stream encode setting of the camera to something that is supported. For example, I set the "Clear" stream to 720P. Then in motioneye, create a new camera with the url:

rtsp://camera.ip.address:554/hPreview_01_main

And select ("RTSP/TCP"). Then set the camera resolution in motioneye to match the stream output (in this example, 1280x720).

I have a 410S camera that will not save updated settings. Whenever I change the Stream Encode settings and press "Save", the camera reboots and returns to a default state with no password, default camera name ("Camera1"), OSD settings default, no change to the stream encode, etc. I tried a hard reset, but the problem returns... Can you give me some suggestions?

I would like to re-apply the latest firmware, but it seems that the camera rejects the firmware unless the new version is greater than the current version. Perhaps it would be better if the firmware would check for "greater than or equal to" the current version? Is there a way to force a firmware installation?

Thanks!
Screen-Shot-2017-01-23-at-15.56.41.png

Hi, thanks for posting the screenshots, they show the situation.
I updated to the latest firmware 16060601, but it did not fix the NTP problem
Is it possible the problem is in the client software instead of the firmware?

This link describes downloading video files *from the camera*, but the question is about files that are sent by email or ftp.

Also, it looks like the menu "Local Playback / Remote Playback" is missing from the OS X client. Is that true?

I am using the RLC-410S. I set my time zone and select the Daylight Saving (DST) mode, and the clock time is set correctly (with the button labeled "Synchronize Local Time"). But, when I enable the NTP server for automatic operation, it sets the time +1 hour from the local time. It seems like the NTP update routine does not respect the DST setting. Has anyone else observed this? Is there a solution? Thanks,
(The cameras have firmware 806_16041901)

I would also like to cast a vote for the idea of an upper limit on the image change amount for motion detection (I have the same problem with fog). That seems like a fairly easy feature to implement.

You might want to have a look at motionEye. It is free and has several motion detection options, including some noise reduction, maximum change threshold, etc.

See this thread: https://reolink.com/topic/video-file-format/

Summary: you can use the client software to decode the .h264 files only when you download from a camera directly. Many people (incl. me) have the same problem that you describe, and have requested a solution from Reolink.

The technical solutions to this problem are not trivial, however it seems to me that a camera with the ability to create and send files which cannot be viewed is not very useful; you could say that it defeats the purpose of the ftp/email features.

Reolink has made many improvements to the hardware and software recently, and so I am hopeful that this will be addressed.

Is it possible for an alarm to capture more than one still image?

In my testing with ftp, each alarm (Motion alarm) creates one .jpg file and one .264 video file. The jpeg image is good, but I cannot view the .264 file. So if the camera could save many .jpg files for each alarm, that could be useful. In many cases, I find that a high-resolution still image is better than a video for identifying people or license plates. Also the video files are large, and it is difficult to scan through them quickly. But video is better in some cases, so if it could be an option for the user, that would be helpful.

After some more testing, I see that when I download videos from a 410S (built-in SD card) using the Client application, the videos are saved as .mp4 files and they can be viewed on all platforms (including Mac). But, when the same camera, sends video files by ftp, the video files are ".264", and cannot be viewed. So, we still need a way to transcode the .264 files, both for the ftp feature and for cameras without built-in SD cards. Thanks,