From: Allan Klinbail Subject: Re: latency with mtpav Date: 25 Jun 2003 22:09:57 +1000 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <1056542997.15801.52.camel@littlewolf2.littlewolf> References: <1056373664.15797.11.camel@littlewolf2.littlewolf> <20030623103932.312a1891.rpav@nwlink.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20030623103932.312a1891.rpav@nwlink.com> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Ryan Pavlik Cc: Alsa-dev List-Id: alsa-devel@alsa-project.org On Tue, 2003-06-24 at 03:39, Ryan Pavlik wrote: > On 23 Jun 2003 23:07:44 +1000 > Allan Klinbail wrote: > > > > In trying to test various applications with sync I have observed some > > serious latency problems with the mtpav driver. > > > > Using ardour I found some serious latency when starting a recording > > (about half a beat at 163.7 BPM (sorry the calculations escape me trying > > to work out the exact latency here)) > > > > Has any9one else experienced this or can come up with a resolution for > > this.. > > > It may be the fact that the application in question is using the RTC, The application is ardour > and the clock just doesn't align with that tempo. Wild guess. (MIDI > apps or JACK usually run it at 1024 ticks/second, so figure how that > would align with 163.7 ticks/s.) > > I haven't had any latency problems with the unit or the driver itself. > Once, I was using the RTC as a timer as well, and the most I'd be off > would be 1-4ms, and that's just because my box is kinda slow. my box is pretty quick.. -- Allan Klinbail ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php