Dear Tom,
I backtraced this call and there is no implementation of gnuradio
preference file. When it is called the architecture, it returns
gr_prefs::singleton()->get_string(“audio”, “audio_module”, “auto”);
Thus, get_string is implemented as this:
const std::string
gr_prefs::get_string(const std::string section, const std::string
option, const std::string default_val)
{
return default_val;
}
As you can see, it does not parse any value of any config file. It just
returns the default value. Even though it is implemented in a different
way in Python (it is a python written module), in C++ there isn’t.
So, are you going to implement it? Have you plans to make working it?
Thanks.
–
Pol H.
Research Engineer, MSc
[email protected]
Centre Tecnolgic de Telecomunicacions de Catalunya (CTTC)
Engineering Unit
Parc Mediterrani de la Tecnologia
Av. Carl Friedrich Gauss, 7
08860 Castelldefels, Barcelona (Spain)
Tel: +34 93 396 71 70 Ext: 2177
Fax. +34 93 645 29 01
www.cttc.es
On Thu, Sep 13, 2012 at 6:40 AM, Pol H. address@hidden wrote:
Dear list,
I have my c++ app written using the audio module. Even though I placed
the
[audio] audio_module=oss inside ~/.gnuradio/config.conf, the
audio_make_sink
loads the ALSA sink. Moreover, if I execute dial_tone.py it takes
correctly
the configuration in config.conf and uses the oss audio_sink.
It seems that when I use python environment loads correctly the
config.conf
but not my app. Do you know I have to specify some path, load command or
something?
Thank you.
Pol H.
Research Engineer, MSc
address@hidden
Pol,
That’s one of the problems with working in two languages and having
some things defined one place and others in another place. It looks
like the Python and C++ preferences don’t behave exactly the same.
Instead of putting the configuration info into your home directory
(‘~/.gnuradio/’), try putting it into the system configuration
directory ($prefix/etc/gnuradio/conf.d) into the gr-audio.conf file.
Tom