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.

Harry May

It seems that a subdiv in a newly loaded patcher wont evaluate a recently assigned prob value as soon as the transport starts...is there a workaround for this?

If you load up this example patcher and then start the transport, the first subdiv of 16 gets output according to subdiv's default @prob 1 while the following subdivs get the more recently assigned prob 0. On subsequent loops, no subdivs are output so its only that first loop where the new prob value isn't evaluated for the very first subdiv. 

This is a dumbed down example but its causing me problems in a sequencer device I'm building whereby the first note is often triggered when it shouldnt be or not triggered when it should be after my device has been loaded and the transport is started for the first time. Beyond that first time, the first subdiv is output correctly. 

For anyone who might want to test it more quickly by deleting/re-loading the device in Live i'll include an .amxd

subdiv-prob-issue.amxd

It seems that a subdiv in a newly loaded patcher wont evaluate a recently assigned prob value as soon as the transport starts...is there a...

fist-subdiv-not-output-when-using-phasor-lock-1-and-transport-is-started-for-the-first-time

Fist subdiv not output when using phasor @lock 1 and transport is started for the first time

Daniel Neshama Itach

So, I built this M4L device. It works great in Max MSP standalone but 

doesn't output audio when running inside Ableton Live

*It does output audio to live when I open it in edit mode. Never happened to me, so weird.

So, I built this M4L device. It works great in Max MSP standalone but doesn't output audio when running inside Ableton Live.

*It does...

no-audio-output-only-when-opened-in-edit-mode

No audio output, only when opened in edit mode..?

izuru inayoshi

I'm developing a Max for Live audio effect called 

 which randomly extracts spectrums from the input audio to create and output grains. I'm struggling to implement a 

 object to allow for multiple overlapping grains. I've tried solutions suggested by AI and various patches found online, but none of them worked. Could anyone provide a working solution or advice on how to properly implement round-robin with 

Spectral Grain Filter prototype.amxd

I'm developing a Max for Live audio effect called Spectral Grain Filter which randomly extracts spectrums from the input audio to create...

implementing-round-robin-voice-allocation-with-poly-in-a-max-for-live-audio-effect

Implementing Round-Robin Voice Allocation with poly~ in a Max for Live Audio Effect

Uasmi Nasser

I'm trying to implement a saving and recalling presets functionality using dict and js. To access an object within a subpatcher with a unique name ("---object", for example), I am using this code:

return this.patcher.getnamed("---main").subpatcher().getnamed("---object").getvalueof();

This works fine until I try to use it after freezing the patcher, where I start to get error messages saying that the object is null. I assume this is related to unique names being assigned with additional characters after freezing? Or am I missing something?

Just to reference the structure of the patch - both dict and js code are located and called in the main patcher, and the objects (with unique names) I'm trying to access are located in the subpatcher (with a unique name as well).

Hi,

I'm trying to implement a saving and recalling presets functionality using dict and js. To access an object within a subpatcher with a...

saving-and-recalling-presets-with-javascript-and-dict-in-m4l-device

Saving and recalling presets with Javascript and dict in M4L device

Ulrich Hofmann

I recently started to experiment with M4L (which is part of my Ableton Live Suite). In addition to all the VST instruments, I have a real Roland JV-1010 that is controlled as an external instrument via a M4L device that I got from Matthew B on the gumroad website (Roland JV-1010 Controller (for Ableton M4L) 2.0).

This device allows to set all the JV-1010 settings via midi messages (which is great). However, the main control (the Category/Bank selector) does not allow automation / mapping knobs on my keyboard to that control.

Now, digging into the M4L code, this control was/is implemented as a jsui object, more specific, as a jsui 360 dial, with “parameter_mappable” grayed out. Reading through the various articles on js, jsui and parameter mapping, I found that this is because the “type” is set to “blob”, and blob does not allow mapping. So, I changed the type from "blob" to "float", changed the parameter visibility to "Automated and Stored", and made sure that all the js methods are implemented (setvalueof(v), getvalueof()).

Now comes the part that I cannot figure out... When I save these changes using Max's "File/Save", and then lock and freeze the device to test it, the mapping just works fine - I can map the 360 dial to my keyboard, perfectly working. But when I close the Max window, all the changes are lost, the mapping capability is gone. When reopening the Max window, I can see that the type reverted back to "blob"...

What am I doing wrong, or is there a reason that the jsui object is only allowed to be a blob type?

jsui-object-reverts-babck-to-blob-type

jsui object reverts back to "blob" type

Pselodux

Hey folks, I've encountered an issue with mc.gen~ when used in poly~ in M4L devices. 

If I have a 16 channel mc.gen~ patch inside a poly~ container, 

 will return 0 on load, even though the patch has been instantiated correctly with 16 channels. For the device I'm developing, I use 

) to calculate harmonic spread for resonators in a modal synth engine. 

 returns the correct channel number, and the patch still makes sound, which shows that the patch is loading correctly, it just doesn't sound right of course.

Strangely, adding a dummy gen~ patch to the device's main patcher fixes this issue, and it shows 16 channels on load. So this is my workaround for the time being, but it feels like a bug to me, particularly since the same patch works correctly in Max standalone.

See attached device (and poly~ abstraction) for an example. 

test.amxd

test.maxpat

Hey folks, I've encountered an issue with mc.gen~ when used in poly~ in M4L devices. 

If I have a 16 channel mc.gen~ patch inside a poly~...

mcchannelcount-not-working-correctly-in-mcgen-in-a-poly-container

mc_channelcount not working correctly in mc.gen~ in a poly~ container

Wouter Van Daele

: I kinda fixed it by removing the observer and using a metro instead. Seems to work as intended now

So I'm trying to build a "MD Assistant" plugin. Excuse me if this already exists but I couldn't find exactly what I was looking for.

So the plan is to have a device that lists all clips in the arrangement view for the device's track. I want to enable the user to specify the number of times the clip should be looped before continuing (like vamps). I want the clip (or track) to be muted for all passes except the last one. This way, I can put some callouts and countdowns on the track that will be sent to the musicians in-ears only. There should also be an option to end the loop prematurely if the MD wishes to do so. In that case, the loop should be disabled and the clip should play as normal.

I had a go on this with some help with copilot (total noob here, but have some JS programming experience), but it doesn't work as expected. A lot of transport.set instructions seem to get lost or are blocked with a warning that I need to defer my response (which I thought I was doing)

Any help in debugging this is helpful. It is still lacking a lot of the functionality. What I have here is populating the UI and if you set the counter to a non-zero value, the clip should loop exactly that many times before continuing.

clips.js

MD Assistant.amxd

UPDATE: I kinda fixed it by removing the observer and using a metro instead. Seems to work as intended now

So I'm trying to build a "MD...

need-help-setting-loop-controls-from-js-script

Need help setting loop controls from js script

Julien Bayle

observing property playing_slot_index works fine (since 2011) but I noticed that it notifies also if you just add a note or edit the midi content of the clip, which is probably a kind of logic for some people but not for some others.

Actually, you play a clip. live.observer detects the one you play, fine.

You manipulate the content, it notifies again.

Live 12.2.1 / Max 9.0.7 (the one provided with Live)

Of course, working around it is possible as there are two different temporalities (in my process, at least): playing (and using the index for doing something, here triggering a markov chain :-)  & editing, so I can gate it and create kind of edit/play modes.

But wanted to report it as I didn't see it somewhere but maybe not looked for enough.

Observing playing_slot_index of a MIDI Clip notifies also if you edit clip content ?!

Max For Live Forum