I think I'm making progress with your help Marcus. The output of "gnuradio-config-info --enabled-components" is:
python-support;testing-support;volk;doxygen;sphinx;gnuradio-runtime;gr-ctrlport;gr-blocks;gnuradio-companion;gr-fec;gr-fft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-atsc;gr-audio;* portaudio;* windows;gr-channels;gr-noaa;gr-pager;gr-qtgui;gr-trellis;gr-uhd;gr-utils;gr-video-sdl;gr-vocoder;gr-fcd;gr-wavelet;gr-wxgui;gr-zeromq What does the '*' before portaudio mean? I think you are also correct in that it appears my config.conf file is not being read. GRC created a ~/.gnuradio directory and populated it with a grc.conf file and prefs directory. I created a config.conf file in the same directory. Adding the [grc] stanza seems to have no effect. I also tried changing the canvas size in the "c:/Program Files/GNURadio-3.7/etc/gnuradio/conf.d/grc.conf" file, which I think is supposed to be the system-wide file, but changes there have no effect either. Is there a way for me to figure out what configuration files are being read? Tony Richardson On Fri, May 6, 2016 at 3:14 AM, Marcus Müller <marcus.muel...@ettus.com> wrote: > Huh, can you verify portaudio is in the output of "gnuradio-config-info > --enabled-components" ? > > Can you add another section, > > > [audio_portaudio] > verbose = true > > Just to verify: you're using the "[..]" section headers correctly, and the > rest of the conf file looks ungarbled, right? > > We might be encountering a case where the config file simply isn't read; > as a quick test: > Close all gnuradio-companions, add > > [grc] > canvas_default_size = 100,100 > > to that file, and open up the companion – your canvas size should now be > 100x100px. Is that the case? > > Best regards, > Marcus > > > On 06.05.2016 00:20, Tony Richardson wrote: > > Thanks, but I've tried that (setting "audio_module = portaudio"). It > doesn't appear to have the desired effect. > > Tony > > On Thu, May 5, 2016 at 4:26 PM, Marcus Müller <marcus.muel...@ettus.com> > wrote: > >> Sorry, not currently running any Windows VM, but in the spirit of giving >> you the info you need as fast as possible: >> >> Quick lecture of the audio sink/source factory tells me that under >> windows, by default the windows audio architecture is used. >> So to use portaudio instead, you need to have a GNU Radio config file >> (under unixoids, that's ~/.gnuradio/config.conf), and add >> >> [audio] >> audio_module= portaudio >> >> >> Best regards, >> Marcus >> >> On 05.05.2016 22:59, Tony Richardson wrote: >> >> I'm using the pre-built Win64 binary of GNURadio listed on the >> gnuradio.org site. The portaudio library was included as part of the >> Win64 build, but I can't seem to figure out how to use it instead of the >> default windows audio. (I want an audio source and the windows audio >> source does not work.) I've tried putting "audio_module = portaudio" (and >> "audio_module = audio_portaudio") in the config.conf file, but when I run a >> simple flowgraph that includes an audio source and sink, I see: >> >> INFO: Audio source arch: windows >> INFO: Audio sink arch: windows >> >> in the console and there is no sound. I assume the lines above are >> telling me that the windows audio devices are being used and not the >> desired portaudio devices. I have tried leaving the device name in the >> audio source blank as well as trying "0" and "hw:0,0", but still see the >> messages above. Can someone tell me how to configure audio for portaudio >> or is it just not supported? >> >> Tony Richardson >> >> >> _______________________________________________ >> Discuss-gnuradio mailing >> listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> >> >> >> _______________________________________________ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> >> > >
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
