Return-Path: Message-ID: From: "I-Chung Chane" To: "BlueZ development" References: <6297d67c0606272049g55cc14cby52254c90863e727f@mail.gmail.com> <6297d67c0606280257y1cda0a8bj5ebdec42e3b1079@mail.gmail.com> Date: Wed, 28 Jun 2006 18:34:03 +0800 MIME-Version: 1.0 Subject: Re: [Bluez-devel] A2DP a2play and a2recv Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2071695285==" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net This is a multi-part message in MIME format. --===============2071695285== Content-Type: multipart/alternative; boundary="----=_NextPart_000_00EA_01C69AE1.6E680DF0" This is a multi-part message in MIME format. ------=_NextPart_000_00EA_01C69AE1.6E680DF0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Mayank: The embeded ARM platform is little endian so I define FORCE_LITTLE. Yeah, a sharp spike noise can be heard in a 10 second interval = while a2play is playing on the other side The a2recv version should be recent one. It runs ok on PC Linux. thanks for helps, Chane The above logs are OK. It means that the A2DP source is streaming to = your target device.=20 The only reason that you do not hear anything can be an endian = problem. Maybe the endian type in which the SBC is decoded is different = from the one that your device supports. Don't you even hear any noise? By the way are you using the latest version of a2recv? ------=_NextPart_000_00EA_01C69AE1.6E680DF0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi, = Mayank:

The embeded ARM platform is=20 little endian so I define FORCE_LITTLE.

Yeah, a sharp spike=20 noise can be heard in a 10 second interval while a2play is playing on = the other=20 side

The a2recv version=20 should be recent one. It runs ok on PC Linux.

thanks for = helps,

Chane

The above logs are OK. It means that the A2DP source is streaming = to your=20 target device.

The only reason that you do not hear anything can be an endian = problem.=20 Maybe the endian type in which the SBC is decoded is different from = the one=20 that your device supports.

Don't you even hear any noise?

By the way are you using the latest version of a2recv?

= ------=_NextPart_000_00EA_01C69AE1.6E680DF0-- --===============2071695285== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 --===============2071695285== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel --===============2071695285==--