Possibly reporting a small bug. I have my JSON file saved within the “/include” folder as Im using it with C++ inserts. When Flashing from MAX in Bootloader mode the flash fails and shows your second version of the bpatcher windows which reads:
created binary 102kb
The LED does not continue to flash/pulse and stays in “ready” mode.
You mentioned the JSON file (with “app_type”: “BOOT_SRAM”,) had to live in the root of the oopsy package but ive been asked to place it in the /include folder so the C++ inserts work.
I’ll answer the latter question first. After you flash the Bootloader Image, you can keep using the Daisy bootloader without needing to flash Bootloader Image every time. UNLESS, you go into DFU in FS Mode (by doing the usual button presses on Daisy) and, let’s say, flash a blink example into the internal flash. That’ll be the “exit”. If you want to use the Daisy Bootloader again, you have to flash the Bootloader Image.
As for the first question, I just want to double check if you were able to get those two features (Daisy bootloader and C++ inserts) working individually/separately? And it sounds like it becomes an issue to you when you try to do it simultaneously.
Could you share that JSON file? As well as the error messages. Thanks!
Thank you Takumi,
That reset to normal operation worked, thank you. I was able to get the C++ inserts working correctly when not in Bootloader Image mode. I’ll do some more tests and get back to you with error messages.
hmmm…are you sure ?
I just cloned that and i still get the same compiler error as before.
No need for access to the hardware to test…just make a new file from Template , choose Petal, uncheck Quiet and press Compile.
Versio also is broken still…
Yes, we’ll definitely want to distribute an example of C++ inserts in the near future. Thank you for bringing it up!
We’ll make announcements regarding the new Oopsy release and examples for it. We would greatly appreciate your waiting!
Hmm - I’m still having trouble getting negative CV values with this update. Is there anything else I have to change in my JSON to get negative CV? Ive changed the cv param to @min -1 instead of @min 0.
Thanks so much for your response! I guess I’m using the Oopsy I just installed from this page along with my custom JSON code for my homebuilt patchsm, but it still doesnt seem to take bipolar. My code is:
If you’re using the version of Oopsy cloned from the bootloader-additions branch, then the JSON file style will be different. And I’m not entirely sure how the range will work differently.
I recommend installing the current version (not the pre-release discussed here) and give that "range": [-1, 1] a try.
Or use the current style of JSON file in the pre-release and see if that helps.
OH, and you’re using [param cv2] even though you changed the range in the JSON for cv_1. That could be it too.