Max 8.2.1 Released

    Nov 16 2021 | 5:53 pm
    We are happy to announce the release of Max 8.2.1. This update primarily addresses issues that came up in Max 8.2. Take a look at the changes below for a comprehensive list of improvements.
    As always, you can download the update here:
    Happy patching! Ben
    Release Notes Fixed Bugs • absolutepath: folders in Project-specific paths are found • Gen codebox: errors report correct line • Gen: Fixed param restore crash • GL3 auto_normals generation improvements • GL3 support for float64 input • GL3 autonormals with triangle mesh work correctly • GL3: 1 plane matrices are displayed correctly • GL3: dynamically update and read buffers in a transform-feedback process • GL3 textures: tex_map 3 projection correctly projected when object is rotated • eliminated animation glitches related to easing • jit.gen: fixed crash with nearestpix sampler and dimcount > 4 • fixed outlet functionality (fixes Inspired by Nature Max for Live devices) • / fixed issues with params texture • color input works as expected when lighting is enabled • fixed broken obj file read • fixed drawing multiple textures • fixed re-initialization when undoing deletion • outputs properly adapt to input type • framerate no longer drops when number box updated (Win only) • live.scope~ / live.adsrui: updated icons • Patching: fixed hang when patching in large patcher (Win only) • Styles: saved in the correct location • subpatcher: no longer appears bogus when opened from project window • umenu: improve popup positioning with multiple displays at mixed resolution/zoom • vizzie: Fixed doubled output causing doubled fps • vst~: eliminated freeobject error and potential memory leak • vst~: fixed potential crash when instantiating new plugin • Windows: increased main thread stack size to match OSX (8 MB)

    • Nov 16 2021 | 6:08 pm
    • Nov 17 2021 | 3:20 pm
      big thanks to the team. Especially the extra gen~ error catching
    • Nov 27 2021 | 3:36 am
      It appears that the "remote packages" don't work on the newest mac's. i just upgraded to the latest version of Max on my new laptop, tried to install the same packages i had on my decades old machine but now they make my patch crash while it's doing basic functions. i see a majority of the packages explicitly state they are not compatible w/ the newer machines but those such as Blocks and others don't give this warning. Patch works fine when i uninstall all the remote packages.
    • Nov 27 2021 | 3:17 pm
      you can install packages that got updated for M1, if any ? or run Max in rosetta
    • Nov 27 2021 | 3:52 pm
      In short, i can not run any remote packages on the m1 from my brief experience trying to do so.
      i was not exactly sure which particular packages are causing of the crash, but i was running Max flawless to my delight on the new machine for several weeks now. Recently a friend asked for package recommendations but when i went to refer to the ones i had i saw that the packages didn't transfer over. So i referred to my old machine and started updating them on my new. i maybe uploaded 3 packages that did not give a warning of compatibility issues before my new m1 laptop crashed w/ max running. Noting that this was the only change, i went and uninstall said packages the following day and then Max ran flawlessly again. i can do without these packages, so i will probably not use rosetta at all.
      Today i just reinstalled Blocks to see if it is truly the culprit & it indeed crashes after using it for about 2 mins. Probably not gonna test out the others right now cuz i just wanna jam. Just sad to not be able to use Blocks but hopefully all the packages get updated in the near future.
    • Nov 30 2021 | 9:27 pm
      @Mr. Banshee
      If you could send report with your use case of blocks, steps to reproduce, and system information, we'd be happy to try and solve this crash:
      Thanks, Joshua