Eric_Singer

I have a number of bpatchers set up to write their parameters into pattrstorage, located in the main patch. Everything seems to be working fine with the store mechanism - the parameters appear in both the storagewindow and clientwindow. However, when I write the file, I get an empty shell of a json file with just the basic bracketed scripting name of the pattrstorage, and none of the (100s of) parameters get stored.

Is there currently a bug in pattrstorage? I actually have the same thing implemented in another patch with fewer (9) parameters, and it works fine.

Hi,
I have a number of bpatchers set up to write their parameters into pattrstorage, located in the main patch. Everything seems to be working fine with the store mechanism - the parameters appear in both the storagewindow and clientwindow. However, when I write the file, I get an empty shell of a json file with just the basic bracketed scripting name of the pattrstorage, and none of the (100s of) parameters get stored.

Is there currently a bug in pattrstorage? I actually have the same thing implemented in another patch with fewer (9) parameters, and it works fine.


pattr-bug

Update: Attached is a pic of the screens that pattrstorage is seeing. Here is the written output of the file:

        "slots" :         {

{
	"pattrstorage" : 	{
		"name" : "MyParams",
		"slots" : 		{

it seems to don't first save your preset in a slot (from your screenshot i can see your datas are in slot 0) before you save your file.

Ah, so slot 0 doesn't count. Cycling: please put this in the docs for 'pattrstorage'!

pattr bug?