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

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

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.

tejan

~' video, I built this sampler for a project I am working on. How do I stop this from looping and instead playing it once and never again until the bang is hit again? I tried changing the groove~ object to groove~ SamplesOne @loop 0. I've removed the @loop attribute altogether, I've tried to replace the trigger with a bang, I've connected the bang to the groove object, to the sig~ object and nothing works. Thank you!

How to make this polybuffer sample player play the sample once and NOT loop.

how-to-make-this-polybuffer-sample-player-play-the-sample-once-and-not-loop

Artem Malyshev

This is an FM kick for use inside poly. I'm using phasor driven cos~s here instead of cycle~s so that the modulating oscillators remain consistent between bangs. When testing inside the patch phasor phase reset works properly but, using it within poly, phase sometimes seems to fail to reset or resets to a wrong value (the mistake persists for a while).

I wonder what could be the issue here or if there is an alternative method to using phasor->cos?

poly-phasor-phase-reset-weirdness

poly~ phasor phase reset weirdness

Ernest

This is part of a series of tutorials on the Husserl3 design. All tutorials in this series:

This time it only took me a couple of hours to convert a polyphonic design into a multiphonic one. This tutorial describes how any number of voices can play different sounds set from any number of channels, with different parameters for each channel. I'll be describing how I'm running 16 MIDI channels with 128 parameters each on any of 32 poly~ voices, but the same technique generalizes to MC.gen~ with any number of voices and any number of parameters, within any available computational limitations. Also this tutorial contains a multiphonic voice allocator patch for MIDI and kslider notes.

While the technique is easy, this is an advanced tutorial that requires at least some acquaintance with Max buffers, pattrstorage, zl objects, gen codebox, Max polyphony, and javascript.

If you're wanting multiphony, really gen~ is the best option. It can do everything the msp~ audio processing objects can, and it is much faster. So first I got a polyphonic design working in a poly~ object in gen~., with all its params stored in pattrstorage.

That meant setting scripting names for all the panel controls, and using the same names for params in gen~, which was the majority of the effort. Using the same monicker for panel obects' scripting names and gen~ Params means for example you can send pattrstorage a 'dump' command and wire its output into gen~ to set Param values.

When I started on the naming thing, I didn't realize how much difference it would really make. Now I can use the same list of param names for javascript panel control, buffer peek/pokes, and midi i/o too. So it was worth the effort.

To convert the polyphonic design to multiphony, first I created a buffer~ called 'programs' with 16 channels, and one sample for each param value, as below. When the patch is closed, the freebang message saves the buffer's state, which is then loaded again when the patch is reopened. This snip also shows how I measure for CPU peaks. When the CPU peak is over 90%, I reduce the number of playing channels automatically.

Screenshot 2021-10-15 223311.jpg

The same buffer can hold multiphonic presets, but it's advisable to arrange them as sequences within the 16 channels, viz., "buffer~ programs -1 16 @samps 12800" for 100 multiphonic presets of 128 params. Max chokes with somewhere around more than 64 channels per buffer, I don't know the exact channel limit, but I tried 32,768 channels in one buffer, and Max was really unhappy about that.

For MIDI I/O and sending parameters to gen~, first I sent a dump message to pattrstorage to print all the script names and used the zl object to concatenate them into a messagebox. I edited the messagebox to create a list of all the param names.

So one can send name/value tuples around with send and receive objects, but each one adds a buffer delay and an additional message in the message queue, so I had painstakingly wired all my panel controls directly to gen~.

As I had hardwired it all, I dragged all the wires from the poly~ object input to an 'unpack' object's second input. Then here's the clever bit. I convert the param names into buffer index offsets with a 'zl sub' object, as shown below. I poke all the param name/value tuples into the buffer channel indices like this....this just pokes it into channel 1, I haven't made the panel control to select different channels yet.

Screenshot 2021-10-15 181801.jpg

The poly~ is very simple. It simply sends a thispoly message to the gen~ object on load. For simpler designs, the loadbang for thispoly~ can be inside the poly~ object, but if the gen~ code is more than about 500 lines it doesn't compile fast enough to receive the thispoly message before it fires. So now I send it a loadbang from the top-level patch.

Screenshot 2021-10-16 010341.jpg

The next stage of the conversion is to convert the gen~ object to read the 'programs' buffer instead of using params. When I got all the Param messages set up to work properly, I simply changed them all to History variables by changing 'Param' to History' in codebox.

Then each gen~ voice peeks the buffer object for its current channel and puts the values into the instantly created history variables. There's a reason to make them static History variables rather than simple variables: by interleaving the buffer peeks for each voice on a simple clock counting from 1 to 

, I was finally able to get the Buffer reads done for all 32 poly~ voices without causing a huge processor peak, and only adding a 0.6ms latency @48khz:

Screenshot 2021-10-15 182134.jpg

At first that may not look very efficient, but in fact Max processes audio I/O in chunks set by the DSP settings, so if it's set to 128, for example, all 128 buffer values for each voice are loaded into the cache at the same time. Programmatically, it would be cleaner if buffer peeks could load more than one value at a time, but as gen~ is compiled, the performance is quite good. the important thing is to keep all the peeks sequential. If you load the values from the buffers where you want them. rather than storing them as variables, the performance is terrible.

For MIDI output, I use a similar technique to the 'zl sub' example above with the output of the pattrstorage object. For MIDI input, a 'zl lookup' object uses the same list as 'zl sub' to create the name/value tuples, which may easily be sent to the panel objects with pattrhub if they are for the currently displayed channel, and which are simply poked into the 'programs' buffer to change playing voices.

Updating the panel to show different channels

So the big problem was how to display the panel controls for each channel. When I was first learning Max, I tried putting all the params for each channel in 'zl reg' objects each poly~ object. That REALLY didn't work. Then I tried making 16 separate panels for each MIDI channel. Updating them from pattrstorage drove me crazy. I tried doing dumps from pattrstorage for each channel and sending them as messages each time a voice switched to a new channel, and the coding for that drove me crazy too.

But I finally worked out to keep it entirely separate from pattrstorage, which doesn't even know there are separate channels, and simply saves and loads presets for whatever channel is currently displayed. When changing the panel controls for a different channel, I simply use a 'for' loop to peek the buffer and send 'set' messages to all the panel controls from JavaScript, using the same parameter list that stuffs index lookup values into the 'zl sub' object above. Piece of cake!

Screenshot 2021-10-15 201230.jpg

After I made a gen voice allocator, Cycling74 made a new voice allocator which may have fixed the problems with the original one. However, I still need to store the MIDI channel numbers with each note and send messages appropriately. So I amended my polyphonic voice allocator to support multiple channels in a matter of minutes. Here is the patch containing the voice allocator.

It also contains velocity shaping described at the end.

Screenshot 2021-10-15 230256.jpg

The gen voice allocator resets to the number of voices set by a negative value on the first input, or a note when a positive value is received on the first input. That simply avoided making it 'hot.' It also turns notes off on the attached kslider object when the available voice count is exceeded. the 'lastv' signal is used to update the display indicators from the last played voice on the currently visible channel, in javascript.

Buffer pch(), vel(), age(), chn();    // voice state buffers
History numv(0), vcnt(32), lastv(32), gcnt(1);
x, aoff = 0; 
chan = in3;
if (in1 < 0){                 // RESETS 
    for (i=1; i<=32; i+=1){
        vel.poke(0, i); 
        pch.poke(0, i);
        age.poke(i, i);
        chn.poke(0, i); 
    }
    numv     = 0;
    vcnt     = neg(in1);
    lastv     = vcnt;
}else if (in2 >0) {        // NOTE ON
    for(i=1;i<=vcnt; i+=1){
        x = age.peek(i);
        if(x == vcnt){
            if(numv==vcnt){
                if(vel.peek(i)>0){
                    out4 = pch.peek(i); 
                    //kb overflow update
                }
            }else{
                numv +=1;
                out4= 0;
            }
            chn.poke(in3, i);
            age.poke(1, i);
            lastv = i;    // last voice on
            out7 = in2;    // velocity
            gcnt += 1;
            out6 = in3;
            out3 = gcnt;    //gate out 0-1
            out2 = in1;     //fc out, Hz
            out1 = i;
            pch.poke(in1,i); 
            vel.poke(out7,i);
        }else{
            age.poke(x+1,i);
        }
    }
    p0  = in1;
} else if (in2 ==0){                    //NOTE OFF
    for(i=1;i<=vcnt; i+=1){
        if(pch.peek(i) ==in1 && chn.peek==in2){
            aoff = age.peek(i);
            pch.poke(0, i);
            vel.poke(0, i);
            chn.poke(0, i);
            for(j=1;j<=vcnt; j+=1){
                x = age.peek(j);
                if(x>aoff && x<=numv){
                    age.poke(x-1, j);
                }
            }
            age.poke(numv, i);
            numv -=1;        
            out6 = in3;
            out4 = 0;     //kb fix
            out3 = 0;     //vel 0
            out2 = in1;     //fr off
            out1 = i;    //voice off
            break;
        }
    }
}
out5 = lastv;

The result has no performance problem. On my 4Ghz 6700k i7, which admittedly is still a pretty good cpu, it only adds 2% to peek all 128 params into gen~ with it running at 48kHz with 256/64 dsp buffer sizes and 32 channels. It was interleaving the buffer reads across clock cycles for each poly~ voice that really made the difference, because otherwise that 2% becomes 64%. It just means a 0.6ms latency between param updates on channels, which actually is faster than the params are typically updated in gen~, which I'm told happens every 256 clock cycles, although I don't know if that's actually dependent on the DSP settings.

Screenshot 2021-10-15 210049.jpg

I hope you enjoyed the tutorial. Happy patching to you all )

This is part of a series of tutorials on the Husserl3 design. All tutorials in this series:
Designing a good LFO in gen~ Codebox:  https://c

implementing-multiphony-in-max

Husserl tutorial series (5). Implementing Multiphony in Max

DaSheng Hen

I use js code to randomly generate 10 numbers and save them in dict. I can receive the numbers normally, but why does dict always prompt "dict: doesn't understand "int"" ?

dict-error-message

Dict error message

Ullstein

I built a standalone app and would like to include a function that the patcher saves to disc at closebang without having a Mac dialog appear. 

The idea is to save a few data in the app each time it is closed without asking the user to save it.

Is there any command available to do so? I checked the complete browser but cannot find any. Is there are workaround to get there?

I built a standalone app and would like to include a function that the patcher saves to disc at closebang without having a Mac dialog appear

save-the-patcher-function-inside-a-standalone

Save the patcher function inside a standalone

Tim Massar

Hi, new max user, i think some of my frustrations come from wanting to do things in Max the way I used to do them in Reaktor (as context)...anyway looking for advice. I wanted a phasor to be synced to the transport, used the standard delta, edge detection for creating bangs at resets to drive a counter that worked independently, but still synced to the transport. What I wanted to do was read what bar and what beat I was on then modulo the counter with the note division i chose, add all those numbers together to get the current step number in relation to the size set by the user in bars - for example, If i set my midi recording to loop every 2 bars I modulo the current bar over 2, multiply by my note division, then add the current beat multiplied by note divisions to get my starting offset value to add to my counter driving current step from 0. But, the phasor was wildly out of sync. numbers that should reset over the modulo at the same time were sometimes two or three steps behind, the phasor was inconsistently throwing out a 1 at the start instead of starting at 0, and just looking at a counter of the phasor edge detection and transport beat readout it was clear they were operating on much different wavelengths. Wish I had the project to share, it was total spaghetti wires anyway, but with all this possibly being irrelevant, what is the best way to independently clock something that is still synced to the transport?

Edit: also is there a way to hold a calculation from being processed until I receive new numbers at both inlets? Because Im still having this sync problem driving from the metronome. Numebers in modulo are rolling over to 0 before the last numbers have arrived from the previous calculation, even though they should be all arriving simulataneously.

Best way to sync a Phasor~ with transport?

best-way-to-sync-a-phasor-with-transport

Was trying to improve on my poly sequencer and ran into an issue where poly~ seemingly ignores the contents of notemessages (messages are structured as follows: notemessage - note - list of parameters).

Things stopped working after I wrapped the "noteGen" subpatch (at the bottom) inside of a different poly object. Output messages looks to be the same but poly~ synth no longer gets it.

Poly~ doesn't receive "notemessage" contents

poly-doesnt-receive-notemessage-contents

Noise Wrangler

I'm sharing this issue to make sure I'm not the only one facing it. When using 

 state anymore. This is a new issue from 9.0.5 for me, 9.0.4 works fine. It seems to be a problem with snapshots as well but since I'm not using them, I have not made extensive tests.

I'd like to know if others face the same issue before issuing a bug report.

MaxMSP Forum