20180602

Based on ccrisan's version 20180602 dev branch, with minor changes. More details here.

Note that this version does not support firmware update to ccrisan's MotionEyeOS. The only way to migrate back to ccrisan's MotionEyeOS is to reflash your SD card.

This is completely untested and highly experimental. Use at your own risk.

20180224

Based on ccrisan's version 20180224 dev branch, with minor changes. More details here.

Note that this version does not support firmware update to ccrisan's MotionEyeOS. The only way to migrate back to ccrisan's MotionEyeOS is to reflash your SD card.

This is completely untested and highly experimental. Use at your own risk.

20180101

Based on ccrisan's version 20180101 dev branch, with minor changes:

• Logs to RAM instead of flash.
• Reduced log file size.
• Runs logrotate every hour.
• Preference for h264_mmal decoder (Experimental).
• Added "ldr-reader" CdS photocell reader.
• Added "overlay_temper" script that overlays CPU temperature on video stream.

This is completely untested and highly experimental. Use at your own risk.

20171008

Based on ccrisan's version 20171008 dev branch, with minor changes:

• Logs to RAM instead of flash.
• Reduced log file size.
• Runs logrotate every hour.
• WPA security update to address KRACK.
• Supports MMAL camera.
• Preference for h264_mmal decoder (Experimental).

This is completely untested and highly experimental. Use at your own risk.

20170827

Based on ccrisan's version 20170827 dev & rpi-omx branch. This branch supports hwaccel on all Raspberry Pi models.
This is completely untested and highly experimental. Use at your own risk.

To get the optimum configuration, tune the following:

• Resolution : higher resolution uses more memory and CPU
• Framerate : higher frame rate uses more CPU
• Pre-capture : pre-captured frames are stored in RAM
• Minimum motion frames : frames are stored in RAM as well
• bcm2835-v4l2 max_video_width and max_video_height : higher number uses more GPU memory, if set lower than configured resolution, camera uses still mode i.e. low fps, no AE/AGC.
  • Remount root filesystem as read-write.
  • Edit /etc/modules file.
• GPU memory : allocating less GPU memory means more memory for MotionEye. Examples below for bcm2835-v4l2 max_video_width=1920 max_video_height=1200
  • 800 x 600 resolution : 66MB
  • 1280 x 720 resolution : 70MB
  • 1280 x 1024 resolution : 75MB
  • 1920 x 1080 resolution : 83MB
  • Use "gpu_stats" script to check GPU available memory.
• Disable FTP server and/or Samba server if not needed.

Pi Zero W example configuration:

• GPU memory: 70M
• Resolution: 1280 x 720
• Frame rate: 20 fps
• Movie format: H.264 (mp4 or mkv)
• Pre-capture: 10 frames or less (higher pre-cap uses more RAM)
• Minimum motion frames: 15 frames (higher value uses more RAM)
• Disable FTP server and/or Samba server if not needed.
• No live-stream and no web browser connection as it loads the CPU.

It is possible to run 1024 x 576 resolution on Raspberry Pi 256MB RAM, but need to tweak a few things to optimize the memory usage:

• /etc/modules: bcm2835-v4l2 max_video_width=1024 max_video_height=600
• GPU memory: 66MB
• Pre-capture: 0 frame
• Frame rate: 15 fps
• Minimum motion frames: 10 frames or less
• Disable FTP server and Samba server (under web UI services section)
• No live-stream and no web browser connection as it loads the CPU.

Note: Please clear web browser cache before using this version.

20170827

Based on ccrisan's version 20170827 minus the password changes. This branch supports hardware accelerated video encoding on all Raspberry Pi models.
This is completely untested and highly experimental. Use at your own risk.

To get the optimum configuration, tune the following:

• Resolution : higher resolution uses more memory and CPU
• Framerate : higher frame rate uses more CPU
• Pre-capture : pre-captured frames are stored in RAM
• Minimum motion frames : frames are stored in RAM as well
• bcm2835-v4l2 max_video_width and max_video_height : higher number uses more GPU memory, if set lower than configured resolution, camera uses still mode i.e. low fps, no AE/AGC.
  • Remount root filesystem as read-write.
  • Edit /etc/modules file.
• GPU memory : allocating less GPU memory means more memory for MotionEye. Examples below for bcm2835-v4l2 max_video_width=1920 max_video_height=1200
  • 800 x 600 resolution : 66MB
  • 1280 x 720 resolution : 70MB
  • 1280 x 1024 resolution : 75MB
  • 1920 x 1080 resolution : 83MB
  • Use "gpu_stats" script to check GPU available memory.
• Disable FTP server and/or Samba server if not needed.

Pi Zero W example configuration:

• GPU memory: 70M
• Resolution: 1280 x 720
• Frame rate: 20 fps
• Movie format: H.264 (mp4 or mkv)
• Pre-capture: 10 frames or less (higher pre-cap uses more RAM)
• Minimum motion frames: 15 frames (higher value uses more RAM)
• Disable FTP server and/or Samba server if not needed.
• No live-stream and no web browser connection as it loads the CPU.

It is possible to run 1024 x 576 resolution on Raspberry Pi 256MB RAM, but need to tweak a few things to optimize the memory usage:

• /etc/modules: bcm2835-v4l2 max_video_width=1024 max_video_height=600
• GPU memory: 66MB
• Pre-capture: 0 frame
• Frame rate: 15 fps
• Minimum motion frames: 10 frames or less
• Disable FTP server and Samba server (under web UI services section)
• No live-stream and no web browser connection as it loads the CPU.

Known issues / limitations:

• Web UI may not load properly. Try clearing browser cache.

20170827

Based on ccrisan's version 20170827 rpi-omx branch. This branch supports hwaccel on all Raspberry Pi models.
This is completely untested and highly experimental. Use at your own risk.

To get the optimum configuration, tune the following:

• Resolution : higher resolution uses more memory and CPU
• Framerate : higher frame rate uses more CPU
• Pre-capture : pre-captured frames are stored in RAM
• Minimum motion frames : frames are stored in RAM as well
• bcm2835-v4l2 max_video_width and max_video_height : higher number uses more GPU memory, if set lower than configured resolution, camera uses still mode i.e. low fps, no AE/AGC.
  • Remount root filesystem as read-write.
  • Edit /etc/modules file.
• GPU memory : allocating less GPU memory means more memory for MotionEye. Examples below for bcm2835-v4l2 max_video_width=1920 max_video_height=1200
  • 800 x 600 resolution : 66MB
  • 1280 x 720 resolution : 70MB
  • 1280 x 1024 resolution : 75MB
  • 1920 x 1080 resolution : 83MB
  • Use "gpu_stats" script to check GPU available memory.
• Disable FTP server and/or Samba server if not needed.

Pi Zero W example configuration:

• GPU memory: 70M
• Resolution: 1280 x 720
• Frame rate: 20 fps
• Movie format: H.264 (mp4 or mkv)
• Pre-capture: 10 frames or less (higher pre-cap uses more RAM)
• Minimum motion frames: 15 frames (higher value uses more RAM)
• Disable FTP server and/or Samba server if not needed.
• No live-stream and no web browser connection as it loads the CPU.

It is possible to run 1024 x 576 resolution on Raspberry Pi 256MB RAM, but need to tweak a few things to optimize the memory usage:

• /etc/modules: bcm2835-v4l2 max_video_width=1024 max_video_height=600
• GPU memory: 66MB
• Pre-capture: 0 frame
• Frame rate: 15 fps
• Minimum motion frames: 10 frames or less
• Disable FTP server and Samba server (under web UI services section)
• No live-stream and no web browser connection as it loads the CPU.

Known issues / limitations:

• Password authentication may not work. Affects web UI, Samba, FTP, and SSH.
• Web UI may not load properly. Try clearing browser cache.

20170710

Based on ccrisan's version 20170710, but with hwaccel for Raspberry Pi. More information about hwaccel here motioneye-project#365.
This is completely untested and highly experimental. Use at your own risk.

To get the optimum configuration, tune the following:

• Resolution : higher resolution uses more memory and CPU
• Framerate : higher frame rate uses more CPU
• Pre-capture : pre-captured frames are stored in RAM
• Minimum motion frames : frames are stored in RAM as well
• bcm2835-v4l2 max_video_width and max_video_height : higher number uses more GPU memory, if set lower than configured resolution, camera uses still mode i.e. low fps, no AE/AGC.
  • Remount root filesystem as read-write.
  • Edit /etc/modules file.
• GPU memory : allocating less GPU memory means more memory for MotionEye. Examples below for bcm2835-v4l2 max_video_width=1920 max_video_height=1200
  • 800 x 600 resolution : 66MB
  • 1280 x 720 resolution : 70MB
  • 1280 x 1024 resolution : 75MB
  • 1920 x 1080 resolution : 83MB
  • Use "gpu_stats" script to check GPU available memory.
• Disable FTP server and/or Samba server if not needed.

Pi Zero W example configuration:

• GPU memory: 70M
• Resolution: 1280 x 720
• Frame rate: 20 fps
• Movie format: H.264 (mp4 or mkv)
• Pre-capture: 20 frames or less (higher pre-cap uses more RAM)
• Minimum motion frames: 15 frames (higher value uses more RAM)
• Disable FTP server and/or Samba server if not needed.
• No live-stream and no web browser connection as it loads the CPU.

It is possible to run 1024 x 576 resolution on Raspberry Pi 256MB RAM, but need to tweak a few things to optimize the memory usage:

• /etc/modules: bcm2835-v4l2 max_video_width=1024 max_video_height=600
• GPU memory: 66MB
• Pre-capture: 0 frame
• Frame rate: 15 fps
• Minimum motion frames: 10 frames or less
• Disable FTP server and Samba server (under web UI services section)
• No live-stream and no web browser connection as it loads the CPU.

Known issues / limitations:

• Wifi stops working after first boot when connecting to certain access points. Workaround here: motioneye-project#1012
• Samba server may not work with Windows 10.

Version 20170710 with hwaccel for rpi

Based on ccrisan's version 20170710, but with hwaccel for Raspberry Pi. More information about hwaccel here motioneye-project#365.
This is completely untested and highly experimental. Use at your own risk.

Minimum hardware requirements: 512MB RAM
If you have the 256MB RAM Raspberry Pi, please use the previous pre-release.

To get the optimum movie quality, tune the following:

• resolution
• fps

Pi Zero W recommended configuration:

• GPU memory: 96M
• Resolution: 1280 x 720
• Frame rate: 20 fps
• Movie format: H.264 (mp4 or mkv)
• Pre-capture: maximum of 20 frames (higher pre-cap uses more RAM)
• Minimum motion frames: 15 frames (higher value uses more RAM)
• No web browser connection as it consumes too much CPU.

Pi2 and Pi3 are able to run at higher resolution, but need 128M of GPU memory. Use gpu_stat script to check available GPU memory.

Known issues / limitations:

• Raspberry Pi with 256MB RAM is no longer supported due to its limited memory.
• Wifi stops working after first boot when connecting to certain access points. Workaround here: motioneye-project#1012
• Fails to create movie previews.
• Movie quality in configuration does nothing.

Changes:

• Log files are stored in RAM to reduce microSD card wear.

Version 20170610 with hwaccel for rpi

Based on ccrisan's version 20170610, but with hwaccel for Raspberry Pi. More information about hwaccel here motioneye-project#365.
This is completely untested and highly experimental. Use at your own risk.

To get the optimum movie quality, tune the following:

• resolution
• fps
• movie quality

The below configuration is a good default:

• Resolution: 800 x 600
• fps: 20
• Movie format: H.264
• Movie quality: 75%
• Pre-cap: 1 (higher pre-cap uses more RAM)

Known issues / limitations:

• Raspberry Pi with 256MB RAM can only run up to 800 x 600 resolution due to limited RAM.
• 1920 x 1080 resolution records at 5 fps.
• 1280 x 720 resolution does NOT work.
• Wifi stops working after first boot when connecting to certain access points. Workaround here: motioneye-project#1012

Changes:

• Fixed fast movie playback issue.
• added gpu_stat script to monitor GPU usage.