<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: &#8220;Storage in the Camera&#8221; versus &#8220;DVR in the Camera&#8221;</title>
	<atom:link href="http://spotonsecurity.com/2009/06/29/storage-in-the-camera-versus-dvr-in-the-camera/feed/" rel="self" type="application/rss+xml" />
	<link>http://spotonsecurity.com/2009/06/29/storage-in-the-camera-versus-dvr-in-the-camera/</link>
	<description>A closer look at the future of video surveillance</description>
	<lastBuildDate>Thu, 19 Apr 2012 09:01:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Doug Marman</title>
		<link>http://spotonsecurity.com/2009/06/29/storage-in-the-camera-versus-dvr-in-the-camera/#comment-129</link>
		<dc:creator><![CDATA[Doug Marman]]></dc:creator>
		<pubDate>Tue, 14 Jul 2009 04:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=148#comment-129</guid>
		<description><![CDATA[Steve,

I appreciate the note of good luck, but fortunately we have got a rapidly growing customer base who love our products.

I&#039;m not surprised that you haven&#039;t found it compelling, since we spent all of our time just discussing what it means to have the DVR built into the camera, and we never got to why it is so valuable.

Here are a few examples of why having analytics and a DVR in the camera are hot:

1. It makes the perfect solution for Remote Guarding, where you can provide better protection than on-site guards at 1/4th the cost. This is why over a dozen monitoring companies have adopted the iCVR. Saving significant money while providing significantly better protection than guards is generating a lot of interest.

2. Wireless networks are increasingly being used for city wide surveillance systems, or outdoor perimeters. The iCVR is a perfect fit, since it solves the bandwidth problem. You can get continuous recording and pro-active detection of potential security breaches, and put as many cameras on a wireless network as you want.

3. We increasingly see schools who want to add IP video systems, but don&#039;t want to add another network or expand their network to deal with the bandwidth. Since our storage is completely in the camera, they can add our iCVRs to their network without impacting the bandwidth. At the same time, they can use the analytics for detection, both outside and inside their buildings.

4. If you have a lot of sites that only need one or two cameras, there is no simpler solution, or less expensive IP cameras, than our iCVR. You just connect the cameras to the network with PoE and you&#039;re up and running.

These are just a few examples. There are lots more.

Thanks.

Doug.]]></description>
		<content:encoded><![CDATA[<p>Steve,</p>
<p>I appreciate the note of good luck, but fortunately we have got a rapidly growing customer base who love our products.</p>
<p>I&#8217;m not surprised that you haven&#8217;t found it compelling, since we spent all of our time just discussing what it means to have the DVR built into the camera, and we never got to why it is so valuable.</p>
<p>Here are a few examples of why having analytics and a DVR in the camera are hot:</p>
<p>1. It makes the perfect solution for Remote Guarding, where you can provide better protection than on-site guards at 1/4th the cost. This is why over a dozen monitoring companies have adopted the iCVR. Saving significant money while providing significantly better protection than guards is generating a lot of interest.</p>
<p>2. Wireless networks are increasingly being used for city wide surveillance systems, or outdoor perimeters. The iCVR is a perfect fit, since it solves the bandwidth problem. You can get continuous recording and pro-active detection of potential security breaches, and put as many cameras on a wireless network as you want.</p>
<p>3. We increasingly see schools who want to add IP video systems, but don&#8217;t want to add another network or expand their network to deal with the bandwidth. Since our storage is completely in the camera, they can add our iCVRs to their network without impacting the bandwidth. At the same time, they can use the analytics for detection, both outside and inside their buildings.</p>
<p>4. If you have a lot of sites that only need one or two cameras, there is no simpler solution, or less expensive IP cameras, than our iCVR. You just connect the cameras to the network with PoE and you&#8217;re up and running.</p>
<p>These are just a few examples. There are lots more.</p>
<p>Thanks.</p>
<p>Doug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Smith</title>
		<link>http://spotonsecurity.com/2009/06/29/storage-in-the-camera-versus-dvr-in-the-camera/#comment-128</link>
		<dc:creator><![CDATA[Steve Smith]]></dc:creator>
		<pubDate>Tue, 14 Jul 2009 03:26:23 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=148#comment-128</guid>
		<description><![CDATA[hmmm I think your 3-day continuous recording in D1 is not a very compelling story...sorry.  Well not for us anyway.  D1 resolution in h.264 is not really a differentiator.  Anyway - good luck - i think u r going to need it!]]></description>
		<content:encoded><![CDATA[<p>hmmm I think your 3-day continuous recording in D1 is not a very compelling story&#8230;sorry.  Well not for us anyway.  D1 resolution in h.264 is not really a differentiator.  Anyway &#8211; good luck &#8211; i think u r going to need it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Marman</title>
		<link>http://spotonsecurity.com/2009/06/29/storage-in-the-camera-versus-dvr-in-the-camera/#comment-127</link>
		<dc:creator><![CDATA[Doug Marman]]></dc:creator>
		<pubDate>Mon, 13 Jul 2009 17:05:24 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=148#comment-127</guid>
		<description><![CDATA[Steve,

As you now see, yes, our camera is currently a standard resolution camera, and our encoders work with standard resolution analog cameras.

I don&#039;t know how you could say that what I wrote was misleading. I thought it was fairly clear when I said &quot;... using Mobotix’s MxPEG compression&quot; that I was talking about Mobotix cameras, not our own cameras. After all, MxPEG compression is proprietary to Mobotix. No other company uses it. We use H.264 compression. My point was simply to show that by my estimate you would need about 900 GB to have 30 days of continuous storage for the Mobotix camera, because that is what it would take to have full DVR functionality in their camera. I can see now, looking back, that you said 2 TB will give over 60 days of continuous storage, which means that 1 TB would cover 30 days, so this is exactly in line with my point. There was nothing misleading here.

I agree with you that comparing the Mobotix camera with our iCVR is like comparing apples with oranges. Mobotix has a megapixel camera. Our iCVR is a camera with video analytics and a full DVR built-in. They are indeed two different animals.

I&#039;ve never tried to compare the two products or to pit the two against each other. In fact, this is exactly why in my first response to you I said that we were talking about two different things. But you told me that I was wrong. 

As I&#039;ve been saying from the beginning, my point has been about what people mean by &quot;storage in the camera&quot; or &quot;DVR in the camera&quot;. The terms are being confused, but they should mean two very different things: Using a flash memory card in the camera works if you only need to capture event type recording, but if you need continuous recording, then you still need external storage. However, if you have a complete DVR in the camera, then you don&#039;t need external storage.

I&#039;m hoping you can now see what I&#039;ve been talking about.

Unfortunately, it still seems as if you are missing what this means. You wrote:

&quot;To make it a fair comparison, as the iCVR cannot record in 1.3 megapixel, but only D1 - if the MOBOTIX camera was recording at D1 resolution @ 6fps, triggering and recording 200 events, you would get 30 days recording on 16GB microSD card.&quot;

But this isn&#039;t a fair comparison, as I&#039;ve said from the beginning, because the Mobotix camera is still limited to event recording on the SD card, while our iCVR can record continuously for more than 30 days with the built-in hard drive. That&#039;s the whole point. Not just event recording, but full continuous video recording.

Here&#039;s a fair comparison, using your example. If the Mobotix camera was only D1 resolution, and you wanted it to be able to continuously record for 30 days at 5 frames per second, my estimates are that you would need about 230 GB worth of storage. It will be many years before you can find an SD flash memory card that large. Obviously, using H.264 compression gives us a big advantage for storage in the camera.

But the whole point of my post was not to compare the Mobotix camera with our iCVR, since they are indeed two different animals, each appropriate for different applications. My point was simply to show what it really means to have enough storage in the camera that you don&#039;t need external storage, and that this is what we mean when we say we have a DVR in our camera.

Thanks.

Doug.]]></description>
		<content:encoded><![CDATA[<p>Steve,</p>
<p>As you now see, yes, our camera is currently a standard resolution camera, and our encoders work with standard resolution analog cameras.</p>
<p>I don&#8217;t know how you could say that what I wrote was misleading. I thought it was fairly clear when I said &#8220;&#8230; using Mobotix’s MxPEG compression&#8221; that I was talking about Mobotix cameras, not our own cameras. After all, MxPEG compression is proprietary to Mobotix. No other company uses it. We use H.264 compression. My point was simply to show that by my estimate you would need about 900 GB to have 30 days of continuous storage for the Mobotix camera, because that is what it would take to have full DVR functionality in their camera. I can see now, looking back, that you said 2 TB will give over 60 days of continuous storage, which means that 1 TB would cover 30 days, so this is exactly in line with my point. There was nothing misleading here.</p>
<p>I agree with you that comparing the Mobotix camera with our iCVR is like comparing apples with oranges. Mobotix has a megapixel camera. Our iCVR is a camera with video analytics and a full DVR built-in. They are indeed two different animals.</p>
<p>I&#8217;ve never tried to compare the two products or to pit the two against each other. In fact, this is exactly why in my first response to you I said that we were talking about two different things. But you told me that I was wrong. </p>
<p>As I&#8217;ve been saying from the beginning, my point has been about what people mean by &#8220;storage in the camera&#8221; or &#8220;DVR in the camera&#8221;. The terms are being confused, but they should mean two very different things: Using a flash memory card in the camera works if you only need to capture event type recording, but if you need continuous recording, then you still need external storage. However, if you have a complete DVR in the camera, then you don&#8217;t need external storage.</p>
<p>I&#8217;m hoping you can now see what I&#8217;ve been talking about.</p>
<p>Unfortunately, it still seems as if you are missing what this means. You wrote:</p>
<p>&#8220;To make it a fair comparison, as the iCVR cannot record in 1.3 megapixel, but only D1 &#8211; if the MOBOTIX camera was recording at D1 resolution @ 6fps, triggering and recording 200 events, you would get 30 days recording on 16GB microSD card.&#8221;</p>
<p>But this isn&#8217;t a fair comparison, as I&#8217;ve said from the beginning, because the Mobotix camera is still limited to event recording on the SD card, while our iCVR can record continuously for more than 30 days with the built-in hard drive. That&#8217;s the whole point. Not just event recording, but full continuous video recording.</p>
<p>Here&#8217;s a fair comparison, using your example. If the Mobotix camera was only D1 resolution, and you wanted it to be able to continuously record for 30 days at 5 frames per second, my estimates are that you would need about 230 GB worth of storage. It will be many years before you can find an SD flash memory card that large. Obviously, using H.264 compression gives us a big advantage for storage in the camera.</p>
<p>But the whole point of my post was not to compare the Mobotix camera with our iCVR, since they are indeed two different animals, each appropriate for different applications. My point was simply to show what it really means to have enough storage in the camera that you don&#8217;t need external storage, and that this is what we mean when we say we have a DVR in our camera.</p>
<p>Thanks.</p>
<p>Doug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Smith</title>
		<link>http://spotonsecurity.com/2009/06/29/storage-in-the-camera-versus-dvr-in-the-camera/#comment-126</link>
		<dc:creator><![CDATA[Steve Smith]]></dc:creator>
		<pubDate>Sun, 12 Jul 2009 21:24:11 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=148#comment-126</guid>
		<description><![CDATA[...That&#039;s 200 events PER DAY by the way!]]></description>
		<content:encoded><![CDATA[<p>&#8230;That&#8217;s 200 events PER DAY by the way!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Smith</title>
		<link>http://spotonsecurity.com/2009/06/29/storage-in-the-camera-versus-dvr-in-the-camera/#comment-125</link>
		<dc:creator><![CDATA[Steve Smith]]></dc:creator>
		<pubDate>Sun, 12 Jul 2009 21:22:34 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=148#comment-125</guid>
		<description><![CDATA[It&#039;s interesting and correct me if I am wrong, but reading your iCVR datasheet... http://www.videoiq.com/uploads/datasheets/VideoIQ_iCVR_CameraEncoder5-9-09.pdf ..It appears that your  iCVR camera is only capable of recording in D1 (704 X 480 pixels) resolution -so it appears your  iCVR cameras cannot stream or record in megapixel resolution.  

Therefore your figures are somewhat misleading! Firstly I am fully aware of of your camera&#039;s &#039;buffering&#039; to 1GB and then archiving to HDD.  BUT you said (quote) &quot;... using Mobotix’s MxPEG compression, my estimates suggest that you would need almost 900 GB to record 30 days worth, even at only 1.3 megapixel at 5 frames per second.&quot;

But you are not comparing &#039;apples with apples&#039;. How can you even talk about megapixel when your own iCVR camera is not even capable of delivering megapixel.  To make it a fair comparison, as the iCVR cannot record in 1.3 megapixel, but only D1 - if the MOBOTIX camera was recording at D1 resolution @ 6fps, triggering and recording 200 events, you would get 30 days recording on 16GB microSD card.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s interesting and correct me if I am wrong, but reading your iCVR datasheet&#8230; <a href="http://www.videoiq.com/uploads/datasheets/VideoIQ_iCVR_CameraEncoder5-9-09.pdf" rel="nofollow">http://www.videoiq.com/uploads/datasheets/VideoIQ_iCVR_CameraEncoder5-9-09.pdf</a> ..It appears that your  iCVR camera is only capable of recording in D1 (704 X 480 pixels) resolution -so it appears your  iCVR cameras cannot stream or record in megapixel resolution.  </p>
<p>Therefore your figures are somewhat misleading! Firstly I am fully aware of of your camera&#8217;s &#8216;buffering&#8217; to 1GB and then archiving to HDD.  BUT you said (quote) &#8220;&#8230; using Mobotix’s MxPEG compression, my estimates suggest that you would need almost 900 GB to record 30 days worth, even at only 1.3 megapixel at 5 frames per second.&#8221;</p>
<p>But you are not comparing &#8216;apples with apples&#8217;. How can you even talk about megapixel when your own iCVR camera is not even capable of delivering megapixel.  To make it a fair comparison, as the iCVR cannot record in 1.3 megapixel, but only D1 &#8211; if the MOBOTIX camera was recording at D1 resolution @ 6fps, triggering and recording 200 events, you would get 30 days recording on 16GB microSD card.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Smith</title>
		<link>http://spotonsecurity.com/2009/06/29/storage-in-the-camera-versus-dvr-in-the-camera/#comment-124</link>
		<dc:creator><![CDATA[Steve Smith]]></dc:creator>
		<pubDate>Sat, 11 Jul 2009 23:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=148#comment-124</guid>
		<description><![CDATA[Before I respond, to you statement &quot;Every 4-5 hours the hard drive wakes up and stores the video from the buffer&quot;....question - what is the maximum resolution of your camera?]]></description>
		<content:encoded><![CDATA[<p>Before I respond, to you statement &#8220;Every 4-5 hours the hard drive wakes up and stores the video from the buffer&#8221;&#8230;.question &#8211; what is the maximum resolution of your camera?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Marman</title>
		<link>http://spotonsecurity.com/2009/06/29/storage-in-the-camera-versus-dvr-in-the-camera/#comment-123</link>
		<dc:creator><![CDATA[Doug Marman]]></dc:creator>
		<pubDate>Sat, 11 Jul 2009 21:08:55 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=148#comment-123</guid>
		<description><![CDATA[Why do you think we are constantly writing to the hard drive?

It sounds as if you aren&#039;t familiar with our product or how it works.

We&#039;ve solved the hard drive failure problem by using 1 GB of solid state memory as a buffer. So, the hard drive is asleep about 96 percent of the time. Every 4-5 hours the hard drive wakes up and stores the video from the buffer. Then the hard drive goes back to sleep.

This extends the life expectancy of the hard drive by a factor of ten.

The notebook class hard drives, by the way, are more ruggedized that desktop drives. They are also quieter and use less power. 2.5&quot; drives are now regularly being used in server farms, to help reduce current and increase storage density. Hitachi was also one of the first to solve the on/off cycle problem with the 2.5&quot; drive, by parking the head when it is off. That&#039;s because laptops need to put up with much more abuse than desktop drives, so they are built better to handle that.

It&#039;s actually perfect for our application.

Doug.]]></description>
		<content:encoded><![CDATA[<p>Why do you think we are constantly writing to the hard drive?</p>
<p>It sounds as if you aren&#8217;t familiar with our product or how it works.</p>
<p>We&#8217;ve solved the hard drive failure problem by using 1 GB of solid state memory as a buffer. So, the hard drive is asleep about 96 percent of the time. Every 4-5 hours the hard drive wakes up and stores the video from the buffer. Then the hard drive goes back to sleep.</p>
<p>This extends the life expectancy of the hard drive by a factor of ten.</p>
<p>The notebook class hard drives, by the way, are more ruggedized that desktop drives. They are also quieter and use less power. 2.5&#8243; drives are now regularly being used in server farms, to help reduce current and increase storage density. Hitachi was also one of the first to solve the on/off cycle problem with the 2.5&#8243; drive, by parking the head when it is off. That&#8217;s because laptops need to put up with much more abuse than desktop drives, so they are built better to handle that.</p>
<p>It&#8217;s actually perfect for our application.</p>
<p>Doug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Smith</title>
		<link>http://spotonsecurity.com/2009/06/29/storage-in-the-camera-versus-dvr-in-the-camera/#comment-122</link>
		<dc:creator><![CDATA[Steve Smith]]></dc:creator>
		<pubDate>Sat, 11 Jul 2009 20:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=148#comment-122</guid>
		<description><![CDATA[It&#039;s a worry that you are using the Travelstar series - these are in the desktop (notebook) class, not design for constant writing applications and thus not robust.  I would never specify these for a surveillance application.  For constant writing, with VideoIQ seems to feel is an industry standard and a requirement, you should be using Enterprise-class HDDs, Hitachi do offer these also in their range.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s a worry that you are using the Travelstar series &#8211; these are in the desktop (notebook) class, not design for constant writing applications and thus not robust.  I would never specify these for a surveillance application.  For constant writing, with VideoIQ seems to feel is an industry standard and a requirement, you should be using Enterprise-class HDDs, Hitachi do offer these also in their range.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Marman</title>
		<link>http://spotonsecurity.com/2009/06/29/storage-in-the-camera-versus-dvr-in-the-camera/#comment-120</link>
		<dc:creator><![CDATA[Doug Marman]]></dc:creator>
		<pubDate>Sat, 11 Jul 2009 01:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=148#comment-120</guid>
		<description><![CDATA[I believe we are currently using the Travelstar 5K series.

Why do you ask?]]></description>
		<content:encoded><![CDATA[<p>I believe we are currently using the Travelstar 5K series.</p>
<p>Why do you ask?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Smith</title>
		<link>http://spotonsecurity.com/2009/06/29/storage-in-the-camera-versus-dvr-in-the-camera/#comment-119</link>
		<dc:creator><![CDATA[Steve Smith]]></dc:creator>
		<pubDate>Sat, 11 Jul 2009 00:54:04 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=148#comment-119</guid>
		<description><![CDATA[that&#039;s ok, give us the models here is the Hitachi HDD url http://www.hitachigst.com]]></description>
		<content:encoded><![CDATA[<p>that&#8217;s ok, give us the models here is the Hitachi HDD url <a href="http://www.hitachigst.com" rel="nofollow">http://www.hitachigst.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

