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).

Your Activation Code was successfully redeemed.

You must be signed into your account to redeem an Activation Code.

Redeem an Activation Code

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

{ name } Releases

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

You must be signed into your account to activate Max.

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

General

Individual

Institutional

General Authorization

Individual Product Authorization

Institutional Product Authorization

Important Information

There was an error sending your application. Please try again.

Max, RNBO, and legacy product authorization for both individuals and institutions.

Product Authorization

 If your inquiry does not fit into any other category, click here!

Other

Sales inquiries for individual licenses purchased from our webshop.

Sales

Technical support inquiries for Max, RNBO, Mira, and Max for Live.

Technical Support

For assistance with your Cycling '74 user account, our website, forums, or the Institutional Admin Portal.

Cycling '74 Account or Website

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 put together a starter template for building Max externals with CMake.

https://github.com/leeMeredith/max-cmake-template

It's a plain object box that adds two numbers. The object itself doesn't matter; it's there so the package is complete and buildable rather than a fragment. What you get is a CMake build that produces a universal binary and ad-hoc signs it, max-sdk-base wired up as a submodule so a --recursive clone builds immediately, the full package layout including a help patch and a reference page, and comments through the source explaining the non-obvious SDK calls.

The logic sits in a separate file that contains no Max code, with the object file handling only the Max side. Replacing that one file is most of what making your own object involves.

BUILD.md is probably the more useful part. It documents seven SDK behaviors that produce misleading symptoms rather than errors — three of them surface as no such object from completely unrelated causes, and one produces an Intel-only binary while still reporting a successful build. Each entry gives the symptom alongside the cause, since the symptom is what you'll have in front of you.

Verified on macOS, Apple Silicon. Windows is untested — nothing in it is deliberately mac-only, but I haven't built it there. :-)

I put together a starter template for building Max externals with CMake.

https://github.com/leeMeredith/max-cmake-template

It's a plain...

max-external-template-with-cmake

Max external template with CMake

Connector

I am working on a Jitter MOP c-external with two inputs and two outputs:

 mop = jit_object_new(_jit_sym_jit_mop, 2, 2);

As far as i understand, this would be the usual way to access the different input and output matrices:

in_matrix = jit_object_method(inputs, _jit_sym_getindex, 0);
in2_matrix = jit_object_method(inputs, _jit_sym_getindex, 1);

out_matrix = jit_object_method(outputs, _jit_sym_getindex, 0);
out2_matrix = jit_object_method(outputs, _jit_sym_getindex, 1);   

if (x && in_matrix && in2_matrix && out_matrix && out2_matrix) {

    in_savelock = (long)jit_object_method(in_matrix, _jit_sym_lock, 1);
    in2_savelock = (long)jit_object_method(in2_matrix, _jit_sym_lock, 1);
    out_savelock = (long)jit_object_method(out_matrix, _jit_sym_lock, 1);
    out2_savelock = (long)jit_object_method(out2_matrix, _jit_sym_lock, 1);

    jit_object_method(in_matrix, _jit_sym_getinfo, &in_minfo);
    jit_object_method(in2_matrix, _jit_sym_getinfo, &in2_minfo);
    jit_object_method(out_matrix, _jit_sym_getinfo, &out_minfo);
    jit_object_method(out2_matrix, _jit_sym_getinfo, &out2_minfo);
  
    jit_object_method(in_matrix, _jit_sym_getdata, &in_bp);
    jit_object_method(in2_matrix, _jit_sym_getdata, &in2_bp);
    jit_object_method(out_matrix, _jit_sym_getdata, &out_bp);
    jit_object_method(out2_matrix, _jit_sym_getdata, &out2_bp);

In this case it seems, that every output matrix has the same properties than the leftmost input matrix. 

But I would need to define different types, planecounts, dim sizes for each input and output matrix like these ones inside the matrix_calc function:

jit_matrix_info_default(&posMatrixInfo); //for out_matrix
posMatrixInfo.planecount = 3;
posMatrixInfo.dimcount = 1;
posMatrixInfo.dim[0] = posSize;
posMatrixInfo.type = _jit_sym_float32;
posMatrix = jit_object_new(_jit_sym_jit_matrix, &posMatrixInfo);

jit_matrix_info_default(&indexMatrixInfo); //for out2_matrix
indexMatrixInfo.planecount = 1;
indexMatrixInfo.dimcount = 1;
indexMatrixInfo.dim[0] = indexMatrixSize; 
indexMatrixInfo.type = _jit_sym_long;
indexMatrix = jit_object_new(_jit_sym_jit_matrix, &indexMatrixInfo);

So how and at wich point can i define my output matrices in the right way?

I am working on a Jitter MOP c-external with two inputs and two outputs:

 mop = jit_object_new(_jit_sym_jit_mop, 2, 2);

As far as i...

handling-multiple-different-output-matrices-in-jitter-mop-external

Handling multiple different output matrices in Jitter MOP external

 as basis for my next external. I just have renamed the

max.jit.gl.simple.c to max.connector.resist.c

When i try to build the external i get following error:

Using jit.gl.simple code from github fails

using-jitglsimple-code-from-github-fails

For a jitter MOP external i want to use two matrices as input and two matrices as output. For the output matrices i want to calculate some values and store it into a t_linklist for sorting the values wich are of the type connector_linesAB:

typedef struct
{
    float x;
    float y;
    float z;
} connector_point_Vec3;

typedef struct
{
    connector_point_Vec3 facePoint;
    long faceIndex;
    connector_point_Vec3 singlePoint;
    long singleIndex;
    float length;
} connector_linesAB;

The sorting and calculation of the output matrices should be done in the matrix_calc function:

t_jit_err connector_lines_matrix_calc(t_connector_lines* x, void* inputs, void* outputs)
{
    t_jit_err err = JIT_ERR_NONE;
    t_linklist* linesList = linklist_new();

    t_jit_matrix_info in_minfo, in2_minfo, out_minfo, out2_minfo;
    void *in_matrix, *in2_matrix, *out_matrix, *out2_matrix;
    char* in_bp, * in2_bp;
    float* indata, *indata2, *pospointer1, *pospointer2;
    long in_savelock, in2_savelock, out_savelock, out2_savelock;
    in_matrix = jit_object_method(inputs, _jit_sym_getindex, 0);
    in2_matrix = jit_object_method(inputs, _jit_sym_getindex, 1);

    out_matrix = jit_object_method(outputs, _jit_sym_getindex, 0);
    out2_matrix = jit_object_method(outputs, _jit_sym_getindex, 1);   

    if (x && in_matrix && in2_matrix && out_matrix && out2_matrix) {

        in_savelock = (long)jit_object_method(in_matrix, _jit_sym_lock, 1);
        in2_savelock = (long)jit_object_method(in2_matrix, _jit_sym_lock, 1);
        out_savelock = (long)jit_object_method(out_matrix, _jit_sym_lock, 1);
        out2_savelock = (long)jit_object_method(out_matrix, _jit_sym_lock, 1);

        jit_object_method(in_matrix, _jit_sym_getinfo, &in_minfo);
        jit_object_method(in2_matrix, _jit_sym_getinfo, &in2_minfo);
        jit_object_method(out_matrix, _jit_sym_getinfo, &out_minfo);
        jit_object_method(out2_matrix, _jit_sym_getinfo, &out2_minfo);
  
        jit_object_method(in_matrix, _jit_sym_getdata, &in_bp);
        jit_object_method(in2_matrix, _jit_sym_getdata, &in2_bp);
       
        if (!in_bp || !in2_bp) { err = JIT_ERR_INVALID_INPUT; goto out; }
        
        indata = (float*)(in_bp);
        indata2 = (float*)(in2_bp);
       
        for (int i = 0; i < (&in_minfo)->dim[0]; i++) {
            long offsetFacePoint = (&in_minfo)->dimstride[0] * i;
            pospointer1 = (float*)(in_bp + offsetFacePoint);
            connector_point_Vec3 facePoint;
            facePoint.x = pospointer1[0];
            facePoint.y = pospointer1[1];
            facePoint.z = pospointer1[2];

            for (int j = 0; j < (&in2_minfo)->dim[0]; j++) {

                long offsetSinglePoint = (&in2_minfo)->dimstride[0] * j;
                pospointer2 = (float*)(in2_bp + offsetSinglePoint);
                connector_point_Vec3 singlePoint;
                singlePoint.x = pospointer2[0];
                singlePoint.y = pospointer2[1];
                singlePoint.z = pospointer2[2];
                             
                connector_linesAB* newLine = (connector_linesAB*) sysmem_newptr(sizeof(connector_linesAB));
                newLine->faceIndex = i;
                newLine->facePoint = facePoint;
                newLine->singleIndex = j;
                newLine->singlePoint = singlePoint;
                newLine->length = distance(facePoint, singlePoint);

                linklist_append(linesList, newLine);
            }

        }
        
        linklist_sort(linesList, mySortListCmpfn);

        connector_linesAB* data;
        long i, count;
        long maxSinglePoints = 5;
        count = linklist_getsize(linesList);
        for (i = 0; i < maxSinglePoints; i++) {
            data = (connector_linesAB*)linklist_getindex(linesList, i);
            post("length=%f", data->length);
        }
         
        jit_object_method(out_matrix, _jit_sym_frommatrix, in_matrix, NULL);
        jit_object_method(out2_matrix, _jit_sym_frommatrix, in2_matrix, NULL);   
        
    }
    else {
        return JIT_ERR_INVALID_PTR;
    }

out:
    object_free(linesList);
    jit_object_method(out2_matrix, _jit_sym_lock, out2_savelock);
    jit_object_method(out_matrix, _jit_sym_lock, out_savelock);
    jit_object_method(in2_matrix, _jit_sym_lock, in2_savelock);
    jit_object_method(in_matrix, _jit_sym_lock, in_savelock);
    return err;
}

The memory allocation, adding Values and sorting the list seems to work but at the end of the matrix_calc function i want to free the memory with the object_free function. When i call the object_free function with the t_linklist i got following error messages:

So how do i do the right memory managment with t_linklist and my own struct types?

For a jitter MOP external i want to use two matrices as input and two matrices as output. For the output matrices i want to calculate some...

memory-management-with-tlinklist

memory management with  t_linklist

I still did not get an answer to my question so i try to edit my original post for better understanding and reproducing my Problem to hopefully some hints to my issue:

I am writing an jitter external for Max 9.0.8 with max-sdk-8.2.0:

max.testexternal.c.txt

testexternal.c.txt

Inside the external i am filling a 2x2x3 matrix and storing the matrix to brightnessTest.jxf in the Filesystem. After reading back into a matrix object i want to get the stored Values back in a jitter Patch. 

Testexternal.maxpat

 While storing the values to the matrix with this code: 

for (x->currentframe = 0; x->currentframe < 3; x->currentframe++) {
    for (i = 0; i < x->nrOfCells; i++) {
        yCellPos = i / x->cols;
        xCellPos = i % x->cols;

        brightness = 25. * i;
        post("i: %ld", i);
        post("x->currentframe: %ld, xPos: %ld, yPos: %ld", x->currentframe, xCellPos, yCellPos);
        post("brightness: %f", brightness);

        brightnessp = brightness_bp  
            + xCellPos * sizeof(float) 
            + yCellPos * sizeof(float) * (&brightness_minfo)->dim[0]
            + x->currentframe * sizeof(float) * (&brightness_minfo)->dim[0] * (&brightness_minfo)->dim[1];
        *brightnessp = brightness;

    }
}

The output to console looks fine (frames 0,1,2 are filled with values):

But when i try to read back the matrix values in the patch

it seems that only the first frame (frames 0) was read back correctly. At the second frame (frames 1) i only get 0. Values and the third frame (frames 2) i get no Values.

Hope anyone could give me a hint to solve my problem. 

I still did not get an answer to my question so i try to edit my original post for better understanding and reproducing my Problem to...

problem-with-writing-a-matrix-to-jxf-file-and-reading-it-back-to-jitter

Problem with writing a matrix to jxf File and reading it back to Jitter

David Landon

I'm working on writing an external that sends max audio signal over the internet, via UDP, directly from Max/MSP. I'm using Libuv for asynchronous I/O in an effort to reduce latency.

My question is this: how can I copy the entire signal vector at once, into a buffer that I can then send. I've reviewed the original Olaf Matthes netsend~ code and then the same netsend~ as updated by Remu and Oliver Guillerminet, and they use the old style performance methods where t_signal **sp is passed to the method and then the signal vector can be grabbed from sp->s_vec.

The new dsp64 process uses double, I know. And I _believe_ that it is a double pointer to another pointer that is an array of the samples, but without access to the code that passes variables into that routine, I'm fumbling around, not really knowing what's going on "under the hood". Does anybody have any insight into how to do this?

At this point, my best guess would be to hop into the perform64 method, and do something to the effect of:

memcpy(my_vector, inL , sizeof(maxvectorsize))???

Thoughts? Ideas? Any help would be GREATLY appreciated!

Dev Forum