1 Oct 02:29
Re: A-V sync
Rich Felker <dalias <at> aerifal.cx>
2007-10-01 00:29:07 GMT
2007-10-01 00:29:07 GMT
On Sun, Sep 30, 2007 at 11:48:33PM +0200, pehache-tolai wrote: > Well, maybe you're right, but I'm not sure. My english is definitely not > perfect, but from the text below I would still vote for my interpretation: > > ---------------------------------------- > `-async samples_per_second' > Audio sync method. "Stretches/squeezes" the audio stream to match the > timestamps, the parameter is the maximum samples per second by which the > audio is changed. > ---------------------------------------- > > Changing the audio /by/ n samples per second means to me that 1 sec of audio > (48000 samples for instance) is resampled so as to last more or less than 1 > sec. (48000 +/- n samples), with n <= samples_per_second OK, here’s a technical explanation. In most formats, audio packets have timestamps, either explicitly or implicitly via a nominal samples-per-packet or samples-per-second header in the container. However, there’s also an actual number of samples stored in each packet, and this might or might not match the packet duration as determined by the timestamps. My understanding is that the -async option corrects this by adaptively resampling audio packets from whatever samplerate the packet actually has (computed from its start and end timestamp and number of samples contained in the frame) to the samplerate specified by the argument to -async. Rich _______________________________________________(Continue reading)
RSS Feed