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
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?
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 ?
@aaronventure The reason is that maintaining this enable/control
feature adds complexity in the compiler that we want now to cleanup.
@aaronventure Guys, we will not maintain enable/control
for backward compatibility , so you are warned !
I don't think so. This would require using a SoundUI
object as explained here: https://faustdoc.grame.fr/manual/architectures/#developing-a-new-soundfile-loader
But since HISE use based on JUCE, then using the already written JuceReader should be strait forward.
The lastest release is Faust 2.79.3, see https://github.com/grame-cncm/faust/releases
/usr/lib/llvm-13/
this LLVM version is too old: use at least LLVM 15.
Faust lib reverbs:
https://faustlibraries.grame.fr/libs/reverbs/ can be tested here: https://faustdoc.grame.fr/examples/reverb/
Some other Faust coded reverbs here:
https://github.com/LucaSpanedda/Digital_Reverberation_in_Faust
@sletz Well, I just discovered that https://github.com/grame-cncm/faust/tree/master-dev-ocpp-od-fir-2-FIR. branch is still quite buggy, so no need to rush
@aaronventure Trying to create binaries on the GitHub CI, but still some problems to solve.
In the meantime you can possibly try the Faust IDE Ondemand aware version: https://grame-cncm.github.io/faustide-od/
@aaronventure Note that in case you can directly compile Faust + LLVM, the WIP branch with ondemand
working is here: https://github.com/grame-cncm/faust/tree/master-dev-ocpp-od-fir-2-FIR.
We are interested in feedback, in case you HISE guys can test it
@aaronventure The reason is that maintaining this enable/control
feature adds complexity in the compiler that we want now to cleanup.
@aaronventure Guys, we will not maintain enable/control
for backward compatibility , so you are warned !