From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: ANISH KUMAR <anish.singh@samsung.com>
Cc: MAHAMMADRAFI MANIYAR <maniyar@samsung.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
lrg@slimlogic.co.uk, lennart@poettering.net
Subject: Re: ALSA DMIX support without MMAP ?
Date: Mon, 18 Jan 2010 11:01:07 +0000 [thread overview]
Message-ID: <20100118110106.GA3827@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <29151493.101581263785131632.JavaMail.weblogic@epml24>
On Mon, Jan 18, 2010 at 03:25:31AM +0000, ANISH KUMAR wrote:
[Reflowed into 80 columns for legibility.]
> Mark thanks for the suggestion and i checked out PulseAudio for my
> requirements.I found out that i don't need all the things in PulseAudio
> a. I just need good resampling code.Can i just use just the resampler code of pulseaudio(mine is mobile enviroment)?
> b. Just want a good mixer at ALSA-LIB level.As of now this is provided by android framework but i want this to be done by ALSA-LIB so that i
> can replace with some good mixer later on(if i find that some other mixer is good).DMIX is providing that but it's not that good.
The mixing (and therefore resampling) are the core functionality of
PulseAudio which is why it seems like a good fit for your application.
> c.Jaroslav suggested to use sox resamplers but for that to work i have to get the sox resampler code(proper license) and need to build it for my system and link it
> with corresponding functions of ALSA-LIB so that they can call relevant functions for resampling.As i am working on mobile domain i think i need to do the
> d. I saw some check-ins related to Scenario Manager.As of now scenario manager functionality is also given in Android(we open a differnet
> device and the corresponding hooks for changing the routes dynamically) but i think if it given in alsa-lib switching will be much faster and this
> will increase the system performance.
The application layer code isn't going to make a meaningful difference
to the performance of scenario switching unless it's woefully
inefficient, the major constraint is almost always the fact that the
CODEC has a relatively slow control bus so the register changes to
implement the change dominate the time.
next prev parent reply other threads:[~2010-01-18 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 3:25 ALSA DMIX support without MMAP ? ANISH KUMAR
2010-01-18 11:01 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-15 12:07 ANISH KUMAR
2010-01-15 13:37 ` Mark Brown
2010-01-14 10:30 ANISH KUMAR
2010-01-14 10:37 ` Jaroslav Kysela
[not found] <0KW800IYGE3P07@ms13.samsung.com>
2010-01-14 9:55 ` Mark Brown
2010-01-13 9:46 ANISH KUMAR
2010-01-13 11:27 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100118110106.GA3827@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=anish.singh@samsung.com \
--cc=lennart@poettering.net \
--cc=lrg@slimlogic.co.uk \
--cc=maniyar@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.