Should the channel mode button be able to be saved with the preset?
- KVRian
- Topic Starter
- 670 posts since 7 May, 2002 from Phoenix, Arizona, USA
11.08
For example in MDynamicEQ I set the channel mode to M+S. Save preset. The plugin remains in M+S mode even when selecting other presets that are meant to be L+R. Manually switching back to L+R, then recalling my preset meant to M+S, the plugin remains in L+R.
The host (Reaper) does save the channel mode state in its own preset saving function, and also upon reloading the project.
Thanks for checking it out.
For example in MDynamicEQ I set the channel mode to M+S. Save preset. The plugin remains in M+S mode even when selecting other presets that are meant to be L+R. Manually switching back to L+R, then recalling my preset meant to M+S, the plugin remains in L+R.
The host (Reaper) does save the channel mode state in its own preset saving function, and also upon reloading the project.
Thanks for checking it out.
-
- KVRAF
- 10310 posts since 2 Sep, 2003 from Surrey, UK
Confirmed (using MEqualizer, picked at random); also applies to Oversampling, Limiter etc
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14019 posts since 15 Mar, 2008 from Czech republic
Well, that's just how it is, the decision has been made a long time ago. Think about it this way - in most effects you just don't know how the users will be using it. They may want to process LR, or MS or anything... and by loading presets you would kill their settings. It would be even more crazy with upsampling... To do what you want however you can use the presets in your host, host will save everything.
-
- KVRAF
- 10310 posts since 2 Sep, 2003 from Surrey, UK
Hmm, I don't see it quite like that - if I create a preset specifically intended for MS processing, then when I load it again on another project I would expect it to process MS again (having said that the preset name would probably include "_MS").
But, following your viewpoint, for consistency, those values should not be passed to the host either to save in a host preset.
But, following your viewpoint, for consistency, those values should not be passed to the host either to save in a host preset.
- KVRian
- Topic Starter
- 670 posts since 7 May, 2002 from Phoenix, Arizona, USA
Ah ok, now I see how not saving the state in the preset is appropriate particularly for plugins other than eqs. For eqs, if the _per band_ channel mode parameter included the options of L or R _and_ M or S, that could satisfy the issue. Currently the per band channel mode options allow for L/R _or_ M/S, depending on the plugins global channel mode.
I understand there are more interesting/important things to work on, so I can deal with the "work around" now that I know what's happening.
I understand there are more interesting/important things to work on, so I can deal with the "work around" now that I know what's happening.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14019 posts since 15 Mar, 2008 from Czech republic
DarkStar, that's a very specific case, while in most cases it is the other way around. Anyways backwards compatibility forbids changing it.