Version 6 Beta

[bp2008]

Is there any indicator or javascript variable to indicate if direct-to-wire is working? I have H.265 direct to disk and tried enabling direct-to-wire both in UI3 and in encoding options, but stats for nerds show much higher bitrate compared to what it should be

Edit:
My bad UI is in bits while BI is in bytes. Looks like direct-to-wire only works for the LIVE view. Interestingly the plyer delay is much higher for direct-to-wire about 11 frames vs 2-3 frames for re-encoded stream from timeline.

Further testing shows that direct-to-wire delay is variable between 2 and 16 frames, maybe it is related to iframe ? It would be nice to have option for player to wait for iframe to always stream with minimal delay.

Nothing is available yet to explicitly say if direct-to-wire is working. I test by checking the codec and bit rate in Stats for nerds. I also configure my direct to wire profile to be very low quality and bit rate otherwise so you can tell by bit rate if direct to wire is working.

The delay is often higher unavoidably with direct-to-wire. I'm not sure why but there's nothing we can do about it.

 

[jrbeddow]

As many others predicted, the list of changes for Version 6 seems rather underwhelming (IMHO). Personally,I was really hoping for a long awaited solution to getting (push/Pushover) alerts for situations where recording starts in a "non-critical" zone but eventually crosses into a zone of higher priority/concern. Before anyone mentions doing this with cloned cameras; no thanks, I have explored that but really don't want to use that cludge.

 

[tmushy]

As many others predicted, the list of changes for Version 6 seems rather underwhelming (IMHO). Personally,I was really hoping for a long awaited solution to getting (push/Pushover) alerts for situations where recording starts in a "non-critical" zone but eventually crosses into a zone of higher priority/concern. Before anyone mentions doing this with cloned cameras; no thanks, I have explored that but really don't want to use that cludge.

Thinking same thing kind of a huge let down. Make me wonder what the future looks like for blue iris.

 

[wittaj]

As many others predicted, the list of changes for Version 6 seems rather underwhelming (IMHO). Personally,I was really hoping for a long awaited solution to getting (push/Pushover) alerts for situations where recording starts in a "non-critical" zone but eventually crosses into a zone of higher priority/concern. Before anyone mentions doing this with cloned cameras; no thanks, I have explored that but really don't want to use that cludge.

I accomplish this with different IVS rules. One IVS rule to trigger the non-critical zone and another IVS rule for the critical zone that sends me a push.

 

[jrbeddow]

I accomplish this with different IVS rules. One IVS rule to trigger the non-critical zone and another IVS rule for the critical zone that sends me a push.

I appreciate the advice: I tried that as well, but with limited success, as I also use BI motion detection (with CPAI), in conjunction with allowing the in camera IVS (ONVIF) triggering. In most cases the CPAI triggers beat out the IVS ones (in terms of timing), but not always, so for these purposes the results are inconsistent.

It would seem that Ken would have to explicitly add an option to genuinely only send an "action alert" on newly added zones to existing triggers/alerts. I have tried all the current additive/exclusive options with no luck either.

 

[biggen]

I accomplish this with different IVS rules. One IVS rule to trigger the non-critical zone and another IVS rule for the critical zone that sends me a push.

Also do this with my setup. Using ivs on my ~50 cam setup across 3 BI installations is wonderful so I never have to use CPAI.