Hi,
Custom JSON files are still a work-in-progress (Oopsy is still in beta…) so there’s no documentation on that yet. There’s probably a few assumptions in the genlib_daisy.h file and oopsy.js to work around yet. We’d need to add a “custom” target option in the Max interface, ensure genlib_daisy.h can work with the daisy_seed.h directly, and fill in the gaps of what a custom JSON can contain. Part of my challenge is not knowing what kinds of code would be needed to be added for a custom seed platform; it’s a less familiar area for me. But I’d be happy to work through ideas if you can help. I added an issue for this on the github (issue 34) – would link it here directly but the forum settings won’t let me
Graham