<?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: The Myth of MPEG in Court</title>
	<atom:link href="http://spotonsecurity.com/2009/05/11/the-myth-of-mpeg-in-court/feed/" rel="self" type="application/rss+xml" />
	<link>http://spotonsecurity.com/2009/05/11/the-myth-of-mpeg-in-court/</link>
	<description>A closer look at the future of video surveillance</description>
	<lastBuildDate>Thu, 02 Feb 2012 08:07:52 +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/05/11/the-myth-of-mpeg-in-court/#comment-357</link>
		<dc:creator><![CDATA[Doug Marman]]></dc:creator>
		<pubDate>Fri, 02 Dec 2011 19:45:49 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=134#comment-357</guid>
		<description><![CDATA[LEvidpro, thanks for your comments. 

I think we should consider this a topic of open conversation, where everyone&#039;s input adds to the discussion and broadens our understanding of it.

I would love to hear more about how the FBI sees it. I&#039;ve talked to a few people from the FBI and some who work with them, but I&#039;ve never spoken to the actual decision makers within the FBI.

The explanations you gave are consistent with what I&#039;ve heard them say. I thought I explained that in my blog post, but I can see you you&#039;ve added the bit about predictive frames.

I agree that, from a theoretical and logical point of view, predictive frames do seem to offer an additional element that could make the video challengeable in court. However, this is where non-technical people get caught up in the details, seeing a nit on the bark of a tree, while missing the forest.

This, by the way, is quite common. In fact, a writer recently wrote about one of the big problems we have in government is that so few of our leaders really understand technology. What they end up relying on are simplified understandings that are often misleading if not used in the proper way.

This is exactly what we have here. The idea of predictive frames is causing the problem. Not the predictive frames themselves.

The concern is that lawyers could argue that what the video compression has done is altered what really happened. And indeed, lawyers will argue anything they can, if it could throw out evidence against their clients. But the point I&#039;ve tried to make is that the FBI is needlessly concerned about this technicality.

The idea that the video compression is altering what actually happened is technically true, but is unimportant. Why? Because the imperfections created are designed to be unnoticeable. 

We watch compressed Hi-Def BluRay movies, and the detail is incredible. It seems perfectly sharp, as if you were there. We don&#039;t notice all the fuzziness created during the compression, because it is designed to be fuzzy in areas that our perception doesn&#039;t notice.

If you wanted to take your argument about modification of what really happened, we could apply this to any form of reproduction. Take faxes, for example. They reduce the image down into dots. A great deal is lost in the process. Some copiers actually use character recognition to compress documents. Copying always alters what was really there.

Film based photographs rely on the grain of the film. If it is black and white, you lose all the color. If it is dark, the image can be quite grainy. Digital cameras have similar limitations. Moving objects can become blurred.

No representation is ever the same as the original. Something is always changed. The question is whether what is lost or modified is significant enough to distort what we can see. 

MPEG and H.264 compression is designed specifically to minimize visual distortion, while maximizing compression. It is by far the best solution.

If you take the FBI&#039;s approach, which is based on a misunderstanding of technology, then you end up with a much worse solution. Why? Because you will have a much more compromised version of reality using their approach.

We have limited storage space to record video. Lossless compression techniques take up so much more space and bandwidth that, in the real world, will force people to use far lower frame rates and far lower resolution images. Both are compromising the details that matter most. You will lose far more valuable and important visual information using that approach, than using forward and backward predictive frames.

If bandwidth were unlimited and free, and if storage was infinite and free, then, sure, why not use lossless compression? I agree. But the whole point of using MPEG and H.264 compression, is to maximize the visual information (including all the most important details) with minimal file sizes. Millions of hours of engineering effort have gone into optimizing the accuracy of the perceptible details.

This is why, when lawyers have tried to argue on the technicality that video compression can modify the image, it has been rejected in court. Judges have ruled on this. They aren&#039;t going to throw out real and valuable evidence if it is visually clear enough to recognize what happened, unless the defense can prove that important distortion or modification has actually occurred. The theory of modification is a technicality and not compelling enough to throw out valuable evidence.

But poor quality video is often thrown out, if it can&#039;t give you enough visual information to accurately determine the scene or the people involved.

Courts are much more concerned about tampering of video, than the compression artifacts introduced, and have urged manufacturers to use watermarks or other means to make it possible to verify if the video has been intentionally altered. However, even without watermark protection, video is still allowed as evidence, unless it can be shown that there is specific evidence for believing the video was tampered with.

The bottom line: The FBI&#039;s approach will lead to worse video evidence, not better. They are better off with higher resolution images and higher frame rates (up to 15 fps, more than that doesn&#039;t buy much), because it will give you far more visual information. They have every right to insist on watermarking of the video, to assure it has not been intentionally tampered with. But insisting on lossless compression is misguided.

Their argument might seem logical, but it is based on a technicality, which comes from having a too simplified understanding of technology. Without real understanding, logic can lead to bad conclusions.]]></description>
		<content:encoded><![CDATA[<p>LEvidpro, thanks for your comments. </p>
<p>I think we should consider this a topic of open conversation, where everyone&#8217;s input adds to the discussion and broadens our understanding of it.</p>
<p>I would love to hear more about how the FBI sees it. I&#8217;ve talked to a few people from the FBI and some who work with them, but I&#8217;ve never spoken to the actual decision makers within the FBI.</p>
<p>The explanations you gave are consistent with what I&#8217;ve heard them say. I thought I explained that in my blog post, but I can see you you&#8217;ve added the bit about predictive frames.</p>
<p>I agree that, from a theoretical and logical point of view, predictive frames do seem to offer an additional element that could make the video challengeable in court. However, this is where non-technical people get caught up in the details, seeing a nit on the bark of a tree, while missing the forest.</p>
<p>This, by the way, is quite common. In fact, a writer recently wrote about one of the big problems we have in government is that so few of our leaders really understand technology. What they end up relying on are simplified understandings that are often misleading if not used in the proper way.</p>
<p>This is exactly what we have here. The idea of predictive frames is causing the problem. Not the predictive frames themselves.</p>
<p>The concern is that lawyers could argue that what the video compression has done is altered what really happened. And indeed, lawyers will argue anything they can, if it could throw out evidence against their clients. But the point I&#8217;ve tried to make is that the FBI is needlessly concerned about this technicality.</p>
<p>The idea that the video compression is altering what actually happened is technically true, but is unimportant. Why? Because the imperfections created are designed to be unnoticeable. </p>
<p>We watch compressed Hi-Def BluRay movies, and the detail is incredible. It seems perfectly sharp, as if you were there. We don&#8217;t notice all the fuzziness created during the compression, because it is designed to be fuzzy in areas that our perception doesn&#8217;t notice.</p>
<p>If you wanted to take your argument about modification of what really happened, we could apply this to any form of reproduction. Take faxes, for example. They reduce the image down into dots. A great deal is lost in the process. Some copiers actually use character recognition to compress documents. Copying always alters what was really there.</p>
<p>Film based photographs rely on the grain of the film. If it is black and white, you lose all the color. If it is dark, the image can be quite grainy. Digital cameras have similar limitations. Moving objects can become blurred.</p>
<p>No representation is ever the same as the original. Something is always changed. The question is whether what is lost or modified is significant enough to distort what we can see. </p>
<p>MPEG and H.264 compression is designed specifically to minimize visual distortion, while maximizing compression. It is by far the best solution.</p>
<p>If you take the FBI&#8217;s approach, which is based on a misunderstanding of technology, then you end up with a much worse solution. Why? Because you will have a much more compromised version of reality using their approach.</p>
<p>We have limited storage space to record video. Lossless compression techniques take up so much more space and bandwidth that, in the real world, will force people to use far lower frame rates and far lower resolution images. Both are compromising the details that matter most. You will lose far more valuable and important visual information using that approach, than using forward and backward predictive frames.</p>
<p>If bandwidth were unlimited and free, and if storage was infinite and free, then, sure, why not use lossless compression? I agree. But the whole point of using MPEG and H.264 compression, is to maximize the visual information (including all the most important details) with minimal file sizes. Millions of hours of engineering effort have gone into optimizing the accuracy of the perceptible details.</p>
<p>This is why, when lawyers have tried to argue on the technicality that video compression can modify the image, it has been rejected in court. Judges have ruled on this. They aren&#8217;t going to throw out real and valuable evidence if it is visually clear enough to recognize what happened, unless the defense can prove that important distortion or modification has actually occurred. The theory of modification is a technicality and not compelling enough to throw out valuable evidence.</p>
<p>But poor quality video is often thrown out, if it can&#8217;t give you enough visual information to accurately determine the scene or the people involved.</p>
<p>Courts are much more concerned about tampering of video, than the compression artifacts introduced, and have urged manufacturers to use watermarks or other means to make it possible to verify if the video has been intentionally altered. However, even without watermark protection, video is still allowed as evidence, unless it can be shown that there is specific evidence for believing the video was tampered with.</p>
<p>The bottom line: The FBI&#8217;s approach will lead to worse video evidence, not better. They are better off with higher resolution images and higher frame rates (up to 15 fps, more than that doesn&#8217;t buy much), because it will give you far more visual information. They have every right to insist on watermarking of the video, to assure it has not been intentionally tampered with. But insisting on lossless compression is misguided.</p>
<p>Their argument might seem logical, but it is based on a technicality, which comes from having a too simplified understanding of technology. Without real understanding, logic can lead to bad conclusions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LEvidpro</title>
		<link>http://spotonsecurity.com/2009/05/11/the-myth-of-mpeg-in-court/#comment-356</link>
		<dc:creator><![CDATA[LEvidpro]]></dc:creator>
		<pubDate>Fri, 18 Nov 2011 17:52:21 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=134#comment-356</guid>
		<description><![CDATA[The FBI actually knows more than you on this one, and there is a good reason for their concern. You oversimplify an important point - capturing the changes between I frames. There are several different ways in which is this done, including B frames, P frames and a variety of methods to develop the contents of these frames. Forward and backward prediction, motion estimation, and blur are all artifacts of different types of compression, and there is no way to regulate the mathematical algorithms used by codecs to achieve the compression.
There are 2 main issues with this type of compression - one technical and one legal - and both are valid. 
First the technical: predictive algorithms are used to estimate and predict what P frames will be. For instance if a ball is moving from point A in one frame to point B another, there are ways to guess where that ball is going to be between point A and point B. P frames use this estimate to recreate the ball in the frames in between. This is not the same as capturing the changes from frame to frame - the data is not captured, but a formula that explains how to estimate where the changes should be are captured. Thus if that ball were to suddenly change course, the guess could be wrong and what is on the compressed video is not what actually happened. This also leads to a loss of definition and motion blur around the ball on playback. 
This leads to issue 2 - the legal repercussions. If a lawyer can show this to be possible (and there are many cases of such things happening, like a person&#039;s head appearing to detach from their body for a frame or two), it makes it very difficult to claim that everything on the video can be taken at face value. 
Not all compression is created equal. Some will have artifacts like this, some will not. But since there is no single standard that describes exactly the mathematical algorithms that must be used for every type of compression, it is safer from a law enforcement standpoint to make a blank call - no lossy compression.]]></description>
		<content:encoded><![CDATA[<p>The FBI actually knows more than you on this one, and there is a good reason for their concern. You oversimplify an important point &#8211; capturing the changes between I frames. There are several different ways in which is this done, including B frames, P frames and a variety of methods to develop the contents of these frames. Forward and backward prediction, motion estimation, and blur are all artifacts of different types of compression, and there is no way to regulate the mathematical algorithms used by codecs to achieve the compression.<br />
There are 2 main issues with this type of compression &#8211; one technical and one legal &#8211; and both are valid.<br />
First the technical: predictive algorithms are used to estimate and predict what P frames will be. For instance if a ball is moving from point A in one frame to point B another, there are ways to guess where that ball is going to be between point A and point B. P frames use this estimate to recreate the ball in the frames in between. This is not the same as capturing the changes from frame to frame &#8211; the data is not captured, but a formula that explains how to estimate where the changes should be are captured. Thus if that ball were to suddenly change course, the guess could be wrong and what is on the compressed video is not what actually happened. This also leads to a loss of definition and motion blur around the ball on playback.<br />
This leads to issue 2 &#8211; the legal repercussions. If a lawyer can show this to be possible (and there are many cases of such things happening, like a person&#8217;s head appearing to detach from their body for a frame or two), it makes it very difficult to claim that everything on the video can be taken at face value.<br />
Not all compression is created equal. Some will have artifacts like this, some will not. But since there is no single standard that describes exactly the mathematical algorithms that must be used for every type of compression, it is safer from a law enforcement standpoint to make a blank call &#8211; no lossy compression.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Illinois Court Records</title>
		<link>http://spotonsecurity.com/2009/05/11/the-myth-of-mpeg-in-court/#comment-350</link>
		<dc:creator><![CDATA[Illinois Court Records]]></dc:creator>
		<pubDate>Sat, 29 Oct 2011 04:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=134#comment-350</guid>
		<description><![CDATA[&lt;strong&gt;court records...&lt;/strong&gt;

[...]The Myth of MPEG in Court &#171; Spot On Security[...]...]]></description>
		<content:encoded><![CDATA[<p><strong>court records&#8230;</strong></p>
<p>[...]The Myth of MPEG in Court &laquo; Spot On Security[...]&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mpeg myths &#124; Keritesorszag</title>
		<link>http://spotonsecurity.com/2009/05/11/the-myth-of-mpeg-in-court/#comment-340</link>
		<dc:creator><![CDATA[Mpeg myths &#124; Keritesorszag]]></dc:creator>
		<pubDate>Mon, 01 Aug 2011 02:25:42 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=134#comment-340</guid>
		<description><![CDATA[[...] The Myth of MPEG in Court &#171; Spot On SecurityMay 11, 2009 &#8230; If you&#8217;ve been working with video over the last decade, you&#8217;ve probably heard the myth that MPEG type compression has been rejected by &#8230; [...]]]></description>
		<content:encoded><![CDATA[<p>[...] The Myth of MPEG in Court &#171; Spot On SecurityMay 11, 2009 &#8230; If you&#8217;ve been working with video over the last decade, you&#8217;ve probably heard the myth that MPEG type compression has been rejected by &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Clift</title>
		<link>http://spotonsecurity.com/2009/05/11/the-myth-of-mpeg-in-court/#comment-142</link>
		<dc:creator><![CDATA[Chris Clift]]></dc:creator>
		<pubDate>Fri, 07 Aug 2009 16:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=134#comment-142</guid>
		<description><![CDATA[A very interseting and insightful article. The comments after were also particularly useful in pointing to some of the background refernces for the information supplied in your blog. Finally a useful article that hopefully will go a long way to debunking the myths around MPEG.

kalagate now part of LGC Forensics]]></description>
		<content:encoded><![CDATA[<p>A very interseting and insightful article. The comments after were also particularly useful in pointing to some of the background refernces for the information supplied in your blog. Finally a useful article that hopefully will go a long way to debunking the myths around MPEG.</p>
<p>kalagate now part of LGC Forensics</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kas MPEG video on kohtus tõendusmaterjalina kasutatav &#171; Videovalve</title>
		<link>http://spotonsecurity.com/2009/05/11/the-myth-of-mpeg-in-court/#comment-98</link>
		<dc:creator><![CDATA[Kas MPEG video on kohtus tõendusmaterjalina kasutatav &#171; Videovalve]]></dc:creator>
		<pubDate>Fri, 26 Jun 2009 13:47:48 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=134#comment-98</guid>
		<description><![CDATA[[...] (võrreldes JPEG piltidega), võiks lisatud artikkel küll pisut murda. Vastava artikli leiab siit. Samas artiklis on juttu ka pildi pakkimisest ja selle edastamisest [...]]]></description>
		<content:encoded><![CDATA[<p>[...] (võrreldes JPEG piltidega), võiks lisatud artikkel küll pisut murda. Vastava artikli leiab siit. Samas artiklis on juttu ka pildi pakkimisest ja selle edastamisest [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Marman</title>
		<link>http://spotonsecurity.com/2009/05/11/the-myth-of-mpeg-in-court/#comment-91</link>
		<dc:creator><![CDATA[Doug Marman]]></dc:creator>
		<pubDate>Wed, 03 Jun 2009 22:06:04 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=134#comment-91</guid>
		<description><![CDATA[Bruce,

I&#039;m just getting a chance to respond.

Is what you are suggesting a part of the MPEG standard? We aren&#039;t familiar with this, but we&#039;d like to know more.

I agree that making the video encoding traceable to the encoder would be a nice addition to the watermarking that is commonly done.

I have seen some discussion that legal experts and law enforcement would prefer that the video not be altered and would rather see metadata that authenticated the video. Is what you are suggesting actually altering the video?

I&#039;m interested in hearing more.

Thanks.

Doug.]]></description>
		<content:encoded><![CDATA[<p>Bruce,</p>
<p>I&#8217;m just getting a chance to respond.</p>
<p>Is what you are suggesting a part of the MPEG standard? We aren&#8217;t familiar with this, but we&#8217;d like to know more.</p>
<p>I agree that making the video encoding traceable to the encoder would be a nice addition to the watermarking that is commonly done.</p>
<p>I have seen some discussion that legal experts and law enforcement would prefer that the video not be altered and would rather see metadata that authenticated the video. Is what you are suggesting actually altering the video?</p>
<p>I&#8217;m interested in hearing more.</p>
<p>Thanks.</p>
<p>Doug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://spotonsecurity.com/2009/05/11/the-myth-of-mpeg-in-court/#comment-90</link>
		<dc:creator><![CDATA[Bruce]]></dc:creator>
		<pubDate>Fri, 29 May 2009 11:26:44 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=134#comment-90</guid>
		<description><![CDATA[Doug,
It is possible to encode MPEG video such that it is provably untampered and traceable to the encoder.  Why isn&#039;t this done?]]></description>
		<content:encoded><![CDATA[<p>Doug,<br />
It is possible to encode MPEG video such that it is provably untampered and traceable to the encoder.  Why isn&#8217;t this done?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Marman</title>
		<link>http://spotonsecurity.com/2009/05/11/the-myth-of-mpeg-in-court/#comment-87</link>
		<dc:creator><![CDATA[Doug Marman]]></dc:creator>
		<pubDate>Fri, 22 May 2009 16:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=134#comment-87</guid>
		<description><![CDATA[Thanks, Sam.

By the way, here is a good link to Sam&#039;s blog at Security Systems News. He has some interesting added comments:

http://www.securitysystemsnews.com/blogs/?p=2218

Doug.]]></description>
		<content:encoded><![CDATA[<p>Thanks, Sam.</p>
<p>By the way, here is a good link to Sam&#8217;s blog at Security Systems News. He has some interesting added comments:</p>
<p><a href="http://www.securitysystemsnews.com/blogs/?p=2218" rel="nofollow">http://www.securitysystemsnews.com/blogs/?p=2218</a></p>
<p>Doug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: On the Editor&#8217;s Desk &#187; Doug Marman crushes compression questions</title>
		<link>http://spotonsecurity.com/2009/05/11/the-myth-of-mpeg-in-court/#comment-86</link>
		<dc:creator><![CDATA[On the Editor&#8217;s Desk &#187; Doug Marman crushes compression questions]]></dc:creator>
		<pubDate>Fri, 22 May 2009 14:04:26 +0000</pubDate>
		<guid isPermaLink="false">http://spotonsecurity.com/?p=134#comment-86</guid>
		<description><![CDATA[[...] I don&#8217;t always get to Doug Marman&#8217;s posts right away. Thus, I&#8217;m only now reading this very good treatise on the ridiculousness of court admissibility problems with compressed [...]]]></description>
		<content:encoded><![CDATA[<p>[...] I don&#8217;t always get to Doug Marman&#8217;s posts right away. Thus, I&#8217;m only now reading this very good treatise on the ridiculousness of court admissibility problems with compressed [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

