mudang

I'm just learning the pattr system and I've come across a strange behaviour.

In a subpatch (abstraction) there's a named flonum and an autopattr object.

In the parent patch, there's a pattrstorage and a pattrhub.

When I try to change or get the flonum's value via the pattrhub nothing happens!

The subpatch is named 'sub' and the flonum 'a'. I send a "sub::a 0.3" or "getsub::a" message to the pattrhub.

Strangely, a pattrstorage in the same parent patch sees the flonum and it can store and restore its value.

When I exchange the autopattr for a binded pattr, setting/getting values via the pattrhub works too!

Is this a bug or am I missing something here?

I've attached a simple demonstration patch

I'm just learning the pattr system and I've come across a strange behaviour.
In a subpatch (abstraction) there's a named flonum and an autopattr object.
In the parent patch, there's a pattrstorage and a pattrhub.

When I try to change or get the flonum's value via the pattrhub nothing happens!
The subpatch is named 'sub' and the flonum 'a'. I send a "sub::a 0.3" or "getsub::a" message to the pattrhub.

Is this a bug or am I missing something here?
Thanks!

I've attached a simple demonstration patch


pattrhub-cant-access-autopattr-in-subpatch

I just realized, that you can also get/set pattr values with [pattrstorage]. This works fine with autopattr in sub-patches, too!

So i suppose, there really seems to be a bug in the communication between pattrhub and autopattrs in sub-patches, because in the same patcher level they work together flawlessly.

ok, I found the solution myself.
I just realized, that you can also get/set pattr values with [pattrstorage]. This works fine with autopattr in sub-patches, too!

So i suppose, there really seems to be a bug in the communication between pattrhub and autopattrs in sub-patches, because in the same patcher level they work together flawlessly.


pattrhub can't access autopattr in subpatch ?