Hi HISE community,

We are always happy to add projects using Faust here: https://faust.grame.fr/community/powered-by-faust/.

Fell free to contact me if you want your project to be added.

Stéphane

Will there be any interest in something related to Faust integration ? I can possibly participate next meeting if you guys have some questions I can prepare answers for.

@etXzat and @Christoph-Hart did most of the hard work of "inside HISE" integration and they have to be thanked for that.

On the Faust side, the project adds to the existing ecosystem (https://faust.grame.fr/community/made-with-faust/) and we are quite happy with that :beaming_face_with_smiling_eyes:

@etXzat or @Christoph-Hart do you have a nice screenshot we could add on the https://faust.grame.fr/community/made-with-faust/ page?

GRAME has been selected as a mentor organization on GSoC for the Faust project.
And HISE integration if one of the proposed projects, hoping somewhere can be interested there?

Here: https://github.com/grame-cncm/faust/releases/tag/2.59.5

@Mighty23

We have tools to help debugging, read:
https://faustdoc.grame.fr/manual/debugging/#debugging-at-runtime
https://faustdoc.grame.fr/tutorials/debugging/

This interp-tracer tool is currently to be used in the terminal, so requires a local installation. But in theory this kind of tool could be integrated in HISE , since the libfaust library used in HISE also embeds the needed Interpreter backend.

For more local NAN protection, using ma.EPSILON is a more portable solution, since is adapts the single/double compilation option.

@Morphoice They are some sophisticated models in the Faust envelop library like https://faustlibraries.grame.fr/libs/envelopes/#enadsrf_bias or the following. Could one of them be used or adapted ?

Official 2.59.6 release: https://github.com/grame-cncm/faust/releases/tag/2.59.6

Yes indeed.

Licence of Faust functions in libraries are the choice of the contributors. Some are GPL, some MIT/BSD like...or others. Each function can have its own licensing scheme, which is usually described as a declare licence XXX line (see https://github.com/grame-cncm/faustlibraries/blob/master/aanl.lib#L261 for instance).

@Mighty23

We have tools to help debugging, read:
https://faustdoc.grame.fr/manual/debugging/#debugging-at-runtime
https://faustdoc.grame.fr/tutorials/debugging/

This interp-tracer tool is currently to be used in the terminal, so requires a local installation. But in theory this kind of tool could be integrated in HISE , since the libfaust library used in HISE also embeds the needed Interpreter backend.

For more local NAN protection, using ma.EPSILON is a more portable solution, since is adapts the single/double compilation option.

@Morphoice abs(x) < 0.0000000000000000555111512312578270211815834045

hum seems like a non human intervention here ?

Really nice !

Ready to be added in the "Powered by Faust" page https://faust.grame.fr/community/powered-by-faust/ ? If yes just send me some material, screenshot, presentation text...etc..

Extract of Shihong Ren thesis "Creating an Online Platform and Tools for Real-Time Music Composition and Signal Processing"

3e5870ee-509c-4f16-880e-65c17ebfbee2-These_Shihong_REN-FFT.pdf These_Shihong_REN-FFT

@AxiomCrux No this FFT code can only work in a specialised "hacked" Faust IDE version that does FFT/iFF around the actual Faust DSP, using a social architecture, basically following the Max/MSP pfft model (https://docs.cycling74.com/legacy/max8/refpages/pfft~). This is not "official".

@Morphoice the first 1* part is just useless right ? (also Faust will optimise this itself of course)

Nice to meet you guys ! Sorry for coming late, I will be more prepared next time.

@whoopsydoodle

• I don't remember in detail how the HISE Faust DSP wrapper works (that is the code this connect Faust DSP to the HIS audio layer) but possibly it already adapts input/output audio buffers
• and yes the proper way would be to open access to the compiler options in the Faust LLVM JIT path as well as the C++ generation path, but I don't where it can be done. @Christoph-Hart has to help here.

Note that using double internally in the Faust generated code also requires the "architecture" wrapping code to be adapted, see for instance https://faustdoc.grame.fr/manual/architectures/#external-and-internal-audio-sample-formats.

@Morphoice They are some sophisticated models in the Faust envelop library like https://faustlibraries.grame.fr/libs/envelopes/#enadsrf_bias or the following. Could one of them be used or adapted ?