[Top][All Lists]

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

Re: [Discuss-gnuradio] multi_tone.py

From: Eric Blossom
Subject: Re: [Discuss-gnuradio] multi_tone.py
Date: Mon, 13 Mar 2006 09:56:48 -0800
User-agent: Mutt/1.5.9i

On Mon, Mar 13, 2006 at 05:25:58PM +0530, Ramakrishnan Muthukrishnan wrote:
> >
> > Why force users to install all modules in order to run a otherwise very 
> > simple
> > test application?

We shouldn't

> > Jack and portaudio may not even be available for some platforms.


> We can provide a way to select an audio module at the audio.py layer
> as it used to be  for OSS/ALSA selection. Not sure whether it has
> changed now.

That's where the fix should go.

> Or under gnuradio-examples, we can have separate directories under
> audio for jack, alsa and portaudio.

No, no, no!

My goal is that we converge, not diverge, the audio handling.  If we
need to change some constructor args, etc to make them all behave the
same, then so be it.  Conceptually, what I'm looking for is a new
abstract interface that covers *all* of the cases.  Then we should
make everything fit that new interface.  Then fix in audio.py, with
possible preference check, etc.  We can probablly make good use of
python keyword arguments to sort some of this out.


reply via email to

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