Melda is not the best example, at least TB plugin presets use a VST2 standard preset format which is the most compatible with hosts, and that shares preset info with the host so when you load one in a track it reports the preset name to the host and in good hosts you can also load the whole plugin list directly (eg in Bitwig they show in the browser, in Kore I can even import presets into Kore's database).andrei.tuduran wrote: Mon Apr 22, 2019 7:02 amBetter email Jeroen. He reads all the emails.Svama wrote: Wed Apr 17, 2019 12:51 pm I think the meters colour is the smallest problem with eq v4.
These are my points:
-a better preset manager. A good example is meldaproduction.
-In- and Outputmetering for better gainstaging and abing.
-External spectrum visualization from any other TB eq v4 instance, including collision detection
Tb eq v4 frequency grid![]()
Melda does nothing of the sort, its presets are completely invisible to hosts, in a proprietary format only Melda plugins can read, and loading presets involves extra clicks.
