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.

phiol

This is a very basic one and yes, I've read some posts on this topic of sfrecord~ >a specific file path.

My question is how do I define a file path using [record~]?

The way that I've build my patch using the [sprintf] patch works fine.

*The only problem is, the clips that I create are saved in the file path of the last patcher window opened.

So how can I tell the buffer~ to place the samples in a specific location using [record~] ?

I suspect that it would have something to do w. path>[thispatcher] or [ ;

qr_rec_path "Macintosh HD:My Audio Folder:"] that I've found the extra's folder.

I thought I would use record~ instead of sfrecord~ because I read in a post that is has less latency with automatic playback. (Also, I like the fact that you can directly see in the [waveform~ display] what is being recorded instead of at the end like w. [sfrecord~]. 

(the downside you have to specify buffer lenght

The way that I've build my patch  using the [sprintf] patch works fine.

I suspect that it would have something to do w. path>[thispatcher] or [ ;
qr_rec_path "Macintosh HD:My Audio Folder:"] that I've found the extra's folder.

I thought I would use record~ instead of sfrecord~ because I read in a post that is has less latency with automatic playback. (Also, I like the fact that you can directly see in the [waveform~ display] what is being recorded instead of at the end like w. [sfrecord~]. 
(the downside you have to specify buffer lenght 

recordbuffer-specific-file-path

I may not be understanding you completely, but basically, record~ is recording into RAM so you can't actually define a file to write to using record~ alone. Instead you record~ into buffer~ and then use the "write" message sent to the buffer~ recorded into to save to a soundfile. Unlike sfrecord~, record~ cannot automatically write to a file stored on your hard-disk because it's writing it into a memory-space allocated in RAM as defined by you when instantiating a buffer~(i guess you could say that while it has less latency with playback it has complete latency with regards to recording-to-file). This means, you must wait 'til after the sound is recorded into a buffer~ to then write it to a soundfile(and this can only be done using the "write" message to buffer~).

With that said, you can probably apply what the posts said about specifying specific paths for sfrecord~ to the "write" message you send to buffer~.... i think... haven't looked up those posts...

That is exactly what i've done. Used [sel 1 0]/toggle

THE REAL PROBLEM IS, any sample I record will then be place in the path of the last patch opened. So if the last one opened is not my "recording patch", then I'm screwed.

Next time I close and reopen max and my recording patch, I will not be able to autoload my samples because they're placed in the wrong folder.

This is specifically what I'm trying to solve. [No matter in what order you open multiple patches to run/ when I use my "recording patch", samples will be place in the right folder.]

THE REAL PROBLEM IS, any sample I record will then be place in the path of the last patch opened. So if the last one opened is not my "recording patch", then I'm screwed. 

This is specifically what I'm trying to solve. [No matter in what order you open multiple patches to run/  when I use my "recording patch", samples will be place in the right folder.]

you can include paths in your "write" message. For example, at least on OSX, I can do "write /test.aif" and this will write it to my root folder. Or I can do "write /Users/karaokaze/Desktop/tester.aif" to write it to my desktop, etc.

Just specify the absolute path to the folder you want.

You helped me solve it. I had tried the [write /path], but the problem was that my destination folder had a space in the title.

So i replaced that space in my title w. an "_"and that was it!

I use the [sprintf]< include some "/" in it. I read somewhere that it's not a good idea to include them in the sprintf, because it can sometime behave erratically. < Is that correct in your opinion?

You helped me solve it. I had tried the [write /path], but the problem was that my destination folder had a space in the title. 

So i replaced that space in my title w. an "_"and that was it! 

One last thing, 
I use the [sprintf]< include some "/" in it. I read somewhere that it's not a good idea to include them in the sprintf, because it can sometime behave erratically. < Is that correct in your opinion?

I haven't seen it behave erratically with "/"s. It should be perfectly fine... 

also, there are ways you can get it to read filepaths that have files with spaces in them. You convert the filepath to a symbol using object and then give sprintf the "symout" argument to have it output everything as a symbol.

Better yet, option-click on for the help-file and check out the

subpatch within its help-file for specific examples of what I'm describing.

I haven't seen it behave erratically with "/"s. It should be perfectly fine... 
also, there are ways you can get it to read filepaths that have files with spaces in them. You convert the filepath to a symbol using  object and then give sprintf the "symout" argument to have it output everything as a symbol.

Better yet, option-click on  for the help-file and check out the


 subpatch within its help-file for specific examples of what I'm describing.

thanks again for all the tips. I really appreciate you efforts. really< I save time and learn and get tips for more dirt to dig.:)

> Or I can do "write /Users/karaokaze/Desktop/tester.aif" to write it to my desktop, etc.

is this the same kareokaze member I suspected to be a sort of guru ;)

you said 
> Or I can do "write /Users/karaokaze/Desktop/tester.aif" to write it to my desktop, etc.

is this the same kareokaze member I suspected to be a sort of guru ;) 

record~/buffer specific file path