Re: Antworten: [Openvortex-dev] Desync in mplayer

[Stanislav Kogan]

Hi.

The sync problem is there in every program. It's just that in video
players one can actually notice it. But, for example, in xmms the first
300ms of audio gets simply chopped off. Also, when recording, the first
300ms are from the previous recording.

I've looked into the code,  and at 44100Hz 370ms translates into 64kb,
which is exactly the maximum size of the PCM buffer in the driver. Makes
one think, eh? :)


On Fri, 06 Jun 2003 19:53:36 -0500
"Callum Lerwick" <address@hidden> wrote:

> >>The cvs on aureal.sf.net seems to be untouched for at
> >>least 20 months. Openvortex is the most advanced oss
> >>drivers isn't it ?
> >>
> >>I forgot to tell I'm using a gentoo with a recent
> >>kernel, and Aureal Binary Drivers don't work with it.
> > 
> > 
> > The only real difference between the drivers are Makefile changes.
> > What is the problem with the binary drivers? Also, why not use the
> > alsa drivers?
> 
> The tui driver worked well for me for quite some time. Its
> disassembled so it doesn't have the GCC version mismatch problems.
> That can be fixed with strip anyway...
> 
> But yeah, the ALSA drivers seem to be mostly usable now on all cards. 
> You really should try it out and help test it. :)
> 
> Also, the ALSA drivers are off in Xine/gxine as well, by the same
> amount using native ALSA or OSS emulation. Setting gxine to an A/V
> sync offset of about -30000 (samples? usec? It doesn't say) gets it
> right on.
> 
> 
> 
> _______________________________________________
> Openvortex-dev mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/openvortex-dev


-- 

Stanislav Kogan
<*>
eMail: address@hidden