Digital-Larry

I asked over at the Faust Slack channel and the guy from Grame said (after looking briefly at the FV-1 instruction set) that it would require a custom backend assuming it's even possible. Which doesn't sound like a ringing endorsement. I think the missing link here is for the other ASICs like fxCore, CoolAudio V1000, etc. Faust is portable to ARM and other general purpose CPUs. They are also working on a project to implement Faust on FPGAs which gets super low latency. My question as always is "how much processing can you get on that"? It remains to be seen.

Yeah maybe that would work. I learned Faust online at Kadenze and have participated on the Faust Slack channel and made a few additions to some build files for making VST3 plugins in Juce. Boy that was a year or two back! I also compiled some Faust to the ESP32 and hacked in OSC support. I was mostly writing in native Faust and debugging in the web IDE although there is at least one block based graphical tool.

I'm really not sure how you would map Faust to something like the FV-1 though - its instruction set is designed to do a handful of structures really efficiently.

I'm not a hardcore CS, I'm just the guy that wrote SpinCAD Designer on top of ElmGen. You could start with an existing graphical editor. I'm all in favor of not reinventing stuff if possible. I think Teensy Audio Tool forked node-red. I spent an hour maybe looking at it and it would take more time than that to figure out what they did. Notably, node-red blocks have 1 input and 1 output. Teensy audio blocks have multiple inputs and outputs possible. Although not necessary, I like the "audio in one dimension and control in the other" aspect of SpinCAD Designer.

Then you gotta have code templates for each target and then also some per-target means of stitching it all together. I only know SpinCAD Designer but that involves doing a topological sort of the model and then walking down it, allocating FV-1 registers and RAM as you go. My recollection of the Teensy audio tool is that it generates function calls for C or C++, which obviously wouldn't work for chips like fxCore or FV-1.