Custom Seed Targets in oopsy v4

Integrations Oopsy / Max/MSP Gen~
4

Looking into it.

Hmm, I can run the simple/pod/versio examples with no problems here.

Tried with both a fresh checkout of v0.4.0-beta and with the current git version of oopsy.

simple:

  • no “Cannot read property ‘OOPSY_IO_COUNT’ of undefined” here.

pod / versio:

  • no “Cannot convert undefined or null to object”

(The user example further down the page is the older, now deprecated JSON format. It looks like changes elsewhere needed for the newer JSON structure have made the old one no longer work. I have updated the wiki page accordingly to mark it clearly as no longer supported.)

I wonder if something didn’t quite work with the install?

Another thing you can try is running the node script directly from a command line. (This will require installing Node.js – you can brew install node if you don’t have it.)

E.g., inside /packages/oopsy/source, run:

node oopsy.js /Users/colorone/Documents/Pedal_Enclosurea/001_digital/oopsy/json/daisy.test.json 48kHz block48 /Users/colorone/Documents/Max 8/Packages/oopsy/examples/reverb.cpp

Should look something like this:

grrr:source grrrwaaa$ node oopsy.js seed.versio.json ../examples/reverb.cpp boost 48kHz block48
using build tools found in /usr/local/bin
Target seed_versio configured in path seed.versio.json
Building to /Users/grrrwaaa/Documents/Max 8/Packages/oopsy/source/build_reverb_seed_versio
Will upload from ../examples/reverb.cpp by writing to:
        /Users/grrrwaaa/Documents/Max 8/Packages/oopsy/source/build_reverb_seed_versio/reverb_seed_versio.cpp
        /Users/grrrwaaa/Documents/Max 8/Packages/oopsy/source/build_reverb_seed_versio/Makefile
        /Users/grrrwaaa/Documents/Max 8/Packages/oopsy/source/build_reverb_seed_versio/build/reverb.bin
oopsy generated code
oopsy compiling...
oopsy created binary 51KB
oopsy flashing...
...
...etc.
1 Like