25 Mar
2024
25 Mar
'24
12:16 p.m.
Hello all,
Triggered by a recent post, I've been dabbling a bit with Faust,
and have some questions :-)
(For the jack-gtk architecture)
- When started the app prints some useless info (a nuisance) and
it also autoconnects (a definite no-go).
Is there any way to avoid this ?
- The faust2jack script says it adds 'preset' functionality
to the GUI. But there seems to be no way to access this.
- The way the PRESETDIR is handled is weird. It is done by
prepending a single line temporary file to the merged cpp file
using cat.
What would be wrong with
# add preset management
if [ $PRESETDIR = "auto" ]; then
PRESETDEFS=-DPRESETDIR=\"/var/tmp/\"
else
PRESETDEFS=-DPRESETDIR=\"$PRESETDIR\"
fi
and then adding PRESETDEFS to the compiler options ?
Sure, I guess this specific thing came by coping an already written « way of doing », lack
of Unix culture, years of history…
(General)
- The various faust2*** programs work by merging the compiled dsp
file with the architecture file. While doing this, also all
include files from the /usr/include/faust directory are recursively
expanded in-line. Now I wonder why this is done. Surely the C++
preprocessor would do this anyway ?
This -i option is there to produce a kind of « self-contained » Faust architecture (so
only inlining the « faust/xxx » files). And possibly not really needed in this specific
example : history, copy/paste…etc...
Stéphane,