M4L bpatcher keeps pointing to the wrong file
I'm working on a device that contains bpatchers.
I have several versions of the contained patcher, but I explicitly point to the correct version (I save it in the same folder as the main patch to avoid confusion). Every time I save my device and reload it, it loads the wrong version, located in the M4L "Project" folder (/Documents/Max 9/Max for Live Devices/DJ_MLR 4.00 Project/patchers/cf_deck.maxpat).
It's driving me crazy. Am I missing something ?
not a Live user, but I woud suggest wipe
or rename, zip whatever all "versions" that you don't want to use.
Or embed selected bpatcher into main one, and keep all other
"versions" outside of that "project" search path.
Maybe project type is needed for proper creation of m4l devices.
I have created quite few without ever using projects.
if they are all in the search path, only the date counts, and the relative */* position means nothing.
also take care when you move stuff while the mother patch which points to it is open - programs like max might track that movement in some situations and update the path.
sometimes happüens to when moving older versions of a file from the desktop to the trash.
Do you mean, by default, it's not looking in the folder where the main patch is ?
@Source Audio :
I never use projects with Max (not really sure what they are about). But when you create m4l devices that have dependencies, editing it automatically creates a Project and it puts stuff in here. Since my "bpatched" patchers are originally elsewhere, it gets really confusing.
Again, embed that bpatchers into main one.
here screenshot with frozen device including external that
only exists in that m4l device.
bpatcher does not get extracted , external does.
Thanks.
I'd rather not embed the patcher since I've got several copies with different arguments, so I'd have to manually copy the changes from one to another, but I might do this anyway.