Hi Ron, > If so, is Faust combined with JUCE then my best option? And if so, can you recommend tutorials showing how this integration works on either or both platforms?
I've been integrating Faust within JUCE for some time now, and it is the best approach I know for high-speed audio plugin development. In fact, I am developing a new course at CCRMA on this, to be given in the spring: https://ccrma.stanford.edu/~jos/intro320c/Schedule.html One thing to know is that there is a name collision between Faust's "dsp" class and JUCE's "dsp" namespace. This only bites if you try to use both Faust and the juce_dsp module, which Plugin GUI Magic happens to require. My solution was to rename the Faust dsp class to faustdsp, and all is working well. I use Faust's APIUI.h as the basis for my Faust architecture file, which I think I learned about from studying faust2api. Cheers, Julius On Thu, Dec 17, 2020 at 6:37 AM Stéphane Letz <l...@grame.fr> wrote: > Hi Ron, > > > Le 17 déc. 2020 à 15:13, Ron Herrema <rherr...@gmail.com> a écrit : > > > > Hi everyone, > > > > I'm wondering what currently is the most efficient pathway to developing > audio-based apps for iOS and Android using Faust. I'm an iOS developer and > electroacoustic composer who has created a couple of generative audiovisual > iOS apps. In the most recent, Infínity, I used Enizen's Heavy Audio Tools > to convert a Pd patch to C code, which worked well - but Enzien stopped > developing Heavy a couple years ago. > > > > When I export Faust code for Android, it generates only an apk file, so > I assume there is no way to hone an Android app working directly from Faust > - is that correct? > > I guess you mean using faust2android yes ? ( > https://ccrma.stanford.edu/~rmichon/faust2android/) > > Yes faust2android (or faust2ios) are tools that automatically generate the > GUI using the abstract description included in the DSP program. > > If you want to control the GUI building yourself, you can use faust2api ( > https://ccrma.stanford.edu/~rmichon/faust2api/) that will generate an > audio engine with the Faust DSP code, but let you design your one GUI on > top of it. > > > > > If so, is Faust combined with JUCE then my best option? And if so, can > you recommend tutorials showing how this integration works on either or > both platforms? > > Using Faust with JUCE is another possibility yes, possibly with > faust2juce, see: > > https://faust.grame.fr/community/news/#2017-02-21-faust-meets-juce > > https://github.com/grame-cncm/faust/tree/master-dev/architecture/juce > > > > > I guess a related question is: what will Faust give me (aside from a > different syntax) that JUCE cannot? > > > Faust is an alternative to C++ to program the DSP part of your > application. > > > > > Finally, an additional consideration is UI - I've been learning React > Native and like the ease with which interfaces can be built using Flexbox, > but it seems JUCE has its own version of this. > > > > Any advice and links will be greatly appreciated. > > > > Cheers, > > > > Ron H > > We are currently experimenting in using PluginGuiMagic (ttps:// > foleysfinest.com/developer/pluginguimagic/) as a way to generate an > editable GUI in faust2juce, but nothing ready yet. > > An alternative is also blueprint ( > https://github.com/nick-thompson/blueprint) and I think a connection with > Faust could be written (using some glue code to connect the generate Faust > C++ cod with the blueprint API), bit nothing has been done yet. > > Stephane > > _______________________________________________ > Faudiostream-users mailing list > Faudiostream-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/faudiostream-users > -- "Anybody who knows all about nothing knows everything" -- Leonard Susskind
_______________________________________________ Faudiostream-users mailing list Faudiostream-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-users
