This page is only visible to admin users. Sorry!

This page is only visible to signed in users.

Contact <link>support@cycling74.com</link> if you believe you're seeing this page in error.

You don't have permission to view this page.

Activity

Billing History for { name }

Licenses

There was a problem removing the addon. Please try again.

Are you sure you would like to remove the <name>{addonName}</name> addon from your Max subscription? Your {addonName} addon license will remain active until the end of your current billing cycle.

{name} was successfully removed from your Max subscription.

Remove Addon

There was a problem resuming your subscription. Please try again.

Are you sure you would like to resume <name>{addonName}</name>? Your billing cycle will be reactivated and you will be billed as normal on {renewalDate}.

Your subscription has been successfully resumed.

Resume Subscription

There was a problem cancelling your subscription.

Are you sure you would like to cancel <name>{licenseName}</name>? Your license will remain active until <expiry>{expiryDate}</expiry>, at which point your subscription will expire and the license will be deactivated.

Your subscription has been successfully canceled.

Cancel Subscription

Next, start up the Max application and sign into your account (Help > User Account and Licenses).

Max has been successfully activated.

You must be signed into your account to activate Max.

Activate Max

Create a New Post

Edit Article

The list of what we're discovering about Max and our users grows each day. We tackle everything from hardware reviews to re-reading books from decades past.

Get the Latest on Max and our Community

Articles

Sign Out

Sign in to authorize License

Authorize Max

Filter by Format

Filter by Language

Find books related to learning Max.

Books About Max

Here are the artists and educators helping people get creative in Max

Meet Our Max Certified Trainers

Certified Trainers

{ firstName } { lastName } - Certified Trainer

There are no open positions at this time.

Please check your inbox for further instructions.

Forgot Password

Error

Success

Actions

Create Forum Topic

Edit Forum Topic

{category} Forum

There was an error submitting your details. Please try again.

Thank you for your submission! Someone will be in touch with you soon.

NFR / Industry Accomodations

Please make sure you use the link you received by email.

There was a problem retrieving your invitation.

Your account has been successfully created. To manage your institutional licenses, please go to <authLink>https://auth.cycling74.com</authLink> and sign in with your newly created account.

You must be signed out to view this page.

Create an Account

Find more details on our <link>Status Page</link>.

Under Maintenance

We are currently carrying out a scheduled maintenance of our website. Some functionality is temporarily unavailable. We appreciate your patience.

Name

Sort By

{ category } Packages

Share a Max Project

Edit Project

Image Notes

Important Notes

Max Projects come in all shapes and forms. Over the years, our users have shared over a thousand ideas and projects with us. We're proud to showcase them here.

Find Inspiration from other Max Users

Cycling '74 will review it within a week and may make minor edits before publishing it, so your project looks best and reads well in our project gallery.

Thank you for your submission! Your project is currently pending.

Account Recovery

Bundled

{ name } { version } Release Notes

There was a problem changing your password. Please try again.

You can now <link>log in</link> with your updated credentials.

Your password was changed successfully.

Reset Password

Your purchase has now been linked to this account. Next, start up the Max application and sign into your account (Help > User Account and Licenses).

Retrieve License

Type

Search the Cycling '74 forums and website

Search {query}

Please enter your educational details

Your Max for Live or Live Suite serial number is required for this purchase. <link>Need help finding your serial number?</link>

There was a problem updating your subscription. Please try again, or contact support@cycling74.com if the problem persists.

Cannot add RNBO

Confirm Subscription Addon

Thank you for your purchase

Thank you

Retrieving your order details, please wait...

Contact <link>support@cycling74.com</link> if you have questions/issues.

Couldn't sign in. Please check that your username/email and password are correct.

Sign in with your Cycling '74 account

There was a problem creating an account. Please try again.

Successfully created your user account! Please check your email for one last verification step.

Create a Cycling '74 account

Select a Product

Thank you! Your request has been successfully submitted to our support team. Please check your email.

There was an error sending your application. Please try again.

There was an error sending your request. Please try again.

By submitting this iLok request, you understand that you will be notified when an asset is deposited to your iLok.com account. After receiving that notification, you can transfer the asset to your iLok USB stick. Please be aware that all iLok requests are manually processed so it can take up to 48 hours to fulfill your request during normal business hours (Monday-Friday, 9am-5pm Pacific Time).

Important Information

Thank you! Your request has been successfully submitted.

Please note that we are no longer taking submissions for Tools and no longer supporting the Tools section, so you may run into broken files and URLs. You can contribute to the Cycling '74 Community by submitting a Package or using the forums instead.

Max Tools Archive

Edit Tutorial

Tutorials are an ideal way to accomplish a task, learn a new strategy or brush up on your skills. In addition to our in-app Examples, Tutorials and Help Files, you can find new ones here.

Explore the Online Tutorials

Tutorials

Thank you. Please start Max and sign in to use your license

Upgrade

Sign In

Your account requires verification. Please check your inbox, or <link>click here to send the verification email again</link> if you didn't receive it.

Unverified Account

Do you have an activation code?

Already own Max 8 and ready to authorize?

Trouble? Please email <link>support@cycling74.com</link> for help.

If you're new to Max, this is just for you.

Thanks for verifying your account!

You're one step closer to being part of the Cycling '74 Community.

Verify Your Cycling '74 Account

Failed to request a new verification e-mail: {message}

A verification email has been sent to { email }. Please check your inbox.

Can't find your verification e-mail or only have an expired one?

There was a problem verifying your email change. Please try again.

There was an error verifying your email address.

Your email address has been successfully verified. Thank you!

Verify Your Email Address

A user token is required to verify your email address. Please follow the link you received via email.

telegrammae

On Windows, two processes spawned by Max 9.0.3 maintain a relatively high CPU usage. Those are 

. Even with no open patches, the processes exist and continuously strain the CPU. In my case, the load is over 10%. They disappear when I terminate the Max application.

On Windows, two processes spawned by Max 9.0.3 maintain a relatively high CPU usage. Those are Node.js JavaScript Runtime and ServiceHost:...

high-cpu-usage-with-no-patches-running-due-to-node-on-windows

High CPU usage with no patches running due to Node on Windows

Oni Shogun

I am trying to relocate patcher windows using JS.

 this method is supported for the Patcher's Wind class:

setlocation(left: number, top: number, bottom: number, right: number): void;

However, this method throws an error. I have fiddled around with other ways to relocate the window but to no avail. Any hidden clues anyone knows of? Bug report?

 object or its properties/methods can be accessed from within JS to, say, change the 

[SOLVED in 9.0.3] patch.wind.setlocation() method not supported

patchwindsetlocation-method-not-supported

Barney Watson

I've taken a bit of a deep-dive into MGraphics since Max 9 came out with the new v8ui object and ES6 support. Over the past couple of days I've been working on an audio-reactive dial.

I was trying to apply a radial gradient fill to a part of the dial. According to both the MGraphics quick-start guide, and the more thorough Max JS API documentation, pattern_create_radial takes 6 arguments: the x and y coordinates of the centre of the first colour stop, its radius, the x and y coordinates of the centre of the second colour stop, and its radius.

In practice, this does not work - the whole shape is filled with the solid colour set for the second colour stop. For example (with relative_coords = 0)...

with (mgraphics){
	arc(0, 0, 200, 0, 2 * Math.PI);
		
	let inner_gradient = pattern_create_radial(0, 0, 50, 0, 0, 100);
        inner_gradient.add_color_stop_rgba(0, 1, 1, 1, 1);
        inner_gradient.add_color_stop_rgba(1, 1, 0, 0, 1);

        set_source(inner_gradient);
	fill();
}

...displays the bottom-right quarter of a circle, filled with solid red.

However, running pattern_create_radial with four arguments appears to work 'correctly'. The first two arguments are the x and y coordinates of the centre of the gradient. The third argument seems to have no effect. The fourth argument is the radius of the first colour stop of the gradient. For example...

with (mgraphics){
	arc(0, 0, 200, 0, 2 * Math.PI);
		
	let inner_gradient = pattern_create_radial(0, 0, 0, 200);
        inner_gradient.add_color_stop_rgba(0, 1, 1, 1, 1);
        inner_gradient.add_color_stop_rgba(1, 1, 0, 0, 1);

        set_source(inner_gradient);
	fill();
}

...displays the bottom-right quarter of a circle, filled with a gradient from white to red.

 guide notes that the pattern_create_radial command was, at least when it was written in 2013, 'not currently working'. I'm unsure whether this bug was eventually fixed - or if I'm experiencing the same issue. At the same time, I might just be misreading the documentation and missing something obvious.

MGraphics radial gradients appear to be broken

incorrect-documentation-for-mgraphics-patterncreateradial

I have been trying in Max 8 and newly in Max 9 to handle/parse (named) arrays passed from Max in JavaScript but I still cannot access their values, let alone nested arrays. Is support for Arrays in JS/V8 part of a future implementation? Or am I overlooking something very obvious? 

max-9-array-support-in-jsv8

[SOLVED] Max 9: Array support in JS/V8 ?

danielj

test-require-package.zip

When trying use require inside a jsextensions folder I get the error:

However, the exact same code will behave as expected when the files are placed outside the Package. I've included a simple package in order to recreate this issue:

When Max launches and the patcher opens, check the max console for the error above.

When trying use require inside a jsextensions folder I get the error:

js calling require without context frame

However, the exact same code will behave as expected when the files are placed outside the Package. I've included a simple package in order to recreate this issue:

1:  Quit Max and then place test-require-package inside your packages folder.
2:  Navigate to  test-require-package > patchers > test and open test.maxpat
3:When Max launches and the patcher opens, check the max console for the error above.


 
When trying use require inside a jsextensions folder I get the error:

js calling require without context frame

However, the exact same 

bug-can't-use-require-inside-jsextensions-folder-in-a-max-package

For comparison here's a version using identical code to the one above, but not including the files in a Package. If you installed the package above in your Packages folder, then launching this patch will trigger the error (this is because the files in jsextensions are global and using a [js] object in any patcher will cause them to be executed).

However, you'll see the message from test-require-patcher is successfully printed below the error messages. 

Bump

Even if this isn't a bug I'd still be interested to know the reason require() doesn't work inside jsextensions. As far as I can see it isn't mentioned as not being supported in the documentation and googling that error message doesn't return anything useful...

Reached out to support and the solution to this was place the files in a folder named code rather than jsextensions 

Bug: Can't use require() inside jsextensions folder in a Max Package.

Brian Gawlik

Has anyone else noticed this or have any information?

I was trying to make a jsui component that displayed some text. Everything worked well at first when I was just displaying a single number, but I noticed that it became really slow/laggy when I tried to add a second number 

 It was actually fine if fontsize was left unchanged, but changing fontsize caused noticeable lag. 

I'm thinking that maybe changing fontsize takes more time than other operations like drawing, moveto, shapes, etc, but damn. Wouldn't expect it to be such a significant impact.

I ended up just pursuing something else, but if I needed text at multiple fontsizes, I imagine I'd have to get creative. Possibly making it so the ondrag() function doesn't call msgfloat() unless the value has changed enough to cause a change in the number ( avoiding unnecessary calls to draw() ).

Curious if anyone has seen this or has any interesting perspective to share!

changing-fontsize-in-jsui-sketch-slow

Changing fontsize in jsui sketch Slow?

Jarrett Confrey

I noticed that the Node.js version bundled with Max is 16.6.0

Node.js 16.x is scheduled for end of life on 2023-09-11

https://github.com/nodejs/release#release-schedule

https://nodejs.org/en/blog/announcements/nodejs16-eol

Node.js 18.x is the current Long Term Support version but goes into maintenance on 2023-10-18

Node.js 20.x is the current version and will become the new Long Term Support version on 2023-10-24

I realize that the node.script object has node_bin_path and npm_bin_path attributes I could use to update my version but I think it would make sense to update the version of node bundled with Max to 20.x

I noticed that the Node.js version bundled with Max is 16.6.0

Node.js 16.x is scheduled for end of life on 2023-09-11

https://github.com/nodejs/release#release-schedule
https://nodejs.org/en/blog/announcements/nodejs16-eol

Node.js 18.x is the current Long Term Support version but goes into maintenance on 2023-10-18

Node.js 20.x is the current version and will become the new Long Term Support version on 2023-10-24

I realize that the node.script object has node_bin_path and npm_bin_path attributes I could use to update my version but I think it would make sense to update the version of node bundled with Max to 20.x

I noticed that the Node.js version bundled with Max is 16.6.0

Node.js 16.x is scheduled for end of life on ... 

bundled-nodejs-version-end-of-life-on-2023-09-11

this is correct, I don’t have an ETA or too much detail right now but we’ll be looking into this for a future update alongside supporting modern module loading that is required by some npm packages. 

In the meantime we recommend using node_bin_path and npm_bin_path as suggested to change the version of node if required. 

Thank you 

Bundled Node.js Version End Of Life On 2023-09-11

Jeff Griffiths

, Max 8.5 ( the version embedded into Ableton Live 11 ) bundles nodejs 16.6, which has been unsupported and has not had any security updates since September 2023. If you intend to build applications in m4l that use node.script, you should be aware of two key issues that affect your ability to support Ableton Live 11 going forward:

1/ node ships with openssl, and the version 1.1.1 of openssl that ships with node 16.6 is no longer supported since Sept 2023. At the time I assume Max 8.6 development was the focus of the team so they decided not to update the embedded version of node in Max 8.5. 

If you use node inside Ableton for networked applications, your applications have known security vulnerabilities.

2/ when nodejs 16.6 was deprecated in Sept 2023, the npm ecosystem moved quickly to drop support for this version, quickly rendering many useful packages as incompatible with Live 11. You will quite often get errors like this:

npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: @sveltejs/kit@2.5.17
npm ERR! notsup Not compatible with your version of node/npm: @sveltejs/kit@2.5.17
npm ERR! notsup Required: {"node":">=18.13"}
npm ERR! notsup Actual:   {"npm":"7.20.3","node":"v16.6.2"}

I contacted cycling '74 support directly and they clarified that they have no plans to update the node version in Max 8.5. They suggested I upgrade to Live 12 to benefit from Max 8.6 and node 20, which I will probably do, because my project is focused on directly embedding web servers and apps inside max for live. If you are working on similar projects, 

you should probably only support Max 8.6 going forward

. This also means dropping support for Ableton Live 11 users, which I had hoped to avoid.

Javascript Forum