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).

Your Activation Code was successfully redeemed.

You must be signed into your account to redeem an Activation Code.

Redeem an Activation Code

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

{ name } Releases

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

You must be signed into your account to activate Max.

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

General

Individual

Institutional

General Authorization

Individual Product Authorization

Institutional Product Authorization

Important Information

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

Max, RNBO, and legacy product authorization for both individuals and institutions.

Product Authorization

 If your inquiry does not fit into any other category, click here!

Other

Sales inquiries for individual licenses purchased from our webshop.

Sales

Technical support inquiries for Max, RNBO, Mira, and Max for Live.

Technical Support

For assistance with your Cycling '74 user account, our website, forums, or the Institutional Admin Portal.

Cycling '74 Account or Website

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.

Daniel Mooney

I'm building a Max for Live device that walks the Live Object Model on set load — reading every track, device, and device parameter to maintain a live session mirror over a local WebSocket. On heavy sets (30+ tracks, 80+ devices, thousands of parameters), the initial walk beachballs Ableton for ~45 seconds.

  The root cause is well-understood: every new LiveAPI(...), .get(), .call(), and .property from the js object is a synchronous round-trip to Live's main thread. The js engine runs on the low-priority thread, but that doesn't help — the LiveAPI calls still block Live's UI thread while they complete. There's no way to batch reads or issue them asynchronously.

  I've thrown every optimization I can at this from the M4L side:

  - Retargeting hot handles instead of constructing new LiveAPI objects (each new LiveAPI registers in a per-device table that never shrinks, and its lookup degrades to a linked-list crawl at scale)

  - Per-tick operation budgets with resume cursors so periodic sweeps have constant main-thread cost

  - Dirty-flag gating so reconcile passes only read what actually changed

  - Deferring parameter attachment out of observer callbacks into coalesced Tasks

  - Caching stable facts (property names, track types) to avoid redundant probes

  These help with steady-state performance, but the initial walk is irreducible — you genuinely need to read every track, every device, and every parameter at least once, and each read is a synchronous IPC to Live's main thread.

  1. Batched reads — a single call that takes an array of LOM paths + property names and returns all values in one round-trip, instead of one IPC per .get().

  2. Async LiveAPI — .getAsync() / .callAsync() that return Promises and don't block Live's main thread while the js engine waits. Even if the reads themselves are still serialized on Live's side, decoupling the js wait from the main thread would eliminate the beachball.

  3. Bulk snapshot — something like LiveAPI.snapshot(path, depth) that returns a JSON tree of an object and its children's properties in one call.

  Any one of these would be transformative for M4L devices that need to read the session state comprehensively. The current model — one synchronous IPC per property read, no batching, no async — makes it effectively impossible to build responsive M4L tools for large sessions.

  Is there any interest in this direction, or any workarounds I've missed? Happy to provide profiling data or a minimal repro.

Feature request: async LiveAPI / batched LOM reads for performance-critical M4L devices

feature-request-async-liveapi-batched-lom-reads-for-performance-critical-m4l-devices

Idriss Sernn

I spent months building a concatenative synthesis device for Live 12 in

TypeScript on Node for Max, and the part that took longest wasn't the audio.

The device analyses a corpus, cuts it into ~90 ms grains, and rebuilds a target

sound out of them. At the end you want the result on pads, playable. The obvious

route is the Live API: make a Drum Rack, load a sample into each pad. It cannot

 wants a BrowserItem, and nothing turns a file path

into one — the browser tree only holds the User Library and folders the user

added. So the API route ends in "copy your sounds somewhere Live can see them and

go find them", which is a file browser detour by another name.

There is a straight road, and it's the one Live's own Convert commands drive on:

with every chosen sound laid end to end and hands over the exact sample offset

each one starts at. Nothing is detected or guessed at the other end: we wrote the

file, we know where the seams are, one pad per sound — where slicing by transient

would have found two in a snare with a long tail.

A few things that cost me time, in case they save you some:

  · the .adg is gzipped XML, and Live is unforgiving about element order

  · a jweb window is a WKWebView on macOS: 

    caret in every text input, silently, while Blink exempts form fields

  · with Live's audio engine off, node.script doesn't boot at all and the

 stays quiet, so the device has to say so

  · Max draws boxes first-to-last, so the FIRST box is the one in front

I spent months building a concatenative synthesis device for Live 12 in

TypeScript on Node for Max, and the part that took longest wasn't...

writing-an-ableton-drum-rack-from-node-for-max-because-the-live-api-cant

Writing an Ableton Drum Rack from Node for Max, because the Live API can't

gmazel

Having Trouble with M4L JS sending an undo to a midi clip that has just changed

    var liveSet = new LiveAPI("live_set");

    outlet(1, "undo error: " + e.message);

Undo function is getting triggered, but Live does not update the undo state to a midi clip. All 

Funny thing, I saw this Undo live.button function 

M4L Midi Device Dev - Having Trouble with M4L JS sending an undo to a midi clip that has just changed

m4l-midi-device-dev-having-trouble-with-m4l-js-sending-an-undo-to-a-midi-clip-that-has-just-changed

Diemo Schwarz

I'm looking for tips and experiences how best to go about controlling specific M4L devices from TouchOSC. This is based on stuff working in Max that I want to port to Live.  I'm not so familiar yet with the LOM and so on, and am happy about all general pointers, too.

My starting point is (left part of the diagram below):

What I'd like to achieve (might look like the right part of the diagram, but maybe there are better ways):

I'm looking for tips and experiences how best to go about controlling specific M4L devices from TouchOSC. This is based on stuff working in...

Max For Live Forum