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.

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.

Luca Schwarz

hi there! i built a simple sampler, and want to use it across my project with different instances of a bpatcher. i called the buffer #0-XY, so that it will create a new unqie name everytime i duplicate the bpatcher, and i am able to load differnet samples in each instance. It all works fine but when i save the patch and re-open it, all buffers will have that same sample loaded which i used in the patch which is the parent patch of that bpatcher. Any ideas how to solve this?

This is how the parent sampler patch looks like:

buffer-in-bpatcher-doesnt-rem

buffer in bpatcher doesnt rem

giftculture

There seems to be a bug in the max documentation for the REPL (both online and offline docs) 

https://docs.cycling74.com/userguide/repl/

 , unless there is something wrong with my max environment (version 9.0.2)

"To create a new button object with a scripting name, enter 

<p> script newdefault button @varname ddd

. Now you can send the newly created button messages such as 

but when I do that, it creates a jbogus object in my patcher.  Instead of "newdefault", if I specify "newobject", it creates the object successfully

There seems to be a bug in the max documentation for the REPL (both online and offline docs) https://docs.cycling74.com/userguide/repl/ ,...

bug-in-repl-documentation-to-create-a-button-newdefault-vs-newobject

Bug in REPL documentation to create a button (newdefault vs newobject)?

Nick

I'm on Max 8.0.2. Given that, under Help > Examles > mc there's an example patcher named "mc_mpe_synth." This thing is awesome. Inside, you'll notice that from the [mc.noteallocator~] object, the 5th outlet for Pitch Bend is not used. I set out to implement that within the example just to get my head around MC/MPE, and I'm way confused.

My question is simply: how do I take the value that comes out of that 5th outlet and map it onto a sensible [-1.0, 1.0] range where a value of -1.0 means "minus one semitone" and +1.0 means "plus one semitone"?

There's a helpful post here on the forums that explains this a bit, and a link shared therein for more information:

https://cycling74.com/forums/pitch-bend-ranges

https://sites.uci.edu/camp2014/2014/04/30/managing-midi-pitchbend-messages/

If I understand correctly, the value from that 5th outlet is this 14-bit MIDI pitch bend message where the first 7 bits are "fine" and the second 7 bits are "coarse." So far this seems good: if I isolate the coarse bits with [& 127] then [<< 7] I get 8192 when I'm applying no pitch bend. If I take this through [scale 0 16383 -1.0 1.0] as per the second link there, I get a value that makes sense (0.0 = + 0 semitones).

Where I'm confused though is that this seems super coarse. I'm playing with a Seaboard BLOCK and I really have to crank the pitch bend to get even up to 8320 for the coarse bits, and I have a hard time getting past that. So, I figure I have some work to do with the fine bits: for these I tried taking the same 5th outlet of [mc.noteallocator~] through [& 0x7F00] to isolate the 7 bits of "fine" information then [>> 7] to align the bits. Finally I OR the coarse and the fine values together and now I have decent behavior centered around 8192 but still it seems way too coarse. I have to slide two notes away on my Seaboard even to get past 8320.

Obviously this doesn't map to any notion of +/-1.0 representing +/- one semitone. What am I doing wrong here? Have I misunderstood the range here or is my math wrong?

There's a helpful post here on the forums that explains this a bit, and a link shared therein for more information:
https://cycling74.com/forums/pitch-bend-ranges
https://sites.uci.edu/camp2014/2014/04/30/managing-midi-pitchbend-messages/ 

Hey all.
I'm on Max 8.0.2. Given that, under Help > Examles > mc there's an example patcher named "mc_mpe_synth." This thing is awesome. Ins

mpe-mpeparse-mc-noteallocator~-and-pitch-bendglide

Nevermind! The issue was that my Seaboard BLOCK was configured to a pitch bend range of +/- 48 semitones, so it was using very little of the [0, 16383] range relative to what I was expecting. Dumb error... but the good news is that the approach above seems to be ok.

Hey Nick, I have another problem, that relates to your though by topic. 
While using exactly the example synth patch, how / where did you actually add the pitch bend value to the note on original pitch?
I am trying different possibilities,  but  somehow adding it whether with the existing mc.target object for pitch or with a new one additionally causes problems. Pitch of other notes or new notes get messed up. 
It is some timing issue I guess, like old value stored for new notes or so. Probably because of the Max  message order etc. I am trying to debug this but no success so far. 
So I though I ask you, before I screw my head even more :D 
   


MPE / [mpeparse] / [mc.noteallocator~] and Pitch Bend/Glide

Peter Seibel

Is there a specification for how patches are represented in JSON? I.e. if I wanted to build tools that understood or generated patches in JSON format, is there something that specifies the structure of the JSON?

Is there a specification for how patches are represented in JSON? I.e. if I wanted to build tools that understood or generated patches in JS

specification-for-maxpat-json-format

Specification for .maxpat JSON format?

Eugenio Scalfi

Hello, today I created a dark mode version of the "default" Max 8 theme, by installing it you can have global dark mode across the whole program (not a single patcher like with styles!) and finally ease your eyes while coding, you can alternate between the "default" theme and this dark mode in the max preferences (interfaces > Color Theme).

https://github.com/MagistraNocte/Max-8-Default-Dark-Mode

To install, follow the instructions at the link and in the readme file.

Feel free to contribute, suggest changes and report problem in the github page.

115965388-59934d00-a529-11eb-9719-7f99118a9d8f.jpg

Hello, today I created a dark mode version of the "default" Max 8 theme, by installing it you can have global dark mode across the whole program (not a single patcher like with styles!) and finally ease your eyes while coding, you can alternate between the "default" theme and this dark mode in the max preferences (interfaces > Color Theme).

You can find it here: https://github.com/MagistraNocte/Max-8-Default-Dark-Mode
To install, follow the instructions at the link and in the readme file.
Feel free to contribute, suggest changes and report problem in the github page.

Have a nice, eye-rested coding!

Hello, today I created a dark mode version of the "default" Max 8 theme, by installing it you can have global dark mode across the whole pro

max-8-default-dark-mode


not sure if that makes things better. max already lacks outlines, parting lines, contrast, everywhere, which makes it really hard to read sometimes.

Omar, I don't think it would be difficult given a solarized (light) theme is already present in the default themes, I'll investigate it


Ok seems like C74 didn't use the official color values for their "solarized" (light) theme but slightly modified them, so I can't easily batch replace them with the dark ones, they should be modified and tried out one by one, that's a little too much work for my spare time, but if anyone's interested you can experiment by opening one of the default ".maxtheme" file (in the location I provided in the installation instructions of my theme) in any text editor and modifing the colors (they're in float rgba format) then saving the file and changing the theme in the max preferences (you don't have to reboot max, just change theme)


both max 8 and windows 10 do not follow the simplest guidelines for graphic user interfaces.

i am used to move 5 windows around in under 1 seconds. impossible with this kind of stuff, as you never know where to click.

hard enough to accept that i no longer can create custom inspector patches, but here you have grey, borderless subwindows in subwindows, opening over grey in grey lines on grey background in a grey operating system.

and now you suggest to make the canvas grey, too? then you cant even see if the inspector is open or closed if you do that. ;)


I'm not sure i follow, most modern program is designed in greyscale because that's minimal and functional (ableton live fore example, speaking of something related to max) I don't see problems in that, also almost everything nowadays has a dark mode because the negative effects on the eyes and circadian rythms of bright, mostly white screens at night are well known by now, that should be an important concern for any programmer spending hours very focused on screens.
The default canvas is already grey, just a light shade, I made it darker and made the rest lightier and tried to keep the contrast relation between the shades in doing so, I didn't just make the canvas black, maybe the rest should be lighter and have more contrast? the inspector and the console have stripes, you can't  mistake them for the canvas, but they could be brighten up if that's what you're suggesting. You seem to have an idea of what doesn't work good in the max palette, what would you suggest changing, while keeping the canvas dark grey?

 
no, it is not functional to keep everything in the same color. :)

except it has a similar meaning, then it would be good if is also looks the same.

for example it would be nice of all windows top bars, where you can move them, would look the same. in the above picture the top bar of the max window is white by default, in explorer it is black by default, and in the popup window in the inspector there is no toolbar at all.

you have to GUESS in all three cases where to click to drag.

even worse, in the patcher window and also in windows 10, that top bar can only be dragged in the upper half. this design doesnt make any sense, it doesnt follow the function.

do you see the word "Organisieren" on the bottom?

and then tell me if the "annotation" window is open or not?

look into the "annotation" window as if you are going to write in it.

is the exporer window covering the bottom bar of the max window or not?

That is an issue with windows though, in MacOS they all looks the same (bright or dark depending on the mode) because that's an OS level design choice, nothing to do with max itself (or themes), the popup window where you enter annotations and hints doesn't have it because it's a max internal popup window and has nothing to do with the OS, but that's a very specific case and you're not supposed to be changing window focus and position while editing a hint anyway

 
you might think i am joking (i am) but let´s compare that to the same 4 windows my old max computer.

all windows look the same - because they work the same. 

they get greyed out when in background, because this was the standard design for the last 30 years.

text entry fields are white, because that was the standard design for te last 30 years.

all inspectors were blue, so that you could see at one blink what it is, where it is, if it is still open, you get the idea.

my OS windows wear custom pictures, so that you always know on which disk or folder you are.

my max patch canvas is grey, and when you unlock it, it is white so that you can always tell if it is locked or not.

sure, it is a joke to compare that to each other. 

but it should serve us as an example for good design here, because of "form follows function", contrasts, read speed and some more things.

in case you dont like the colors, you can of course also change them to your liking, and probably much faster than today.

but dont do them grey on grey with grey lines on grey background, or at least put some green lines between the different elements.

MaxMSP Forum