[absolutepath] not working in Max 7 M4L?


    Jul 01 2015 | 6:52 am
    I'm running into some strange behavior with [absolutepath], I just upgraded to Max 7 and the new Ableton Live 9.2, it seems that absolutepath doesn't work inside of .amxd files?
    When I first create an absolutepath object it works but after saving the file and loading it as a device it shows up orange and the circular arrow menu shows its name as "jbogus", if I edit the device and try to create any additional absolutepaths they show up the same and don't even have inlets or outlets, needless to say the functionality is also broken. The Max console shows "newobj: absolutepath: No such object"
    I've attached a small test device to demonstrate what happens.

    • Jul 01 2015 | 8:42 am
      Make sure you don't have another file in Max's search path called 'absolutepath'. This will cause a naming conflict.
      -Ben
    • Jul 01 2015 | 8:48 am
      Ok that makes sense thanks, I had a file that I called absolutepath.js just because I was trying to get the same functionality from js. Btw I made a couple unrelated mistakes in the device I attached..