From: "Markus Vogl" <markus.vogl@gmx.net>
To: alsa-devel@alsa-project.org
Subject: Re: frequency analysis with alsa and fftw
Date: Sun, 27 Dec 2009 14:50:20 +0100 [thread overview]
Message-ID: <DCFE698CA76D4C32B964618FB02D7745@RDF2008PC> (raw)
In-Reply-To: <20091227125343.GG7599@lug-owl.de>
hi,
i have to do this in realtime (like a guitartuner) and with my "project" i
have to see the frequency shift in realtime in a terminal window.
regards
markus
-----Ursprüngliche Nachricht-----
Von: Jan-Benedict Glaw [mailto:jbglaw@lug-owl.de]
Gesendet: Sonntag, 27. Dezember 2009 13:54
An: Markus Vogl
Cc: alsa-devel@alsa-project.org
Betreff: Re: [alsa-devel] frequency analysis with alsa and fftw
On Sun, 2009-12-27 13:26:31 +0100, Markus Vogl <markus.vogl@gmx.net> wrote:
> my project is to analyse the mic input frequency from my asus eepc
> 1008ha with ubuntu 9.10 and show it in a terminal window. i would use
> my acoustic 6 string guitar to play in front of my netbook.
>
> i´ve testet the howto from linuxjornal.com ..
> http://www.linuxjournal.com/article/6735
>
> ...but i´ve no plan to use the mic input and then analyse it with fftw.
Why do you need to do ALSA programming in the first place? Isn't it enough
to use any given ALSA-capable audio recorder (eg. arecord) to record some
sound, convert it to raw PCM data (eg. cut off the WAV
header) and then shift all the data into the FFT lib?
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481
Signature of: If it doesn't work, force it.
the second : If it breaks, it needed replacing anyway.
next prev parent reply other threads:[~2009-12-27 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-27 12:26 frequency analysis with alsa and fftw Markus Vogl
2009-12-27 12:53 ` Jan-Benedict Glaw
2009-12-27 13:50 ` Markus Vogl [this message]
2009-12-27 14:04 ` Jan-Benedict Glaw
2009-12-28 12:16 ` Markus Vogl
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=DCFE698CA76D4C32B964618FB02D7745@RDF2008PC \
--to=markus.vogl@gmx.net \
--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 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.