Re: [Alsa-user] strange period size behaviour

2006-09-21 Thread Tomas Carnecky
Lee Revell wrote: You are mixing up period_time (which is in microseconds) with period_size (which is in frames). period_time defaults to 125000. Why do you want to use an .asoundrc at all? I want to set period size or time to a value so that the buffer is 16kb - because that's what the

Re: [Alsa-user] strange period size behaviour

2006-09-21 Thread Tomas Carnecky
Clemens Ladisch wrote: Tomas Carnecky wrote: The thing is, in my application I can't set period time to anything else than 21333 and that is, well, kinda bad. Your application must be able to handle any period size. Why does the period size matter at all? My app can handle that now

Re: [Alsa-user] strange period size behaviour

2006-09-21 Thread Tomas Carnecky
Sergei Steshenko wrote: I might be wrong, but it seems that 4096 bytes limit comes from these facts: 1) on Linux page size is 4096 bytes; 2) if one allocate more than 4096 bytes, the system cannot guarantee the pages are contiguous; 3) ALSA uses DMA whenever the card supports it; 4) DMA

Re: [Alsa-user] make alsa-lib/alsa-oss multilib-friendly

2006-02-05 Thread Tomas Carnecky
Lee Revell wrote: On Sun, 2006-02-05 at 17:21 +, Tomas Carnecky wrote: It's a real pain to compile those two packages for 32bit in a 64bit environment. I needed to recompile both packages because they'd break TeamSpeak (http://gentoo-wiki.com/HOWTO_ALSA_and_TeamSpeak_on_amd64) and I can't

Re: [Alsa-user] make alsa-lib/alsa-oss multilib-friendly

2006-02-05 Thread Tomas Carnecky
Lee Revell wrote: mplayer, many codecs are not available for free, mplayer uses windows dlls to decode such streams, and many people use a 32bit version of mplayer because there aren't any 64bit libs for windows codecs.. Please file an ALSA bug report/feature request and describe what you