From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ed Wildgoose Subject: Re: Problem with RME 9632 and Plug Date: Wed, 04 Aug 2004 11:30:56 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <4110BAE0.6070309@wildgooses.com> References: <200408040018.i740ITg5017942@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Takashi Iwai , Paul Davis , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org Jaroslav Kysela wrote: >On Wed, 4 Aug 2004, Takashi Iwai wrote: > > > >>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)... >> >> > >The situation is not quite clear for this hardware like for CS46xx etc., >because it has already the big ring buffer with max period size - 8192 >frames. So only another timing source is enough. > > Ahh, yes, I see now. The max period size SHOULD be 8192. For some reason when I request anything larger than 2048, I only get 2048... I have tried asking for exactly 8192, and "_near" 8192 with the same results. I will try giving the machine a reboot in case something has grabbed the card and it's ended up in a funny state which might be causing this. However, I can currently happily choose 512, 1024, and 2048 period sizes, but nothing larger. Ed W ------------------------------------------------------- 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