I've been working for a while on this rbpi5 pedalboard using NAM tested v0.1.0 on rbpi5 8gb and working pretty well and i'm pretty happy with the result 😁

Feel free to test it, it should be able to run standalone on x86 and aarm64, Ive mainly tested it in QEMU x86 and Rbpi5 with a focusrite.

Integrated with Tone3000 to download directly profile from OpenRig

Open to suggestion, features requests and issues.

Next step for me are packaged OS updates and Hardware GPIO to make it look a real pedalboard.

On perf side, on rbpi5 it boots in ~3sec, I can chain 6-7 NAM profile easily without any drops.

https://github.com/Siryu6/OpenRig

It baffles my mind how the M-vave Pocket Amp (probably their cheapest?) can run NAM A2 Lite native, while the budget devices from Valeton, Sonicake, Hotone, Mooer, Soran, etc can't, and have to do NAM conversion. This is even running 44.1kHz which I initially thought was one of the reasons why others have to do conversion.

Anyone have any clues what's happening here? One thing I noticed is that M-vave devices generally have higher latency, which sometimes can go up to 7-10ms while others are usually 3-5 ms. Is this a factor?

Here's the video for reference:

https://www.youtube.com/watch?v=2S7Auzy9nqg

As a comparison, the Valeton GP-150, one of Valeton's more modern budget units can run NAM A2 Lite native but it uses 70% CPU so it already limits the number of effects you can use. If you want to use the full chain you have to do NAM conversion. Is it just a case of inefficient firmware or is it something else?

I mean this is why we need to allow people to share their work! Look at the innovation going on here it’s magical 😱