At Tue, 20 Aug 2002 12:30:11 +0200 (CEST), Tim Goetze wrote: > > Takashi Iwai wrote: > > >> How can we implement the latency-optimal behaviour with alsa-driver > >> framework? > >> Can we implement something like a snd_1ms_elapsed() routine (called from > >> USB-interrupt), which in turn triggers a waiting app with the available > >> period size (which would be 44 or 45 frames for 44100Hz)? > >> I would like to see this in ALSA / JACK. > >> What do you think? > > > >hmm, it's not so easy, since this will break also the assumption of > >constant period "frames" by applications. if we introduce the > >time-based period size, it won't work as compatible as older one, > >e.g. jack wouldn't run properly if the period size changes > >dynamically. > >hence, this should be handled in a special case. > > With the current setup and cycle code for mmap'd IO (like Jack for > example does it), is it possible to use these devices at all?
on 48kHz my usb speaker worked fine with 1ms or 2ms period size (not under high loads, though), since the frames per urb becomes integer in this case. on 44.1kHz xrun could happen. > What kind of hw/sw params, especially period size, should one set? the frequency aligned to 1000Hz. > Can one choose larger period sizes (45 frames/cycle is too tough for > a userspace process, at least on this box)? of course, depending on the kernel :) in theory, 1ms latency is enough possible. ciao, Takashi ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
