Max 7 "package.txt" file support


    Nov 12 2014 | 5:41 pm
    Hi, The possibility to add a package which is in another repertory than the authorized ones with the help of the "package.txt" file was a very useful feature for us in Max 6. Does it still works in Max 7 ? Where should I put this file ? I tried "/Documents/Max 7/package.txt", "/Documents/Max 7/Packages/package.txt", both don't works. Thanks

    • Nov 13 2014 | 2:59 pm
      ..bump
    • Nov 13 2014 | 3:06 pm
      Sorry, this is a feature of a third-party extension to Max, you'll need to get in touch with the responsible parties:
      is presumably what you're using...
      Jeremy
    • Nov 13 2014 | 3:21 pm
      Hi Jeremy, In fact i think it was a cycling'74 feature : From MaxSDK-6.1.4, Distributing Packages section
      Additional folders containing packages may be added by creating a text file in your Max application folder, named "packages.txt". This file may then contain the path to a folder (that contains package folders) of your choosing on each line, terminated with a semi-colon. For example:
      ~/code/Jamoma/Implementations/Max; ~/code/JamomaUserLibraries/TapTools;
    • Nov 13 2014 | 3:25 pm
      Lol. Sorry, hard to keep track of all of these features. :-)
      I'll need to check, but try putting it in ~/Documents/Max 7/Library .
      jb
    • Nov 13 2014 | 3:40 pm
      Unfortunately, I already tried to put this file in "Max 7" root folder and on every Max 7/* repertories but it doesn't seems to work ! Maybe you have an alternate solution ? An other solution would be to support package aliases folders in the package repertory ?
    • Nov 13 2014 | 3:45 pm
      You can put symlinks/aliases in the package folder. I'll look into the packages.txt issue and report back.
    • Nov 13 2014 | 4:12 pm
      Thanks for noticing this issue. As a workaround until we fix it, you can put packages.txt in your /Applications folder on OSX. We'll provide support for a less problematic location or locations in a future update.
      Jeremy
    • Nov 13 2014 | 4:27 pm
      Thanks for reply, It works !
    • Nov 13 2014 | 4:44 pm
      Followup and final word: we've decided to axe support for this file. Please use symlinks. On Windows, the Link Shell Extension (http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html) can be used to create real symlinks -- Windows .lnk files are not supported. Sorry for the confusion and disinformation above (and for the workaround, which will be non-functional in the next release).
      Jeremy