outlet_rm: wasn't in table
any way to consistently not get these message when using [pvar] and closing your patches?
they are really annoying me
problems mostly with [prepend] boxes
----------begin_max5_patcher---------- 209.3ocuP1rCBBCDD9b6SQSOiFJQiQu4yggXJvpVCTZnEEk36t8G.i2TO3kI oyzc+1L8XDMqtCzTxFxNBB0iQHuky.M7FQq3c4kbs+aTIbsN6LMJDYfNi2Vc g2PzJ.JFiTbS9Ig739FH2DHvVNONhrvqqhcZhUIoCSHaqpaMkfwShM3JJ7.r PmkLt6C0RijWA9jsMBd4XRXAlaJHfjRmVuaHs3tOfkXoOQUHmf57dfwNI5mZ DaOLcYu0GuppFPAxhOrsB5Z122Vr+ZaQRwOvOIKJK5E -----------end_max5_patcher-----------
nobody else seeing this?
it’s semi-repeatable and so annoying!
Your patch creates it repeatable for me. Looks like a bug, maybe send it as well to support, though its claimed that the forum is monitored, but without a direct feedback from cycling I wouldn’t count on it…
As far as I can tell, pvar only works with UI objects. In your example, the prepend object has its scripting name set to speed, which causes the post in the Max window to appear.
I see nothing to say that the use of [pvar] objects is restricted to being associated with only certain types of objects. Indeed, that is not how I’ve been using it!
The [prepend] object has its name set to ‘speed’ because that’s how [pvar] works. The inlets and outlets of a [pvar] object are associated with the inlets and outlets of the named object.
For example, this patch does not repeatedly produce the error:
----------begin_max5_patcher---------- 214.3ocqP1rBBCCDD9bxSQXOWk1nEAu4ygHRZMpQZSKsqZ0hu6llzV+AEEwK CjYlM6xWMk.QYUxRfMkMmQH0TBwZ0XPZeSfTQUbhnzVCzxiYQ6.OWDJqPqc9 AQAqLWJW0Eo2mlsGSjnctfVW0JacyWLf20zUCOkKcGB.rEsQqyznVjZCfYEJ QBbWRo5rMIfOz+1VU5mWZt.i2pzaVVHiQ2NBBMivFa0I9MJ2nrEMCbgRaDue hHFNzevOvidTo9ZBE7VBoz3+BR7OAImNhOL7EPx73B8JsXzgzC -----------end_max5_patcher-----------