Audio input

[dromer]

It is unfortunate that the platform wasn't made with audio input and effects processing in mind.

Does anyone have a suitable recommendation on how to get an additional codec with input?

(and maybe a hint for a future v2 ;) )

[bwhitman]

I would start by building a breadboard or breakout board Tulip but replace the DAC with a DAC+ADC chip, something like the SGTL5000 on the Teensy audio board? https://www.pjrc.com/store/teensy3_audio.html

The next step would be to turn on i2s audio in in the audio setup code of Tulip. We do this all in C here:

tulipcc/tulip/shared/alles.c

Line 151 in c13accf

amy_err_t setup_i2s(void) {

You could grab the audio buffer during rendering of the audio output around here :

tulipcc/tulip/shared/alles.c

Line 73 in c13accf

void esp_fill_audio_buffer_task() {

And pass that buffer to whatever you want, either in C to a third party effects library, or make it available as python callbacks for people to write live callback effects or to sample audio to disk/RAM for the Tulip sampler.

Re "v2": no osborne effect allowed here! :) tulip is brand new and I really want to focus on getting a great community going on the existing hardware. we're just getting started! building your own and getting audio input on it is awesome and I'd be delighted to help document it once you get a prototype.

[dromer]

Thank you for the input, and of course I didn't mean to steer into an "osborne effect" ;)

I'd probably find a different codec as imo what the Teensy audio board offers is really sub-par.
Good to know that it's at least possible!

[bwhitman]

Cool let me know what chip/board you find! I'm happy with the PCM5101 as far as audio quality/cost goes. I think you can just use a second in-only i2s chip and share the MCLK pin, but don't quote me on that.