I'm guessing that the AD part is just being used as a CODEC even though it apparently has some DSP capabilities?
[...]
It can be both really, from hardware perspective I kept both options open. the AD can do all the processing while being controlled and programmed from the Teensy (or not, it can also run standalone via the on-board EEPROM) using I2C but the audio can be routed to the Teensy as well to be processed there (or both are performing DSP operations, why not?) The idea to use a AD stems from a Cab Sim project by Nathan but I wanted to experiment with Faust as well so I thought 'why not make a hybrid that can do both?'
[...]
I'll keep watching this thread. When you said that the Teensy could be expanded with additional RAM, how is this done? I'd sorta like to have 1 or two seconds of delay RAM available.
Via SPI. It can support both RAM and flash on the same (and it's something I realized today, I have to add a RAM chip as well and not just flash

)
The Teensy Audio Adaptor shows the schematic:
https://www.pjrc.com/store/teensy3_audio.htmlI'm also wondering about the ability to support a network stack, e.g. so I can send OSC messages from a tablet. I suppose that one could map OSC to MIDI in the PC but that starts getting pretty complicated.
The Teensy 4.1 also has a Ethernet PHY on-board. Have not really looked into it though as I'm using the 4.0 (which is smaller and I'm aiming for a 125B).
I'm not really interested in building or debugging things any more (bad vision mostly, followed by "been there, done that").
DL
Me too haha but in my case it's just a matter of being too lazy hahaaha

I'd rather spend a little more time designing than to have to fix stuff afterwards

I also selected the components such that I can let do JLC the assembly

(jayyy Chinese datasheets

) (except for a couple through holes and the pedal connectors).