It’s been a long time since there was an update. I know Oopsy is mostly sort of bug free in the bootloader-additions version but not quite.
What is left to be done and are there plans moving forward to continue the work?
Plllllease don’t make me learn C++ 
2 Likes
I’m with you! Oopsy is just too good. An update would be wonderful.
1 Like
yes. +1 for oopsy
1 Like
!!! +1 for oopsy !!!
I can’t talk about what, but there are things happening that some of us are testing that will make you folks very happy.
4 Likes
RNBO code recompiler?
That would be difficult, but awesome.
1 Like
Just hearing that is making me very happy! Thank you!
1 Like
pls end the torture! 
I love gen~ but adding the convenience of RNBO could bring things to a next level. I’m sort of waiting for this since I read about it. GitHub - Cycling74/rnbo.example.daisy: Example of how to use RNBO code on the Daisy Audio Platform
That would make me extremely happy and I guess it must have been “around the corner” for ages now 
I just hope the patch_sm usage is well documented. At this moment I’m struggling to define a MIDI in port for it. Can’t find any examples, everything I come across is for the seed… 
Let me know if there is the need for any patch_sm testers. I have some time and will to make it work.
1 Like
Is there any guidance on whether to get started in Oopsy or RNBO? I don’t want to put the money and time into learning both. It doesn’t look like either repo is active so I’m wondering if there are still things happening behind the scenes?
Looks like the new RNBO release has improved support for Daisy and they reference their own fork of Oopsy so I’m guessing that the wheels are in motion behind the scenes. Exciting to see!
1 Like
This is amazing! Can’t wait to dig in.
Of course, I’ve been so spoiled by Oopsy being so easy. The command line stuff is tough for me to get right…
This is amazing. I can not fathom why Electro-Smith doesn’t keep us in the loop for advancements such as this.
2 Likes
I’m getting updates about the Daisy-support for RNBO at the same time as the community here actually 
Awesome to see that there’s been a development! Been meaning to dive into RNBO.
Hello I hope this is the correct place for this post. Been wanting to bring some of our Max ideas to hardware/eurorack and have 0 code expereince and still not clear of a few things after online research. I am a bit confused as to which path to take, I would prefer to keep everything just in Max - NO GEN if possible. If that means purchasing RNBO that is fine. Right now I see Oopsy, Eurorack-Blocks or RNBO as possible paths to take, is this corect or am I not understanding some fundamental thing about this workflow. Thank you for your time and if there is a better place for someone getting started please let me know and I’ll jump over there.
Unfortunately “vanilla” “normal” Max/MSP has no path to compile or port a project. You are best served by gen~ and RNBO~. As far as I know, the RNBO integration is unfinished but will be done “soon” and you “can” implement it yourself with some digging and mucking about with the sample RNBO GitHub example maybe. Converting from RNBO to gen and reverse isn’t entirely complicated but is also not entirely simple where some objects/processes are concerned.
Thanks for the reply, it’s been hard as a lot of the info around this seems to be geared towards people with better understanding of the Daisy ecosystem already. Sounds like I should hold off until the RNBO integration is completed and then at that point hopefully some beginner guides will be created. At least I’ll save a bit of $ this month : )
I’m assuming you’ve read Getting Started - Daisy ?