DSP Robotics Support

There are DAWs that are capable of storing preset parameters externally (like reaper), and there are DAWs not able to do that, and you need to save parameters within your plugin. If what you need does not works in reaper, then there is an issue to follow. If you use other DAW - I don't know how it behaves in its native mode. My old DAW did not stored plugin parameters. My old DAW did not even stored the chain of plugins in use.

But there is some work around possible, although it will require a little more skills of you. Your plugin - when it starts - can load its own options (external options file) in which there is a path of last saved preset. Thus - each time when you save the preset - this path would be also stored to that option file (plus - preset file can be automatically copied to some sort of temp folder, so that your plugin has its own backup). But before you do this - find out what is the issue.

1) What DAW you use, so that others can give you advice?
2) Are other plugins saved within that DAW in a way you desire?
3) Are other SM/FS made plugins saving their parameters within your DAW in a way you desire?
(and how it is done - native way or work around like described above?)

Hi !

I use cubase as DAW.

All the other plugins save their parameter when i save and close the session.

I need to add a component for allow save the configuration of the exemple reverb....

It's complicate ?..

I don't use Cubase, so I don't know.

All the other plugins save their parameter when i save and close the session.

That's why I ask whether other plugins made in SM/FS also are saved (parameters) when closing the session. If not - then it is a matter of how the DAW communicates with SM/FS made plugins (limitation of preset related primitives). If yes, then it is a matter of finding out what's missing (some unclear setting in preset related primitives), and others may have a word for you too, because you would be not the only one with this problem.

i think it didnt work right because you added a presetmanager primitive extra which you dont need just add the presetmanager module on the top layer of your app module..

if you like to see the presetmanager in your app you need to set "show in parent" to on (its the symbol with the eye when you select the PM module) and enlarge tha appmodule so that there is enough space to view the presetmanager

then you can use all the PM functionalities like save presets or choose presets.. all this works well in cubase

Hi,


I don't want see preset manager in cubase.


I want simply that my plugin keep the parameter when i save my project cubase and close.

When i open my session i want see the last parameter in the same position.


exemple :

knob led on.

After save project and re open session, the led must to be always ON.


Cubase must keep the last parameter saving.

rustyou wrote:I don't want see preset manager in cubase.
.

That is why NuBeat mentioned the 'eye' symbol on the PreSet manager.

Click on the 'eye' and it will toggle a slash mark. That hides it from view in the main GUI ... but the PM is still active.

Yes, i have undersant but....

I have add the preset manager but when i close the session, the parameter are not keeping....

Why ....?

please test my first example i`ve posted for you and tell me if it is working on your machine, it should do exactly what you want

Oh !!

I'm sorry !! exact, it works !

thank you very much to all !