From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: ALSA application programming: route audio from one PCM to another
Date: Wed, 14 Apr 2010 10:00:11 +0100 [thread overview]
Message-ID: <hq406t$sjk$1@dough.gmane.org> (raw)
In-Reply-To: <4BC58082.6090508@gmail.com>
'Twas brillig, and Stefan Schoenleitner at 14/04/10 09:44 did gyre and
gimble:
> Colin Guthrie wrote:
>> 'Twas brillig, and Stefan Schoenleitner at 13/04/10 16:23 did gyre and
>> gimble:
>>> Hi,
>>>
>>> I finally managed to write an ALSA I/O plugin that does what I want.
>>> The plugin supports both playback and capture.
>>>
>>> Now I would like to write a simple audio application that takes audio
>>> samples
>>>
>>> * from the microphone and plays it back on my plugin
>>> and
>>> * from the plugin (capture) and plays it back on the speakers
>>>
>>
>> This sounds like something that would be more appropriate for jack
>> http://jackaudio.org/
>
> Thanks for your response, that really sounds like a job for JACK.
>
> However, due to the nature of jack it seems that running the jack-daemon
> is always necessary.
> As my code is supposed to work on a very small scale embedded target, I
> would prefer to have a small stand-alone application that does not
> require a running jack-daemon.
>
> * Do you know if it is possible to use the jack functionality without
> having to run the jack-daemon ?
I'm afraid not. Like PulseAudio, Jack needs the daemon to do all the
hard stuff.
I guess you'll just have to write some small app that does the
record/playback. I doubt it'll be that hard.
That said, with this approach, the fact that you've got an alsa plugin
doing the processing in the middle seems slightly irrelevant... why not
have your app sample the input, do the DSP it needs to do, then play the
output? No need to: sample, play [process] sample, play. Rather: sample
[process] play.
Perhaps I'm not understanding the other needs/use cases of the plugin
tho'. Just idle thoughts :)
>>> Hence as long as the application is running, it should do the above.
>>>
>>> * Is there a special ALSA way to route audio from one PCM to another ?
>>>
>>> * If not, I suppose it would just work if I open the plugin PCM and the
>>> hw PCM at the same time and copy audio frames between them ?
>>
>> Dealing with this can be quite complex, especially if the pcms are
>> clocked of different sources, you have to deal with a degree of
>> resampling to ensure that clock skew doesn't get out of control.
>
> Both PCMs are on the same machine, hence they should be clocked from the
> same source as well ?
I believe this is quite likely, but I'm not really certain that it holds
true in all cases.
Someone more clued up than me may be able to comment.
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mandriva Linux Contributor [http://www.mandriva.com/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
next prev parent reply other threads:[~2010-04-14 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 15:23 ALSA application programming: route audio from one PCM to another Stefan Schoenleitner
2010-04-13 16:23 ` Colin Guthrie
2010-04-14 8:44 ` Stefan Schoenleitner
2010-04-14 9:00 ` Colin Guthrie [this message]
2010-04-14 9:36 ` Stefan Schoenleitner
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='hq406t$sjk$1@dough.gmane.org' \
--to=gmane@colin.guthr.ie \
--cc=alsa-devel@alsa-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).