From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: A suggestion for better resamplers in alsa. Date: Mon, 04 Apr 2005 18:10:53 +0200 Message-ID: References: Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Clemens Ladisch Cc: James Courtier-Dutton , alsa-devel List-Id: alsa-devel@alsa-project.org At Mon, 4 Apr 2005 17:49:27 +0200 (METDST), Clemens Ladisch wrote: > > Takashi Iwai wrote: > > ... > > IMO, the only "perfect" solution is to change API to allow variable > > period sizes. Otherwise the size mismatch always occurs regardless > > what trick you apply. > > This is yet another case of a constant-period-size device, like USB or > ymfpci. > > > However, the variable period size would introduce the significant > > changes to the core part. > > Maybe we could generalize what usb-usx2y's hwdep does. > > > For example, currently the hw/appl pointers are accumulated until > > the boundary near to INT_MAX. The real DMA buffer position in the > > ringbuffer is calculated as 'hwptr % buffer_size'. With the > > variable period size, it's no longer true. > > But buffer_size would remain constant, wouldn't it? I don't think so (in the above, I suppose the input-hwptr on rate plugin, not the output-hwptr on the real hardware). Takashi ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click