Max 6 Public Beta is HERE
Awesome – about to check it out . . .
Just spending a few minutes with it you can tell that the advancement in documentation is a HUGE step forward. The sidebar integrated into the patcher is such an awesome feature.
I notice the mac version’s for intel machines only (&os10,5+).
Will there be builds for ppc machines at all?
Sorry, but Max 6 is (and will remain) Intel only.
OK– looks like it’s time to upgrade… any suggestions as to the most appropriate mac to get re max 6 ( I do mainly audio stuff, very interested in the gen suite)
Thank you all so very much!
Also, it seems that the new [dict] structure has gone unheralded, yet has single-handedly changed my life!
Quick question… I just opened a Max5 patcher that contains a poly~ that has a vs attribute of 1 to do some tapin~ & tapout~ stuff. It hitting a whole new CPU high with the 64 bit processing. Are there any recommendations regarding how to make the switch? I guess I’m asking if I just have to port my existing patch to gen~ to be efficient in Max6?
We are currently in the process of doing some optimization of Max 6. If there are particular patchers that you can provide us to clearly demonstrate performance differences between Max 5 and Max 6 we’d love to take a look at them.
However, both the 1-sample feedback scenario and really awesome performance are areas where gen~ really shines bright!
The elves have given us an early (insert festival here) present!
The beta version request an authorization, can we already purchase max 6?
Is it compatible with Max5? Does it read the patches?
Are there any plans to include a 64-bit integer data format in Max6?
64-bit vs 32-bit numbers followup:
the number~ object seems to be 64-bit, its outputs read "double" — is there a non-audio object for double-precision floats? in the documentation I still see "float" input but not "double".
@Hans Mittendorf : Yes, it reads Max 5 patchers. Max 5 will also read Max 6 patchers (the patcher format hasn’t changed), but obviously new features won’t be supported.
@efe you should just be able to use demo mode for now. we will be releasing the full version before this demo period is over and you can purchase it then.
@hans Yes, Max 6 can read Max 5 patches. and Max 5 can read Max 6 patches, as the format hasn’t changed. However, any new objects/features will not be preserved when opening and saving Max 6 patches in Max 5.
@000masa000 There will be no 64bit atom type (for Max int/float) until we make the change to 64 bit binary application. Changing MSP to support this was much simpler to change than to do this for arbitrary atom lists and all the third party objects which rely on this.
great new 3D tools… thanks for that. I was waiting for this release.
But if I have to be critical, I have to admit I’m still messed up with the new object palette.
Previous palette was more efficient to me.
The palette is now bigger, and dragging objects to the patch is not really user friendly to me…
It is all the more the case since the patch is big. double clicking at the exact place I wanted my object to be inserted was perfect. But I may be the only one to feel it this way?
Is there a way to go back to the old palette?
Quick question about [gen~] – is the attached effectively sample-accurate, or does it still involve a single sample’s worth of delay? (It’s for a pattern step counter whose length can be adjusted on the fly… I usually use a homebrew external counter for this.)
@christripledot — below is a patcher that I believe will make you very happy. Turn on the audio and then take a look at the two capture~ objects. You should see the first sample for the input trigger is a "1" and in the other capture~ you will see that the output is stepped-up immediately.
----------begin_max5_patcher---------- 1044.3oc4X00iapCD8YxuBDu1zHrIPRpz998gp6yWoUWsxAbHtkXi.y1rsp6 u8ZrMrlt.w4itMqxKjcmAOblyL93A9wDGu0r83RO2O4duqiyOl33HMUavQ++ Nd6P6iyPkxayC+8DT7ydSUtnU6HzLLW5CpMli3waIzzGJvwbUrCfgy7m5BC7 q+YdXyU2+WuFRhL5r0e4i.einyp3Mg2u13OmLo9xTKQKE+MQHahGGuWhGujx 7RNhi6OO.CmGPnLAVJSfn4xbBzeZrpI1aXTNEsCK87O3rGwbRLx8ewUX2OSR 2x6OcmqspLweJGqffGgJVgq2lLFR9G5+u9mVbT+LKIeWtD.b1Ej5hQ47pB7y tabA999GKAB.RBDFJ+YU3XL3xyjA8u5IC64hEWObw5JNmQOwcN.sPfey09R1 n9yAvP6HVinohd+KWcsjj9rKH5nywEpbbgLGUk0gJnyOyB5fjg.6TT1kUJnZ 2ZbQqXo3IHaol4O1o.6XI3Cbpftm.Fp3qnw3qfyjufGfuZUTeKzPyHwe8TO6 ADoNCELFaAeO0c0OIkhoG8XFMMTJg0fkiQQf+7MTCSSlo.tPSNZ1Qb2jL7i3 hRhPl8khgiGJO2vriwRpozuvjAJZZqIBUYxu0TA9QRy58UFEEpIMNa3wnEPY OFTskbohNMYRQQMMlkoh+8BsfUS6dw7FyXweEmXhDOVNlRn4E3RLULIVCjZb mf2fpx3OzOu00+FTLdvEaSg0wKsfjvn0XpSfpM27zu2UIRYRAR+TTdOKsd7x px0nhZ9dcVW.xYrrttZKwhsJHJYmX1TNQgbne65H6xKji4YDKLEIhw1x3BVV VmPo77XOdRDcAw3uQR3a6HjW6Qb6j7l5gWKCkPRwk7t13nzxtV571DlsmlZ. crOlVPW8fsjRNq3ISe8obdfAOAqLdCjNMzCLv0QIQLrRZ+REdcd58ok5znmp 2pd4406taPJEZGkFEpjGlENNkFcqPoe3jozPygjOLiFdqvnDpKXPN02FNUcM v+P66A2PTJ7ToT8.V1xovaENcuXdnyZm+JK23GbqvnBPMxNefMbJTe9zxC0l N+BQp9GGq8x7jYD5PiOIytZ+8Smkrph3l5lVFysahJFsiSnsiZeeaizuceaI IIcGlUM+WY8zjIFu3vAJ8GKhCrDwgWMHNzRDO+cGhitZPL7HPL3p.wQVh3EW Mb7hiXmG3cEhCtPH9EI5Dr3M8EQH9oGhQwaw8qV2dvgXffY61yd4rBulyW8H eF8edivIsw3C2c1g3tyOD5W+1t3n9V7ZFT+4.kbX2i3Tecveu3q+Fgupnuxr naiv0qK1utP+puUosnAXAZV9lgFnEnYwaFZhr.Mv2LzL2Bz.LEJ9qWo.WUcw AmHZDh.+bxu.dg2dn -----------end_max5_patcher-----------
Oh Tim, I could kiss you :)
Are we likely to see better quality interpolation with [play~] as with [groove~]? (i.e. will you be making my soon-to-be-completed click-triggerable playback object redundant too?) :D
I very much agree about the object explorer. It’s an inefficient use of space to have it on screen all the time, and I also have to scroll the view to get access to objects that in the old object palette were visible immediately.
ohhhh yeaaah !!
Gen is amazing :)
OUCH! Don’t open the filterdesign help patch with audio on. Nearly took out my monitors!
glad to see polybuffer~ is official now! much appreciated.
these new alignment guides are nice. i will not miss pressing command+y all day long.
For those complaining about the object explorer, try the sidebar. Seems a lot better to me.
How exactly do Max5 and Max6 co-exist? I noted that once I installed Max6, all my patchers’ icons changed to the Max6 picture.
What does one do to switch between one and the other (needed until I’m sure everything I’ve done is compatible)? Is it sufficient to just use Get Info on a single patcher and change the file association?
max6 installs into "applications/max6" where 5 lives in "applications/max5" so nothing is overwritten.
to change the default association back to max5, after you get info and choose max 5, from the "open with" drop-down menu, click the "Change All" button.
Great – that’s what I hoped but I saw something from someone that suggested this was not the case.
Did you try it ?
Please, could confirm that it works well as I also saw the 2 posts mentioning a problem.
I don’t want to install the beta if I’m not sure to be able to use my max5 patches.
Did you read previous posts? Max 6 doesn’t overwrite Max 5, they can both live on the same hard drive, and the file type is the same for Max 5 and Max 6, so there’s nothing to worry about.
That’s precisely what I was concerned about!
I haven’t had a chance to try this yet, but I will.
the file type is the same for Max 5 and Max 6
It’s only a concern with regard to which version of Max is set as the default to open the files automatically. Opening the files from within Max 5 or any other numerous means works just fine.
Yes, that is what I would expect, but as someone observed, there was an earlier post (which I can’t find) that suggested that there might have been an issue.
Now, I just tried it and it’s failing! What happens is that I selected a .maxpat file, did a "Get Info", changed the "Open with:" back to Max 5.1.8, and clicked Change All.
I was prompted with the expected dialog about whether I was sure I want to change all similar documents, etc.
I clicked "Continue" and then the "Get Info" immediately reverted back to Max 6.
So for whatever reason, switching back to Max 5 is NOT working.
Hopefully this is something simple to address.
Thanks for your suggestion !
But not only I’ve read all the posts earlier (and, I think, all the posts concerning Max6) but found this one : http://cycling74.com/forums/topic.php?id=35590
And as we speak of reading, the question asked was not to know if wether or not, the beta overwrites the previous installation but if the files made in Max5 could be, in the worst case, be read again, by default, within Max5 (and in my case M4L)
So far, I’ve not heard from someone who has done the "return trip" with success…
OK — I tried several suggestions from the Apple forums, none of which worked.
I then moved Max6 to the trash and emptied the trash.
That worked — I have Max 5 back again.
Now "fademode" message doesn´t work with chucker~.
I see the behavior you’re talking about now.
1) Is this really a deal breaker? So you can’t double-click from the Finder to open in Max 5? Not really that big of a deal to me.
2) I have experienced this kind behavior in OS X with other file types in the past, so it is at least possible that it could be an OS level issue.
Well, in my live setup, I have various top level patches, each one representing a song. Normally, I cause those top level patches to be opened remotely from my iPad via the pcontrol. However, every now and again, it’s very convenient (sometimes a lifesaver if the network between my iPad and laptop fails) to simply double-click on a song patch to open it.
So until I have an opportunity to confirm that my current collection of patches works perfectly with Max6, of course it’s a deal breaker for anyone who depends on the product for day to day work.
Also, it is almost certainly an OS issue and is probably fixable through means other than temporarily deleting Max 6.
FWIW, this is an OS-level issue.
It sounds like it might be time to explore the Project window in Max 6.
Remember this is a ‘Beta’ so expect there to be issues that need to be resolved . . .
I don’t know what you are saying Piet. I thought Max 5 was a step backward in making new objects. Max 6 is definitely an improvement. The previous Object Palette made you double click in the Patcher window and then choose from it’s narrow contents inside the HUD. Now we can access every object directly from the Object Explorer and can choose from whatever look to the Explorer we want. I like the list view most, more information is better.
I was always frustrated in Max 5 that I couldn’t make a new object similar to Max 4, where I could drop a blank object and type the contents with the click of a mouse. Now we can do this same thing in Max 6, making the addition of new objects to the patcher window much faster. Just open the patcher Sidebar and while in the Object Explorer, click the cogwheel at the bottom and Choose Create Object Box Before Showing Explorer. Now you can click anywhere in a patcher window and a blank object box appears, type in the name of the object and Max 6 will autocomplete, you can even go one step further and begin adding attributes. This is a way faster method than in previous versions.
For some more tips about the new interface changes, check out the blog post I wrote on Installationspace.com. I’m writing another one shortly about some of the new objects I am finding in Max 6.
Good work everyone at Cycling ’74! I’m going through old patches and finding a lot of Max 5 patches that use Open GL objects aren’t working now, but to be expected given the overhaul of Jitter. I’ll always keep the last version around, knowing from experience in new releases.
"I was always frustrated in Max 5 that I couldn’t make a new object similar to Max 4, where I could drop a blank object and type the contents with the click of a mouse."
Eh? Wha? Um, the best thing about Max 5 by six million miles is the ability to press ‘n’ to create a blank object right where your mouse pointer is and immediately type the contents, without the click of a mouse.
Max 6 is actually slower in this regard, because although it "autosuggests" the object you’ve started typing, it doesn’t autocomplete like Max 5 does (unless I’m missing an option somewhere).
"Max 6 is actually slower in this regard, because although it "autosuggests" the object you’ve started typing, it doesn’t autocomplete like Max 5 does (unless I’m missing an option somewhere)."
I miss the autocompletion feature too
Using the Windows installer, can I specify the installation path?
@christripledot do you have an exact sequence of keys you are pressing that you can provide us?
1. Press ‘n’ to get a new object box
2. Type ‘b’
3. Type ‘o’
4. Hit the down arrow key 2 times to select ‘borax’
5. Hit return
My sequence autocomplete borax and creates the object. Perhaps you have a slightly different sequence?
Is there an official release date for Max 6 yet?
I think the difference between the new and old autocompletion is that in the old system, when you pressed enter the current completion guess would be filled in to the object box. In the new system if you press enter without pressing the down arrow to select an object then the box remains uncompleted.
I haven’t tried 6 yet, but I think the current way of pressing enter once for autocompletion is the way to go. Why the extra down arrow press. Down arrow makes you move your hand from the familiar keys. Maybe not good on something that is done often. Building in Max is light years speedier than any other option, keep that trend IMO.
Just downloaded the beta: FANTASTIC!!!!! Can’t wait until it is stable.
One Question: is the new patcher mixer accessible from somewhere else than the gui?
I was searching the the documentation and could find anything. the places I’d expect it would be either an object an object such as [mixer~] [patchermixer~],
or a message to msp maybe.
Max 5: ‘n’, ‘b’, ‘o’, enter = [bondo]
Max 6: ‘n’, ‘b’, ‘o’, enter = [bo] (no such object)
David Butler is on the same wavelength: you don’t have to hit the arrow key in Max 5 if the first suggested object is the one you want.
it would be nice to be able to use multi-touch to scroll in windows that have disabled scrollbars. otherwise i have to add margins to a lot of my patches cos theyre either ‘on’ or they pop up when i go near a button thats near the edge
also agree about autocomplete
it sounds amazing :)
I really like the ability to mix different patches. Is there a way to automate or control the faders for various patch windows? This would be incredible. I would also like to see a pan for each patch too! :)
I find myself in agreement with other opinions about the autocompletion being better in max 5. It’s simply much quicker when you already know which object you want to make.
I wish there were a way to detach the sidebar so that you could have it as a window that is constantly open and refreshes its contents based on which patch/object is in focus/selected.
Also is there no way to view the full reference and tutorials in the sidebar?
This looks fantastic!
However, I am already getting nightmares about how to migrate all those externals I’ve downloaded the last few years to Max 6. They are scattered all over the place. What are people’s best advice on how to migrate? And where do you people keep your 3rd party externals? They can’t all be placed in a separate folder, AFAIK.
Yes they can. Make one folder "myExternals" somewhere and it to the search path. If you include sub folders it makes it easier to keep a clean structure:
like this you don’t need to move anything if a new max version comes out. just add the search path again.
"I am already getting nightmares about how to migrate all those externals I’ve downloaded the last few years to Max 6. They are scattered all over the place."
You could add the external and maxhelp extensions to Max5/Cycling ’74/init/max-fileformats.txt and make a little patch with [shell] (or Win equivalent) and Alex Harker’s [recursivefolder] to search for them all and move them to a new "myExternals" directory :)
I can’t install it.
I’m on 10.5.8, double click to install, :double click:, nothing, just the same picture telling me to double click…
Thanks for all the migrating hints and tips – nice to know you can place externals in separate folders!
However, is there a (clever) way to separate third party externals from the original maxmsp externals?
You’ll get the best results from posting your beta-related questions to the new "Beta" topic of this forum, and no longer to the "MaxMSP" one. Thanks much!