From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Problem with RME 9632 and Plug Date: Wed, 04 Aug 2004 11:44:40 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <200408040018.i740ITg5017942@localhost.localdomain> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Jaroslav Kysela Cc: Paul Davis , Ed Wildgoose , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Wed, 4 Aug 2004 09:39:08 +0200 (CEST), Jaroslav wrote: > > On Tue, 3 Aug 2004, Paul Davis wrote: > > > >However, quick question. Is it possible to create a virtual device > > >which will effectively change the default for period size if the app > > >doesn't specifically ask for something different (some asound.conf > > >magic?). > > > > as i mentioned, try using the pcm device name "plughw:N" where N > > appropriate. > > It won't help. We don't convert count of periods in the plug plugin. > The only one solution is that the application will start using > an external timing source for PCM (see set/get_tick_time functions) > - or another timer available for applications - in this case when > hardware has this constraint. Hmm, basically RME h/w can generate enough fine interrupts with a small period size, but it can handle only two periods. If we have an intermediate buffer, any number of periods must be able to handle (only when the given period size or size/N is supported by hw)... Takashi ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com