Oopsy: Daisy from gen~ in Max/MSP

I've really been looking forward to announcing this! Oopsy is a way to embed the precise flexibility of Max/MSP's gen~, from microtemporal scheduling to single-sample feedback loops, into the hands-on flexibility and performative happy accidents of modular analog and digital hardware, using Daisy-enabled devices.
Where:
Get Oopsy from github.com/ele...
Get Max/MSP + gen~ from cycling74.com
Get Daisy from www.electro-sm...
Oopsy on Cycling '74 forum: cycling74.com/...
Oopsy on the Electrosmith forum: forum.electro-...
Oopsy on MW: www.muffwiggle...
Oopsy introduction on C74: cycling74.com/...
Background: I got excited about Daisy hardware when I heard about the kickstarter, and backed it immediately, as I'm really fascinated by the possibility of putting the capacities of digital signal processing and control in gen~ (from microtemporal scheduling to single-sample feedback loops), into the midst of modular analog and digital hardware, with its hands-on flexibility and performative happy accidents. The folks at Electrosmith kindly sent me some other Daisy hardware, and in spare moments over the past months I put together this Oopsy package to streamline the mapping of gen~ to the Daisy hardware. It's now open sourced on the ElectoSmith Github, and I'll be continuing to add more features, hardware support (e.g. Noise Engineering's Versio), examples, and posting videos here.
What is gen~? An open-ended domain of audio-processing inside of Max/MSP, which regenerates its optimized machine code with every edit you make, allowing a variety of things that are difficult or impossible to patch normally, like sample accurate granular scheduling and single sample feedback for complex filters. Also the code can be exported as C++ for use outside of Max for embedded devices etc. Also gen~ was kind of my PhD thesis :-)
What is Daisy? A fantastic kickstarted DSP platform that runs in Eurorack, guitarpedals, synths, etc.-- with a few commercial users already like Noise Engineering Desmodus Versio, the QuBit Surface & Data Bender, etc.
What does Oopsy do? It snoops your Max patch, exports and snoops and the C++ code of each gen~ it finds, and wraps that up in a bundle of code to make it work with the Daisy with some nifty mappings. So, every time you hit Ctrl-S to save, it can rebuild & upload to your Daisy hardware.
Like, subscribe, etc. etc. to hear more about it :-)
/ grrrwaaa

[@markparfitt]

Thank you!! Really helped me demystify some of MAX / daisy world. Would love to see more if you could.

[@aeko]

This is so wicked! Thanks for making Daisy so much more approachable for Max/MSP users.

[@Raumweiter]

Incredible patches

[@anthonypalomba351]

Absolutely amazing! I think this module alone may make me take the eurorack hardware plunge.

[@KLI333-9]

This is amazing! Thank you for making this, I am looking forward for more tutorials.

[@Boodaman]

Thank you. Can you quickly explain how do you manage the screen infos & animations?

[@grahamwakefield]

Hi -- all the screen interface (scopes, param controllers, app menu, etc.) is generated automatically by Oopsy, according to what you have in your patcher.

[@Cloroqx]

Ordered one. This is incredible.

[@dragonstuff1983]

I have no idea what you are saying, but this looks amazing!

[@grahamwakefield]

... is the microphone bad or my accent weird ? (genuine question!)

[@dragonstuff1983]

@@grahamwakefield No, not your accent. It's the subject matter that is beyond me.

[@Paradiesgestalter]

interesting! specially the fast upload inside maxmsp! ?> can the display adapted or used for USER code? (like show the waveform of a buffer) - short: can i use normal C++ in combination with Ooopsy? (aka build my own motherboard for daisy, use my own ssd1306-build a interface, load samples from sd into a Buffer which is accessable for oopsy, and make me a one shot sampler? (recording data, buffer data, and doint gen~ stuff with it)...... or in short: can i combine C with MaxMsp.... thx for tips.

[@AnugrahPrahasta]

Dear Mr. Graham, very interesthing to use Daisy + Oopsy to build Audio interface, if you could and want, can you make some tutorial about it ? many thanks

[@laserspaceninja]

I am throwing money at the screen.

[@luisguerra217]

NEED ONE ASAP!

[@bobrogue]

YES!!!! Thank you!

[@danielreizinger548]

Is midi input well supported now, if I wanted to use the daisy seed with midi serial alone to control it? Thank you

[@sxastewxdsxastewxd7578]

wow great work!

[@fuzzpope]

Brilliant, thank you!!!

[@impulsecoupling]

This looks super cool. Are you guys continuing development? Looks like the last commit was mid Dec 2021.

[@grahamwakefield]

Yes indeed development continues! The last development push in December focused on support for the Daisy patch submodule, including the new patch.init() hardware, but there's more updates on the way.

[@impulsecoupling]

@@grahamwakefield nice! Great project, thanks for the hard work.

[@alexfortunatomusic1951]

Would I be able to flash to the Daisy within MaxforLIve? Or does this only work within Max/MSP standalone?

[@grahamwakefield]

As far as I know, gen~ requires a full Max license in order to compile (and export) code.

[@bobrogue]

Was wondering the same. Cross grading for a full version of Max/MSP if you're using M4L is about $200. I think Graham has demonstrated that it's totally worth it with this video.

[@MatheusLeston]

thank you for the video! I got my daisy a few months back and I was waiting to get into gen~! but as far as I understand, for not it is only available for those "standard" devices, right? not for custom hardware, only presets for the kits

[@grahamwakefield]

Support for custom hardware is in the works, but I focused on the "standard" targets first since that's what I have to test against!

[@MatheusLeston]

@@grahamwakefield Thanks for the answer! Any ideia on when this will be available? My situation is the exact opposite: I don't have any of the standard devices! Hahaha.

[@grahamwakefield]

@@MatheusLeston It's being tracked here: github.com/electro-smith/oopsy/issues/34 - I think most of the necessary infrastructure is already done in the `dev` branch. At this point it needs some actual custom platform testers to find out if there's anything missing!

[@MatheusLeston]

@@grahamwakefield Amazing! So far I haven't built anything with it yet, but let me know if you need any help!

[@grahamwakefield]

@@MatheusLeston Great! The best thing is probably to post questions etc. on the electrosmith forum (link in youtube description) when you do!

[@mathieumorel448]

Hi! So it can be stereo, polyphonic, can it also read long stereo audio files? How many "instances" can be played simultaneously? What's the CPU limit, is it comparable to the er-301 in this regard? Thanks a lot

[@mathieumorel448]

Hope you're alright with me questioning.. did you encounter any undesirable noises? From screen, encoders, rejections, any reaction to neighbouring modules?..etc... Many many thanks

[@grahamwakefield]

@@mathieumorel448 I don't have an ER301 to compare unfortunately, but you can see more info about the core processor and other capabilities here: www.electro-smith.com/daisy/daisy The Daisy seed itself is stereo in & out, the Daisy patch expands this to quadrophonic in and out, and the latency can be sub millisecond. Number of instances/voices etc is all dependent on the complexity of the algorithms yu put on it. I've had quite complex granular and reverb algorithms running at 48khz without hitting the cpu limit, for example. I haven't personally heard any noise from encoder or display etc. I recommend sking on the electrosmith forum.

[@mathieumorel448]

@@grahamwakefield many thanks Graham, that's kind. From your answer it sounds like I can dig the forum 😉, I shouldn't be desapointed! Cheers!

[@Owoshima_]

I've been hyped for quite a bit, and have spent an all-nighter making a nice oscillator patch to try out. While I wait for my Patch to get here, and my email registration for the forums, I have 1 question. 1) What is the current status on being able to load samples from the SD card? (as Wavetable stuff would be amazing)

[@grahamwakefield]

Great to hear! In answer to your questions: 1) SDcard support will come in the next couple of weeks; I've been holding off adding that while some changes were happening upstream in libdaisy. 2) The audio ins & outs are AC coupled

[@Owoshima_]

@@grahamwakefield Alright good to know, I've got a neat wavetable oscillator, and currently using Buffers to load them.

[@juliencautru7222]

This is great ! What is the current status on accessing the SD card from gen~ ?

[@grahamwakefield]

There's currently basic support for reading WAV files from the SD card into buffer objects, but we hope to expand this further in future.

[@juliencautru7222]

@@grahamwakefield awesome

[@neutron7]

This is really cool, are the compiled files a single hex or whatever that you can save or send to a friend with a daisy patch?

[@grahamwakefield]

Yes, a single binary -- even the "multi-app" patches create a single binary.

[@kobi-kobsen]

Fuck yeah :)