[Top][All Lists]

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

Re: [Discuss-gnuradio] gqrx in MacPorts

From: Michael Dickens
Subject: Re: [Discuss-gnuradio] gqrx in MacPorts
Date: Mon, 12 Aug 2013 12:41:07 -0400

Hi Alex - OK; that all makes sense.  Thanks for the clarification.  Next gqrx 
update I'll add in a variant for +portaudio.  And, I'll hopefully get the OSX 
native audio fixed up in the next couple of weeks.  In the meantime, if anyone 
is using gqrx on OSX (via MacPorts or otherwise), I'd love to hear if/how it 
works for you, both display and audio.  Has anyone used it with a HackRF 
Jawbreaker? - MLD

On Aug 12, 2013, at 11:06 AM, Alexandru Csete <address@hidden> wrote:
> I wasn't very clear in my original explanation so let me try again.
> If you build gqrx using:
> $ qmake
> $ make
> Then gqrx will be built without any portaudio specific code. It will
> use gr-audio for both audio input and output, whcih in turn will use
> the native OS X backend unless the user configures gnuadio to use
> something else. This will work just fine except that input source is
> broken so no funcube dongle support and gqrx will not be able to
> enumerate the available audio devices (gr-audio does not have such
> API).
> If you build gqrx using:
> $ qmake AUDIO_BACKEND=portaudio
> $ make
> then gqrx will use portaudio specific code meaning:
> - It will set the GR_CONF_AUDIO_AUDIO_MODULE environment setting to
> portaudio so that gnuradio will use the portaudio backend regardless
> of what the user has configured (I assumed that 99% of gqrx on the Mac
> users have no idea that they can configure gnuradio via
> ~/.gnuradio/config.conf)
> - It will use portaudio API functions to enumerate the avaialble audio
> devices and present that to the user. This is used for both input
> devices and output devices.
> Because of the last point portaudio is a build time option in gqrx.

reply via email to

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