I'm building one right now :) How much would you be comfortable paying for such a device, given it has a stereo jack input, a stereo jack output, a headphone jack, and a USB-C connection?
They all use underpowered DSP chips from yesteryear. ESP32 is a great platform, and P4 is doing even better. I have a prototype running 2 A2-full profiles, along with 10 other effect blocks, on a P4.
I believe we are starting the age of personalized hardware, and Waveshare & co are doing a great job at bringing affordable, multi-purpose devices our way.
Would love to hear your experiences if you try out this build.
From what I read you need an external interface if you want to use the board. The cable is just passing the audio signal through USB if I'm not mistaken (i.e. no Analog-to-digital conversion happening there--mac doing it for you I guess)
Not clear to me at all, but I just did a bit of a google to follow up on a thought — do you mean your hypothesis is that it's using the USB-C-specific Audio Accessory mode?
I was not aware that the Mac supported Audio Accessory mode. And the blurb for these cables talks about a sampling rate, which suggests there's a DAC in the USB-C connector end.
(Works well on the Mac, anyway — it is too much fun simply plugging my lap steel into my Mac in a way that would have been complete fantasy when I first started playing electric guitars.)
ETA: OK so it's always time to play guitar, and I plugged it into the Mac, which reports:
Product ID: 0x126e
Vendor ID: 0x3302
Version: 0.01
Serial Number: 3302126E250214
Speed: Up to 12 Mb/s
Manufacturer: TTGK Technology
Location ID: 0x14400000 / 1
Current Available (mA): 500
Current Required (mA): 100
Extra Operating Current (mA): 0
Which suggests it's one of these DAC-in-connector boards:
It appears as an ordinary USB Audio device in the Sound panel. My likely ignorant surmise as to why it doesn't work on the iPad is that it also presents a (disconnected) output device and this is confusing the iPad. So perhaps it kind of is working but I can never hear it…
Ah, the cable arrived and I tried it. The problem is, the cable only works with USB2.0, High Speed devices, but ESP32-S3 is only USB1.1, Full Speed, so unfortunately it doesn't work.
Thank you! I am surprised it doesn't work with iPad Pro. They don't ship to Germany, otherwise I'd buy one and try. If you have an ESP32-S3 device, I can help you with it if it doesn't work.
Sorry — I should have added that there is a variation of this device that (allegedly) does work with the iPad Pro, so if you have time to amend your order…
I don't know why this one would work and the other not, but my guess will be that this one has a chip that doesn't offer up a disconnected output device as well (which would be my totally uneducated guess as to why my iPad hates the other cable and the Mac, which has switchable output devices, doesn't)
There was an ESP32 board I wanted to try (below) but it looks like it's a 1.8" sibling of the one you are using so maybe I'll just track down the one you're using.
Of course, what we are missing here is audio output :))) how are we going to listen to it? This S3 board has a tiny speaker, and I think for a demo it will work just fine, but :))
S3 doesn't have enough floating point processing power, so what I do is to split the model in two, run the model in series, and represent floating point values as block floating point, essentially compressing the floating point representations.
The null test peak sits at -60dB in the worst case, in 193 different NAM profiles I tested, which is basically inaudible. You can listen to the different profiles here https://playtaurus.com/blog/running-nam-a2-full-natively-on-... and listen to the difference between A2-full and A2-lite, vs A2-full and my approach.
One small clarification, this approach isn't really a "model conversion". Current pedals on the market quantify the entire model, so you are essentially running a separate model. Here I use the same weights, but only change the floating point representation. That's why the difference to A2-Full is basically inaudible. Mooer's NAM conversion, for example, has a null test peak at -8dB. They also need to do this because of the 44.1kHz conversion, so it's incomparable.
Depending on your guitar interface, it's around 4-10ms. Some interfaces have really unnecessary buffers, accounting for very old and low power devices. iRig HD X has an unused buffer of 4ms in its firmware that I patched. As atoav said, you don't really feel it, especially if you play on headphones, it's like sitting 1 meter away from the speaker.
Because I wrote Gea Stack :) and CoyoPedal also serves the purpose of a demo app for Gea. The DSP is native code, most of it is in assembly. The UI is portable for any device. One small correction, Gea doesn't have a TypeScript runtime, it's all compiled to C++ ahead of time, so effectively all the code that runs on the device is native.
ESP32-S3 is a great USB host. I have a custom version where I use a Daisy Seed 3 as the ADC/DAC (it uses I2S for audio, not USB) that I built with around 4ms total latency. If you turn off the amp model (which is pointless, but) it's around 2.6ms. I also patched the iRig HD X firmware so its analog latency is around 1.2ms, practically achieving the same performance as the custom Daisy Seed 3 interface.
It's the author here. AMOLED is beautiful to look at. And you can stick this device on your guitar. Having said that, the same code can be compiled to any ESP32-S3, even headless boards, to use in a custom pedal (like the ones with Daisy Seed 3). CoyoPedal uses Gea Stack that allows us to target any device, including macOS and even the web, https://coyopedal.playtaurus.com has the exact same DSP and UI code built for WebAssembly.
Ah damn, this is a leftover from literally the first day of our Android target build. Of course it's native for Android, too. Will fix it ASAP, thank you!
Amazing questions, thank you for the careful read!
We should ship a compatibility matrix... at some point we were hoping to report test262 coverage for ECMAScript compliance, but we had to prioritize the release. Of course any of the typical web APIs work, including localStorage, and even so far as the Web Audio API (and we're working on WebRTC to make it cross platform. It's especially interesting to be able to build real-time communication apps, say, on an ESP32-S3, with just the web semantics).
In short, most app code stays inside the portable model. You need to know the target when you use host APIs that are constrained on small devices: blocking I/O, memory limits, file sizes, and of course you can combine it with native code for the target. I'm building a guitar effects processor, for example, where the UI is powered by Gea Stack but all the audio processing happens natively (https://github.com/dashersw/coyopedal).
On AI: yes, it's mostly me plus agents for the compiler. We have a team at Coyotiv that helps with everything else. I use Claude Code with Claude Opus as the main model and Sonnet subagents for parallel work, with a fair bit of Fable. I also combine this with whatever GPT model is available over Codex. During the past 6 months I've started working on the compiler, I've changed several model versions :)
What makes AI perform on a compiler:
Hard gates the agents can't argue with, like a diff gate that names every program whose output changed, plus conformance sweeps, a diary that captures past failures so they don't repeat, and treating a passing exit code as insufficient and the outputs get checked against Node.js behavior and unit tests.
The biggest differentiator for me is, even though I'm a pretty relaxed manager for humans, I'm a heavy micro-manager for AI. I read its thinking tokens and its code live and as soon as I spot something I don't like, I intervene and guide the model to the output I want to see.
It wasn't easy, Gea Stack in total I think burnt more than a million dollars in AI credits, and I've been working on it literally non-stop for 6 months.