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.

jake rodriguez

I've got a standalone app I've built in 8.2.0 and running on a Mac Mini M1 processor. When i run the standalone on the mac mini, I get the security "app would like to use the microphone" prompt on every start of the application, despite my having granted it, and every change i make to the audio status also brings up this prompt. if i quit out of the standalone, and check security preferences, i can see my standalone has been granted access to the microphone, but it still prompts me every start and every driver change i make.

I've got a standalone app I've built in 8.2.0 and running on a Mac Mini M1 processor. When i run the standalone on the mac mini, I get the s

standalone-created-in-8-2-0-on-m1big-sur

Hey Jake! I can repro here and we will investigate. It just seems to be a problem on Big Sur (as far as I can tell).

hey Ben. yes--can confirm the security stuff is not an issue on my Mojave machine.

Hi, I think Big Sur tightens up security a bit more than Catalina and insists on a code-signed and properly entitled application for some types of persistent security permissions (like mic or camera). It's unclear from your post whether your app is signed/entitled with the "com.apple.security.device.audio-input" key set to true.

In case helpful, steps for code signing your standalone application are outlined here:

https://cycling74.com/articles/max-8-1-mac-os-10-15-catalina-support-and-notarization

In case helpful, steps for code signing your standalone application are outlined here:
https://cycling74.com/articles/max-8-1-mac-os-10-15-catalina-support-and-notarization

thanks pals for this help. it's been a minute since i've bundled to a standalone and didn't realize Apple had gotten so touchy. will attempt to code sign and try again.

thanks pals for this help. it's been a minute since i've bundled to a standalone and didn't realize Apple had gotten so touchy. will attempt to code sign and try again.
jk

I'm having issues distributing a standalone using a fork of an external (max-ble) which I compile myself.

I'm actually building the standalone on a 2015 macbook pro running catalina, and it doesn't work as expected on a recent M1 macbook running mac os 11, which of course I don't have access to.

I was still using Max 8.1.11 and everything worked fine except the scanning of BLE devices ([max-ble] seemed to work correctly but couldn't find any device), so I gave a try with Max 8.2.2 and apparently it doesn't even open any window anymore, except the console which doesn't display anything.

For information, I distribute the standalone by zipping it and uploading it to a public folder on my server.

Enabling the "rosetta" option on the standalone from the M1 apparently doesn't help in any case.

As suggested by Joshua, I tried to sign the standalone with the following Entitlements.plist file :

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<key>com.apple.security.device.bluetooth<;/key>

codesign -s <my_developer_id> --options runtime --timestamp --force --deep --entitlements ./Entitlements.plist -f <my_standalone_path>

But then when I open the standalone on my machine, no object is found, everything is red and I get a load of error messages in the console, which seems to indicate that my entitlements somehow override default entitlements applied during the standalone build process.

Any further hints on the use of an entitlements file to sign a standalone ?

Any other advice would be much appreciated too.

It looks like things were going better with Max 8.1.11 (and the standalone size was much smaller : 64 Mo with Max 8.1.11 compared to 235 Mo with Max 8.2.2), so meanwhile I'll give another try with it and double check with my standalone user if he didn't do anything that could have prevented BLE devices to be discoverable.

I'm having issues distributing a standalone using a fork of an external (max-ble) which I compile myself.
I'm actually building the standalone on a 2015 macbook pro running catalina, and it doesn't work as expected on a recent M1 macbook running mac os 11, which of course I don't have access to.
I was still using Max 8.1.11 and everything worked fine except the scanning of BLE devices ([max-ble] seemed to work correctly but couldn't find any device), so I gave a try with Max 8.2.2 and apparently it doesn't even open any window anymore, except the console which doesn't display anything.
For information, I distribute the standalone by zipping it and uploading it to a public folder on my server.

As suggested by Joshua, I tried to sign the standalone with the following Entitlements.plist file :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>com.apple.security.device.bluetooth<;/key>
    <true/>
</dict>
</plist>

using the following command line :
codesign -s <my_developer_id> --options runtime --timestamp --force --deep --entitlements ./Entitlements.plist -f <my_standalone_path>

But then when I open the standalone on my machine, no object is found, everything is red and I get a load of error messages in the console, which seems to indicate that my entitlements somehow override default entitlements applied during the standalone build process.
Any further hints on the use of an entitlements file to sign a standalone ?
Any other advice would be much appreciated too.

It looks like things were going better with Max 8.1.11 (and the standalone size was much smaller : 64 Mo with Max 8.1.11 compared to 235 Mo with Max 8.2.2), so meanwhile I'll give another try with it and double check with my standalone user if he didn't do anything that could have prevented BLE devices to be discoverable.

Any news or solutions for this problem? I encounter this problem with Max 8.6.2 and MacOS Monterrey 12.6.1.

On Mac, you need to notarize your standalones to conform Apple security policies... (it's more an Apple problem than a Cyling '74 problem).

It's quite a process and not very user friendly but if you script it, you have to do it only once (until these policies change...).

I make Mac installers with standalones for several years now, and I can report this is working and from what I've seen, the article sent by @Joshua is still up to date.

standalone created in 8.2.0 on M1/Big Sur