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.

oshii

what is the best way to create and work with a custom wave form (hand drawn one)?

I am currently only aware of the [waveform~] + [buffer~] combo, however I guess in order to save the drawn waveform I have to save it as a file, which I don't find too neat, since I guess it won't load (automatically) when a preset is invoked (i know everything is possible in Max, but I'm first thinking of something more elegant).

Hi guys,
what is the best way to create and work with a custom wave form (hand drawn one)?

I am currently only aware of the [waveform~] + [buffer~] combo, however I guess in order to save the drawn waveform I have to save it as a file, which I don't find too neat, since I guess it won't load (automatically) when a preset is invoked (i know everything is possible in Max, but I'm first thinking of something more elegant).
Any other ways?

Hi guys,
what is the best way to create and work with a custom wave form (hand drawn one)?

I am currently only aware of the [waveform~] + [

custom-waveform-buffer

not sure if that's exactly what you're looking for, but someone did something like this a while back on this forum, using the old lcd object. I'm sure there are tones of other ways to do similar drawing/buffer stuff. 

I created a custom 'vertical' buffer~/waveform view using jit.mgraphics in this thread long ago, that can be used as a starting point on how to access and draw the buffer~ info. your own way, someone told me LCD and jit.lcd might be deprecated someday so i then redid it in jit.mgraphics:

https://cycling74.com/forums/viewing-buffer-info-vertically

[Edit: also in that thread, you'll see a bunch of us shying away from JSUI because javascript was more sluggish back then, but times have changed, so JSUI might be a better option at this point.]

https://cycling74.com/forums/viewing-buffer-info-vertically 

[Edit: also in that thread, you'll see a bunch of us shying away from JSUI because javascript was more sluggish back then, but times have changed, so JSUI might be a better option at this point.]
Hope it helps.

I'e been happily using one I made using jitter openGL in a pwindow, probably is an adaptation of one of the techniques in the thread mentioned by Wrappin Raja. Makes it GPU accelerated!

No, what I would like is to be able to save a waveform I've drawn, like in [waveform~], so it can be recalled with a [preset]. So far I am only aware of one way doing that, i.e. save the buffer content as a wav/aiff file and then recall it, but I don't like this option much.. I think it only complicates things, and I'm looking for a smarter solution.

this would actually be the best/easiest/quickest solution if you save a lower-resolution of the wav/aiff file only.

if your waveform~ view is 225 pixels wide by 79 pixels high(as in your patch), then you only need 225 samples of information only(you could divide the higher/original-resolution buffer~ length by 225(width) of waveform~ to get the length at which you'd step through the buffer~ to obtain the 225 points of data needed).

edit: you can also just store this data in a coll/dict or anything else that stores data by indices and then use presets to recall all the data rather than storing the external low-resolution wav/aiff.

i can't find the time at the moment to show this to you in your patch, but hope it makes sense and maybe someone else will have a better idea anyways :D

So far I am only aware of one way doing that, i.e. save the buffer content as a wav/aiff file and then recall it...

this would actually be the best/easiest/quickest solution if you save a lower-resolution of the wav/aiff file only.
if your waveform~ view is 225 pixels wide by 79 pixels high(as in your patch), then you only need 225 samples of information only(you could divide the higher/original-resolution buffer~ length by 225(width) of waveform~ to get the length at which you'd step through the buffer~ to obtain the 225 points of data needed).

i can't find the time at the moment to show this to you in your patch, but hope it makes sense and maybe someone else will have a better idea anyways :D


you might want to consider if polybuffer~ could help in this. you would need to save the individual buffers to file but it has an embed attribute that will load all the files when the patch is loaded and you can select different buffer using presets.

I could also imagine using javascript to base64 encode a small buffer and store that in a dict (which could be embedded in the patcher), or even send it into a object so it would be recorded by pattr. Then youd also have to decode when reloading the patch.

I could also imagine using javascript to base64 encode a small buffer and store that in a dict (which could be embedded in the patcher), or even send it into a  object so it would be recorded by pattr. Then youd  also have to decode when reloading the patch.

My wish is to avoid dealing with external files because i like my patches to be self dependent as much as possible. 

👽MC WRAPPIN R∆J∆👽, if i understand your second suggestion correctly I can achieve this by storing the data from buffer~ to a coll object, and then recall the data with the presets? If correct, can you pls give some further advice how to do it? i don't find this in the help files.. 

TESTCASE, for the reason above I will first try with MC WRAPPIN's approach, then as a last resort, if nothing else can be done I will have to consider working with external files.. Will let you know how it goes.

ARVID TOMAYKO, unfortunately I still haven't started learning javascript (in my bucket list though), so I can't try out your tip.

My wish is to avoid dealing with external files because i like my patches to be self dependent as much as possible. 
👽MC WRAPPIN R∆J∆👽, if i understand your second suggestion correctly I can achieve this by storing the data from buffer~ to a coll object, and then  recall the data with the presets? If correct, can you pls give some further advice how to do it? i don't find this in the help files.. 
TESTCASE, for the reason above I will first try with MC WRAPPIN's approach, then as a last resort, if nothing else can be done I will have to consider working with external files.. Will let you know how it goes.
ARVID TOMAYKO, unfortunately I still haven't started learning javascript (in my bucket list though), so I can't try out your tip.

yes, coll or dict is fine. you would only store a 'reduced' form of the data.

2) go into your waveform~ inspector and determine the width in pixels(your original patch had a waveform~ with a width of 225)

3) divide the buffer~ length by the width of that waveform~

for example, if your buffer~ length is 1125, then you divide 1125 by 225 = 5... now you use 5 as the number of samples to step through in buffer~ to obtain 225 data points (....you can use uzi to count to 225 in increments of 5 by multiplying the output of the right-outlet of uzi by 5), then attach that to peek~ and peek~ will read one sample for every 5 samples in the buffer~ giving you 225 samples in total.

4) once you have those 225 samples, you store them in dict(or coll, whichever is easier for you, i'd recommend dict because it is newer and fancier :D)... then you can use that data to store in a small buffer~ which would only be used for waveform~ viewing.

By following the steps above, you might use just a little extra RAM to store the visual data in the smaller buffer~, but you will not have to store any external files and your patch will be self-contained.

If this is still not enough info. to help you, try it out for now, and i might have time later this weekend to help you further.

yes, coll or dict is fine. you would only store a 'reduced' form of the data.
here are some steps to try:
1) load a file into buffer~
2) go into your waveform~ inspector and determine the width in pixels(your original patch had a waveform~ with a width of 225)
3) divide the buffer~ length by the width of that waveform~
          for example, if your buffer~ length is 1125, then you divide 1125 by 225 = 5... now you use 5 as the number of samples to step through in buffer~ to obtain 225 data points (....you can use uzi to count to 225 in increments of 5 by multiplying the output of the right-outlet of uzi by 5), then attach that to peek~ and peek~ will read one sample for every 5 samples in the buffer~ giving you 225 samples in total.
4) once you have those 225 samples, you store them in dict(or coll, whichever is easier for you, i'd recommend dict because it is newer and fancier :D)... then you can use that data to store in a small buffer~ which would only be used for waveform~ viewing.

If this is still not enough info. to help you, try it out for now, and i might have time later this weekend to help you further.


Thanks for the thorough explanation, I will try it out!

In the meantime I think I also found a solution! :)

Yes! That's the way to go, very nice 👌 😃

multislider! 🙌
Yes! That's the way to go, very nice 👌 😃


custom waveform (buffer?)