Hi Francesco, Welcome to the mailing list!
If we are very committed to open-source for Faust, nothing prevents using Faust for closed-source software. I am thinking in particular of GeoShred by Moforte, or Noisy a synthesizer by ExpressiveE. So if you have Closed-Sources projects to present, they will be welcome too. Yann *Yann Orlarey* Directeur scientifique/Scientific director orla...@grame.fr <x...@grame.fr> T : +33 (0) 4 72 07 37 00 GRAME - Centre national de création musicale 11 cours de Verdun Gensoul | 69002 Lyon www.grame.fr | facebook <https://www.facebook.com/Gramelyon/> | instagram <https://www.instagram.com/grame_cncm/> | twitter <https://twitter.com/GRAME_LYON> Le lun. 1 juin 2020 à 01:23, francesco mulassano < francesco.mulass...@gmail.com> a écrit : > what characteristics must the projects have to be presented? > Do they have to be open source, do they have to be ready or can they be > prototypes? > > Thanks > this is my first message! > Francesco > > Il giorno lun 1 giu 2020 alle ore 01:17 Sam Pluta <spl...@gmail.com> ha > scritto: > >> As a newer user, seeing some larger structured projects would be nice. I >> am mostly using this language as a way to make plugins in SC. My brain is >> wired to use oop structure in larger projects. Seeing some larger >> functional projects would be really helpful for me. >> >> Sam >> >> On May 31, 2020 at 12:27:56 PM, Gary Worsham (gary.wors...@gmail.com) >> wrote: >> >> Here are some thoughts. I started by taking the Kadenze Faust online >> course. I've made VST plugins for Windows, jaqt for Linux, Android apps, >> Bela and ESP32. Still I feel like a beginner because the syntax is >> occasionally baffling, especially if you are using recursion. >> >> a) I usually start with a block diagram of an algorithm in mind and then >> struggle to represent it in Faust. What I'd like to see is a step by step >> strategy for decomposing an arbitrary block diagram into Faust, especially >> with recursion and routing complications. >> >> b) There's sometimes a gigantic gap between the basic examples and some >> of the more elaborate ones, e.g. JOS's recursion example immediately jumps >> to some ridiculously complex FFT structure. Way over my head. Maybe >> that's not a separate concern from point (a). >> >> c) When writing code for the ESP32 for example, figuring out how much >> code would run without triggering watchdog timer errors is trial and >> error. I got pointed at some of the code profiling tools but I could not >> figure out how to use them. When targeting smaller embedded systems >> there's going to be a limit on algorithm complexity and figuring out what >> will or won't fit is frustrating. For example, one ESP32 algo I worked >> with would not allow even a single pole filter to be added but I could add >> another flanger and LFO. So, I'd like a bit of a session devoted to >> showing how to use the profiling tools. >> >> Thanks, >> >> Gary W. >> >> >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> >> Virus-free. >> www.avast.com >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> >> <#m_-4647718005420343869_m_-8713102643393980965_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> >> On Sun, May 31, 2020 at 7:09 AM Dario Sanfilippo < >> sanfilippo.da...@gmail.com> wrote: >> >>> Hello, Yann. >>> >>> On Fri, 29 May 2020 at 10:51, Yann Orlarey <orla...@grame.fr> wrote: >>> >>>> We plan to organize new Faust online workshops in the coming weeks. >>>> Among the themes we have thought of, two of them involve contributions from >>>> the community. And we'd love to hear what you think about them. >>>> >>>> 1/ Workshop Q&A >>>> The idea would be to collect in advance questions and problems that you >>>> may have about Faust and for which we will try to find answers. Then we >>>> will organize a workshop where the most representative questions will be >>>> presented as well as the answers we can give them. >>>> >>> >>> This perhaps depends on the direction that Faust is taking for its >>> future developments. >>> >>> Personally, I've found that Faust is an environment where aspects of >>> algorithmic composition and audio engineering can coexist beautifully. I >>> can also see that the interest of electronic musicians for Faust is growing >>> a lot recently: I've already asked on the list and other musicians use >>> Faust extensively; three (the most recent ones) of the seven performance >>> projects in my music PhD portfolio are entirely developed in Faust. And >>> many colleagues are asking about Faust lately. >>> >>> Yet, I see that they're often concerned about Faust being more for >>> engineers rather than musicians, and that it may only be good for sound >>> synthesis rather than composition. While this is partially true, I also >>> think that Faust can be an environment where both sound and music can be >>> developed. >>> >>> If the idea of Faust as an environment for both sound and music >>> synthesis is part of its development, then one question that a new audience >>> might want to hear is: >>> >>> Can Faust be used as an environment for algorithmic composition? >>> >>> This answer would then be followed by one or more examples of simple >>> compositions entirely developed in Faust that demonstrate how algorithmic >>> techniques can be implemented for formal developments besides sound >>> synthesis. >>> >>> If this direction seems to be important for the future developments of >>> Faust, I think that we could also think of a new Faust library, perhaps >>> "composition.lib", where some algorithmic composition techniques such as >>> chaos theory, L-systems, Markov chains, self-similarity, or adaptation, are >>> implemented including some basic music examples. >>> >>> >>>> >>>> 2/ Workshop Faust based projects >>>> There are now many projects that use Faust to varying degrees. The idea >>>> would be to have the developers of these projects do a 10mn informal >>>> presentation/demo of their project. We could imagine having a dozen or so >>>> projects present >>>> >>> >>> I really don't mean to do self-promotion and I'm only interested in >>> making Faust better or more appreciated, so I will mention my library in >>> case you find it appropriate for that purpose: >>> https://github.com/dariosanfilippo/edgeofchaos. >>> >>> The library is the developing environment for my music projects, which >>> investigate adaptive audio feedback networks for live performance. The >>> library includes information processing, audio processing, and mapping >>> processing functions, among others, to implement the recursive chain of >>> cognition-adaptation-transformation to model complex autonomous behaviours. >>> >>> The future development is to turn the library into an audio complex >>> adaptive systems generator following the paradigm of Kauffman's random >>> Boolean networks. >>> >>> Ideally, it should be as easy as having something like >>> >>> process = CAS(N, seed); >>> >>> where N is the number of nodes/agents, and "seed" is a float that feeds >>> a number of uncorrelated pseudo-random generators to determine, among other >>> things, the type of audio processing functions in an agent >>> (transformation), its information processing infrastructure (cognition), >>> and the positive or negative feedback relationships between information >>> signals and audio processing variables (adaptation). >>> >>> Hence, process(4, .743); and process(4, .744); would result in two >>> different systems, although the systems themselves are always >>> deterministic. >>> >>> But this is just an idea that I haven't started developing yet. >>> >>> Best, >>> Dario >>> >>> >>>> >>>> The two other workshops we have thought of are: >>>> >>>> 3/ a workshop dedicated to architecture files and how to design them. >>>> >>>> 4/ a workshop for the general public on writing VST plugins with Faust. >>>> >>>> Tell us what you think. If the first two seem interesting to you, we'll >>>> start collecting questions and projects very quickly. >>>> >>>> Thanks >>>> >>>> Yann >>>> >>>> >>>> *Yann Orlarey* >>>> Directeur scientifique/Scientific director >>>> >>>> >>>> orla...@grame.fr <x...@grame.fr> T : +33 (0) 4 72 07 37 00 >>>> GRAME - Centre national de création musicale >>>> 11 cours de Verdun Gensoul | 69002 Lyon >>>> www.grame.fr | facebook <https://www.facebook.com/Gramelyon/> | >>>> instagram <https://www.instagram.com/grame_cncm/> | twitter >>>> <https://twitter.com/GRAME_LYON> >>>> _______________________________________________ >>>> Faudiostream-users mailing list >>>> Faudiostream-users@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/faudiostream-users >>>> >>> _______________________________________________ >>> Faudiostream-users mailing list >>> Faudiostream-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/faudiostream-users >>> >> _______________________________________________ >> Faudiostream-users mailing list >> Faudiostream-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/faudiostream-users >> >> _______________________________________________ >> Faudiostream-users mailing list >> Faudiostream-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/faudiostream-users >> > _______________________________________________ > Faudiostream-users mailing list > Faudiostream-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/faudiostream-users >
_______________________________________________ Faudiostream-users mailing list Faudiostream-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-users
