(Actually you could reduce the number of history objects by having one history store the current button-selected mode as an integer value, which might be simpler…)
Also found a bug in that patch; the [and] should come afterr the [or]. This fixes it & shows the better mode-value based method:
----------begin_max5_patcher----------
1907.3oc0asziaaCD9r2eED5PQKfyBQR8L.oAAnG5k1BTzaIAFzRbsYhLkgD
85caPxu8xWxVxqrsjskW2KqW9dlONyGGMR7a2MxYZ9SzRGvaAeDLZz2tazHc
UpJFYKOxYA4ojLRotaNI4KVP4Bmwl1DzmD55ohjp53qVjuRjQE5Q3Zqkkp6W
9zu7FDppqKIhj4L9rIEzDgQLP9d26NF.CQ5eb0+fbu2E74syOiWM8PUce+t6
T+Y74pCbAs.rHOkBPcWYfcPY7ceMUFX2UF2NnLHuqtx7HIaEE7PduUHX7ATH
bfVChGtMG4DLkV7i1EWTKhaPUWeHmKJY+KUuxJIyTsY3hmWRMpfSIaFmj4LF
37PVNQpXet1DvIKz8y4CELUmLsHGhFs1Lo6GZ7iT+3aJfpgLpsg55PCjBUSD
dfjn6n6IfdDgnXEqcvC1B344rOTZKrzhtBcw0YbL9pMzVkfnWloqDhbN1oU6
CakorxkYjmqPnnqfhiOMEO13H6E0Q8FMz5MmtVpOuv6eFk+iNCFHmi3pbHDw
Z1CMFDwuDQZUy0SDsvpXVMSZ9yxnORKJY47Z8VhpKWVq5Q0FhBN9RtdhhFuo
JF2TEbSUEzGYUieaGIER0QH0kUEFu9mBp7HrdrEboUUEUldiwJR5s.EaQ4Rq
+pSZ4x6k.e0D3rEj7gAFBSn5mv.MXE.i1BSx84YY4IeklViVVtirjxY7kEzR
IGOQXUfMMmRefrJSLocpulsugVosFak1ajyrBVZNWIDM1NTUWsbRx.eiyPck
Q2CNYYKCVZwIwk8zXoTIWUNkTn1sllUmvTZcmmm0roMiKi9fv17RFmuCJJxW
t+FKXylefwNMW13hCM25VJmrhaZchzvPLoj7XSzVPxxrNqMm9mHb1BhfJXls
.j6lFobhTQmWlTjmk0PeMs7XKsjJMzSnqYoh4MNxR0hr6rkUFQNa1kSYynkh
l0IHyJaVSo3YCnWqpUSsNxSDzERpLwNcP5hvJEkyyWWZ6XkgVc.Xa3z0crqy
70n9CF.TSZveOeMPjCXRYip5Df.xrTXfuxym9I9+Lmp+O.qDjyydFPRDrGMA
NQ.KIEBVxpLRAvDOE6AvZJfTHiSjwAB4f0lO.Ca+aTLFiAe3O+McS54cNoDH
JHJ5KZpbBKE51JE4Exx5Y8s0k8LFmljuhqU.bsFpSBLoQuBp0qVCuaWB+PT8
UrERc4Aag9lH6FCvgt2ijk7Bq4g2drdipN.yxUN.aoqmyRlahoUtMn1MX726
zaD.dDD.CgVHvu9Q8t2BPveHU9RZF8qRan9q4tGQyQw5yphCeUz6FwyzTsmy
TNMOueMF1tFGDWeH6Odu8AHAlf4gAZnvya2Hbd0.j2C75OXDddfguMjeCXfh
u2+XfA5ZAF39CFAmGX3EAuGqXItEgCT+gC+yCNvw2vvAr+vg24AGVhzaOvPF
UCYgMjkSfAw8xvf.iU+DEbb5T2qOrbBbIvKEWxMMvbBrJnKEqxMMvbB7K3KC
+xMGrjLmvmQ6Md3elwoEpiTGC8MlKlbzc8BT6PQrKe.vjuB9Iv77rzdGwNN5
HQraRmjmM4Rnal.10OpcuMCvmaDpZXvCYRHIFdbqfqzwtDdZ+Aiyj7D44qB6
.Go8MBtchA4PO459vB7kAK7wuFwicH5AahLzrDRY98ehKJpmrIUtlrmxXx7g
JCS+7Z0fjMRxJnjzm2Lbve82aS8zR45SS0obRmqoeYu4ZxqS4Zxu2rWdGKSK
nHclVr6KvXOc1lB9+bJGv9WFSUX3MVJGd26NgGjBCuHA5XQCL914b8MYfrg6
Y+SGIJ7XNIXOiSBL7lKcjhB1Lv54Ttg0Qy3TZXa1KYCp2os7H.DDoiBFa9jD
hhprTd08XLOifBY5seC7RDHj8wCrgEdK73AmJo5YFJTbn9.+.Sd8ug3T+09S
ndIdPITTrAIf2NAEtR.LTnvIuf+nSzDGKXCiOguWrw0.dZFAaeO2JRs871K0
qtp81wjx7UEIUaYUO2CnofjRKEL9lW6+G2ni6zu7hTy2RQ2rX6qjE30QIScP
+0UzZYE2inIYOj1VedX.n3NJEp29xvIEccapEwcAKcYNiKr1xXWc7mvXyYGv
3VJY7gBB72Tp8Md2gQY6p2h5c7LbPdPWkB+gTJf8AKbGJovsONAClT32Uova
H2QP8wtXvvBbevhgRJ76J4nJ+Npcj8SKE4oepXYraAQ5ONCC4SUECjBf65lI
1+X7pHecnWdlOGPDN7kkvt1uiX+Mktl7pcWYCO1t0FkUG3s5aE12V5pFg.tO
QHzkcOUxT8G2nzPY442GWmgxAtq.Xki9fHDc1rb.Y06bD5G0RJvU6KXeUElW
eS8BH6mbja3lRWSR.Xe3.tpw6C6gYPG1APQA5mA1bvhoT2AZqYlolA99JfNs
6qPDt98O532WA3s18zv+zzaysRv5EcH0tVh41+cWROrlOquQW2070pwGl8ZO
lrvZAm+BPsqKDzuCqD5RrPdWqEBesVHzIsPFaictfJp0XmKlxNWJkWdgT1+k
QY2Khh9Rnz1EPQ45c22u6+nRjWXA
-----------end_max5_patcher-----------
2 Likes
Thank you @grrrwaaa
LATCH! Duh
I’m definitely running into that “I don’t know what objects are in Gen~” wall I bang my head against.
2 Likes
Hey, this possibly deserves its own thread but –
How are daisy projects using the Gen~ library licensed? Is there a separate EULA anywhere? or is it the same as with Gen~ in Cycling74 Max? (as described here https://support.cycling74.com/hc/en-us/articles/360050779193-Gen-Code-Export-Licensing-FAQ#link-0 )
Kind Regards,
Asher
@grrrwaaa
I know Versio support is forthcoming but is Terrarium being added also?
I feel like I could problmaybe write that in myself, if need be, but I’d rather not 
@as-her
As far as I can see It’s the same realm as Cycling74 licensing. So… until you make $200,000 with your Gen~ exported code then you are good, as far as money goes.
Honestly I need to re-check the licensing for this specifically but as standard practice it’s good karma to attribute code snippets where applicable.
I’m sure Graham can clear this up in a jiffy and I’m just wasting forum space.
As far as your other point goes, YES we need an Oopsy forum header aside from “Integrations” because I imagine there will be an increasing amount of activity moving forward this year.
1 Like
Agreed!
We’ll set up a dedicated Oopsy category today.
1 Like
The Oopsy category is live!
I moved all existing Oopsy posts into the new category.
1 Like
Hey there,
sorry if this has been brought up already, but is there a way to incorporate buffer objects? Apparently, Oopsy doesn’t allow buffer object. Also not sure on how to access sd card files?
Any ideas?
you can use [data] instead for storing values/recording input for granular verbs and beat slicing things
-at this time there is no way for [Oopsy] to access the SD card and load anything into [buffer]
however, this is being worked on by (not me)
Yep, the SDcard support is waiting on some changes upstream in libdaisy – it’s tracked in the github issues here SDcard: using to fill [data] objects · Issue #16 · electro-smith/oopsy · GitHub but nothing to report yet.
BTW probably this conversation should be in #integrations:oopsy-max-msp-gen
1 Like
Hi there! First time post for me here. I’ve recently started using a NE Versio module and I’m curious about getting into some Oopsy. I see some versio references in the codebase, though documentation doesn’t mention support yet and I can’t see anything in the max examples or gh issues. If it’s not ready yet, I’d love to help out where I can
Hi there,
If you can switch over to the dev branch of Oopsy, you’ll find Versio support is already there 
Graham
1 Like