Moving presets to disk

[woodslanding]

As promised, HH5 supports saving and loading presets to disk. Olivier has suggested that the instability I've encountered in my WKP is likely due to the huge number of presets in the WKP. Presets for VSTs such as Kontakt and Reaktor can be truly huge, and my WKP is over a gigabyte as a result. This also means that it loads very slowly-- so when I do have a crash, it takes a long time to reboot.

So, I'm planning to move all my presets to disk. I'm thinking I could write a script/patch to automate the process.

It would go something like this:
1. Set the file name/path input to [patchname] / [presetNum]-[presetName]
2. save the preset without dialog.
increment the preset number and repeat...

Do you think this could work? My biggest concern is making the script wait for the previous save step to conclude, before starting the next. The last script I wrote that initiated a sequence of time-consuming events did not seem to do so correctly, and therefore dropped lots of steps in the process.

If anyone has been experimenting with saving presets to file, please chime in. Otherwise, I will forge ahead

cheers,
-eric

[senso]

normally, yes, it should work ! even without a script if you use new strings modules to create the proper filename.
senso++

[woodslanding]

okay, this has been working really well, and the controls on the new PM make it very easy to wire up! I've rearchitected my WKP to use the new method, and it loads in 20 seconds rather than 4 minutes! It also uses half the memory.

But I am having a problem with Keyscape. It won't load presets created from my old wkp. Kontakt, Reaktor, Synthmaster have all had no problem.

I opened up the preset files in a text editor, and files created with the new WKP have these lines:
[7442856270553789059]
CHUNK=504730310000000....

The same preset created in the old wkp, which won't load in the new one, shows:
[4869531422799764010]
CHUNK=504730310000000...

Looks to be the same data, but stored with a different key. Do you know why this would be?

Currently all my presets for Keyscape are stored in the old WKP, and they are all modified from factory. I'd rather not load them into the old WKP, one by one, save them all in Keyscape, and then load them from the keyscape menu into the new WKP-- but I could certainly do that.

I could also write a find/replace script to convert the old key to the new one for all the presets in the folder. Since it looks like the chunk data is intact, it seems like it might work.

Thoughts?

[senso]

the preset ID has probably changed for many possible reasons.
Unfortunately, nothing to do except change preset ID manually.

[woodslanding]

Okay, I wrote a script to do the conversion... but it concerns me that someday I might make some kind of edit to a patch, and then it won't load its old presets any more?

I guess if that happens, I'll just have to do another conversion.