[Clam-devel] My adventures with sample by sample processing (part II)

[Xavier Amatriain]

The only reason is that I evolved this from the BasicFlowControl and
ended up using the same Do() structure. Besides, I wanted to avoid any
performance time penalty so adding many processing pointers at
configuration time is not an issue as long as then all I have to do is
traverse a list on execution.

On Wed, 2007-01-03 at 20:45 +0100, Pau Arumi wrote:
> En/na Xavier Amatriain ha escrit:
> > ...
> > For instance if you have audio in + sample by sample processing + audio
> > out, you have three branches that make the cycle:
> >
> > fire once: audio in
> > fire 512 (or whatever the framesize is): all the sample by sample
> > processings
> > fire once: audio out
> >
> >   
> I see. but you insert 512 processing pointers, don't you? why do not 
> just let Do() know the pipeline+nloops information? just wondering if 
> there is any special reason.
> > I could provide with a working example. The problem is that this means
> > overwriting the MainWindow.hxx file in the NetworkEditor because that is
> > where the Flow policy selection is done at the moment.
> >   
> neteditor is asking a proper commandline handling (we need to choose 
> audiobackend also)
> 
> 
-- 

/*********************************
 *       Xavier Amatriain        *
 *  Associate Director - MATi    *
 *  Research Director - CREATE   *
 *    UCSB, Santa Barbara CA     *
 *      1-(805)- 893 83 52       *
 ********************************/