discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss-gnuradio] gr-audio: one component to rule them all


From: Josh Blum
Subject: [Discuss-gnuradio] gr-audio: one component to rule them all
Date: Wed, 09 Mar 2011 16:53:22 -0800
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8

Hello list,

I have created a new top level component called gr-audio. The goal of
gr-audio is to combine all supported audio architectures under a single
source and sink block.

Gnuradio has 6 different top level components, each for a different
audio architecture. If you used audio in python, this was transparent,
as the python file was test-importing each possible architecture. But if
you used audio in c++, you would have to hard-code a specific audio
architecture into your code.

gr-audio presents one interface to the user in both c++ and python. At
build-time, all architectures available to the compiler are built into
the library. At runtime, an available audio architecture is selected.
This selection is based on default priority, or if present, a
configuration file setting.

The build system will continue to configure and build the old top-level
components; so this will not break C++ that was coded for a specific
audio component. Anyone using audio block in python will be
automatically calling into the new component.

Try it out!
http://gnuradio.org/cgit/jblum.git/log/?h=wip/gr-audio

I was able to test 4 of the 6 architectures. Testers for the osx and
windows audio support would be appreciated.

Thanks,
-Josh



reply via email to

[Prev in Thread] Current Thread [Next in Thread]