fgrond

My experience from the ambitools implementation from Pierre Lecomte (which is complex and therefore a good example, I think) and compiling it for SC is the following: 1) Big FAUST...

I believe most of the ideas above need to be implemented on the FAUST side. @LFSaw, I'm sure you would have a wishlist yourself ;-) I would suspect that FAUST...

I was just reading up on code documentation options in FAUST: see section 9 in this doc: http://faust.grame.fr/images/faust-quick-reference.pdf There is plenty of stuff addressing many of the points from above....

yes, this is the section I mean, and yes, this would be the main point: translating the LaTeX-file into schelp. I am wondering though if we could extract from this...

Yes, the regrouping we could take care of separately, we just need to find out how to properly document inputs (outputs) in FAUST. I think this should be of general...

This output is showing in the postwindow only if the plugins are compiled from the cpp source which usually don't set the -NDEBUG flag. If compiled with the faust2supercollider script...

Thank you Carlo, this is great news indeed! On Jul 20, 2017 7:14 AM, "Carlo Capocasa" wrote: Great news! Faust also merged my modification of the supercollider2faust script into their...

I believe it is Stéphane Letz @sletz who has control over the faust2supercollider script This is the faust2supercollider script: https://github.com/grame-cncm/faust/blob/master-dev/tools/faust2appls/faust2supercollider The faust2supercollider script has debug-flags but the print debug code...

@sletz we had discussed similar matters in the past maybe you can do the changes Stéphane? What we need for Faust contributions to the SC3plugins repository is fairly simple: _Faust...

OK got it! I'll try to come up with a suggestion, probably this Friday. www.grond.at On Wed, Jan 31, 2018 at 2:18 PM, Brian Heim wrote: > If you wanna...