[Alsa-user] Audigy2 ZS PCMCIA - no mic?
Hi, I have Audigy2 ZS PCMCIA card. I use emu10k1 driver from gentoo alsa-driver-1.0.13_rc2. I can play sound but I have problems with capture. I turned all things in mixer to 100% level and I can't record anything. In Windows it works ok. How get mic/linein working? Thanks in advance, -- Marcin Lewandowski - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] strange period size behaviour
Sergei Steshenko wrote: > Tomas Carnecky <[EMAIL PROTECTED]> wrote: > > Clemens Ladisch wrote: > > > Your application must be able to handle any period size. > > > > > > Why does the period size matter at all? > > > > My app can handle that now, but the way how I had to do it defeats the > > 'zero-copy' paradigm. > > > > The situation is this: the application requests a 16kb buffer, at 2 > > channels / U16LE this makes a 4096 frames. It's a streaming buffer and > > the app writes in the data in chunks of 4096 bytes. I can't map the alsa > > mmap'ed buffer to the application (because of the different size) so I > > have to create my own temporary buffer and then copy the data to the > > mmap'ed buffer. > > I might be wrong, but it seems that 4096 bytes limit comes from these > facts: > > 1) on Linux page size is 4096 bytes; (depends on the architecture) > 2) if one allocate more than 4096 bytes, the system cannot guarantee the > pages are contiguous; One can try, but the system doesn't guarantee that it succeeds. > 3) ALSA uses DMA whenever the card supports it; Almost all cards actually _require_ DMA. > 4) DMA needs contiguous buffer, so we are back to one page 4096 bytes > buffer. ALSA's buffer is continuous (when needed). If ALSA isn't able to allocate it, setting the hardware parameters fails. HTH Clemens - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] strange period size behaviour
On Thu, 2006-09-21 at 08:55 +0200, Tomas Carnecky wrote: > 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 application expects. For now I simply made the > buffer slightly bigger (18kb) and 'force' the application to use all of > it, but I hear periodic artifacts and I think it has something to do > with the buffer size since the pauses between them increase > proportionally with the buffer size. Well, you won't ever get true "zero-copy" with this device, because the hardware only supports S32_LE - software format conversion will be required. Lee - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] strange period size behaviour
On Thu, Sep 21, 2006 at 02:09:30PM +0200, Tomas Carnecky wrote: > If we're at it, can I snd_pcm_mmap_begin()/commit() more than 4096 > bytes? It seems as at it's possible since wine's alsa driver does that > on the whole buffer, which can be more than 4096 bytes. Certainly it can. My soundcard has 10 input channels. With a period size of 1024 and 32 bit sample format that makes 40960 bytes. > Does the alsa driver allocate DMA memory in that case? No idea. -- FA Lascia la spina, cogli la rosa. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] strange period size behaviour
On Thu, 21 Sep 2006 14:09:30 +0200 Tomas Carnecky <[EMAIL PROTECTED]> wrote: > 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 needs contiguous buffer, so we are back to one page 4096 bytes > > buffer. > > It's a windows application running through wine. This app uses dsound > and I configured wine to use the alsa driver. > > If we're at it, can I snd_pcm_mmap_begin()/commit() more than 4096 > bytes? It seems as at it's possible since wine's alsa driver does that > on the whole buffer, which can be more than 4096 bytes. Does the alsa > driver allocate DMA memory in that case? > > tom > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user > I am not an ALSA developer, so I do not know. --Sergei. -- Visit my http://appsfromscratch.berlios.de/ open source project. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] strange period size behaviour
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 needs contiguous buffer, so we are back to one page 4096 bytes > buffer. It's a windows application running through wine. This app uses dsound and I configured wine to use the alsa driver. If we're at it, can I snd_pcm_mmap_begin()/commit() more than 4096 bytes? It seems as at it's possible since wine's alsa driver does that on the whole buffer, which can be more than 4096 bytes. Does the alsa driver allocate DMA memory in that case? tom - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] strange period size behaviour
On Thu, 21 Sep 2006 12:16:25 +0200 Tomas Carnecky <[EMAIL PROTECTED]> wrote: > 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, but the way how I had to do it defeats the > 'zero-copy' paradigm. > > The situation is this: the application requests a 16kb buffer, at 2 > channels / U16LE this makes a 4096 frames. It's a streaming buffer and > the app writes in the data in chunks of 4096 bytes. I can't map the alsa > mmap'ed buffer to the application (because of the different size) so I > have to create my own temporary buffer and then copy the data to the > mmap'ed buffer. > > tom > > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user > 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 needs contiguous buffer, so we are back to one page 4096 bytes buffer. --Sergei. -- Visit my http://appsfromscratch.berlios.de/ open source project. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] strange period size behaviour
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, but the way how I had to do it defeats the 'zero-copy' paradigm. The situation is this: the application requests a 16kb buffer, at 2 channels / U16LE this makes a 4096 frames. It's a streaming buffer and the app writes in the data in chunks of 4096 bytes. I can't map the alsa mmap'ed buffer to the application (because of the different size) so I have to create my own temporary buffer and then copy the data to the mmap'ed buffer. tom - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] strange period size behaviour
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? Regards, Clemens - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
