Arpi: we need to discuss MPlayer's A/V sync

Albeu said that MPlayer needs timestamp for every audio frame and that 
it cannot just decode those frames and use the duration given by the 
decoder for sync.

So, how exactly does this thing work? How does it handle most current 
containers (AVI, Ogg) that usually contain audio frames without timecodes?

Adding timecode (or even time offset) for every frame makes overhead 
significantly bigger.

Would it be possible to just handle frames of a single Block as one big 
frame, when doing sync? This way you wouldn't need to quess timecodes 
for frames which don't already have one.

In case you are not familiar with MCF, Block is an element that contains 
timecode and data. With audio it normally contains several frames and 
then you only have timecode for the first one. Of course a Block only 
contains audio for around 50 ms, so there is no trouble with seek 
accuracy nor sync drift.

- Tronic -