I've been lobbying for this behavior for years (maybe decades.)

Pasting at the mouse position makes so much more sense than the existing method of pasting at the same point as the original copy. The existing behavior is so very rarely useful that it should be jettisoned, IMO.

yeah, I've had a few situations where I've struggled with this recently - especially when attempting to paste into an already crowded space.

Max seems to still be strangely weighed down by legacy functions and limitations in this respect.

Another example is that lack of key command for "save as", which is another really odd basic omission.

I think Max's history of "new versions must not break IRCAM composers' old compositions" has resulted in embedding bugs in amber. At one point I had a new version of Counter (which was my first Max object, and my first C code) which fixed a lot of stuff, and added a couple of features, but it was decided that people might be relying on the buggy way Counter worked. For a while I maintained a parallel path with Kounter, but eventually gave up on that.

Key commands are easy to add or modify, though. (at least for some values of "easy") All the mapping is contained in maxinterface.json. You'll want to make a copy of any edits and keep it somewhere that the Max installer doesn't know about, as it will get overwritten with any new update.

Hi Chris,

Do you think it is possible to modify the maxinteface.json to enable pasting at mouse position?

Joe

Always wondered why this is not the case. Chris please, bring back your non buggy counter object, the standard one drives me mad...

not that this has to do anything with copy/paste ...

@ stephane: [f0.ultimate_counter] done by Frederik Olofsson behaves more predictable than his schizophrenic older brother ...