This unstable release is the latest in the bleeding edge of development. This release resolves a critical problem where the default storage path (/) used 95%, which meant once the storage path was full the system could stop functioning or cause random problems. By default the default percentage is 94%.
This release resolves an issue with analog cameras having long camera names. This also helps to resolve some problems where two ethernet cards are installed in the same computer and the ethernet cards switch between eth1 and eth0 randomly on startup, causing license problems. This release also resolves a problem where storage paths are using a Windows Share (SAMBA).
There is also support to triggering recording from an API call. Currently this API is very limited and you can only trigger a recording for a pre-set period of time. We will update this page with more information once we expand the API in future releases.
Download instructions for the unstable repository can be found here. Please post questions or comments to the unstable / bleeding edge forum (community.bluecherrydvr.com). It is not possible to downgrade from the unstable release back to the stable release without completely removing and reinstalling the software (including the database).
The following changes were added in this release:
* Fix solo6x10 text overlaying for cameras with long names
* Emit warning on incorrectly low min_thresh, and don’t silently discard that Storage path
* Drop chmod over recordings
* Introduce license check against a set of machine ids (for each ethernet device)
* Fix live view for odd-sized MJPEG streams (fixed in libavformat)
* Trigger Mode support to recording schedule
* Ignore unexpected elementary streams, correctly
* Close AVIOContext immediately after muxer open failure
* Drop check for available inodes on storage filesystem (fails on Windows share)
* Change default Storage.max_thresh from 95 to 94
* Silence the scary log messages from is_media_max_age_exceeded()