Ben Bracken

We are happy to announce the release of Max 7.0.1!.

With over 80+ bug fixes, this update focuses on adding stability and fixing problems introduced in Max 7.

As always, you can download the update here:

• audio file drag and drop: drag in locked patcher no longer causes errant purple border

• AVF video backend: fixed memory leak / crash

• bpatcher: fixed ui interaction issues with offsets and clickthrough

• buffer~: fixed issues with resizing buffer~ while recording

• calendar: fixed crash after opening a file in stream view

• comment: background color from a style is properly applied

• crash recovery: fixed issue for when there is nothing to recover

• Doc Browser: properly escapes apostrophes and other characters

• docs: can open help files from refpages where helpfile name !== .maxhelp

• filebrowser: proper path for bookmark when dropping folder from secondary volume to sidebar

• filebrowser: renaming collection snippet no longer removes it from the collection

• filebrowser: sidebar pop ups properly scroll on overflow

• filewatch: fixes for (some) paths containing accented characters

• gen patcher: snippets browser lists collections alphabetically

• Gen: clicking file->save while in the embedded gen offers 'save as' dialog

• Gen: double click on [in] and [out] in gen brings parent patcher forward

• Gen: fix for filename arg on gen subpatchers not being used

• Gen: fix for issues with gen subpatcher loading

• Gen: fix for Params when not connected with patchcords

• gen~: fix for buffer not compiling due to missing symbols and prototype

• gen~: fixed codegen error with splat due to re-use of local variable name

• GenExpr: code that buffer is dependent on is not erroneously deleted

• groove~: buffer is properly cleared when timestretch is on

• groove~: loop points/loop start work with timestretch enabled

• inspector: fixed section header under 32-bit

• inspector: standalone inspector on Windows works

• jit.gl.mesh: fixed @cache_mode vertexbuffer usage

• jit.gl.multiple: support for velocity render target

• jit.grab: avf unique output_texture works as expected

• jit.phys.picker with jit.world: fixed issues when modified by jit.gl.handle

• jit.record: fixed avf engine error in Max Console

• jit.world: @hi-res 1 no longer posts "invalid object" message to the Max console

• Lessons: bar captions properly disappear

• Max Console: additional fix for mystery white columns

• maxdb: AU plugins are no longer reharvested on every restart of Max

• maxdb: files in subfolders of package aliases are properly harvested as package files

• maxdb: fixed harvesting metadata from plugins with a ' in the manufacturer name

• MFL editor: toolbars can be customized

• nslider: note color properly changed when setting patcher style

Fixed Bugs:
• audio file drag and drop: drag in locked patcher no longer causes errant purple border
• AVF video backend: fixed memory leak / crash
• bpatcher: fixed ui interaction issues with offsets and clickthrough
• buffer~: fixed issues with resizing buffer~ while recording
• calendar: fixed crash after opening a file in stream view
• comment: background color from a style is properly applied
• crash recovery: fixed issue for when there is nothing to recover
• dial: fixed drawing issues
• dict: documentation of js usage
• Doc Browser: properly escapes apostrophes and other characters
• docs: can open help files from refpages where helpfile name !== .maxhelp
• File Browser: sidebar is resizable
• filebrowser: proper path for bookmark when dropping folder from secondary volume to sidebar
• filebrowser: renaming collection snippet no longer removes it from the collection
• filebrowser: sidebar pop ups properly scroll on overflow
• filewatch: fixes for (some) paths containing accented characters
• gen patcher: snippets browser lists collections alphabetically
• Gen: clicking file->save while in the embedded gen offers 'save as' dialog
• Gen: double click on [in] and [out] in gen brings parent patcher forward
• Gen: fix for filename arg on gen subpatchers not being used
• Gen: fix for issues with gen subpatcher loading
• Gen: fix for Params when not connected with patchcords
• Gen: fixed problems with require
• gen~: fix for buffer not compiling due to missing symbols and prototype
• gen~: fixed codegen error with splat due to re-use of local variable name
• GenExpr: code that buffer is dependent on is not erroneously deleted
• groove~: buffer is properly cleared when timestretch is on
• groove~: loop points/loop start work with timestretch enabled
• inspector: fixed section header under 32-bit
• inspector: standalone inspector on Windows works
• inspector: restrict title bar size
• jit.gl.mesh: fixed @cache_mode vertexbuffer usage
• jit.gl.multiple: support for velocity render target
• jit.gl.pass: MRT works with @adapt 0
• jit.grab: avf unique output_texture works as expected
• jit.phys.picker with jit.world: fixed issues when modified by jit.gl.handle
• jit.record: fixed avf engine error in Max Console
• jit.world: @hi-res 1 no longer posts "invalid object" message to the Max console
• jit.world: fixed drawto attribute
• Lessons: bar captions properly disappear
• Max application: can rename
• Max Console: additional fix for mystery white columns
• maxdb: AU plugins are no longer reharvested on every restart of Max
• maxdb: files in subfolders of package aliases are properly harvested as package files
• maxdb: fixed harvesting metadata from plugins with a ' in the manufacturer name
• meter~: fixed orientation issues
• MFL editor: toolbars can be customized
• MFL MuBu device: fixed crash on load
• nslider: note color properly changed when setting patcher style
• number: properly converts values when switching between integer and decimal
• pach cords: implement revert to default for color
• Paste From: fixed conflicts with clippings and snippets in the same package
• patcher font: change is properly reflected in attrui, umenu, tab, textedit
• Patcher Inspector: fixed crash when clicking on 'show in reference'
• patching: click on inlet/outlet creates a connection even with segmented cords off
• path: fixes for OSX aliases on Yosemite
• playlist: added notifications for starting playback
• reference sidebar: section headers have gradient
• Rewire: misc fixes
• saveas dialog from patcher: removed entries for files we don't directly save
• scheduler: SIAI improvements
• sidebar: disabled in floating / nogrow windows
• snippets patcher browser: fixed status view for files
• snippets: conversion utility for clippings
• snippets: fixed crash when editing/saving a snippet with no contents
• snippets: fixed drag/drop from a non-known snippets location
• snippets: save notification / browser link appears longer in toolbar
• standalone: no longer crash on startup (Win)
• stretch~: fixed crash or hang when deleted while stretching
• subpatchers: pin state is saved
• Templates: first-time template creation properly updates menus
• Templates: subpatcher grid settings saved properly
• text fields: Max no longer crashes when hiding textfield attributes
• textbutton: fix for jspainter usage
• Toolbars: fixed double object creation issue
• typeroute~: added refpage
• umenu: arrow attribute is back
• umenu: fixed dropdown menu appearance in Mira with Max 7
• umenu: imports Max 4 colors properly
• umenu: popupmenu uses specified font
• umenu: setcheck always draws
• User Docs folder: fixed issues when username contains accented characters
• vst~: fixed crash when pressing recall directly after dropping
• wave~: fixed error when using @interp attr in the box


max-7-0-1-released

Thank you for the update! May I ask if vertical border lines for objects/num boxes is something I could hope for in future updates or not?

Da capo [N871]: Great work, Max-team, thanks ... but may I also hope, that borderlines around the objects will come soon?

(@Phiol : surely you mean +2 ? one for each side)

Awright Vichug, because of you they both get a +1 and so do you.

Awright Vichug, because of you they both get a +1 and so do you.
"+3 on borderlines"


"• patching: click on inlet/outlet creates a connection even with segmented cords off"

Is that why clicking on inlet no longer gives me the contextual menu with suggested objects/messages? Any way to revert this?

right click on the inlet still opens up the contextual menu @walker

-Could we have the color option (rainbow circle) back in the menu when

you right click on the object. IMO Much faster workflow than in inspector

Small request
-Could we have the color option (rainbow circle) back in the menu when
you right click on the object. IMO Much faster workflow than in inspector


new Max7. Where I am supposed to put my external Max lib and the pats for the extra menu ?

Since I'm brand new to Max, I have to ask:

Does this just install over Max 7 while keeping all my projects and patches in the same place? Do I need to go back and direct Ableton Live to this update since it is using 7 for Max For Live? Thank you.

Since I'm brand new to Max, I have to ask:
Does this just install over Max 7 while keeping all my projects and patches in the same place? Do I need to go back and direct Ableton Live to this update since it is using 7 for Max For Live? Thank you.


thanks for fixing groove~, no problems anymore.

Since I’m brand new to Max, I have to ask:

Since I’m brand new to Max, I have to ask:
Does this just install over Max 7 while keeping all my projects and patches in the same place? Do I need to go back and direct Ableton Live to this update since it is using 7 for Max For Live? Thank you.


no, updates (not major ones) do not require you to redirect ableton or move any files.

Hmph I just bought Ableton Suite legit, I thought it would have Max 7, but they gave me 6.1.9 and offered me to upgrade to 7 for $150! I guess I should've expected it.. but (sigh) oh well

if I were you NDIVUYO I'd hassle c74 and ableton for a free upgrade-- get on the phone and call head office

why did show/hide toolbars change to cmd+8 instead of cmd+4? cmd+4 hides my cursor?

did i turn on left handed mode or something? :) (both would be nice :) )

why did show/hide toolbars change to cmd+8 instead of cmd+4? cmd+4 hides my cursor? 

did i turn on left handed mode or something? :) (both would be nice :) )


@JONAH because in order to do a cmd+4 on a french keyboard (and probably others) you have to make shift+command+4 which makes a screen capture.

my +5 to re-add borders in objects as in Max 6.

Just to make really possible to customize templates for the ones who prefer to work with a dark text and light background objects

my +5 to re-add borders in objects as in Max 6.
Just to make really possible to customize templates for the ones who prefer to work with a dark text and light background objects
thanks


thanks for the explanation, that makes sense. it's working fine now, i changed it to 4 by editing the json file in max. editing in textedit stopped max's toolbar menu items from showing up.

@jonah You'll have to do that at each updates ;-( probably better to get used to command+8, I can do that with the right hand too ;-)

Adding my support for re-instituting side borders on all objects. PLEASE.

And please consider that textbuttons can have a flat look instead of the gradient style they currently have now. This really interferes with other objects like umenu and slider. Also when hovering over the textbutton they will have a slighty darker color which I find annoying. Again not consistent with other objects.

+1 for removing the darker hovering color, it doesn't match at all with the retro look of Max 7.

@EMMANUEL JOURDAN thanks for the heads up. :) that'll be no problem. the thing is my right hand is on the trackpad mostly and my left hand is closer to the left side of the keyboard. :) so doing cmd + 8 with my left in the dark i can't really see.

btw, layoutbubbles 0 doesn't seem to work to turn off the x/y coordinates pop up bubble anymore?

crashed on 10.6.8 so I spent the day formatting and installing OSX again. I needed to format anyway. one of the computers here is not capable of upgrading OSX without breaking protools 7 HD (TDM). I would love to see 10.6.8 supported but I may be a minority. I would only ask that it installs and runs I would not ask for extra bug fixes after that.

can I no longer purchase GEN separately as a $100 upgrade to max 6? I did not see it in the store. I own live 9 with m4l (max 6). does beap work in M4L or do I need to upgrade to max 7 for gen + beap?

Gen is now included in Max 7 you don't need to purchase it. For Beap: Yes it is basically a collection of bpatchers following some standards regarding signal inlets and outlets. you can also download it separately.

Hi Robert,
Gen is now included in Max 7 you don't need to purchase it. For Beap: Yes it is basically a collection of bpatchers following some standards regarding signal inlets and outlets. you can also download it separately.


Come on guys! Please update the modulo operator(%) in EXPR/VEXPR to support floats!

Come on guys! Please update the modulo operator(%) in EXPR/VEXPR to support floats!
I believe this is the fmod in C.
thanks


On a similar topic, I was wondering if there was any hope for bitwise manipulations in gen~.

Please give us the option to choose side borders on objects.

I can't save the formatting of any objects. If I make one message green and another red (for play and record), they go right back to "default" when I open them. I've tried this with a number of objects, and I can't make any formatting "stick".

PROBLEM FIXED! I deleted all the "File Paths" that I had added at startup and the problem went away. I don't actually know what the problem was, but it made Max unusable. I suppose Max 7 could find some Max 5 object that screwed it up... I don't know, my Filepaths included a 

 of files. As soon as I deleted the Filepaths, I could save colors, sizes, fonts, everything that I couldn't before. So, if this is your problem, here's the solution.

I can't save the formatting of any objects.  If I make one message green and another red (for play and record), they go right back to "default" when I open them.  I've tried this with a number of objects, and I can't make any formatting "stick".

PROBLEM FIXED!  I deleted all the "File Paths" that I had added at startup and the problem went away. I don't actually know what the problem was, but it made Max unusable. I suppose Max 7 could find some Max 5 object that screwed it up...  I don't know, my Filepaths included a lot of files.  As soon as I deleted the Filepaths, I could save colors, sizes, fonts, everything that I couldn't before.  So, if this is your problem, here's the solution.


Moving wires is a little easier with 8.01, thank you! also I like the toolbar improvements. Thank you very much.

can someone reproduce this weird behavior of curve~ ?? (right outlet sends a bang when Live's tempo is changed) see screen capture.

The strange thing is: Support can't reproduce this but I can reproduce this with Max 6 or 7, Win 7 or OSX, Live 9.1.6 or 9.1.7 in any type of m4l device.

Hi,
can someone reproduce this weird behavior of curve~ ?? (right outlet sends a bang when Live's tempo is changed) see screen capture.
The strange thing is: Support can't reproduce this but I can reproduce this with Max 6 or 7, Win 7 or OSX, Live 9.1.6 or 9.1.7 in any type of m4l device.
O.


https://dl.dropboxusercontent.com/u/21064404/curve%7E_bug_2015-2-9.zip

Exactly the same behavior here on OS X 10.9.5 for Ableton Live 9.1.7 (2014-12-12_411c6f8237 / 64-Bit) and Max 6.1.9 OR Max 7.0.1

I can reproduce the curve~ issue and we will take a closer look. There was a similar fix for line~ a while back, so it will hopefully be fairly easy to tackle.

hey, that was so incredible fast to confirm the bug and reach the right person compared to the 6 day support experience before that.

Are this kind of release threads a possible official way to report bugs?

hey, that was so incredible fast to confirm the bug and reach the right person compared to the 6 day support experience before that.
Are this kind of release threads a possible official way to report bugs?


The best way to report possible bugs is to email Support. This one just happened to be a thread that I was subscribed to, and a type of bug that I was familiar with previously.

Thanks for the suggestion, Ben, but for some issues it seems better to share publicly. This is a pretty minor issue I guess, but I am sure it is something you may want to fix, depending on feedback from Ableton perhaps.

When building a 64-bit .amxd version of a Live device on both MacOS and Windows 7-64bit, with the current version of Max for Live 6.1.9, a huge amount of memory gets locked up and is not released after building a project. I was building from three .maxpats totaling 4MB (one of which was a 1MB poly~ object with 16 instances), three .wav files totaling ~40MB, and two ,json files less than 2ooKB. Each time I built it, the project consumed >1GB more DRAM memory. After three builds on my 6GB windows machine, and one build on my 2GB MacOS machine, there are out of memory errors requiring reboot.

The 32-bit version also did not release memory after each build, but as 32-bit version runs in protected mode, it does not crash the computer. On the other hand, it would theoretically be much slower than the 64-bit version if the 54-bit version did not allocate >1GB to complete a build.

Maybe it is an Ableton issue but it seems more likely that each file is loading a complete Max library simultaneously, rather than sharing the library date. That's just at a guess. I don't think many users will run into it, but Ableton would probably appreciate a fix.

Thanks for the suggestion, Ben, but for some issues it seems better to share publicly. This is a pretty minor issue I guess, but I am sure it is something you may want to fix, depending on feedback from Ableton perhaps. 

When building a 64-bit .amxd version of a Live device on both MacOS and Windows 7-64bit, with the current version of Max for Live 6.1.9, a huge amount of memory gets locked up and is not released after building a  project. I was building from three .maxpats totaling 4MB (one of which was a 1MB poly~ object with 16 instances), three .wav files totaling ~40MB, and two ,json files less than 2ooKB. Each time I built it, the project consumed >1GB more DRAM memory. After three builds on my 6GB windows machine, and one build on my 2GB MacOS machine, there are out of memory errors requiring reboot. 

The 32-bit version also did not release memory after each build, but as 32-bit version runs in protected mode, it does not crash the computer. On the other hand, it would theoretically be much slower than the 64-bit version if the 54-bit version did not allocate >1GB to complete a build. 

Maybe it is an Ableton issue but it seems more likely that each file is loading a complete Max library simultaneously, rather than sharing the library date. That's just at a guess. I don't think many users will run into it, but Ableton would probably appreciate a fix.


Max 7.0.1 Released