File Association Changed by Max 7

    yota
    Nov 12 2014 | 10:46 pm
    Hello,
    I just installed Max7 and have tried some patches.
    Since my installation, all the Max patch files with .maxpat suffix are associated with Max7, whether previously or newly created.
    As I am not planning to change my developing environment to Max7 but will stay with Max6.1 for the next while, I tried to restore the file association doing:
    OSX (10.9.5) Finder - Get Info - Open With - Selecting Max 6.1.9 - Change All
    This process does not restore my original association but it remains Max7.
    If anyone knows a workaround, please let me know.
    Thanks!
    • joeman
      Nov 13 2014 | 3:41 am
      Same problem here. OSX lion 10.7.5
    • Frans-Jan Wind
      Nov 13 2014 | 8:19 am
      This is not new to Max 7, This association also occurs when building an app, patches get opened with the newly build app. Did you try quitting all apps and then change "open with" / "change all"?
    • Jeremy
      Nov 13 2014 | 8:36 am
      @Frans-Jan Wind, when you are building an app, you can use the 'standalone' object to set a bundle identifier on OSX. Setting it to something other than com.cycling74.Max will avoid that problem. I am afraid that don't have a solution to the OP's issue, though -- this is an OS problem as far as I know.
      Jeremy
    • DiGiTaLFX
      Nov 13 2014 | 3:57 pm
      Could you just update the bundleid to com.cycling74.Max7 so that clicking change all wouldn't revert back from 6.1 to 7?
      Edit: It seems like this distinction of the identifier would make sense anyway, seeing as v7 doesn't use the same preferences or document locations as v6.
    • Jeremy
      Nov 13 2014 | 4:00 pm
      For technical reasons involving, among other things, Max for Live, changing the Max bundle ID isn't possible.
      Jeremy
    • yota
      Nov 13 2014 | 4:19 pm
      Thanks for your responses.
      Frans-Jan Wind:
      Yes, as I wrote, I tried "change all" but it did not work.
      Jeremy:
      If this is an issue of the OS like you mentioned, is there any solution?
    • vichug
      Nov 13 2014 | 4:50 pm
      fwiw, changing the name of the max 7 application to Max7.app (instead of Max.app) solved the issue here. Of course, it has to be temporary and can possibly lead to a lot of other unexpected problems.
    • Jeremy
      Nov 13 2014 | 4:55 pm
      Changing the name of the Max.app is not recommended and is known to cause problems in Max 7.0.0, particularly in Max for Live. We already have some improvements in the pipeline to permit this for an update. But you've been warned.
      Jeremy