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.

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

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.

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.

i have a live.dial mapped and controlled by a hardware encoder.

this live.dial is controlling any assigned parameter set with an id.

to do that i set it with the selected_parameter. (with the mouse)

everything is working fine, the value is set to the live.dial so there are no value jumps on the encoder when changing the id.

but, two things are not working properly:

first. when making fast value changes then the live.dial starts to jitter and dont stop anymore.

i tested with different encoders or even analog pots mapped to the live.dial. same.

second. when im recording in ableton then

both the live.dial and the mapped parameter are recorded to automation.

now, i dont want to have the live.dial recorded to automation.

the live.dial has to be <Visible to Mapping> to be mapped - obviously.

if its set to <Automated and Stored> it is recorded in automation. - dont want.

if i set it to <stored only> or <hidden> then its not mappable anymore.

hi, beginner here.

i have a live.dial mapped and controlled by a hardware encoder.

this live.dial is controlling any assigned parameter...

mapped-livedial-undesired-value-jittering-and-make-it-invisible-to-automation

mapped live.dial undesired value jittering - and make it invisible to automation

I've made a device in M4L whose parameters I control with a Faderfox EC4. Mostly it works great. 

I am trying to set up an init button that would send starting values to the parameters in the patch and to the EC4. I am doing this to avoid parameter jumps when the controller and parameters have gotten out of sync (on startup, or if I've been editing some things in the patch). 

As of now, I am using udpsend to send data to a Max patch which sets the value to the EC4. It works but it's not very elegant. 

I feel like there is another way to do this that I am overlooking. What am I missing?

Hi,

I've made a device in M4L whose parameters I control with a Faderfox EC4. Mostly it works great. 

I am trying to set up an init...

set-init-values-on-faderfox-ec4-and-in-patch

set init values on Faderfox EC4 and in patch 

skrasms

If I have custom Max externals that I've written in C, is it possible to use those in a Max For Live device? If so, is it possible to share that Max For Live device with someone else if the other person is on the same platform (e.g. x86) as I am?

If I have custom Max externals that I've written in C, is it possible to use those in a Max For Live device? If so, is it possible to share...

max-for-live-custom-externals

Max For Live Custom Externals?

chapelier fou

I'm working on a m4l device that controls parameters in the live set in a contextual way. I can store presets so one single dial would control a different parameter for each preset. 

It's working great but I have two questions, the first is about reliability, the second is about ids "validity" : 

I'm working on a m4l device that controls parameters in the live set in a contextual way. I can store presets so one single dial would...

about-persistence-of-ids-and-ids-validity

About persistence of ids and ids validity

Marc Assenmacher

I need to use a [live.observer] to observe a changing string. So far I could only find strings on hidden parameters, which can be observed but won't update.

Is there any way to observe a changing string with [live.observer]?

I need to use a [live.observer] to observe a changing string. So far I could only find strings on hidden parameters, which can be observed...

how-to-observe-a-changing-string-with-liveobserver

How to observe a changing string with [live.observer]?

syrinx

Hi all, I'm building a simple frequency analyzer M4L device using Volker Böhm's 64-bit version of fiddle~ (found here: https://cycling74.com/forums/fiddle-64-bit-version). I've noticed that when I load more than one instance of this device, each one on its own track, the frequency output of all of the fiddle~ objects in the Live set gets glitchy. It seems to alternate between 0, numbers in the tens-of-thousands, and accurate values. This behaviour stops as soon as the set goes back to having only one fiddle~ object in it.

The problem doesn't happen when multiple fiddle~s are loaded in a regular Max patch. It also doesn't occur if multiple fiddle~s are present in a single M4L device. It doesn't even happen if multiple devices are loaded on the same track.

Even weirder: let's say you have a single track, (1), with two M4L devices containing fiddle~, (1a) and (1b). Then you add a second track, (2), with another device containing fiddle~, (2a). At this point, (1a) and (2a) will be glitchy, but (1b) will be fine. If you then add a second fiddle~ device (2b) to track (2), (1b) will become glitchy. From this, it seems as if the M4L devices in corresponding slots across multiple tracks are affecting each other.

To see if the placement/ordering in the effects rack is what determines this, I created two tracks with fiddle~ devices, and then placed a Live Audio Effect (EQ Eight) before the fiddle~ device on one of the tracks. The glitchiness still happened. Adding a blank MaxForLive effect before the fiddle~ device also didn't prevent the glitches. In other words, it doesn't seem like the absolute position of the fiddle~ devices in the effects racks has to be the same across multiple tracks for this to happen. Rather, it seems like the first instance of fiddle~ device on one track will cause all the first instances of fiddle~ on other tracks to glitch out, the second instance will mess up all the second instances, etc., regardless of other effects/devices on the track.

Hopefully this convoluted account clarifies more than it obscures! It's very strange behaviour.

In case it helps, I'm attaching an M4L device containing fiddle~ and one containing sigmund~ (see below), as well as a Live 10 set where the behaviour is visible.

fiddle_test.zip

I have no idea if Volker is still around, or if anyone else with Max object development chops is able to take a look at this, but the source for the 64-bit version is here: 

https://github.com/v7b1/fiddle_64bit_version

Edit: I just tested with sigmund~, and it's having the same problem. I added a gate~ to my test device, and found that sigmund~ and fiddle~ both glitch out even if the devices in the other tracks aren't receiving a signal.

I have no idea if Volker is still around, or if anyone else with Max object development chops is able to take a look at this, but the source for the 64-bit version is here: https://github.com/v7b1/fiddle_64bit_version .

Hi all, I'm building a simple frequency analyzer M4L device using Volker Böhm's 64-bit version of fiddle~ (found here: https://cycling74.com

fiddle~-in-multiple-m4l-devices-causes-glitchy-output

If you're tracking a monophonic signal, would the native [retune~ @pitchdetection 1] do the job?

Hi Jean-Francois! Unfortunately [retune~] seems to have difficulty accurately reporting the frequency of a sine wave - in my experiments using [cycle~] as an input, it tracks accurately bet the frequency between about 95 Hz and 875 Hz, but outside that range it's inaccurate. [fzero~] has a slightly better range, but still only tracks a sine input accurately up to about 4.5 KHz. [fiddle~] seems to have much better accuracy with sine inputs, but unfortunately this weird M4L issue makes it unusable for me at the moment.

fiddle~ (or sigmund~) in multiple M4L devices causes glitchy output

elisabatti

hello everybody! I have a little problem. I am using fiddle~ to detect the pitch of microphones in ableton. I have created this patch. I have 4 microphones. So I place this .amxd patch in four separate tracks . If I have only one track everything is fine, but then, when I start adding the four tracks, each one with his own pitch detection, fiddle starts behaving erraticaly. ANY HELP???

Trigg.me antenna02.amxd

hello everybody! I have a little problem. I am using fiddle~ to detect the pitch of microphones in ableton. I have created this patch. I hav

fiddle-in-max4-live

fiddle in max4 live

Michael Gary Dean

So I've created a bunch of MaxForLive devices that modulate Live parameters in different ways. I use either live.remote~ or m4l.api.DeviceParameter to do the modulations. One thing that has been a real problem with both methods is the fact that all adjustments made to live parameters with these objects add adjustments to the undo history in Live.

Does anybody have a solution for this problem?

The two things I found that might be useful:

https://cycling74.com/forums/live-remote-and-track-mute

http://www.ableton.com/articles/buffer-shuffler-generates-lots-of-undo-steps

So I've created a bunch of MaxForLive devices that modulate Live parameters in different ways. I use either live.remote~ or m4l.api.DeviceParameter to do the modulations. One thing that has been a real problem with both methods is the fact that all adjustments made to live parameters with these objects add adjustments to the undo history in Live. 

The two things I found that might be useful:
1. https://cycling74.com/forums/live-remote-and-track-mute
2. http://www.ableton.com/articles/buffer-shuffler-generates-lots-of-undo-steps

Hi all,
So I've created a bunch of MaxForLive devices that modulate Live parameters in different ways. I use either live.remote~ or m4l.api.

Max For Live Forum