Jul 27, 2012 at 10:55am
I’m altering saved object data using the setstoredvalue function with Pattrstorage.
Here’s the message I’m sending “setstoredvalue pitch 1 12.79806″ – where ‘pitch’ is the object name, ’1′ is the slot number, and ’12.79806′ is the value.
So I have 4 slots in Pattrstorage, and I’m using uzi to cycle through the messages and push the same value to all four slots. I’ve printed this to the Max window and everything looks good.
The problem is that Pattrstorage doesn’t seem to be updating when I send the messages. If I save a preset, then all four of the ‘pitch’ values should be the same, but they’re not. When I switch to a different preset in the patch, the pitch value isn’t the same. I noticed that in Pattrstorage help, using the setstoredvalue function doesn’t update the storage immediately, but when you recall the slot it does.
This ‘pitch’ object is in a bpatcher is that’s any help.
I can knock up an example patch if need be, but hoping it’s a simple oversight somewhere!
Aug 30, 2012 at 1:57pm
The fix for this was using the full path (as pattrstorage sees it) when sending the message to pattrstorage.
The message now looks like ” setstoredvalue nameofbpatch::pitch 1 12.79806″
You’ve got to use the old “::” majig.
Oct 8, 2012 at 6:15pm
e.g. anything -> [setall container_name::object_name $1] -> [pattrstorage] sets all slots to whatever value you send.
You must be logged in to reply to this topic.