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.

yaniki

MaxMSP/Jitter and P5*js - a simple solution for interfacing "patches" created in MaxMSP/Jitter and "sketches" written in P5*js (

This is a side effect of my current work on some projects with WRO Art Center, dæd bɑɪtz, and others. It's an simple interface allowing communication between the MaxMSP and P5*js sketches loaded into Max [jweb] object, but can be very useful... for small number of people.

This "solution" is very basic, but may be easily adapted to individual needs, so I decided to share it with you.

Btw: Using the P5*js together with Max is opening some new horizons (I explore this issue for some time). I will try to elaborate on this in the near future.

http://paweljanicki.jp/projects_maxandp5js_en.html

MaxMSP/Jitter and P5*js - a simple solution for interfacing "patches" created in MaxMSP/Jitter and "sketches" written in P5*js (http://p5js.org).

more info, download: http://paweljanicki.jp/projects_maxandp5js_en.html


sharing-is-maxmspjitter-and-p5js

Thank you for sharing this! Huge p5.js fan!


I have updated (and simplified) the instructions a bit.

Generally, to communicate P5js sketches loaded into Max [jweb] object with the parent patcher we have to avoid namespaces conflict between Max and P5js APIs. Fortunately, there is a very simple solution for this: just run your P5js sketch in so called "instance mode" (not default "global mode").

Example project and details: https://www.paweljanicki.jp/projects_maxandp5js_en.html

I have slightly updated  example project by adding a mechanism to enable/disable background (opaque/transparent switching). So now it is possible to use P5js sketch loaded into MaxMSP [jweb] object as a transparent "layer". This should make a little bit easier to create your own GUI elements in P5js - you no longer need to adjust the background color of the p5js sketch to the background color of the patch in MaxMSP.

Project's URL is still the same: https://www.paweljanicki.jp/projects_maxandp5js_en.html

I have updated MaxAndP5js a bit. I added a second example, showing how to launch (from a jweb object in MaxMSP) a p5js sketch using Vida library for simple motion detection.

I made some updates to the project: on the p5js side I refreshed the syntax of the example sketches (no more var!) and compatibility with new versions of Max is improved (8.2!).

Oh, and there is a new example: Euclidean/Bjorklund's rhythm generator (easy to adapt to any algorithm for generating rhythmical patterns). Bjorklund's algorithm is implemented on p5js side (JavaScript) and you may find Max-native, more robust, versions on the forum (e.g. https://cycling74.com/forums/using-euclideanbjorklund-algorithm-for-rhythm-generation-purely-in-max), but you can, with very little effort, integrate your preferable - Max-native or not, Euclidean or not - rhythm generator with the a handy GUI solution for visualising rhythmical patterns used in this example.

The location is unchanged: https://www.paweljanicki.jp/projects_maxandp5js_en.html 

I updated my pet-project MaxAndP5js - a simple solution for interfacing "patches" created in MaxMSP/Jitter and "sketches" written in p5js (https://p5js.org).

This time I added another example and corrected the descriptions of the existing ones. So, we now have the following examples:

01_messaging_and_dictionaries - basic mechanisms, messaging, sharing dictionaries between Max and p5js;
 
02_camera_and_motion_detection - simple "camera and motion detection based instrument". Motion detection is made "inside" jweb (and p5js sketch loaded into it) using Vida library (https://www.tetoki.eu/vida) for p5js;

03_euclidean_rhythm_generator - Euclidean/Bjorklund's rhythm generator (easy to adapt to any algorithm for generating rhythmical patterns). Bjorklund's algorithm is implemented on p5js side (JavaScript) and you may find Max-native, more robust, versions on the forum (e.g. https://cycling74.com/forums/using-euclideanbjorklund-algorithm-for-rhythm-generation-purely-in-max), but you can, with very little effort, integrate your preferable - Max-native or not, Euclidean or not - rhythm generator with the a handy GUI solution for visualising rhythmical patterns used in this example;

04_generative_text_with_rita - a text generator based on RiTa library (https://rednoise.org/rita) for p5js. Generating sentences based on Markov strings, access to the RiTa lexicon (random words, rhymes). It's only a small fraction of RiTa features exposed in this example, but it is relatively easy to bind more RiTa mechanisms to your patch.

The location is unchanged:  https://www.paweljanicki.jp/projects_maxandp5js_en.html 

[sharing is...] MaxMSP/Jitter and P5*js

ygreq

I believe lots of years have past since you changed the forum. And since then the search engine is broken. I have to go to google to search inside this forum. I really hate ranting, But it's been years now.. :(

Hi guys and girls of C74!

I believe lots of years have past since you changed the forum. And since then the search engine is broken. I have to go to google to search inside this forum. I really hate ranting, But it's been years now.. :(

What gives? Please let us know!

Hi guys and girls of C74!

I believe lots of years have past since you changed the forum. And since then the search engine is broken. I have

fix-forum-when

hey, what do you mean exactly by 'its broken' ? it seems mostly fine to me :O

Try searching in the forum something composed of 2 or more words. You will mostly find results related to one of the words without the other. So totally irrelevant. 

My recent search was crop jit.gl.pix. On top of the list I had one result that did not have jit.gl.pix in any of the comments. Of course I looked for crop jit.gl.pix cycling74 on google and found lots of posts inside of the forum. 

But a functioning forum would let you properly search inside it, not having to go to goole.com to search for something. :/ At least they should just integrate the google search engine inside of the forum. 

ok. I see that now and confirm there's a problem :))

..it seems too that the "~" is not seen by the search.
I was looking for informations today in the forum about the [max~] object.
impossible to have a good result. I tried searching for : "max~",  [max~]  ,  "[max~]"  ...Same results


Fix Forum. When?

Luigi Castelli

after spending some months thinking whether I should actually ask this question or not, in light of some new threads that have recently popped up in this Forum and at the risk of sounding controversial or argumentative, I decided to finally ask the damn question anyway.

https://cycling74.com/forums/max-sdk-vs-max-api

the final conclusion is that if we are setting up any new projects, we are probably better off using the traditional Max-SDK, unless we have concrete needs of min or maxapi.

What is there to need in min-devkit or Max-API though?

The Max-API is a copy of the traditional max-SDK API headers, put inside a C++ namespace.

Sure... that could have the advantage of making name conflicts less likely to occur, but honestly in the world of Max/MSP object development I never had that issue. However that also creates an undesired side-effect: it duplicates all the traditional Max-SDK headers. Now in case of updates to the Max-SDK there are two sets of identical headers to maintain. Not ideal if you ask me.

The min-devkit features a number of basic DSP modules. (delay, limiter, filters, etc...)

Most of them are already available in the standard distribution as compiled Max external objects. Remember that it is possible to instantiate Max/MSP external objects in code as well, in case you need their functionality inside your C/C++ project. Also, there already exist a number of C/C++ DSP libraries that have been around for some time and thus are more robust and well-tested than Min. Many of them even feature a richer set of DSP classes. So why reinventing the wheel?

I have read threads on this Forum that explicitly refer to the Max-SDK as "deprecated" in favor of the min-devkit. As far as I can tell that is simply false. I don't see that happening any time soon.

The vast majority of Max externals are written in C using the traditional Max-SDK.

Even in the above mentioned thread Rob Ramirez said: "for the most part the max-sdk remains the source of truth and the maxapi is there to support min-devkit projects."

I see very committed users (such as Omar Hamido for example) trying to make sense of certain programming topics (i.e. threading), where the answer would be much more easily found if the context were switched to the traditional Max-SDK.

I am not trying to discourage the use of C++ or C++ APIs in any way. C++ is my language of choice and I personally think Max/MSP/Jitter should be written in C++. But that's a conversation for another time... :)

I am really struggling to see what the purpose of the min-devkit is, given the way the Max/MSP/Jitter infrastructure is setup.

Where does it position itself in the spectrum of developer tools related to Max/MSP/Jitter?

What specific problems is it aiming to resolve?

When would it be better/more convenient to use over the traditional Max-SDK API written in C?

1) our beloved friend Tim Place spent a considerable amount of time writing and maintaining it

2) there is a GitHub repository where users are regularly contributing to the code.

Therefore I am sure there must be value to it and it must have a well defined purpose.

What is the purpose of the min-devkit?
What problems is it aiming to resolve?

According to this thread,
https://cycling74.com/forums/max-sdk-vs-max-api
the final conclusion is that if we are setting up any new projects, we are probably better off using the traditional Max-SDK, unless we have concrete needs of min or maxapi.

What is there to need in min-devkit or Max-API though?
The Max-API is a copy of the traditional max-SDK API headers, put inside a C++ namespace.
Sure... that could have the advantage of making name conflicts less likely to occur, but honestly in the world of Max/MSP object development I never had that issue. However that also creates an undesired side-effect: it duplicates all the traditional Max-SDK headers. Now in case of updates to the Max-SDK there are two sets of identical headers to maintain. Not ideal if you ask me.

The min-devkit features a number of basic DSP modules. (delay, limiter, filters, etc...)
Most of them are already available in the standard distribution as compiled Max external objects. Remember that it is possible to instantiate Max/MSP external objects in code as well, in case you need their functionality inside your C/C++ project. Also, there already exist a number of C/C++ DSP libraries that have been around for some time and thus are more robust and well-tested than Min. Many of them even feature a richer set of DSP classes. So why reinventing the wheel?

I have read threads on this Forum that explicitly refer to the Max-SDK as "deprecated" in favor of the min-devkit. As far as I can tell that is simply false. I don't see that happening any time soon.
The vast majority of Max externals are written in C using the traditional Max-SDK.
Even in the above mentioned thread Rob Ramirez said: "for the most part the max-sdk remains the source of truth and the maxapi is there to support min-devkit projects."

I am really struggling to see what the purpose of the min-devkit is, given the way the Max/MSP/Jitter infrastructure is setup.
Where does it position itself in the spectrum of developer tools related to Max/MSP/Jitter?
What specific problems is it aiming to resolve?
When would it be better/more convenient to use over the traditional Max-SDK API written in C? 

I am asking all these questions because:
1) our beloved friend Tim Place spent a considerable amount of time writing and maintaining it
2) there is a GitHub repository where users are regularly contributing to the code.

Therefore I am sure there must be value to it and it must have a well defined purpose.
I just can't see it.

Hello developers,
after spending some months thinking whether I should actually ask this question or not, in light of some new threads that 

what-is-the-purpose-of-the-min-devkit

Hey Luigi, thanks for the thoughtful question regarding min. Unfortunately the best person to give a thoughtful answer to this is Tim Place, who is unlikely to respond anytime soon since he is no longer with the company.

My best concise answer is, don't overthink it (winky emoji). If you have taken a look at min and what it offers (of which there is plenty of documentation) and it doesn't start your engine, then there isn't much to say. You are an experienced developer, fully comfortable with utilizing the max-sdk to achieve what you want from it and don't have a need for all the bells and whistles offered by min.

To expound a bit, min-devkit and max-sdk are not comparable, as min is a completely new environment for developing max externals. This should be evident simply by looking at the code for any external distributed with min (for an experienced max external dev, it's almost unrecognizable). Some of the benefits of min should also be evident from looking at that code, e.g. minimum boilerplate, and  max external specific templates providing common functionality.

In addition to fully embracing modern c++, min also provides a testing framework, cmake scripts, automatic documentation generation, package creation scripts, object creation scripts, and a max-patch cmake interface (recently broken, but soon to be updated).

According to this thread, https://cycling74.com/forums/max-sdk-vs-max-api the final conclusion is that if we are setting up any new projects, we are probably better off using the traditional Max-SDK, unless we have concrete needs of min or maxapi.

For that particular user, given what they posted that was my best attempt at advice taken with a grain of salt.  but please note I ended that post saying "I strongly recommend taking a look at the various components of min before making that decision."

I have read threads on this Forum that explicitly refer to the Max-SDK as "deprecated" in favor of the min-devkit. As far as I can tell that is simply false. I don't see that happening any time soon. 

Yes absolutely, the max-sdk is not deprecated. If you are comfortable with the max-sdk, stick with it. If you want to try out some new hotness, give min a spin. We will be updating the Package Manager version to address some breakage with the cmake patch interface sometime in the next few days.


Dev Forum