Printing, the new @popup and redirect feature request

Oct 28, 2011 at 11:45am

Printing, the new @popup and redirect feature request

I like the new print popup attribute but there is no option to turn off its output to the Max window. I suggest to add another attribute to turn off the Max window output, or a @popup 2. Since Max5 the Max window is really cpu hungry and therefor you can’t use the new popup window in an interface for anything other than occasional feedback.

And while we’re on the subject I would like to propose a feature request for an option to redirect all Max output to a log file instead of the Max window. This would allow you to:
- save cpu
- redirect all output for a standalone app
- inspect high volume dataflow
- be able to use commandline tools or your favorite texteditor with search to inspect the data.
- support / debugging for standalone apps or installations without monitor output.

Right now you can’t debug high volume inputs like sensors or osc streams using print. I’m sure there are objects for writing to log files, but having an application level redirect (including the output from externals) would be awesome.

At the moment there is a setmirrortoconsole message to max, but this doesn’t solve the problem of the Max window hijacking your cpu. I can imagine C74 is not really eager to fix this cpu issue at the source because you might have to sacrifice some functionality which was added in Max5 like clicking on a message and seeing where it came from. So I’m thinking a feature like the one I described could keep everyone happy.

Thanks for listening.

#59613
Oct 28, 2011 at 1:09pm

“an option to redirect all Max output to a log file instead of the Max window.”

+1!!

#214548
Nov 7, 2011 at 11:58am

I must say that I really notice a huge improvement in the Max window performance. It seems like it’s not causing any real problems anymore when you print a lot of stuff to it. Thanks for fixing this!

#214549

You must be logged in to reply to this topic.