true init preset for MPS?
-
ZentralmassivSound ZentralmassivSound https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=344121
- KVRian
- 762 posts since 13 Dec, 2014 from Germany
Hi,
I noticed that when I click the default preset, all areas that were not used before (or disabled, respectively) still have settings that were used in some before used preset. E.g. the default preset uses normal osc mode, and I then switch to harmonics mode, then there are leftover settings, volumes and phases are not initialized.
Same problem if I save the default preset with osc in harmonics mode. If I open it and then switch to normal mode, then there are leftover settings everywhere, the advanced settings, phase/skew/etc, harmonics, transfer shapes etc.
Could you provide a true init preset that resets *all* MPS settings to their default values, including multiparams, modulators, arp?
This also affects e.g. step sequencer values if you make the sequence longer than the default 8 steps, there appears previously used stuff instead of initialized values. And it's like this in many places, where the default preset / default settings does not use every possible range.
Cheers, Thorsten
I noticed that when I click the default preset, all areas that were not used before (or disabled, respectively) still have settings that were used in some before used preset. E.g. the default preset uses normal osc mode, and I then switch to harmonics mode, then there are leftover settings, volumes and phases are not initialized.
Same problem if I save the default preset with osc in harmonics mode. If I open it and then switch to normal mode, then there are leftover settings everywhere, the advanced settings, phase/skew/etc, harmonics, transfer shapes etc.
Could you provide a true init preset that resets *all* MPS settings to their default values, including multiparams, modulators, arp?
This also affects e.g. step sequencer values if you make the sequence longer than the default 8 steps, there appears previously used stuff instead of initialized values. And it's like this in many places, where the default preset / default settings does not use every possible range.
Cheers, Thorsten
- KVRian
- 1094 posts since 23 Sep, 2006
+1
I've asked for this before for effects too.
I've asked for this before for effects too.
- KVRian
- 1059 posts since 28 Jun, 2006 from Germany
Exactly my method, hehe.jmg8 wrote:Yes, I've also asked for this too.
At the moment I open a new instance of the plugin to get to a default state.
System: Win 10 64 bit / i9 9900K (8x 3.6 GHz) / 16 GB DDR4-3200 RAM / 1TB M.2 SSD + 2x 500 GB SSD / RME Babyface / Reaper
Tagirijus.de
Tagirijus.de
-
ZentralmassivSound ZentralmassivSound https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=344121
- KVRian
- Topic Starter
- 762 posts since 13 Dec, 2014 from Germany
Ah... so it could also be an init button that every plugin should have.
I'll try the new instance, though that is a little odd workflow.
I'll try the new instance, though that is a little odd workflow.
- KVRian
- 1059 posts since 28 Jun, 2006 from Germany
Cool idea: init button!
System: Win 10 64 bit / i9 9900K (8x 3.6 GHz) / 16 GB DDR4-3200 RAM / 1TB M.2 SSD + 2x 500 GB SSD / RME Babyface / Reaper
Tagirijus.de
Tagirijus.de
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Well, it's not that simple actually
. The problem is performance - the plugins, especially the huge ones such as MPowerSynth, contain so many features, that storing all of them would make the presets huge and the storing itself would take a lot of time. So the system basically stores only those that are actually used to speed things up and makes them smaller. Then there's backward comptibility stuff...
So, for now, I'm afraid using a new instance is the way to go
.
So, for now, I'm afraid using a new instance is the way to go
