Masa

I made two test M4L devices to illustrate the issue.

The device called 'filtergraph~_test_without_set', you can change values by dragging inside the visual graph, but not from the live.numbox objects. live.numbox works just for displaying the values. When duplicating the track containing this object (or save and reopen the project file), the values and the state of filtergraph~ object will be recalled.

The device called 'filtergraph~_test_with_set', you can change values either by dragging inside the visual graph and by dragging or typing into the live.numbox objects. When duplicating the track containing this object (or save and reopen the project file), the values and the state of filtergraph~ object will be lost.

I made two test M4L devices to illustrate the issue.
The device called 'filtergraph~_test_without_set', you can change values by dragging inside the visual graph, but not from the live.numbox objects. live.numbox works just for displaying the values. When duplicating the track containing this object (or save and reopen the project file), the values and the state of filtergraph~ object will be recalled.
The device called 'filtergraph~_test_with_set', you can change values either by dragging inside the visual graph and by dragging or typing into the live.numbox objects. When duplicating the track containing this object (or save and reopen the project file), the values and the state of filtergraph~ object will be lost.
I'd appreciate your insight.

Issue around auto save&recall filtergraph~object values in M4L