Branch Manager - Runtime Patch Selector

Patching
21

Sure, just (save a copy of and) open the branch manager.axp then IIRC go inside the sub patch and delete the string that says “branch manager”

I was playing around with last patch recall, it would involve either

  • leaving a text file on SD card, then we’d almost be back to patch bank mechanism

or

  • reworking the display code so you only need the Branch Controller not the startup patch

I am hoping the latter will work somehow, the challenge is to block off any display action of the running patch so the controller can display the list without being constantly overwritten

22

Might building Branch Manager into the display object itself simplify things?

Especially given every patch optimised for Gills/Big Genes really needs a Display object, anyway (if only to clear the display after any previous patch).

23

That’s a good idea actually. No more controller object and uploading as startup. Only drawback would be having to pay the Manager’s high salary at all times: hundreds of bytes for the string buffers and manager access to the SD card functions.

But maybe still a reasonable price to pay. Companies are starting to realize that all their employees are worth more than minimum pay.

24

You could keep the current display-only object for those who don’t need preset-management.

Or add an option you can turn off, and the preset-management code will be compiled out of the patch binary.

25

Indeed! By the way there is a ksoloti/[device]/clear display object which does just that during patch start, then stops consuming resources (as the full-featured display object would do). Only useful if the newly started patch does not use the display, of course.

1 Like