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.

neuwirthe

I finally managed to create an AU component plugin with the following interface

In this view, I can only change the parameter values with the mouse, typing does not work

I can enter values from the keyboard, but entering 60 in the centerpitch slot immediately changes the value to 96

I finally managed to create an AU component plugin with the following interface

[Image: image.png ]
In this view, I can only change the...

ui-of-au-component-plugin

UI of AU component plugin

Marigold Maripol

I'm experimenting with a feedback loop idea where jit.world outputs as a texture, sent to jit.gl.asyncread and fed back into the world.

What I don't entirely understand though, is why an erase_color for the jit.world is no longer operational in this context - and whether there might be a way to work around it. 

jitworld-feedback-loop

jit.world feedback loop

F_Dos

I have 4 different patches and I would like to control them from one main patch.

At the main patch I should be able to press a button to open the first patch. another button to close the first patch and open the second one. Another button to close the second one and open the third one and another button to close the third one and open the fourth one. One last button to close the last patch.

How can I do the following?

I have 4 different patches and I would like to control them from one main patch.

At the main patch I should...

one-patch-to-open-and-close-series-of-patches

One patch to open and close series of patches?

In this patch, I am generating a [jit.gl.mesh] shape and a diffuse map from a [jit.noise 3 float32 20 20] object.  I am struggling to get this to apply as the map that I would like, though - since it is only projecting a single color on the shape, rather than a noise character, as it would on a [jit.gl.gridshape].

In this patch, I am generating a [jit.gl.mesh] shape and a diffuse map from a [jit.noise 3 float32 20 20] object.  I am struggling to get...

applying-jitglmaterial-to-jitglmesh

Applying jit.gl.material to jit.gl.mesh

Tomás Cabado

I'm relatively new to Max, and while working on a project I stumbled with a problem I cannot sort out. I'll try to be as simple as I can as uploading the patch with its subpatches would be unpractical, while giving the most precision I can.

In my patch I have 12 instances of a synthesizer (which is 2 voices [poly~] for reasons I'll explain in a moment) and to all of them I send the same adsr values through [send], using [line~] as method to process the attacks and releases. From a root frequency I generate, with several [expr], one pitch for each of these instances, which is at a specific interval in just intonation from the fundamental (instance 1 has the fundamental pitch, instance 2 has its 5th, instance 3 its 3rd, etc). With a toggle I send the attack and release of each instance. All fine until here, but the issues come when I modify the pitch on the fly.

I have two ways of doing this. One is by affecting the octave of the pitch of each instance with [incdec] and an [expr]. The other one is by modifying the fundamental pitch through transposition by an specific interval, which provoques changing all pitches. Therefore I'm sending three messages to each instance: frequency [float], octave shift [int] and attack/release (1/0). I'm using a 2 voices [poly~] as I try to achieve a crossfade when an active instance receives a new pitch. That's when I have troubles, so here's what I want to achieve:

- When the instance receives an attack (1), it triggers the frequency and then sends the attack to the first voice of [poly~].

- If the frequency changes while one voice is sounding (i.e. while the instance is active), it turns out that voice, triggers the new frequency and then sends an attack to the new voice. This repeats alternating between both voices as long as the instance is active and the frequency changes.

- When the instance receives a release (0), it sends an off message to the active voice.

- If a frequency changes while the instance is inactive, it doesn't trigger any attacks.

- The 2 voices of each instance exist only to achieve crossfade between different pitches, they are never on sustain at the same time.

Hope this is somewhat clear. I've tried several options getting more or less success, but at some point something fails (triggering a release for an inactive voice, or not matching the voice with the correct frequency after transposing back and forth), and I think mostly my problem has to do with the order in which data flows. Hope somebody can help me with this!

I'm relatively new to Max, and while working on a project I stumbled with a problem I cannot sort out. I'll try to be as simple as I can as...

handling-frequency-attackrelease-and-octave-shift-for-several-instances-of-a-synth

Handling frequency, attack/release and octave shift for several instances of a synth

ianjojo

So I know this is an oft brought up topic after searching through this forum.  I just thought I'd bring it up again and see if anything has changed.

I have an M4L device with randomization controls and each time a parameter is changed it adds to the Live undo history.  When using an LFO to control many parameters often, this of course makes regular undo tasks impossible due to all the changes added.

I know I can change the parameters to hidden to prevent this but I do want the device dials to be mappable.

to adjust parameters without adding to the Live undo history, but it seems that the ids for my live.dials change with every load of my device.  Also, I'd like to eventually share this device with others.  So I guess my question is, is there a reliable way to first "get" each param id that I need upon device load?

Or is there some way in 2025 that this can all be handled better? 

Hi all,

So I know this is an oft brought up topic after searching through this forum.  I just thought I'd bring it up again and see if...

clogged-undo-history-in-live-due-to-randomization-controls

Clogged undo history in Live due to randomization controls

I just started working with the min-devkit a little bit and I am running into a weird crash I don't quite understand (see code snippet below).  I am on Sequoia 15.1.1 on a 2023 M3 using Max 8.6.5.

If I send something out an outlet, starting with a string followed by a single number (e.g. float), that works. Anything else seems to cause a crash.

What I am trying to do is add a string before a list of floats so I can use [route] in max to further process the output.

Furthermore, when I use a string followed by atoms 

No matching member function for call to 'push_back'

referring me to c74_min_outlet.h line 282

 // utility: queue an argument of any type for output
    template <typename argument_type>
    void queue_argument(const argument_type& arg) noexcept
    {
        m_accumulated_output.push_back(arg);
    }


 to add a value to the end of it. However, if I look at the type of m_accumulated_output it is of type 

If I go to c74_min_atom.h it clearly states on line 319 that:

// We don't own the array of atoms, so we cannot do these operations:
    // insert
    // erase
    // push_back
    // push_front
    // pop_front
    // pop_back

I might have a fundamental misunderstanding here, but it looks like that if we deal with atoms we can't use 

, but in queue_argument() from c74_min_outlet.h (line 282) we clearly use .push_back() to try to add something to 

So, long story short: what is the correct way of sending something like:

std::vector<float> data = {....};
std::string routing = "data";

to_outlet.send(routing, data);

Cycling '74 Forum