kparagraphic

hi there i'm experiencing some bizarre behaviour with poly~ patches in a max instrument i am creating. i am making changes to the contents of the poly~ subpatches, but my max4live device is still loading old versions. when i manually refresh the poly~ objects in the patch (like load different patch then re-load the original) it still loads an old version of the poly~ patch. i have no idea where it's getting the old versions from, these files should no longer exist on my hard drive in this form. i've checked my search paths to make sure there are no duplicates. i've been using max for 10 years so I am no newbie to this sort of thing. i am convinced that max is misbehaving. convince me otherwise?

EDIT: i think it is pulling old patches from the 'Project' folder. what is this folder and why do i need it? how do i stop this from happening?

hi there i'm experiencing some bizarre behaviour with poly~ patches in a max instrument i am creating. i am making changes to the contents of the poly~ subpatches, but my max4live device is still loading old versions. when i manually refresh the poly~ objects in the patch (like load different patch then re-load the original) it still loads an old version of the poly~ patch. i have no idea where it's getting the old versions from, these files should no longer exist on my hard drive in this form. i've checked my search paths to make sure there are no duplicates. i've been using max for 10 years so I am no newbie to this sort of thing. i am convinced that max is misbehaving. convince me otherwise? 

EDIT: i think it is pulling old patches from the 'Project' folder. what is this folder and why do i need it? how do i stop this from happening? 

hi there i'm experiencing some bizarre behaviour with poly~ patches in a max instrument i am creating. i am making changes to the contents o

m4l-device-keeps-loading-old-versions-of-poly~-patches-that-no-longer-exist-on-my-hdd

You should be able to see in the bottom bar a icon for 3 nodes connected to one node "show containing folder" - this is where all your files are kept. You should be able to right click and open the file location from there to find out where it is (and delete it).

i can only see that on the main max 4 live device editing view, all the subpatchers don't have that icon.

it is creating a folder called "Max for Live Devices" and reading some files from there. why is this happening? I do not need this.

are subpatches embedded in max4live devices? when i try to open my device to edit it max, it moves up updated poly patches to a folder called 'discarded'. pretty concerning considering this would be an easy way to lose work for anyone who has no idea what is happening.

i think i figured out that it has something to do with editing the bpatcher files without having the main .amxd open for editing. when i opened the .amxd again, it realised the bpatchers had changed and replaced the new ones with the ones that had been compiled into the .amxd, moving my updated bpatchers into a folder called 'discarded'. and then also the 'projects' folder plays some role in all this confusion but i am yet to figure out exactly how. gonna leave this thread up in case anyone else has this problem in the future and it sheds some light on how m4l operates.

it is creating a folder called "Max for Live Devices" and reading some files from there. why is this happening? I do not need this. 

are subpatches embedded in max4live devices? when i try to open my device to edit it max, it moves up updated poly patches to a folder called 'discarded'. pretty concerning considering this would be an easy way to lose work for anyone who has no idea what is happening. 

i think i figured out that it has something to do with editing the bpatcher files without having the main .amxd open for editing.  when i opened the .amxd again, it realised the bpatchers had changed and replaced the new ones with the ones that had been compiled into the .amxd, moving my updated bpatchers into a folder called 'discarded'. and then also the 'projects' folder plays some role in all this confusion but i am yet to figure out exactly how. gonna leave this thread up in case anyone else has this problem in the future and it sheds some light on how m4l operates. 

M4L device keeps loading old versions of poly~ patches that i think no longer exist on my HDD