|
![](/i/fill.gif) |
Invisible wrote:
> On 25/01/2011 06:28 PM, Darren New wrote:
>> Invisible wrote:
>>> OK, so you can change the frequency weightings and how often a
>>> keyframe is put in, and so forth. I'm not seeing much that
>>> fundamentally changes the whole algorithm such that it might require
>>> less computer power.
>>
>> Making every frame a keyframe reduces the computing and memory you need.
>
> Presumably the bitrate is going to skyrocket if you do that though.
Yes. Or the quality sucks ass.
>> Not doing motion prediction reduces how much compute power you need.
>
> Does the standard actually allow that?
I would think so. All you have to do is say you didn't find any motion. Or
perhaps only look for identical pixels at the identical place (i.e., motion
prediction of zero velocity).
--
Darren New, San Diego CA, USA (PST)
"How did he die?" "He got shot in the hand."
"That was fatal?"
"He was holding a live grenade at the time."
Post a reply to this message
|
![](/i/fill.gif) |