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.

Andrew Benson

Do you indulge in last minute patching on the day of a gig, or do you only use tried and proven patches? Are you a devoted tweaker or a pragmatic tester?

We've asked this same question on Twitter and got some great responses. Where you do you fit on this spectrum?

Do you indulge in last minute patching on the day of a gig, or do you only use tried and proven patches?  Are you a devoted tweaker or a pragmatic tester?
Any good stories?  

We've asked this same question on Twitter and got some great responses.  Where you do you fit on this spectrum?


survey-tweaker-or-tester

I'm more of a tester; as such I ironically rarely finish anything :)

i'm more of a devmatic tweaster, in that I build an app for performance which is guaranteed never to crash(on my machine for myself), and then if I need to at the last minute, I'll make only small changes/tweaks.

the 2 apps i made for the monome community C¥¶€R and MonoMahna(project 90-something'r'other here on the c74.com) have reportedly never crashed for anyone(I also performed with MonoMahna and tried it out for a year, never had a crash). The recent app I made for my monome512, ~SerpentEclipse), I took on a small tour to 3 events here on the west coast(just got back yesterday), still never crashed. So for the full-on apps I make, definitely more of a pragmatic tester, but one area I've been running into trouble and do more tweaking in is M4L(it crashes on me all the time, and I don't seem to care enough about Live or M4L to trace bugs; I just end up using it for experiments and to generate sounds).

The pragmatism of a tried-and-true environment has impact on whether I will engage in my own pragmatism or not.

i'm with Raja, but then again, I learned much directly from him.

and then again, since I don't perform as much I guess that makes it easier for me to be a pragmatic tester.

________________________________
*Never fear, Noob4Life was never here!*


How do you know when your patch is finished? Is it ever finished?

How do you know when your patch is finished?  Is it ever finished?


You're probably asking Tim the question, but as for my particular experience:

i've always thought they would never be finished, but in the case of C¥¶€R and MonoMahna, they really did reach a finishing point: when i moved on to the next app, that's when the old one was finished.

Of course, i have an outline of basic features in mind, once those basic features are in, the app is at a stage of maturity where i can leave it for awhile. What ends up happening then is, upon moving onto the next, i sometimes go back to the old ones simply to use them, not to develop them any further, at which point, i often realize they are even more finished than i originally anticipated because(in the case of MonoMahna in particular), I end up being addicted to the way in which the app works as is. This has only been a recent phenomenon in my life, whereas previously nothing was ever finished in my view and I kept moving on to do better and better because I was constantly unsatisfied.

In short, my apps(nowadays) are finished when they meet 3 basic conditions:

1. the app has the basic feature-set fully implemented which i originally outlined for myself when first beginning its development,

2. my actual use of the app in a state of maturity has led me to believe that i can either do better or do something newer by moving on to making a completely different and newer app,

3. i return to use the app after moving on to develop another and find that it is satisfyingly useable as i left it.

This actually means that no current app I'm using to make art, having just finished development without moving on to make something newer, is something I consider 'finished'. Instead it's more important that it is at a 'state of maturity' or 'useable'(for that art). It isn't until a newer app is started, that I finally glean a 'finished' state for the older one relative to the state of the newer one(s).

Keep in mind, I no longer make that many 'patches' I make what I like to consider 'apps'(the difference being: apps contain full and extensive feature-sets/uses, they 'apply' to a larger set of performance considerations rather than a specific use which a patch might specialize in(at least according to my own experience only; as limited as my experience might be relative to other greater veterans...)). And also, the 3 conditions I listed above are really only according to my own experience of the apps(I make apps for myself first and foremost and then hand them out to anyone else interested, rather than making them for people at large and then finding my own specific way of using it... unless, of course, i'm working for someone else in which case, the few times that has happened, it's all up to their direction (and how happy I am with any compensation given in exchange)).

Hope that helps. All the best in this very interesting survey!

You're probably asking Tim the question, but as for my particular experience:
i've always thought they would never be finished, but in the case of C¥¶€R and MonoMahna, they really did reach a finishing point: when i moved on to the next app, that's when the old one was finished.

In short, my apps(nowadays) are finished when they meet 3 basic conditions:
1. the app has the basic feature-set fully implemented which i originally outlined for myself when first beginning its development,
2. my actual use of the app in a state of maturity has led me to believe that i can either do better or do something newer by moving on to making a completely different and newer app,
3. i return to use the app after moving on to develop another and find that it is satisfyingly useable as i left it.

Hope that helps. All the best in this very interesting survey!


Actually, I don't like calling things finished :) I like to think that everything I do is imperfect and has lots of room for improvement.........some patches start off going in one direction, sort of plateau at some point, then start off in another direction; and I don't usually think of them as different patches, just little idea-journeys that produce interesting things and then evolve into something else.

I don't do any performing with max (yet...) so I don't have any particular incentive to build an entity that does particular things; whether or not those particulars are specific or vague.

I tend to call something "finished" when I get bored of the idea :P Up until that point, whatever it is is probably in a state of flux, but being pedantically tested and messed with to make sure it works properly before my requirements change.

I just like the exploration, maybe I've got creative ADD.

Actually, I don't like calling things finished :)  I like to think that everything I do is imperfect and has lots of room for improvement.........some patches start off going in one direction, sort of plateau at some point, then start off in another direction; and I don't usually think of them as different patches, just little idea-journeys that produce interesting things and then evolve into something else.

I tend to call something "finished" when I get bored of the idea :P  Up until that point, whatever it is is probably in a state of flux, but being pedantically tested and messed with to make sure it works properly before my requirements change.

I just like the exploration, maybe I've got creative ADD.


2000+ abstractions should give you an idea.

and: never change a running system, for example mac os 9.

I guess I live a bit more on the edge. Any patch that has seen more than one performance or installation becomes a living record of last-minute tweaks or solutions to problems that would happen onsite. Eventually, I figure out the parts that always need to be changed and I spend time to make a proper UI for it, but I'm generally better at adaptation than planning.

I guess I live a bit more on the edge.  Any patch that has seen more than one performance or installation becomes a living record of last-minute tweaks or solutions to problems that would happen onsite.  Eventually, I figure out the parts that always need to be changed and I spend time to make a proper UI for it, but I'm generally better at adaptation than planning.


FWIW I always start out being (or trying to be) more of a tester but the last minute tweaker in me always pops up @ ...the last minute!!

ya, i think what spectro said is true for all. Max is not a finished product, therefore, it's a pretty necessary thing to be a tweaker at some point. I think we're all forced to 'live a bit more on the edge' by it. Living on that edge is probably an easier thing for people who are more experienced at it, therefore not really an 'edge' persay but rather a calculated risk(i know what could possibly lead to crashes or simply cause slower performance and i stay away from tweaking that kind of thing last minute (example, huge pattrstorage organizational changes, etc.))

Survey: Tweaker or Tester?