> Le 10 sept. 2019 à 09:49, Lukas Degener <lukas.dege...@posteo.de> a écrit : > > Hello everyone, > > I am new to FAUST, and right now feeling like the metaphorical child in > the sweet shop. :-)
Welcome Lukas ! > > There are some things, I would like to try, but I am not sure where to > start. I have no problem with creating my own custom architecture file > if this is what it takes, but I want to make sure I am not overlooking > something obvious. > > Here are some of the things, I would like to try: > > I see there is a clever naming convention to control polyphonic DSPs via > midi. But let's say, I wanted to use OSC instead of MIDI -- would it be > feasable to have some multi-argument OSC message instead of a Note-On? The mydsp_poly wrapper class (that allows to duplicate a DSP voice to create a polyphonic DSP) is usually triggered by MIDI messages, and so is usually started in the dynamically allocated voice mode (see mydsp_poly constructor) See https://github.com/grame-cncm/faust/blob/master-dev/architecture/faust/dsp/poly-dsp.h @param control - whether voices will be dynamically allocated and controlled (typically by a MIDI controler). * If false all voices are always running. But you could perfectly allocate a mydsp_poly object with control = false, so that to be able to control each voice individually with OSC messages. > > What if I need to have more per-voice parameters (i.e. other than freq, > gain, gate)? Is there a "default" way to extend the existing logic? Then you can use all OSC like paths of all voices, for the freq/gate/gain parameters, but also all other parameters the voice may have. > > To take this a bit further: I see there are some bits (FUI, PresetUI) > that deal with storing/recalling presets. I would like to be able to > store more than one preset (I think PresetUI does this, but it is only > included in ca-qt,cpp?). And .... I would like to be able to select a > different preset for each individual node I "play". > > Are these feasable ideas? Yes, PresetUI was a first try for that, this is the reason it is only used in ca-qt.cpp for now. But It should be usable in other contexts. > > Is creating a custom architecture file the intended approach for this? > Or would I just use faust2api and create the logic I need on top of > this? I would say hacking/adapting an existing one should be enough. > > Can you point me to some documentation or existing code for inspiration? Possibly this generic paper http://www.grame.fr/ressources/publications/09_C_B_137724.pdf > > Kind regards, > Lukas > > p.s. In case you were wondering: I want to use Faust to synthesize sound > effects (collision sounds mostly) for a video game in real time. Is the video game running as a standalone application? it case it helps we have an architecture for Unity, see faust2unity here: https://github.com/grame-cncm/faust/tree/master-dev/architecture/unity > My prototype uses puredata for this, which works fine, but some things > are really cumbersome to do in pd, so I was looking for alternatives. > The combination of DSPs written with FAUST + maybe some additional > control logic written in c++ seems like a realy nice fit. But of course > this needs further evaluation. Feel free to ask more help ! Stéphane _______________________________________________ Faudiostream-users mailing list Faudiostream-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-users
