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
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Faudiostream-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/faudiostream-users
