I just uploaded a short video demonstrating what I'm doing. I tested with GPT mini 5 and Sonnet 4.5, I will test with all my 20 models.
https://www.youtube.com/watch?v=atRLCZ2IBF0 Debugging on for demo. Currently the faust service seems offline/broken/502/ certificate errors etc, I can't get a VST download. MICHAEL CHOURDAKIS, PhD DSP & ARTIFICIAL INTELLIGENSE SOFTWARE ENGINEER www.turbo-play.com Στις Τρί 17 Φεβ 2026 στις 4:28 μ.μ., ο/η yann orlarey <[email protected]> έγραψε: > Interesting. Do you already have a testable prototype? > > Le mar. 17 févr. 2026 à 15:05, Michael Chourdakis <[email protected]> > a écrit : > >> Thanks for the update, my idea is not necessarily a full editor but >> something like what I have for image effects: Copilot instantiated -> User >> says "make it darker" -> Copilot generates HLSL code -> user can preview >> and edit if it wants using a simple editor effect applied. >> Similar for faust, say -> Copilot effect -> User says "reverb hall with >> distortion" -> Copilot generates Faust code -> user can preview and edit >> with a simple editor -> applied. >> The difference in HLSL is that copilot can take image input to modify the >> code, where in audio there is no input. >> >> >> MICHAEL CHOURDAKIS, PhD >> DSP & ARTIFICIAL INTELLIGENSE >> SOFTWARE ENGINEER >> www.turbo-play.com >> >> >> >> >> Στις Τρί 17 Φεβ 2026 στις 3:07 μ.μ., ο/η yann orlarey <[email protected]> >> έγραψε: >> >>> Hi Julius, Michael, and Stephane, >>> >>> As mentioned by Stéphane, we are currently developing this kind of >>> environment, in particular FaustForge: >>> >>> https://github.com/orlarey/faustforge >>> >>> The core objective is to reduce friction between AI-assisted code >>> generation and actual DSP validation: write or refine Faust code, hear >>> results, inspect generated artifacts, and iterate quickly : >>> >>> - Fully Dockerized: setup is reproducible and isolated, so you can run >>> the same environment on any machine with minimal host dependencies. >>> - Live workspace mode: `.dsp` files are watched automatically; creating >>> or editing a file immediately updates the active live session. >>> - Continuous recompilation: changes are picked up in near real-time >>> while staying in the same working view. >>> - Multi-view synchronization: Regular UI, Orbit UI, and remote control >>> all reflect the DSP parameter state consistently. >>> - C++ inspection workflow: in the C++ view, you can now choose Faust >>> compilation flags using reusable presets, making it easy to compare >>> generated code under different compiler options. >>> >>> AI-friendly documentation is key in this type of project... >>> >>> Cheers, >>> >>> Yann >>> >>> Le mar. 17 févr. 2026 à 14:00, Stéphane Letz <[email protected]> a écrit : >>> >>>> We already have: https://github.com/grame-cncm/faustbrowser-mcp (my >>>> try..), and Yann more sophisticated version: >>>> https://github.com/orlarey/faustforge >>>> >>>> More to come probably... >>>> >>>> Stéphane >>>> >>>> >>>> > Le 17 févr. 2026 à 13:29, Michael Chourdakis <[email protected]> >>>> a écrit : >>>> > >>>> > I'm currently experimenting with Copilot to see If I can create an >>>> AI-driven faust editor >>>> > MICHAEL CHOURDAKIS, PhD >>>> > DSP & ARTIFICIAL INTELLIGENSE >>>> > SOFTWARE ENGINEER >>>> > www.turbo-play.com >>>> > >>>> > >>>> > >>>> > >>>> > Στις Τρί 17 Φεβ 2026 στις 2:21 μ.μ., ο/η Julius Smith < >>>> [email protected]> έγραψε: >>>> > Hi All, >>>> > >>>> > Interesting exchange with Claude just now: >>>> > >>>> > Me: ❯ Do you already know Faust well enough to write it, or should we >>>> make a Claude Code "skill" for more Faust expertise? >>>> > >>>> > Claude Opus 4.6 [Thinking]: >>>> > >>>> > ⏺ I know Faust reasonably well from training -- the composition >>>> operators, standard libraries, how compute() loops are structured in >>>> generated C++, >>>> > etc. But I'd be more reliable with a skill, for two reasons: >>>> > >>>> > 1. Subtle semantics -- The interaction between ~ feedback, <: split >>>> fan-out rules, and partial application can trip me up on non-trivial >>>> programs. >>>> > Having the primer in context would catch those. >>>> > >>>> > 2. Project-specific Faust→C++ patterns -- Your faust_cpp/ directory >>>> has a specific style: JGFaustLib.h utilities, hand-optimized biquads, the >>>> way >>>> > mydsp::compute() structure maps to native classes. A skill could >>>> load both the language primer and your project conventions so translations >>>> stay >>>> > consistent with what's already in faust_cpp/. >>>> > >>>> > My recommendation: make a skill. It would be lightweight -- just >>>> load FAUST_PRIMER.md plus a project-conventions section drawn from >>>> > faust/JGFaustLib.h and an existing example like JGCabinet. Then any >>>> time you ask me to write Faust, /faust would put the right context in the >>>> window. >>>> > >>>> > [I attach my FAUST_PRIMER.md, ~12.8kB, written by Claude from my >>>> teaching tutorial, but note that it is NOT COMPLETE! It's just what I >>>> regularly use. A better primer would condense the Faust Quick Reference >>>> manual. (Claude, Codex, or Gemini would all do a good job on that).] >>>> > >>>> > Cheers, >>>> > Julius >>>> > >>>> > P.S. I've written ~0 code in 2026, but I've managed a LOT >>>> > >>>> > -- >>>> > AI has taken my job, but only I know what it is. >>>> > _______________________________________________ >>>> > Faudiostream-devel mailing list >>>> > [email protected] >>>> > https://lists.sourceforge.net/lists/listinfo/faudiostream-devel >>>> > _______________________________________________ >>>> > Faudiostream-devel mailing list >>>> > [email protected] >>>> > https://lists.sourceforge.net/lists/listinfo/faudiostream-devel >>>> >>>> >>>> >>>> _______________________________________________ >>>> Faudiostream-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/faudiostream-devel >>>> >>>
_______________________________________________ Faudiostream-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/faudiostream-devel
