Announcement: The Max 8.2 Public Beta
We are happy to announce the Max 8.2 public beta. Max 8.2 will be the first version to natively support the latest Apple Silicon based Mac computers. We’re all excited by the potential of these machines and look forward to hearing your reports using this update. Beyond native support for Apple Silicon, the underlying infrastructure of Max has been updated on every platform and a big list of bugs have been fixed and a few new features have been added. Testing on any machine you use for Max (including Windows) will help ensure that no new problems have been introduced as a result of these changes.
Like many of the big platform transitions we have been through (OS 9 to OS X, Mac Intel, Mac to Windows, 32-bit to 64-bit), we hope we can count on the support of the whole community to try things out and let us know what’s working. We also know Max is much more than the core application and will be working closely with third-party developers to get packages and externals recompiled and ready to test using the updated SDK.
Keep in mind that third-party externals will need to be recompiled to provide native support for this new architecture, so Apple Silicon testing should be restricted to core features and externals that have been updated with the most recent SDK. Testing with existing third-party objects on all other platforms will be helpful.
You can download the Max 8.2 public beta here:
https://www.cycling74.com/public-beta-download
Over the course of the public beta period, new installers will be made available at the above link and announced here via a new Beta forum post (which will outline any additional improvements and fixes).
Please report any problems you experience on the Cycling ‘74 Beta Forums, with clear and complete information.
Here are some of the key improvements in Max 8.2 that we'd like to highlight:
Mac arm64 support
The most notable addition, this brings native support for the latest Apple Silicon-based Mac computers.
CEF Update
We've updated our shipping version of Chromium Embedded Framework to CEF 90.
Dynamic Colors
To make the colors in your patches and devices more responsive to the environment they find themselves in, we've added the ability to reference Max / Max for Live application colors via static names that automatically adjust to follow the active Max/Max for Live color themes.
Documentation Browser Updates
The Documentation Browser has a new home page, spiffy new navigation tools (breadcrumbs, open in browser, sidebar tweaks), and a brand new Glossary of Max terms.
live.adsr~ / live.adsrui
These are two new objects for generating and visualizing sample-accurate Attack-Decay-Sustain-Release envelopes.
Improved Random Numbers
Some objects now take advantage of a new random number generator implementation that is more efficient and has improved statistical qualities. Some of the affected objects include noise~, noise in Gen, random, drunk, decide, urn, and live.step.
Node for Max Update
The shipping version of Node has been updated to v16.6.0.
Jitter Tools Package
This package is a collection of tools that we think almost any Jitter user will want to take advantage of. Currently, this package features three tools: jit.gl.textureset (a texture version of jit.matrixset), jit.polymovie and jit.gl.polymovie (polybuffer type objects for movie files), and jit.gl.meshwarp (customizable grid of points to control the shape of a mesh and associated texture).
loadbang on paste / Reinitialize
There is a new preference called 'Edit Operations Trigger Loadbang', which allows for loadbangs to be fired when pasted. There is a new entry in the Edit menu, 'Reinitialize', which will fire loadbang and loadmess objects in the parent patcher all the way down the patcher hierarchy.
200+ bug fixes
That’s a lot of bug fixing!
Take a look at the detailed list of New Features and Bug Fixes here:
http://cycling74.s3.amazonaws.com/support/version_8_2_0.html
Thanks in advance for your participation and feedback, which will continue to inspire us to push Max forward into the future!
Hi there, very excited for this update!
Is it only me having issue with this version? It keeps crashing when I try opening any patch file. Is anyone having the same issue?
Hi yoshie026! Sorry to hear you're having issues. Please try a clean install first to see if that fixes the crash. If you still have issues, send over your Support information, crash log, and detailed steps to reproduce. You can find a summary of everything we need for bug reporting here.
In the future, please feel free to make a new post on the beta forum to report any issues that you have.
Noted! Thank you, Ashely.
Amazing update! Big thanks to everyone who worked on it.
Exquisite!!! Is this to say we mac users shouldn't update if we rely on intel-compiled externals? or is there a backward compatibility mode similar to the 32-64 bit transition?
Thanks Crew! Ever Max!
Thank you so much for the expand feature in the dict-view object. It's now useful for viewing large dictionaries in a controlled fashion. Excellent!
@AUDIOMATT You can use this build on either Intel or M1 machines, but if you want to run natively on M1 machines, only externals compiled for arm64 architecture will work. On these machines, you can run Max 8.2 in Rosetta 2, which will allow old externals to be used. In the Finder, select the Max.app, then go to File->Get Info and select "Open using Rosetta" in the Info window.
@Ben Bracken Got it!!!! Thank you!
We've just released new installers for the Max 8.2 public beta (build bfe3faf7). You can download the update here:
https://cycling74.com/public-beta-download
We've fixed a few things that have come up since last week, and added a few new features, all listed below.
If you want to see all the improvements in Max 8.2 so far, you can find them here:
https://cycling74.s3.amazonaws.com/support/version_8_2_0.html
Although we would love as much testing as possible, please keep in mind that this is beta software, so we recommend that you do not use it for any mission-critical work.
Thanks for all of the feedback so far, keep it coming!
Ben & Cycling '74
New Features
• node.script: restart attribute to suppress restarts on uncaught errors
• Reinitialize: parameters are reset to initial values
Fixed Bugs
• Save dialogs: improved usage when there are no writable types specified
• Patch loading: improved patch / project loading times
• attrui: improved switching between dynamic and regular colors
• jit.gen: fixed wrap algorithm
• node.script: works on standard user account
• Projects: disabled amxd type in inspector when Max is the M4L editor
• node.script: tmp folder sockets are cleaned up
• attrui: color chooser works right away
• Package Manager: fixed blank rendering
• pitchshift~: fixed issues with 'enabled' attribute
• gen~: fixed NaN reporting when 'Show CPU Usage' is enabled
• Poundsign replacement: fixed object_attr_enforcelocal errors
Hi Ben, do you know if the font-size bug for the max console has been fixed on Mac? It would be really nice for teaching online to be able to increase the font of the Max console. (Reported it about a year ago)
@IAIN It appears that the Max Console font size can be set per-session by selecting a line in it, going to Object->Show Fonts and selecting the size you would like, or setting it in Max->Preferences->Max Console Font Size. However, it doesn't look like the font size gets applied when restarting. I've made a note of this.
After a short recon on 8.2 I have an impression, that package manager works much more reliable (at least on my laptop [MBP, Intel, Big Sur]) - previously, package manager would often stop somewhere along the way (though, in the end, a restart did the trick). I don't know if it's a coincidence or some kind of fix, but I'm very happy about it.
Oh... Jitter Tools Package... that's a real time saver... or maybe time consumer as I will probably spend a lot of time with this package.
I didn't find anything about this missing mc.poly~ feature in the list, which is a showstopper for multichannel synths: https://cycling74.com/forums/no-mc-out~
Excited about live.adsr~ !
We've just released new installers for the Max 8.2 public beta (build c5aea01). You can download the update here:
https://cycling74.com/public-beta-download
We are continuing to fix bugs that come up during the beta, so be sure to take a look at the list below.
If you want to see all the improvements in Max 8.2 so far, you can find them here:
https://cycling74.s3.amazonaws.com/support/version_8_2_0.html
For M1 users out there, we'd love to hear about how these builds are performing for you, both natively and in Rosetta. Thanks!
Ben & Cycling '74
New Features
• Message to Max: userdb.resetvalidated resets list of extern validations
Fixed Tickets
• 3rd party objects install / quarantine: cache improvements
• M4L timing: improved locked metro accuracy
• jit.movie / AVF video engine: frame or frame_true messages work as expected
• poly~: fixed crash when multithreading is enabled and there is no audio device
• pattr bindto: finds correct attribute
• hint attribute: hint correctly hidden in presentation mode when object is not
• limi~: ref page opens correct help file
• filtergraph~: added retro-compatible messages for gainresonant / gainapass
• bpatcher: eliminated visual glitching when resizing new view
• amxd~: fixed crash when instantiating while active is set to 0
Small question: Did something change in the permissions that allows max patchers/js to write in the application package contents? I have always used the max-toolbox and in previous versions you could click "activate" in the patcher on first startup and it would write a patcher named "toolbox-start.maxpat" in Resources/C74/max-startup. Now since the beta it doesn't do that anymore and instead the patcher ends up in the toolbox package in the "extra" folder, which does not start itself when starting Max. It's not a big deal, I can move the file manually, but maybe this behaviour was not intended or effects other patchers as well.
@TIMO I'm not aware of any change in that department, but I would strongly discourage writing anything to the app package. It sounds like this package needs an init folder.
We've just released new installers for the Max 8.2 public beta (build f87939c). You can download the update here:
https://cycling74.com/public-beta-download
We are continuing to fix bugs that come up during the beta, so be sure to take a look at the list below for this week's improvements.
You can check out the complete list of improvements in Max 8.2 here:
https://cycling74.s3.amazonaws.com/support/version_8_2_0.html
Thanks for taking a look!
- Ben & Cycling '74
New Features
• GL3: now a factory package (included with install)
Fixed Tickets
• amxd~ / vst~: re-fixed drag and drop behavior
• dict: improved saving / window closing behavior
• dict: fixed writeagain issues
• jit.gl.model: fixed file loading when embedded in M4L device
• parameters: load correctly when hot swapping bpatcher contents
Hey do you have plans to get [mc.gain~ @multislider 1] working w/ [preset] that doesn't recall sliders at this time. https://cycling74.com/forums/bug-report-mc-gain~-w-preset
Thank you for max improvments .
Omg.
jit.gl.textureset
jit.gl.polymovie
And more...?
I should directly upgrade FRGMENTS peojext
https://julienbayle.net/works/frgments/
This week's Max 8.2 beta installers (build ba4ca3e) are now available for download:
https://cycling74.com/public-beta-download
Check out the list below for the improvements in this week's release. Thanks for taking a look!
New Features
• jit.gl.pass: bloom-hq effect and corresponding SUBPASS functionality / documentation
• Package Manager: option to 'update all' that have available updates
Fixed Bugs
• absolutepath: fixed issues when using '.'
• Dynamic Colors: locked_bgcolor does not overwrite bgcolor
• Gen noise: no longer outputs a -1
• jit.dx.grab: fixed alpha channel when output_texture is enabled
• jit.gl.model: files can be loaded from Projects and collectives
• Object Palette: icons added for all live.* UI objects
• Package Manager: Website link styled correctly
• Patcher Templates: dynamic colors can be used
• Patching: don't try to autoconnect when target has no corresponding inlet/outlet
• pattrstorage: fillempty handles missing values in pattr objects appropriately
• vst~: fixed cases where sampling rate and vector size is ambiguous
thanks for this awesome update.
however I am still having problems loading not ARM extentions.
is there a fix - workround yet.
@BALAM Although Cycling '74 is attempting to update the Packages we maintain, many Packages on the Package Manager are maintained by third parties. For Packages that have not yet been updated to support arm64, you can run Max 8.2 in Rosetta 2, which will allow old externals to be used. In the Finder, select the Max.app, then go to File->Get Info and select "Open using Rosetta" in the Info window, then open the Max app. You should be able to download and use non-arm64 Packages in this mode.
Here are this week's beta installers (build 665eec0):
https://cycling74.com/public-beta-download
A handful of improvements are in this week's builds, so be sure to check out the changes below. Happy patching!
New Feature
• dict.route: permit comparisons of nested elements
Fixed Bugs
• autoconnect: fixed usage in Gen patchers
• dict: parameter attributes approriately shown in the inspector
• jit.gl.material browser: is theme-aware
• jit.gl.model: fixed errors and crash when banged before jit.world is enabled
• jit.gl.model: improved fix for multiple context errors
• live.meter~: bgcolor appropriately applied
• Max application: fixed potential crash on quit (Windows only)
• maxdb: improve warning when attempting to rebuild database while another rebuild is active
• Object Browser: Max for Live UI objects shown in correct category
• peak: fixed bad reporting when float ends with an odd number
• Snippets: fixed crash on save
• Video Browser: fixed crash when playing some files (Windows only)
Dear Friends
I found this info at https://cycling74.s3.amazonaws.com/support/version_8_2_0.html:
"jweb: allow "max" property on root object (ie window) to be writeable".
Can anyone explain to me (or indicate where to get the information from) what it basically means? For example, can I change the root object (to which the max API is attached) from "window" to some other?
I probably missed something, but I can't figure it out on my own.
thank you in advance
congrats Cycling'74 team!
@YANIKI This improvement stemmed from an issue where a web page had a 'max' property of the global Window object and therefore wouldn't render. This change fixes web pages that rely on writing to window.max. It should be noted that such pages won't be able to use window.max for jweb <-> Max API usage, but at least it won't break other jweb instances.
Dear Ben
Thank you very much! I have to conduct some tests, but for now, from my point of view, it looks like this is a great improvement, solving a lot of problems and saving a lot of time.
Was working great for two days, now it will not open in regular or rosetta mode. I will wait on next version as I don't have much time to debug right now, but was quickly getting attached to hit.gl.polymovie and hit.gl.meshwarp. Will these be backwards compatible soon? PS max 8.1 still runs fine. Thanks for all your work!
@CHRISTOPHER thanks for the report. Can you describe what happens when you try to open the app? Does it silently quit?
What exact OS version are you running? We have had some reports of 11.4 having issues. An update seemed to solve the issue in that case.
One thing to look at is the output log in the Console utility (in /Applications/Utilities). I recommend starting it up, clearing the console, then starting up Max.
What happens when you try trashing your preferences? They are located here:
~/Library/Application Support/Cycling '74/Max 8
I have Mac 11.6 on M5 or M1 or whatever... I watched in the console and duplicated opening process a few times. Finally it opened. This is what the last report was before I had a success.... Not sure why I eventually had success, I never got to trashing preferences. Seems related to NDI, which I have the newest version of, maybe? or not.
copy/paste console follows....
Sep 27 20:09:00 ChristopherOs-MacBook-Pro login[3165]: USER_PROCESS: 3165 ttys001
Sep 27 20:09:01 ChristopherOs-MacBook-Pro Core Audio Driver (NDIAudio.driver)[273]: [NDIVA1 273 : 2854] has_property : unkwown property taps
Sep 27 20:09:01 --- last message repeated 6 times ---
Sep 27 20:09:01 ChristopherOs-MacBook-Pro Core Audio Driver (NDIAudio.driver)[273]: [NDIVA1 273 : 2854] has_property : unkwown property cfsz
Sep 27 20:09:01 --- last message repeated 1 time ---
Sep 27 20:09:01 ChristopherOs-MacBook-Pro Max Helper (GPU)[3196]: getattrlist failed for /System/Library/Frameworks/OpenGL.framework/Resources//GLRendererFloat.bundle/GLRendererFloat: #2: No such file or directory
Sep 27 20:09:01 ChristopherOs-MacBook-Pro VTDecoderXPCService[3199]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated; set a breakpoint on _dispatch_bug_deprecated to debug
Sep 27 20:09:01 ChristopherOs-MacBook-Pro VTDecoderXPCService[3199]: DEPRECATED USE in libdispatch client: Changing target queue hierarchy after xpc connection was activated; set a breakpoint on _dispatch_bug_deprecated to debug
Sep 27 20:09:01 ChristopherOs-MacBook-Pro VTDecoderXPCService[3199]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated; set a breakpoint on _dispatch_bug_deprecated to debug
Sep 27 20:09:01 ChristopherOs-MacBook-Pro VTDecoderXPCService[3199]: DEPRECATED USE in libdispatch client: Changing target queue hierarchy after xpc connection was activated; set a breakpoint on _dispatch_bug_deprecated to debug
Sep 27 20:09:01 ChristopherOs-MacBook-Pro VTDecoderXPCService[3199]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated; set a breakpoint on _dispatch_bug_deprecated to debug
Sep 27 20:09:01 ChristopherOs-MacBook-Pro VTDecoderXPCService[3199]: DEPRECATED USE in libdispatch client: Changing target queue hierarchy after xpc connection was activated; set a breakpoint on _dispatch_bug_deprecated to debug
Sep 27 20:09:01 ChristopherOs-MacBook-Pro VTDecoderXPCService[3199]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated; set a breakpoint on _dispatch_bug_deprecated to debug
Sep 27 20:09:01 ChristopherOs-MacBook-Pro VTDecoderXPCService[3199]: DEPRECATED USE in libdispatch client: Changing target queue hierarchy after xpc connection was activated; set a breakpoint on _dispatch_bug_deprecated to debug
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0400-0000-0000-000000000000[3155]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0500-0000-0000-000000000000[3157]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.02000000-0100-0000-0000-000000000000[3154]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0500-0000-0000-000000000000[3144]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.06000000-0300-0000-0000-000000000000[3152]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0000-0000-0000-000000000000[3131]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0100-0000-0000-000000000000[3130]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0C000000-0200-0000-0000-000000000000[3138]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0500-0000-0000-000000000000[3139]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0000-0000-0000-000000000000[3132]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0400-0000-0000-000000000000[3143]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0D000000-0500-0000-0000-000000000000[3156]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:16 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0300-0000-0000-000000000000[3158]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:44 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0E000000-0700-0000-0000-000000000000[3159]): Service exited due to SIGKILL | sent by mds[105]
Sep 27 20:09:49 ChristopherOs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0000-0000-0000-000000000000[3162]): Service exited due to SIGKIL
PS... When it succeeded it was in Rosetta mode. Though it had been in that mode for a few retries and restarts. I'll try opening it in native mode as soon as I get some work done...
OK... Both modes work, but crashes as soon as I load my patch with NDI stuff. What made it finally work was that it wasn't opening patches from last session (which contained a old version NDI external). So all is goodish. Although, I would think the rosetta should have handled it... Anyways, thanks. But again, will you make the new jitter objects Mac-backwards compatible, and windows compatible? Maybe they already are, I haven't duplicated them...?
We have no plans to back-port any of the new features in Max 8.2.
It does seem like the NDI externs should work in Rosetta. I'd recommend contacting that developer to see if they can repro, or plan on updating them.
Here are this week's beta installers (build 6465d36):
https://cycling74.com/public-beta-download
We've fixed a few older bugs and a recent regression in Gen cycle, so be sure to check out the short list of improvements below.
Thanks for the feedback so far, keep it coming!
Ben & Cycling '74
Fixed Bugs
• delay: Fixed potential ITM crash
• Gen cycle: fixed phase errors
• jit.gl.material: fixed normals and lighting calculations for vtf-normals
• jit.phys.*: fixed potential crash when retrieving object arguments
• JS maxObjListener: fixed issues with listening to some some attrs
• triangle~: improved argument / attribute parsing
Dear Friends
Maybe this is a stupid question and I just forgot, how [select] always behaved, but I'm expecting, that if I send a list into the [select] and first element of the list is not handled entire list will by passed into rightmost outlet (and I thought rightmost outlet would do the same for [route] and [select]). But I see, that only first element of the list is passed...
Max 8.2, of course, so I'm asking in this topic ;-)
As far as i know [sel] always worked with only a single value. What you are looking for can be achieved with [routepass]
As far as i know [sel] always worked with only a single value. What you are looking for can be achieved with [routepass]
Yes, that's the way set works.
I think there was a modification to select a version or two ago but I think it was just that it got extra inlets.
memory could be incorrect.
Haha... false memories syndrome.. ok, thanks.
As Windows 11 is returning to rounded corners, any chance of Max having rounded corners again? I designed my website with rounded corners because that's what Max used, lol.
hello.
Can someone confirms than using "Convert last message to object" truncates long lists on 8.2 ?
(right click on a cord patch)
It seems to only create a message with the 10 first elements...
@SCHLAM Due to some technical limitations, this feature will truncate lists longer than 10 items. We've updated the documentation to reflect this.
Hello Ben
Thanks to answer..
It should be a very useful (at least for my usage) to be able to use " Convert last message to object " without truncation...maybe one day =)
But I have found a real performance downgrade between 8.1.11 and 8.2beta while used with Live 11.1b3.
Maybe a bug..
The devices attached below are only parts of a bigger patch, I tried to isolate the problem.
Steps to reproduce :
-load the attached live.set in Live 11.1b3 bundled with Max 8.2beta
-There is two devices. 0ne is a device containing a [vst~]
-load a VST with the button (in my case I use this device with DIVA. I don't have any other "big" vst to try.)
-in the other device : save one of the two preset slots.
-in the VST device, open the vst window and choose another preset
-save the another preset slot in the first device.
-move the pink dial quickly with the mouse
Results :
with max8.2b the slider is very laggy, the synth morph is not smooth at all
--> in Live's preference, choose to do not use the bundled version and choose max 8.1.11
, restart Live,
- do previous steps again
-->now with max8.1.11 and the same Live 11.1b3, the slider and the morph of the vst are totally smooth.
Can you reproduce that ?
I am on windows..
Thank you !
Julien
@JULIEN I can't repro with the plugins that I have. Can you send me a link to the plug that you are using?
I used DIVA 1.4.3 from U-he. https://u-he.com/products/diva/
I didn't find any demo for you to test
I did the test with other vst. With "little" ones it's working the same in both max versions.
But for "big" vst (more than 250 parameters), here, the difference is really high in the smoothness of the slider !
I can reproduce the issue with Serum,
A demo is downloadable at the bottom of this page :
https://xferrecords.com/products/serum
Please do the same procedure,
here with Live11.1b3/max8.2b -> after saving two differents presets ; slider is veeeery laggy.
with Live11.1b3/max8.1.11 -> slider perfectly smooth !
@SCHLAM Thanks for the additional steps, I think we have tracked down the issue and will investigate a fix.
Great !
20% faster on Win10, thank you very much!
Hello.
There is a new live beta bundled with a new max 8.2 beta. Can we have the release notes of this new max version please ?
Thx!
https://www.ableton.com/en/release-notes/live-11-beta/
Yes thank you, I already saw that but Ableton only talks about improvment of Live, they just said that this new beta is bundled with Max build version 8.2.0 Beta 6465d36.
..We don't know the specific release notes about this new Max beta version..
Max build version 8.2.0 Beta 6465d36 - https://cycling74.com/forums/annoucement-the-max-8-2-public-beta/replies/1#reply-61560c1f7dd9204775a5d73f
Thank you Rob !
I didn't see it was not a "new" beta release.
We've just released the official version of Max 8.2, and there have been a few fixes for bugs that were introduced during the development process. They are listed below.
You can download the official Max 8.2 release installers here:
https://cycling74.com/downloads
Thanks for all of the testing during the beta!
Ben
• Audio Driver: fixed hang when enabling overdrive and audio is on (Win only)
• Audio Driver: fixed setting default audio driver
• coll: UTF-8 strings work as expected
• Debugger: fixed hang with breakpoints (Win only)
• Doc Browser: Home / Index page loads even while DB is rebuilding
• Doc Browser: Home page loads when selected package is not present in Database
• Package Manager: improve the reporting of compatible versions of packages
• patcherargs: fixed issues with initialization
• pitchshift~: fixed issues with attr state being saved unknowingly
• poly~: fixed crash on sending target messages with no patcher loaded
• retune~: fixed authorization warning on first instantiation
• vst~: improved performance when updating many parameters at once
" • vst~: improved performance when updating many parameters at once "
thank you so much !
Hi,
I can't get my patches to run on Apple silicon that are using the SQL wrapper Andrew Benson demonstrated in this tutorial. As it works on my intel Macbook I suppose this is a silicon issue.
Is this known and are there plans to fix it? Maybe there is even a better SQL-Max connection existing or planned that I somehow don't know? I am struggling with the low priority js wrapper solution at the core of these patches anyway... If anyone has a solution I'd be very happy.
Cheers