Max 6.1.1 Released

    Mar 18 2013 | 10:56 pm
    We are happy to announce the release of Max 6.1.1!
    A major impetus for this release is to fix an issue with certain third party externals and various issues in Gen, although you can see from the release notes that there are some other nice fixes as well.
    You can download it here:
    Enjoy! -Ben
    Fixed Bugs: • 3rd party external objects: fixed notify_free() crashes for old third-party externs • bendout: fixed • buffer~: Fix for misc crashes • closebang: fix for use in MFL • Collective loading factory externals changes • detonate: fix for read/import midi files • Extras: fix for subfolder usage • Gen: fix for freeverb x64 crash • gen~: samplerate properly updates in subpatchers • javascript: improved script load execution • fix for order attribute • jit.qt.grab: fixed memory leak • Jitter Gen: fix for TWOPI and friends in object boxes • JS: fixes for 'Max' method • LOM: 'access' column info is rendered (Win) • project: searchpaths are not forgotten on project load • Projects: file singleton fixes • Projects: fixed crash on windows • regexp: reads arguments properly • sfrecord~: fix for not writing any bytes to file (Win) • standalones: remove Cg.framework error messages • vst~: initialization improvements

    • Mar 19 2013 | 12:13 am
      Exciting. Does the vst~ in this update include the fix that was discovered a week or two ago?
    • Mar 19 2013 | 4:50 pm
      @dhj Yes. It might not solve all of the issues, but it should be better for many if not all the cases of crashing on load for several plugins. Please let us know if you still see issues.
    • Mar 19 2013 | 4:59 pm
      I ran it through my testing system and unfortunately, there still seems to be a problem where it hangs on freeing VSTs (only sometimes) so I still can't use this version for live work. I think this is a known issue so I'm hoping it will get addressed soon.
      Thanks, D
    • Mar 19 2013 | 6:46 pm
      TWOPI and friends are fixed! I'm very happy. I'll check asap.
    • Mar 19 2013 | 7:54 pm
      one bug from 6.1 i noticed which does not appear to be fixed in 6.1.1 is a display problem which occurs when moving a patch from a retina display to a non-retina display or vice-versa (i.e. when using an external display with a retina macbook pro).
      when moving a patch from a retina display to a standard pixel-density display, the objects in the patch render like this:
      and after moving from a non-retina to a retina display, they render like this:
      the display setting can sometimes be reset by refreshing the object rendering (e.g. by toggling edit mode or presentation mode) but it doesn't always seem to work correctly, and is in any case gets in the way of a smooth workflow.
      is this a known issue? thanks!
    • Mar 20 2013 | 11:06 am
      nice :) are you planning to push jit.lcd to 64bit world? or are you "only" pushing MGraphics & Sketch inside JSUI to replace it ?
    • Mar 20 2013 | 1:43 pm
      On Windows 7 x64, saving a patch containing abstractions crash in both Max 6.1.1 x86 and x64. Not so in release 6.1 or in patches containing only externals.
    • Mar 20 2013 | 4:30 pm
      Julien, I would recommend moving towards MGraphics with JSUI and jit.mgraphics as a replacement for lcd/jit.lcd.
      Alessandro, There is a known issue in Max 6.1.1 for saving to the D: drive on Windows. Is this what you are doing?
      Thanks, -Ben
    • Mar 20 2013 | 4:51 pm
      Thanks Ben. Yes, the problem is saving to D:. But if I first save the patch to C: then I can save it to D:. Hope the fix will come soon!
    • Mar 21 2013 | 1:48 am
      No multitouch support yet :(
    • Mar 21 2013 | 2:26 am
      No multitouch yet ;-)
    • Mar 23 2013 | 5:13 pm
      Thank you for making the wheel less obtrusive by adding "show after click" in the preferences. I used to accidentally open that thing at least 50 times a day :)
    • Mar 24 2013 | 8:18 pm
      Will this export svg files and 3d model from inside a patch?
    • Mar 25 2013 | 10:16 am
      Not sure if this happened in 6.1 or 6.11, but it seems that older third party help files now only open from the object's context menu if they have .maxhelp extension - .help files don't open. You can rename them .maxhelp or open them manually, but I'm wondering if there's another way to have them open more automatically? The context menu is much easier for students.
    • Mar 25 2013 | 10:54 pm
      uebergeek, I see that if you option-click, it does not open the help file if it has the extension '.help' but I do see it working when using the contextual menu that pops up when right or ctrl-clicking. It also doesn't seem to work from the 'Help' menu.
      Is this the behavior you are seeing? Also, what platform are you running, and which Max architecture (32/64)?
      Thanks, -Ben
    • Mar 26 2013 | 6:32 am
      Does this version allow for exporting svg and 3d models from inside a patch?
    • Mar 26 2013 | 3:19 pm
      ^ No. I really want this feature for making vector-based examples.
    • Mar 26 2013 | 5:03 pm
      when a help in others languages?
    • Mar 27 2013 | 11:10 pm
      Hi Ben,
      I can't open Help from the contextual menu when I right click. E.g. OpenSoundControl from CNMAT: If I right click, I see "Open OpenSoundControl Help" at the top of the contextual menu. But when I click on that, nothing happens. osc-route's help does work, though. OSC-Route uses .maxhelp extension, while OpenSoundControl Help uses .help.pat extension. (I believe .help and .help.pat's are behaving the same way.)
      Running under OSX (10.6.8), Max Version 6.1.1 32-bit.
      Thanks, -Amy
    • Mar 27 2013 | 11:20 pm
      Interesting, I don't see that exact behavior here. There is definitely something going on with these extensions, and back compatibility would be nice.
      It should be noted that these extensions are deprecated.
      Thanks, -Ben
    • Apr 03 2013 | 11:28 pm
      hi, i can confirm this bug reported by but i'm saving on E: where my personal patch and abstraction folder is. the folder is a Max path in the file preferences
      On Windows 7 x64, saving a patch containing abstractions crash in both Max 6.1.1 x86 and x64. Not so in release 6.1 or in patches containing only externals.
    • Apr 03 2013 | 11:30 pm
      We will have an update soon with a fix for the non-boot drive saving issues.