Yes, that's how I currently do it too. But it would be so much nicer if one could write the whole thing in faust :)
On Thu, Apr 25, 2013 at 9:56 PM, Harry van Haaren <[email protected]> wrote: > On Thu, Apr 25, 2013 at 5:56 PM, Jonatan Liljedahl <[email protected]> > wrote: >> Any news on this? > > There's a hacky workaround: it involves wrapping your "faust units" in C++, > but it works. > > Basically code faust .dsp files per "section" that you want to be able to > turn on / off individually. > Export each one to a separate C++ class. Write a wrapper class that has > interacts with your > program / environment in a way which works. Add in some logic for calling > compute() only > on the class instances which you want to run. > > Yes its a hack, but I'm using faust to generate C++ anway, so its do-able. > I've split reverb & echo > off the main processing, and can the "reverb-echo unit" when the user uses > either of them. > > I think theoretically it should be possible to run the resulting "wrapper" > class back trough an > architecture file, and then having multiple "sub-faust" units... but there's > probably a much > cleaner solution somewhere. > > I do feel this is an important aspect for FAUST to address, on my modestly > old laptop it chews up > CPU % pretty easily.. -Harry -- /Jonatan http://kymatica.com ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ Faudiostream-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/faudiostream-users
