Max 7.2 released
We are happy to announce the release of Max 7.2!
Along with a number of other bug fixes, this version brings Multidimensional Polyphonic Expression (MPE) MIDI support, new Video & Graphics tutorials, as well as some great Max For Live parameter automation optimizations. Take a look at the list of new features and fixed bugs below.
As always, you can download the new installers here:
https://cycling74.com/downloads/
This can be installed over your previous Max 7 installation, and will not affect installs of Max 6.x or lower. We hope you enjoy this new version of Max!
-Ben
New Features:
• New Tutorials: Video & Graphics (found under Help->Reference->Documentation Home, links on the bottom of the left grey 'Contents' sidebar)
• Multidimensional Polyphonic Expression (MPE) MIDI support
• midiparse / midiformat: @hires attribute to output a two-byte list to set high-resolution (14-bit) pitch bend output
• mpeconfig: Configure MIDI devices that support MPE
• mpeformat: prepare MPE-compatible MIDI messages
• mpeparse: Interpret and parse raw MPE data (similar to midiparse)
• polymidiin: Output MPE MIDI data in a patcher loaded by poly~
• poly~: @midimode attribute to send MIDI events to all voices
• poly~: @zone attribute for setting the MPE 'zone' that the poly~ will listen to (the default is to ignore zones)
• vst~: accepts 'mpeevent' message to handle MPE data
Fixed Bugs:
• amxd~ / vst~ snapshots: check mark appropriately changes after new snapshot is added
• deferlow: no longer breaks 'stdlist' behavior (autofanning of lists to object inlets)
• dict.print: no longer changes dictionary if it contains strings
• function: documented mousemode and mousereport
• gen~: fix for gen~ curve~ emulation in the case of the curvature being zero
• gen~: fixed delay time calculations (spline/cubic delayed by proper amount and @feedback 0 works)
• gen~: fixed subpatchers reverting to default gen patcher issue
• jit.gl.material: fixed errors when sending texture to emission and heightmap inlets
• jit.gl.mesh: autonormals works with large dims
• jit.matrix: fixed exportimage memory leak
• jit.matrix: png image import correctly calculates alpha channel
• jit.movie: outputs file name on read failure
• jsui: fixed crash when parameter enabled (x64)
• live.dial: fixed mousing in 'enum' mode
• live.step added 'next' message
• live.step: added 'getcurrentstep' message
• live.step: dump_to_dict properly contains interval
• live.step: set message properly et the targeted sequence
• Max For Live: device development path respected in Max
• Max For Live: fixed jit.gl.render / jit.pwindow memory leak after open / close in Max editor
• Max For Live: pattr in parameter mode properly outputs value when @_parameter_linknames is set to 1
• Max For Live Device Project: amxdtype attr is correct for default / old devices
• Max For Live Devices: SVGs appropriately deleted from User/Temp folder (Win only)
• Max For Live parameters: blob param fixes
• Max For Live parameters: automation optimizations
• maxurl: always process incoming headers
• playlist~ / jit.playlist: improved memory leak issues
• objects explorer: filters duplicates
• parameter: fixed problem when typing values into parameter box UI
• Parameters: fixed deferred parameter output
• seq: fixed crash on reading text files
• Side Bar: minimization behavior improvements
• standalone: fixed crash when building project
• standalone: no longer creates a ~/Documents/Max 7 folder
• toolbar calendar: fixed week start
• vst~: snapshot message works as expected when changing file name
Sweet! Is it possible to expand on this:
• Max For Live parameters: automation optimizations
Thanks
@benj3737 you should see improved CPU usage when automating parameters and other similar tasks.
-Ben
@BEN BRACKEN: Does that relate to automate e.g. a live.numbox with the Live automation and/or to controlling parameters via the Live API & live.remote~?
especially the latter one would be great!
-Jan
@Jan, this specifically relates to Live automation of parameters, but you might see some CPU improvements elsewhere.
i had submitted a bug about [screensize] object, and Tom Hall confirmed it, and now i just tested it (in max 7.1) and it seems fixed but i can't recall any notes form the version changes about fixing it
anyways, interesting to see that [function] documentation was updated. Has there ever been a request for larger point size in [function]? Sometimes it can be tricky to grab the point.
thanks for the update
I guess I have no idea what MPE is. I feel weird about that.
Hello everybody,
just installed and here is some issue:
Max7.2 (32 bit) on Windows 7 (64 bit machine)
I just opened an existing project and as I load its main patcher the max window gets filled with "You are using an older version of ..." alerts. One per each external (!) loaded by the patcher...
I reduced my searchpaths to the "factory" ones: User Library, Global Library, Examples and Snapshots and I uninstalled Max 6 and restarted the PC.
The alerts are still there... all of them.
Is this going to affect performance?
How can I clean up this mess?
Many thanks in advance!
@ESTEVANCARLOS:
MPE bundles multiple MIDI channels to play a single sound (one channel per key) - the goal is to achieve expressiveness per MIDI note where MIDI is/was limited to channel commands (e.g. pitchbend) without breaking the MIDI protocol. The seaboard (Roli) is one controller that uses this format.
Cheers Jan
It seems to me that these two patches from the new Jitter tutorial:
jitter_core_-_5_-_Jitter_Matrix_Exploration_1.maxpat
jitter_core_-_5_-_Jitter_Matrix_Exploration_2.maxpat
Are the same.
Thanks
@Haugbui:
Thanks for letting us know and sorry that we missed it. Here is the correct file. If you want it to function within the tutorial system, you can place it in the package here -
Resources/C74/packages/Video & Graphics/docs/tutorial-patchers/
Now it works. Thanks!
The update has broken my computer's ability to make an application with a hidden max console! Up until today I could build my application to launch with the max status window hidden, but now, even with the windowstatus flag set to zero, the max console opens when I launch a newly built standalone. I'm running Max 7.2.1 on OSX Yosemite. I tested this with some older code that I know did not have this problem on 7.2, and I had the same issue there as well.