From: Florian Schmidt Subject: Re: emu10k1 device naming Date: Sun, 25 Jul 2004 12:53:10 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <20040725125310.389c4ce5@mango.fruits.de> References: <1090729766.1952.7.camel@mindpipe> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1090729766.1952.7.camel@mindpipe> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Lee Revell Cc: alsa-devel , tiwai@suse.de, pzad@pobox.sk List-Id: alsa-devel@alsa-project.org On Sun, 25 Jul 2004 00:29:27 -0400 Lee Revell wrote: > Now that the emu10k1 driver supports low latency, multichannel capture, > it would be useful to rearrange the devices. Currently you have to use > hw:0,0 for playback, and hw:0,2 for capture. This works down to 32 > frames (you have to record more than 2 channels to get 32 frames, > because 512 bytes is the smallest period JACK supports). JACK requires > the playback and capture device to be the same for both directions. Actually jack supports period sizes smaller than 512 frames. I can easily start jackd with a period size of 64 frames. This is not a limitation of jackd but rather of your soundcard. > > The current hw:0,0 device could be moved to hw:0,2. This is the best > arrangement, because these are the only two devices that it makes sense > to use for full-duplex. The hw:0,2 playback device is a special AC3 > passthrough device, there is no capture device that corresponds to it. > The same applies to the current hw:0,0 (ADC capture) and hw:0,1 (mic > capture - 8000 Hz) devices, there is no corresponding playback device. > > It was suggsted to use the 'asym' PCM plugin for this, but JACK does not > support using a PCM as the device name, you need to give it a hardware > device. jackd also supports using non hw pcm devices. it should only spit out a warning to the user.. I just tried and besides some other weird behaviour it hardlocked my machine.. So this might be a bug that should be reported to the jack people.. But by design it should work.. One other thing that bothers me about jack is that it requires a ctl device by the same name as the used pcm device [which is only needed in the case of hw monitoring].. For people who don't need hw monitoring, this should not be required.. I'll write to jackit-devel about this [forwarding this mail :)].. Flo -- Palimm Palimm! http://affenbande.org/~tapas/ ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click