<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 11/17/2011 20:07, Mitchell Gore wrote:
<blockquote
cite="mid:CAGspLbEKFykKrWPkMtc0CNU2Z5g5im6FJCyF0FYhwGw4YoUkPg@mail.gmail.com"
type="cite">That depends. Are you talking about analog RTJPEG
recordings? MPEG2?<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
MPEG4? H264? Or are these digital MPEG2 recordings? or H264?
At what<br>
bitrate?<br>
</blockquote>
</div>
MPEG2 off OTA and QAM.<br>
</blockquote>
<br>
The commflagger is multithreaded, and runs at one quarter
resolution. With MPEG2, there is an optimized decode path that runs
at low quality and high speed. On a modern dual core processor, you
should be running HD MPEG2 commflags at several times realtime. A
test of a 12.5Mbps 1080i recording from CBS just ran on my 3.3GHz
dual core at 310fps.<br>
</body>
</html>