http://cycling74.com/forums/forum.php?id=11

If you have a specific bug report, it would be best to directly contact our Support team by filling out the Bug Reporting Form, found here:

http://cycling74.com/max6betabug_form/

The Beta Forum topic can be used for more general conversation, sharing, and more general functionality questions.

Thanks for downloading and checking it out!

-Lilli

I wonder if it’s a simple bug or design issue.

Any comment from the developers?

with some model some part goes in bad position.

I wish to have Zoom and Snap in the toolbar like the old Max 5,
and also double click to make new object .
I saw a triangle on every patch cords when hover on ,good to have an option to disable it in preferences.

thanks .

I got a crash turning the mixer thing on and off, not quite sure how that works (turns the audio on/off?)

In Max 5 there is hardly any latency, in Max 6 there’s plenty, and changing vector sizes doesn’t fix it.

Any ideas?

I’m a little bit on the fence with Max 6, the applications I’ve developed run at about twice the amount of CPU compared to Max 5, so I certainly wouldn’t be able to distribute them if they were built with 6.

Is there much difference in terms of CPU usage from the Max 6 beta to the released version?

I’m also on the fence wit gen~, for some reason I thought I’d be able to take most of my patches and just quicken them up with gen~, but it doesn’t seem to work like that. What are the obvious applications of gen~? The delay network posted recently was good, but I wonder how often I’d actually use it.

Personally I’ve been enjoying the new possibilites of weird filtering in comb delay loops (such as the Karplus Strong + Hilbert transform example), and the sample-accurate buffer based processing (such as the waveset stuff).

Adapted from the Gen Overview doc:

General
- You want to create processes that can’t be easily achieved with ordinary Max/MSP/Jitter objects
- You want to program visually at a low level (or using a concise text-based expression language (codebox)) while getting the performance of compiled C code
- You want to design these new algorithms and see or hear them immediately
- You want to avoid having to compile separate windows and macintosh versions of algorithms (and in the future, 64-bit application binaries)

Examples
- arbitrary new oscillator and filter designs using single-sample feedback loops with gen~
- reverbs and physical models using networks of short feedback delays with gen~
- sample-accurate buffer~ processing such as waveset distortions with gen~
- frequency-domain processing such as spectral delays using gen~ inside pfft~