JS works very fine to create/remove bpatchers and load dynamically some .maxpat into them.
I just met a strange problem: the same code & maxpat loaded from a script into a subpatcher, (the bpatcher is created into that subpatcher) doesn’t work.
Doesn’t work mean:
- it correctly creates the bpatcher, size it, place it etc)
- the bpatcher is empty
@name is used as usual in my parent patcher but in the subpatcher, it seems there is a path problem (no complaints in the max window, btw)
making a replace with the ABSOLUTE path after the newdefault works.
I forgot to say: I’m designing a max for live device so I need make collectives & to load dynamically .maxpat from inside collective
any clue to avoid to use ABSOLUTE path inside JS?
I can deploy hard stuff in my patch to find the path but it wouldn’t be nothing more than a workaround :-/
Hi Julien how is your project going.
This has just struck me as a way of dynamically creating live objects.
Create object dynamically is more expensive than loading all at the same time and using a powerful routing system in order to use only those you need at a particular moment.
Almost all my architecture patches work like that now.
I did the same thing today, call bpatcher since my main patch, a suggestion :
in the patch used as bpatch, create your presentation mode interface with the parameters you wish to use by placing them in the top left patch …. Back to your main patch, load the bpatch and maybe the magic will effect ….
C74 RSS Feed | © Copyright Cycling '74