Quote:
Originally Posted by fundorin
To get rid of the unneeded parameters? But, instead of completely ditching them, just move them to last assign pages, while mapping the important ones to the first pages?
|
Oh, just arrange them any way you like, in your use case, put unused ones last.
Then, you can just comment out any lines you don't want read.
Quote:
Originally Posted by fundorin
As for "separate vs single" mapping files format: in the world of plugins, there's .fxp (for single preset) and .fxb (for banks)
|
Yeah, had a look at those file formats, they're binary, we definitely won't be doing anything like that
Quote:
Originally Posted by fundorin
anyone can create either a whole pack of presets (maps) in one file or make them available as separate files, for convenience. They can live happily side by side.
|
That's actually an argument for one monolithic file, for a very simple reason:
What happens if there is an fxp definition for a plugin and a conflicting one in an fxb file, who wins ?
That issue could be solved by adding the ability to load configurations, but then you have a more complicated system, is the extra flexibility too costly in terms of easy human understanding ??
Quote:
Originally Posted by fundorin
P.S. Yesterday I accidentally stumbled upon a plugin that uses the .xml format to store its presets. Never seen this approach before.
The plugin is from DiscoDSP - Corona. https://i.imgur.com/oa7FXMk.png
At the same time, DiscoDSP Discovery Pro uses regular .fxb for storing banks and .xml for parameters, layers and zones. |
Had a look at that link, seems like a really good argument for having one monolithic file, uggghhh what a mess