[MPlayer-dev-eng] [PATCH] multi-threaded lavc

[Reimar Döffinger]

Hi,

>>>The results are not bitwise identical to a single-threaded encode, but
>>
>>this is because the motion estimation normally uses the motion vector of the 
>>MB above the current one, but thats not possible if the top one happens to be 
>>handled by a different thread
> 
> So, theoreticaly the motion estimation is a little bit worse if
> multithreading is used ? I think this should be mentioned in the

I understood it that usually it takes the vector of the MB above as a 
starting point, thus speeding up the search. So I thought it should only 
be slower a bit. Is this right? or maybe a mixture of both is right ;-)

Greetings,
Reimar Döffinger