Dynamic ***** **** - *** *** *******
**** *** ***** ******* ***** rate (****) ** *********, allowing *** ***** **** to **** *** **** based ** ****** ********. While **** ****** ** not *****, ** ** being ******** **** ********'* ******* scene *********** *** ******* I-frame *********, ** ******* massive ********* *******.
***, ********* *** *********** ***** frame ***** *** ***-******** times. ********* ****** ***** on *** ******** *****, if *** ***** *** a ***** ****** ** activity ** *** **** from ***** ** *****, while * **** ****** scene **** ** * hallway *** **** ** low ** ****.
** *** ********* *****, Axis ***** *** * ******* framerate (** *****) ***** reduce ******** ******** ** a ******** *** ******* (in *****):
**** ********* ***** ***** more ********:
**** *** ** ******* (or ***) ************* ** the ******** *********** *** I ***** ********. ** the ***** *******, ***** is ** ******** *** a ***** ** ******* frame **** *** *** can ** **** ** 1. **** **** * future ******** ******* **** add ****.
************
*** *** ********* **** DFPS **** ** ********* in *** **** ***** starting **** *** *.** firmware.
Original ********* ******* ***********
*** ******** **** ********* **** ****** ************* ******* ** 50%+ ***********, **** **** just ******* *********** *** I ***** ********.
**** ** * ********** from *** ********** *****-* ****:
Projected ********* ******* *** ***
** ***** **** ******* of *** ******** (********, stairwalls, ***** ***** *****, etc.), *** ******** ** DFPS **** ****** **** ********* by ******* **% ** so.
** **** ******, ** are *********** * *****, where *********, **** *** HD *****, ** ********* becoming **********.
Motion ***** ********* ***********
******* ********* ** ********* may ***** ********* ** enable ********** ********* ******* of ******-***** *********, ******* having ** ******** ***** storage ******.
******-**** ********* *** **** a **** *** ********* like ****** ****** **** can ** ******* ** fraudulent ******. ** * customer ******* ****** **** were ******* ** * store, ***** *** ** no ***** ******** (** the ***** ** *****, there *** **** **** no ********, *** **** nothing ** ******* * recording), * * *** image ****** *** ** ********** to ***** ** ******** did *** ***** ** claimed.
** *** ***** ****, some ***** **** ****** to ******** ***** **** at ***. *** *****, Zipstream **** ** *** a ***.
Avigilon **** ***** **** **********
**** ***** * ***** advantage ** ******** ****. Now, **** *** ***** the *** *** ********* feature **** ******** ***** (DFPS ** *** ***** equivalent ** ******** **** Scene ****) *** **** also *** **** ***** codec ******* ***** ******** has ****.
Hikvision *.***+ **********
***** *.***+ ****** ********* quickly ***** *** *** on **** *********, **** has *** **-****** **** with *** ******** ** DFPS. ** ******, ********* is * **** ******** so ** ** ***** paying ********* ** **** / ** ********* ******* suite.
Overall ****** ******
*** *** **** ****, since******* **** ******** *********, ** **** ******** that ***** ****** *** an ********* *****. *** addition ** **** ** an *********** *******, ****** not ** *********** ** the ******** *********, ** *** another **** ** ******** bandwidth *********** *** ******* competition ** ***** ***** advances ** **** ******.
****
Comments (23)
Ross Vander Klok
This is huge for us. Zipstream alone is huge for us, but as they refine it further it is truly going to be a game changer. Even though bandwidth is not an issue (as in we have plenty) our IT staff continues to push us to lower our usage.
Create New Topic
Undisclosed #1
Can't this already be done with Zipstream, albeit crudely, thru a VMSes speed up on motion mechanism?
Create New Topic
Undisclosed #1
So the green is without Zipstream and the black is with DFPS Zipstream?
Where's the same comparison from New Zip to Old Zip? Isn't that what we need to see to evaluate how much of an improvement there is?
I think that they are wringing out a damp sponge at this point.
Sure 50% sounds great, but as you say the savings are greatest when the activity is least. And since the dynamic GOP can already be set to drastically reduce those times to little more than the motion difference between the frames, I'm thinking that the savings might not be very much at all when you are already cranking the GOP up.
Is that a graph that they showed at one time with the old zip?
Create New Topic
Undisclosed Manufacturer #3
I would be interested to know if anyone has had any experience with Indigovision SMART.core in this regard? As I understand it Indigovision has done something in this area for a while.
Create New Topic
Undisclosed Manufacturer #4
DFPS is soundingly awfully like what Dedicated Micros used to call Multimode:
MultiMode Recording - Dynamically-switchable resolution, record-rate & compression (MPEG-4/H.264/JPEG) settings
Maybe Mike is going to return as a patent troll ?
A feature like this is quite suitable for in cam edge recording where there is little live monitoring and only event based after the fact viewing. Limited storage, limited life of storage, but still having a 24/7 chain of evidence and not requiring a centralised NVR.
Create New Topic
Brad Silvernail
This is a huge improvement. Now we need someway to predict the benefits when sizing storage. Most NVR storage calculators are way behind the camera / codec technology. This puts more emphasis on our "guess-timating" and accepting the risk if we undersize the storage. Any ideas or help?
Create New Topic
Undisclosed #1
Another possibly less risky and more beneficial approach to Axis version of dynamic frame rate would be to implement VMS based frame rate paring.
The way this would work would be that the camera would transmit at full rate always, along with its motion meta-data. The VMS would record at full rate.
After a suitable period of time has elapsed, (normally corresponding to the first order review time, 48 hours for instance), those streams with little motion would be retroactively reduced based on a similar algorithm to the one used by Axis.
This has the advantage of providing the full frame rate video during the time period when it's most likely to be needed. The overall storage reduction is nearly the same, adding only the extra storage for those 48 hours. Also an automatic mechanism could be added to prevent such reduction if the footage has ever been reviewed in that period.
Server side proceessing of the reduction could take place in the background, during the low utilization periods corresponding with high dynamic GOP.
One caveat, for this to work on h.264 efficiently and without decoding, svc-t encoding or its equivalent would have to be implemented at the camera. Hikvision and Dahua have this option on some lines today.
Create New Topic