newtfish

Im wondering why max does this. Ill be working on a patch and I can put a message box underneath an object to see what is coming out, but when I attach to print, nothing.... Its like print just breaks after a while.

It happens so often and is very confusing, I have to restart max in order to get printing again.

why-does-max-sometimes-not-print

never happened to me... i suspect your patch :s

or maybe not your patch, system ? os ?.. what kind of info/rate of incoming datas ?

never happened to me... i suspect your patch :s
or maybe not your patch, system ? os ?.. what kind of info/rate of incoming datas ?


I never experienced this kind of problem with [print]. Maybe it's something in the patch? In theory, very high data rate may produce some drops, but - IMHO - more probably it's something related to the patch architecture.

i've experienced this quite a bit and it is annoying.... i did have a conversation about this with c74 in the past, but no real conclusion was reached... all I can say, is that for me, it eventually catches up and the window fills up with everything you've sent it (not ideal i know!)

i've only ever seen this in M4L tho, and mostly in the editor - never seen it in MAX itself... is that the case you you?

Yes, I think Lee you are seeing the same thing as me, occasionally it does catch up and prints things a few seconds/or even minutes after they should have printed, sometimes not at all. It does seem specific to M4L. Im constanly having to close/reopen, quit max start all over again and it really spoils the workflow.

If that's the case you might to try sending your output through a deferlow from js objects into a print - this seems to help - can't remember why originally we thought this might be a solution (I've probably got an email chain somewhere) - kinda makes so sense, but appears to help...

I've intermittently experienced exactly the same behavior: nothing appears in the Max window, then everything appears several minutes later. Only in M4L. Not something that can be reliably reproduced in an example patch. (Unfortunately the js -> deferlow workaround doesn't help in my case)

This is happening to me more and more now. It's the most annoying thing about max - because it's often taken me hours to resolve, and it's hard to see what the fix was?

However, if I use a global send "s printall" from the patch and then setup a new amxd (that is saved and closed) with just a receive "r printall" connected to a print object, I prints just fine.

I get this so often that I completely gave up on using the print object altogether, I did however find that you can sometimes get it working by right clicking the patch cord that goes to the print object and selecting "Add Watchpoint - Monitor"

Something I found more reliable though was using textedit as a print, it's fine if you don't care about line returns:

Why does max sometimes not print????