All the new preset functions in 9.6 are great, especially local/portable VST3 presets. Making presets easier to handle, lets you appreciate the wonderful world of all the presets in the world.
One thing that VstHost does, that would be a great function in MuLab, is when you save a preset in VstHost, its pre-inserts a standardized name for you. It will first list the Vst name "BabylonEx", and then the preset name "BA Sine x Sine 10", for "BabylonEx - BA Sine x Sine 10.fxp". Listing the Vst makes it easier to know what preset goes to what Vst in the folder, if you have multiple Vst's in a root folder, and pre-inserting an available name expedites 2-3 small steps to either copy and paste a name or typing one out.
I think it would add to the already excellent workflow in using MuLab.
One thing that VstHost does, that would be a great function in MuLab, is when you save a preset in VstHost, its pre-inserts a standardized name for you. It will first list the Vst name "BabylonEx", and then the preset name "BA Sine x Sine 10", for "BabylonEx - BA Sine x Sine 10.fxp". Listing the Vst makes it easier to know what preset goes to what Vst in the folder, if you have multiple Vst's in a root folder, and pre-inserting an available name expedites 2-3 small steps to either copy and paste a name or typing one out.
I think it would add to the already excellent workflow in using MuLab.
Statistics: Posted by TorresBob88 — Mon Jul 15, 2024 7:34 am