Re: [Bluez-devel] yes, a2dp timing is whacked

[Marcel Holtmann <marcel@holtmann.org>]

Hi Henryk,

> > So the best thing is too encode two or three full AVDTP frames in
> > advance and have them ready to send. The sending can't be controlled
> > be usleep(). We need a time that kicks in every whatever msec and
> > makes us to transmit the next frame.
> 
> That's what I would favour. According to the libc manual setitimer()
> would be the function of choice, if nobody else has a better idea (RTC,
> anyone?).

so in general the time that a SBC frame is calculated for, is always the
same if we don't change the parameters, right?

Using the ITIMER_REAL domain may works and since you can setup your
timer in microseconds, then this would be the way to go.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel