Return-Path: <clemens@ladisch.de>
X-Original-To: tronic@trn.iki.fi
Delivered-To: tronic@trn.iki.fi
Received: from trn.iki.fi (localhost [127.0.0.1])
	by trn.iki.fi (Postfix) with ESMTP id 1C73145B7D280
	for <tronic@trn.iki.fi>; Fri, 14 Nov 2008 10:12:39 +0200 (EET)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com
 [66.111.4.25])
	by trn.iki.fi (Postfix) with ESMTP
	for <tronic+cv5n@trn.iki.fi>; Fri, 14 Nov 2008 10:12:39 +0200 (EET)
Received: from compute2.internal (compute2.internal [10.202.2.42])
	by out1.messagingengine.com (Postfix) with ESMTP id 19C3D1B4B4D;
	Fri, 14 Nov 2008 03:12:38 -0500 (EST)
Received: from heartbeat2.messagingengine.com ([10.202.2.161])
  by compute2.internal (MEProxy); Fri, 14 Nov 2008 03:12:38 -0500
X-Sasl-enc: oLLt9i8Rmbv9HSIss5FczHuwW6BR64JrNx3YjspqLxA6 1226650357
Received: from [10.1.2.10] (srv004.schk01.int.dmc-one.com [85.232.8.141])
	by mail.messagingengine.com (Postfix) with ESMTPSA id F361F1EAC1;
	Fri, 14 Nov 2008 03:12:36 -0500 (EST)
Message-ID: <491D3300.5050405@ladisch.de>
Date: Fri, 14 Nov 2008 09:12:48 +0100
From: Clemens Ladisch <clemens@ladisch.de>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: James Trevelyan <james@jamestrev.com>
CC: =?ISO-8859-1?Q?Lasse_K=E4rkk=E4inen?= <tronic+cv5n@trn.iki.fi>,
 alsa-devel@alsa-project.org, james@jamestrevelyan.com, timc@wnsp.com
Subject: Re: [alsa-devel] Roland/Edirol M-16DX
References: <487F10EE.6030405@trn.iki.fi>
 <48883AAC.6060101@ladisch.de>	 <4917B029.7010809@trn.iki.fi>
  <491C6E10.7090308@trn.iki.fi> <1226624101.4836.95.camel@localhost>
In-Reply-To: <1226624101.4836.95.camel@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-LimZero: valid lzID=cv5n

James Trevelyan wrote:
> ...
> However, what I did notice is that in all circumstances the windows
> driver was capturing at the same time as playback, even when I was not
> asking it to record.  This suggests to me that the comment in the driver
> source about synchronising playback to capture has some relevance ...

Indeed.  The driver would have to send the data at the exact speed of
the device's internal clock, and the only way to determine that clock's
speed is to capture data.

So far I haven't found the time to rewrite the driver to support this
synchronization mechanism.


Best regards,
Clemens
