DSP Robotics Support

Hi guys.
Having some problems with using multiple preset managers at once in the same schematic. I use 13 of them
I need them to control multi channel sampler which every channel in it is actually a separate instrument with it's own controls. Well it works, but FS crushes after a little while of working and gives "Out of memory" message

Does anyone knows about any reasonable working solution for this? Thought about abandoning completely the preset manager solution (it would be stand alone program) and moving to text files. There is any sence in doing that?

are you sure preset managers are the culprit? "out of memory" basically means your plugin uses more than 3GB of RAM. You mention 13 multi-channelled samplers...

Hi Kortezzzz

Page 389 of the Component Reference:
You must have one and only one preset manager per module if you want to have preset support. In
the majority of cases the Preset Manager module will be all you need.

The "per module" I believe means the whole project because I tried to have more than one a long time ago (in a sub-module) and it didn't work.
The Preset module is used to control global dialogue between the host and the plugin so there can be only one. I never tried this in a stand-alone export but my guess is that there would be issues there too, since the compiled preset function will be the same I assume.

Re Out of Memory message: I found this can happen on large schematics with lots of data if you don't regularly close FS and re-open. I think this is because every time you make a change an undo image is created and, importantly, this is NOT deleted when you do a Save (many other programs don't seem to behave like this). You can undo after a Save so the memory usage will steadily increase as you make changes. This is probably not related to the preset issue.

If I'm wrong I would appreciate being corrected (as always); that's how we all learn!

Cheers

Spogg

KG,
I'v reduced the channels to 8 yesterday, and now using "only" 9 preset managers. 8 for the audio paths and one for the midi path. Also replaced 7 of samplers with 7 wavetable synths. It works fine with a single preset manager but dies when going back to 9. when I export my project as a VSTI, the DAW (studio one3) shows a very reassonable memory useage with 1 preset manager and even with 4. The stand alone version goes as high as 600 mb max, but still crushes with 9 preset managers.
Anyway, may replacing the preset managers with text files give better preformance?

Thanks for the comment, spog. Yes my schematic is huge (as always ), and yes, I do a lot of changes. That might be a cause. 4 of my preset managers do work now inside the DAW, but studio one shows (and controls) only one of them. Maybe completely "hiding" the preset managers from the DAW and keeping it "internal" is better solution (or maybe moving to text files).

How would you "hide" the preset managers though?

Even if you can't see them the plugin and the DAW will be confused. It's just a guess but probably the fully active one is either the first or last one added to the schematic...

However, if you do get it to work the way you want I'll be fascinated to see how you did something you shouldn't be able to

Good luck!

Spogg

well, hiding is not an option, of course. Just a cynical wishful thought

But boy, you was right about that closing\reopening suggestion It realy works. And after rebuilding my rickety trust in FS, I finally seeded the 9 preset managers successfully, so they now work great with studio one (as long as you ignore the fact that the DAW "sees" one of them and use the buttons based preset manager, The same one which I've seeded in your synth a week ago ). Unfortunately, I can't share my schematic here, but I would explain to anyone who is intersted how to do that

Well it's probably no surprise that I'd like to know, in principle at least, what you did and what you mean by "seeded"!

Cheers

Spogg

Just sent you a PM, spogg

Cheers!