Pattr vs snapshots for VSTs - I've noticed reliability differences
While snapshots have always been rock-solid reliable when it comes to saving the total internal state of a large VST plugin such as MSoundFactory, pattr has not and often failed to save a complete state of a plugin.
Any ideas why?
there can be a number of reasons, among them interpolation activated for pattr or the plug-in uses the chunk format and hence ignores the request to send its state.
i am huge fan of custom systems which go parameter by parameter - but that also fails with chunk formats.
safe to my knowledge is only snapshots, and idiotproof is only import/export. (the import/export path could eventually be stored in a pattr...)
Thanks, Roman.
Interesting thing is that the pattr variant often works flawlessly for a particular VST state when you try it multiple times but there are also occasional attempts when it simply fails completely - again, for the identical state. Whereas Snapshots simply work. And since the docs speak about snapshot support in pattr reference I find it puzzling why is it different and so unstable.
Could you explain the import/export thing? What exactly are you talking about?
vst preset file to disk. (read/write to vst~)
i see, "sometimes works sometimes not" seems releated to the amount of data. beside the tip to check if interpolation on i have no further experience with pattr when to comes to this.
"vst preset file to disk. (read/write to vst~)"
Ah, of course.
"i see, "sometimes works sometimes not" seems releated to the amount of data. beside the tip to check if interpolation on i have no further experience with pattr when to comes to this."
OK, thanks a lot Roman. Will try to investigate a bit more.