Date: Fri, 7 Feb 2014 00:00:44 -0500
Reply-To: AUDITORY - Research in Auditory Perception <AUDITORY@xxxxxxxxxxxxxxx>
Sender: AUDITORY - Research in Auditory Perception <AUDITORY@xxxxxxxxxxxxxxx>
From: AUDITORY automatic digest system <LISTSERV@xxxxxxxxxxxxxxx>
Subject: AUDITORY Digest - 5 Feb 2014 to 6 Feb 2014 (#2014-41)
To: AUDITORY@xxxxxxxxxxxxxxx
Message-ID: <AUDITORY%201402070000441030.B52B@xxxxxxxxxxxxxxx>
Precedence: list
List-Help: <http://lists.mcgill.ca/scripts/wa.exe?LIST=AUDITORY>, <mailto:LISTSERV@xxxxxxxxxxxxxxx?body=INFO AUDITORY>
List-Unsubscribe: <mailto:AUDITORY-unsubscribe-request@xxxxxxxxxxxxxxx>
List-Subscribe: <mailto:AUDITORY-subscribe-request@xxxxxxxxxxxxxxx>
List-Owner: <mailto:AUDITORY-request@xxxxxxxxxxxxxxx>
List-Archive: <http://lists.mcgill.ca/scripts/wa.exe?LIST=AUDITORY>
There is 1 message totalling 28 lines in this issue.
Topics of the day:
1. Apps, apps, apps...
Date: Wed, 5 Feb 2014 15:45:14 +0000
From: David Morris <dmorris@xxxxxxxxx>
Subject: Apps, apps, apps...
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
=0A=
I'd like to know if the Android delay is handset or software related? With=
iOS there are some nifty APIs like auriotouch where handset input-output d=
elay, with the in-line mic, is even less than those figures you mention Lar=
s.=0A=
=0A=
Delay is a restriction on audio-visual applications and as an average Joe I=
don't understand why this hasn't been addressed by Google.=0A=
=0A=
=0A=
=0A=
David Morris Ph.D.=0A=
Speech and Hearing Therapy=0A=
Department of Scandinavian Studies and Linguistics=0A=
University of Copenhagen=0A=
Njalsgade 120=0A=
2300 K=F8benhavn S=0A=
http://inss.ku.dk/ansatte/beskrivelse/?id=3D398661=0A=