Julien Bayle

is there an issue why we cannot save xy parameter of the [nodes]'s knob within a [preset] object ?

There are many ways to workaround it but... just why ?!

Hi there,
is there an issue why we cannot save xy parameter of the [nodes]'s knob within a [preset] object ?

nodes-and-preset

There is some history to this fact, as you might suspect. In my original implementation of nodes, there was no knob. The primary purpose of the UI was setting up the node space and saving that information, and another UI was expected to provide the controls. So the preset/pattr functions are all focussed on the nodes themselves, and haven't really changed since the object was first introduced. When it was brought into the Max distro, EJ had the idea to add an optional knob, which turned out to be a great added feature. We generally thought of it as a convenience though and not really the core of the object.

All that said, I can see your argument, and will file a feature request. :)

There were a few arguments to leave the knob out of the presets:

And you can preset both with just a little bit of patching:

the knob is often controlled by an external process (some random walk), so having nodes recalling values would be more problematic

if used in Max for Live in parameter mode, it would add to many information in the undo stack

it's easy to store a list of 2 values, it's more complicated to recall the nodes position/size

you can separate the knob presets from the nodes position/size

[nodes] and [preset]