Am 29.11.2017 um 11:43 schrieb Stéphane Letz:
Faust options been forwarded from the caller to faust. Usually the dsp2cc script calls faust. and read the stdout from it. The dsp script checks if a special option is given and act accordingly. For example: if self.options.vectorize: s["compute"] = self.replace_ioref_vector(self.copy(r"\t}$")) self.has_vector = True else: s["compute"] = self.replace_ioref_scalar(self.copy(r"\t}$")) were replace_ioref_vector handle the vectorized sources. Unfortunately my experience with vectorize been not so well. Here it push the CPU usage to a unwanted level last time I've tried it. Could it be that it ain't work so well on small audio buffersizes like 128?Finding the best compilation parameters for a given DSP is somewhat complex. Have you read this post that explains some automatic tools to help ? http://faust.grame.fr/news/2017/04/26/optimizing-compilation-parameters.html I would be interested to now is those tools help for guitarix ! Stéphane
I'm still on faust(0.9.90), but this reads very interesting. I'll check that out as soon I've switched to the latest faust-git.
Surly we can't use that in our dsp2cc script (without implement it ;-) ) but I'll check it out and find out if it could help to reduce the CPU usage even more, and will come back on you to report my findings. Just let me say that the CPU usage of faust generated plugs been low anyway.
Thanks for all your work on it. regards hermann ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Faudiostream-devel mailing list Faudiostream-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-devel
