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

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.

This website uses cookies.

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

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.

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. Once an asset has been deposited to your iLok account, Cycling '74 cannot remove it. Therefore, you cannot go back to the Cycling '74 account sign-in method to authorize the given license. 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.

Chaz Dean

I'm surprised that I haven't been able to find a Serum-like  'FM-from-B'   m4l device out there, in which the frequency of an audio signal can be mapped to parameters in Live similarly to the Envelope Follower device.  I've fooled around with retune~ and it is providing me with reasonable frequency data, ...

BUT: I can't figure out how to convert that data into useable input for the  Abl. MultiMap  patcher.    The output of the mapping seems binary even after I used the scale object (input 0-20,000; output 0-1.) and regardless of the min / max settings in the device's UI.  

Hewwo,

I'm surprised that I haven't been able to find a Serum-like  'FM-from-B'   m4l device out there, in which the frequency of an audio...

mapping-fm-from-b

Mapping  "FM-from-B"

zuchtfisch

Hi, i'm currently porting my sensor interfacing patches into M4L and use live.remote~ a lot for parameter control. With the api resource patches and some modifications i was able to port most of my settings. But i'd like do make the mapping of remote controlls more accurate by retrieving the selected parameters range and unit and then have the modulation range max and min number boxes automatically adjust their displayed range accordingly. So if i chose an EQ-eight's A-1Frequency parameter, they would have a Range of 30 (Hz) to 20000 (Hz) but when i chose the Frequency of an LFO in a Chorus, they'd be something like 0.1 to 10 (Hz) or 0 to 100 (%) for a dry wet. But for most parameters the range you can get from live.object is the raw 0.-1. range. Is there a standard range (0. always translating to 30 Hz for frequencies for example)? Or not at all?

get-a-parameters-displayed-range-and-unit

Get a parameters displayed range and Unit?

Marc Assenmacher

I made this little M4L device that lets you change your selected parameters value in Ableton with an encoder. You can also map the parameter to the encoder by a click on a button (or ideally the encoder, if it has a button integrated).

I made this little M4L device that lets you change your selected parameters value in Ableton with an encoder. You can also map the...

sharing-m4l-device-encoder-for-selected-parameter

[Sharing] M4L Device - Encoder for Selected Parameter

AudioMatt

matlearnreport.zip

This took so much hacking. Apologies for multiposting here but this deserves a new topic.

I'm a priss about my interfaces. I like custom ones. Until Ableton/Cycling decide to expose a javascript or C method for map mode, my solution has been to unhide live.numboxes when the user goes into map mode.

Mat.learnreport is an abstraction that sends 1s and 0s based on when the user hits Midi or Key in Ableton for this purpose.

If someone finds this is useful I can submit it to the package manager. Not sure if cycling will take it since it's based on something unofficial.

This took so much hacking.  Apologies for multiposting here but this deserves a new topic.

I'm a priss about my interfaces.  I like custom ones. Until Ableton/Cycling decide to expose a javascript or C method for map mode, my solution has been to unhide live.numboxes when the user goes into map mode.

If someone finds this is useful I can submit it to the package manager.   Not sure if cycling will take it since it's based on something unofficial.


 
This took so much hacking.  Apologies for multiposting here but this deserves a new topic.
I'm a priss about my interfaces.  I like custo

mat-learnreport-hack-solution-to-mapping-jsui

no idea how did this. (Really, how?)
This should be a live. object in Max.

(since you're back?) Can you give me some pointers as to how this is done?
I've spent some time trying to figure it out and I'm pretty much lost here.
I don't even think the MIDI remote script thing would allow one to do this.
My best guess right now, is that I've been looking in the wrong direction: 
maybe you are not even worrying about a live API, and just figured out a way to read the state change of a live.object when the environment goes to a MIDI map mode. Again, I have no idea how this is done (would love to!) but it seems like something that should be available in vanilla max by default.

Mat.LearnReport (hack solution to mapping JSUI)

Alexander Whitney

Hello, I am VERY surprised I cant find this anywhere so I'm starting to think its impossible. I want to use the CC out information from XFER LFO tool or CABLEGUY MIDISHAPER to control Ableton macros. I am aware of and know how to use SHAPER MIDI and LFO and SHAPER on Ableton but they are lacking in some features.

Is it possible? Is it difficult? Would someone charge me for it?

midi-cc-to-ableton-macro

MIDI CC TO ABLETON MACRO

derf07

it-is a bug? I don't understand whow work this object?The points are attracted to the horizontal lines.

Hello. I use Max for Live 8.

it-is a bug? I don't understand whow work this object?The points are attracted to the horizontal lines.



function-object-grid-attribut

function object / grid attribut

Martin

I'd like to make a device that's able to merge midi from two channels together into one.

For example, I have one drum pad at home with which I like to drum in everything. Logically, every line I play on this instrument ends up on one note. In my ideal setup, I'd have a second midi channel with long legato melodic notes which would be sidechained to the single drum channel. The pitch information of this channel would be merged with all the other midi information from the drum channel.

This way, I would be able to drum in melodic lines with a single pad. This would also be handy for live use.

I know it's possible to sidechain midi into a M4L audio effect, is it also possible in a midi effect?

Hi,

I'd like to make a device that's able to merge midi from two channels together into one.

For example, I have one drum pad at home...

merge-information-from-two-midi-channels-together

Merge information from two midi channels together

Evan

Not sure if this should go to Ableton or not (already have a bug report out on a similar topic), but thought it might be helpful to open a discussion here regardless.

Background - I have been using the control surface API since it arrived with m4l way back when. took a while off from musicking, and am returning to some of my previous work after getting a Push3 standalone a few weeks ago. Im going to scope this post to just the touch strip component, but some of this can be applied to (presumably) a lot of the controls that are children of the Push3 control surface object.

I have a m4l device that takes control of the touchstrip on the Push, sets its mode to bi-directional latching (mode 2), and then uses inout to control the position of the crossfader in Live. using the exact same patch that was developed for Push1/2 I am getting wildly different behavior.

1) The (call set_mode X) message to the touchstrip [live.object] is not recognized as a function. The error coming back is "live.object: 'ControlProxy' object has no attribute 'set_mode'" - this seems to indicate that this control on the Push3 lives behind some proxy that is control agnostic. Which leads me to my next point...

2) Why are all controls on the Push3 of the same 'ControlProxy' type instead of their actual type, i.e. TouchStripElement in the case of the touchstrip element - I noticed this when attempting to take over control of the button matrix for another device. All controls seem to sit behind this ControlProxy object. And when calling getinfo on them, they all return the same base functions, with no control specific information. For instance, you'd expect see different info about the touch strip as opposed to an encoder, matrix button, etc. I leveraged this extensively for prototyping and developing LiveAPI calls in JS.

3) The observed output is not useful at all - The output is a series of -128, -64, 0, 64, and 128 values. On Push 2, you get the full pitch bend range of 0 - 16384 (the upper end is clipped a bit, but close enough).

I understand that the Push3 isn't a traditional control surface written in Python, and I'm certainly don't understand the nuances of the technical implementation. That being said, some of these changes to the control surface API, and they way it communicates with Push3 are 100% breaking changes for me, and some of the devices i depend on. I was hoping to port some of my work to standalone mode, to untether from a computer while performing and writing, but now I am questioning not only if it's possible now, but if it will EVER be possible with the way M4L communicates with the Push3.

Will there ever be any documentation released around things that have changed in this regard? Or is something already out there and I just haven't stumbled upon it yet?

I've attached text output of some getinfo calls to the touchstrip control, and the patch used to generate said outputs. 

EDIT: Tested on both the current release version of Live (Max 8.5.5), as well as the latest version of the Live Beta (Max 8.5.6).

push2_touchstrip_info.txt

push3_touchstrip_output.txt

Not sure if this should go to Ableton or not (already have a bug report out on a similar topic), but thought it might be helpful to open a discussion here regardless. 

Background - I have been using the control surface API since it arrived with m4l way back when. took a while off from musicking, and am returning to some of my previous work after getting a Push3 standalone a few weeks ago. Im going to scope this post to just the touch strip component, but some of this can be applied to (presumably) a lot of the controls that are children of the Push3 control surface object. 

I have a m4l device that takes control of the touchstrip on the Push, sets its mode to bi-directional latching (mode 2), and then uses inout to control the position of the crossfader in Live. using the exact same patch that was developed for Push1/2 I am getting wildly different behavior. 

2) Why are all controls on the Push3 of the same 'ControlProxy' type instead of their actual type, i.e. TouchStripElement in the case of the touchstrip element - I noticed this when attempting to take over control of the button matrix for another device. All controls seem to sit behind this ControlProxy object. And when calling getinfo on them, they all return the same base functions, with no control specific information. For instance, you'd expect see different info about the touch strip as opposed to an encoder, matrix button, etc. I leveraged this extensively for prototyping and developing LiveAPI calls in JS. 

3) The observed output is not useful at all - The output is a series of -128, -64, 0, 64, and 128 values. On Push 2, you get the full pitch bend range of 0 - 16384 (the upper end is clipped a bit, but close enough). 

I understand that the Push3 isn't a traditional control surface written in Python, and I'm certainly don't understand the nuances of the technical implementation. That being said, some of these changes to the control surface API, and they way it communicates with Push3 are 100% breaking changes for me, and some of the devices i depend on. I was hoping to port some of my work to standalone mode, to untether from a computer while performing and writing, but now I am questioning not only if it's possible now, but if it will EVER be possible with the way M4L communicates with the Push3. 

I've attached text output of some getinfo calls to the touchstrip control, and the patch used to generate said outputs. 

EDIT: Tested on both the current release version of Live (Max 8.5.5), as well as the latest version of the Live Beta (Max 8.5.6). 

Not sure if this should go to Ableton or not (already have a bug report out on a similar topic), but thought it might be helpful to open a ... 

push12-vs-push3-control-surfaces-api-differences-and-documentation

Push1+2 vs Push3 control surfaces API - differences and documentation? 

Dan Gayle

Is there a way to mark a device itself as a template, similar to how the Max Instrument/Max Audio Effect/Max Midi Effect devices work? I want to make new devices that don't use the dark gray color scheme in the patcher window and I want to be able to set up some better defaults for things like midi/mpe support.

Screen Shot 2023-02-16 at 2.38.37 PM.png

Is there a way to mark a device itself as a template, similar to how the Max Instrument/Max Audio Effect/Max Midi Effect devices work? I ... 

Max For Live Forum