pauleary

Hey all, I finally upgraded to max7 and patches that I've been working on for years

are completely broken in max7. The biggest thing is CPU clipping, my patches,

which are complex and GUI intensive, are completely blown out. They worked

fine in max6, running at about 50% cpu. The damn thing doesn't even have to be

I read somewhere that retina display can be part of the problem, but my friend

is having the same problem on a PC with my patch. I couldn't really find any more

I've attached a picture of one such patch. It's a drum machine running 8 channels

I've spent too much time on these interfaces to lose them to an upgrade; help! Right

Hey all, I finally upgraded to max7 and patches that I've been working on for years
are completely broken in max7.  The biggest thing is CPU clipping, my patches,
which are complex and GUI intensive, are completely blown out.  They worked
fine in max6, running at about 50% cpu.  The damn thing doesn't even have to be
running for the CPU to spike.

I read somewhere that retina display can be part of the problem, but my friend
is having the same problem on a PC with my patch. I couldn't really find any more
info online.

I've attached a picture of one such patch.  It's a drum machine running 8 channels
with effects for each channel.  

I've spent too much time on these interfaces to lose them to an upgrade; help!  Right
now they are completely broken.


max6-patches-running-at-50cpu-are-clipping-at-around-90-on-max7

Useful info, thanks for sharing. Just, i planned to upgrade from v6 to 7 too, but, not sure yet, How much it will be advisable.

It would be good to get answer to your comment on the issue from the experts.

Useful info, thanks for sharing. Just, i planned to upgrade from v6 to 7 too, but, not sure yet, How much it will be advisable.
It would be good to get answer to your comment on the issue from the experts.


I found that I can make it work, running at around 50% by changing the signal vector size

up to 512. But this is also after reducing instances of poly~ from about 46 down to 36.

This works for my PC friend too, who's got an old machine.

I found that I can make it work, running at around 50% by changing the signal vector size
up to 512.  But this is also after reducing instances of poly~ from about 46 down to 36.

This works for my PC friend too, who's got an old machine.


If you are seeing major performance discrepancies like this, please drop a note to 

 so we can look into it further. We've done quite a bit of work to improve performance in many areas of Max 7, but there are always edge cases. The more we know, the more likely we can either make appropriate fixes or recommend more performant approaches.

If you are seeing major performance discrepancies like this, please drop a note to https://cycling74.com/contact-support/ so we can look  into it further. We've done quite a bit of work to improve performance in many areas of Max 7, but there are always edge cases.  The more we know, the more likely we can either make appropriate fixes or recommend more performant approaches.


Max6 patches running at 50%CPU are clipping at around 90%+ on Max7