Message-ID: <3837d8b10807250948l20d30a1ld9f2867b382f54f7@mail.gmail.com>
Date: Fri, 25 Jul 2008 11:48:15 -0500
From: "keith preston" <keithpre@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
In-Reply-To: <2d5a2c100807241345x48a0b1co22975c0fb0e0c8d9@mail.gmail.com>
MIME-Version: 1.0
References: <3837d8b10807241238r3284fdb6q60f4c86265146756@mail.gmail.com>
	<2d5a2c100807241345x48a0b1co22975c0fb0e0c8d9@mail.gmail.com>
Subject: Re: [Bluez-devel] [PATCH] a2dp_write patch
Reply-To: BlueZ development <bluez-devel@lists.sourceforge.net>
Content-Type: text/plain; charset="us-ascii"
Sender: bluez-devel-bounces@lists.sourceforge.net
Errors-To: bluez-devel-bounces@lists.sourceforge.net

> Well done, now Im wondering if it isn't possible to use alsa buffer
> all the time instead of copying to a temporary buffer?

You definitely can't depend on the buffer still being there.   There
are two options, you can just refuse to process any part of the buffer
that is not a certain size, or you can do what we are trying to do and
store it off temporarily.   I think the last is the best solution,
because it makes it easier on the our clients,  we have to deal with
the extra instead of an application needed to deal with half processed
buffers.

 I mean can't we
> just point to the first pcm frame processed but not encoded? (If not
> freed already by alsa)
> Also there is some code duplication, but still the idea is very good.
> If you could please check the performance with oprofile.
>
>
> --

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel