Forums > MaxMSP

clogged console cut

October 13, 2009 | 5:11 pm

Hi all,

doing cut or copy of the console when there are MANY (thousands) of long lines in it can be very slow and take lots of RAM.

This happens to me often when I try to quickly clear the console by key commands alone in order to save time (banging in CMD-M, -A, -X), instead of digging up the console window, navigating to that little cross way down on the 2nd monitor, then back into my patch under development on the 1st monitor, homing in to the bang that starts another round of debug output…

So there are two corollary feature requests:
1. clear console by key command without copying it into the clipboard
2. clear console by message to ; max

Here’s a patch that fills the console, so you can try:

– Pasted Max Patch, click to expand. –

October 13, 2009 | 5:45 pm

try pressing delete instead of cut.


October 13, 2009 | 8:01 pm

Thanks, Rob!

That avoids the memory saturation, and luckily, even the sequence CMD-M, CMD-A, CMD-Delete works, so it requires less fine motor function =-)

Still, instead of these 4 keys to press, I’d prefer a menu item that I could bind a key to, or a message to max…

And the memory saturation when you do copy huge amounts of text to the clipboard might have room for optimisations, or invoke a dialog box asking if one really meant to copy 100000+ lines.


Viewing 3 posts - 1 through 3 (of 3 total)