MSF doesn't send preset name to DAW - getProgramName()

[astey]

Hi Meldaproduction,

I just bought Msoundfactory
and wonder now, if its possible to implement the exchange of preset names with the DAW: getProgramName().
Why is this beneficial?:
-Presets can be called fully by the DAW
-Preset names are visible inside the DAW
-Presets can be imported way faster into the DAW preset browser
-Preset browser is synched with current vst preset

However MSF doesn't transmit the preset name nor does it transmit when a preset changes.
getProgramName() becomes even more interesting as soon as new preset packs are released and user want to import them into there existing patch library.

Just some random examples of vsti which support names:
Xfer Serum
Native instruments Massive
FXpansion Strobe2, Cypher



Personal background:
I use Akai VIP to manage all my patches. VIP is the equivalent to Native Instruments Kontrol software.
VIP can import patches easily and fast, if the vst provides the patch names. Just load the next Preset and VIP fetches all necessary parameters including the name and store them.


Here is a quote of the developer of Zen, who is working for Akai now. This is how I got this request:

Thanks. I'm the crazy one I'm afraid. But I never understood why developers who couldn't be arsed to implement things like getProgramName(), that have been in the VST standard since 1999, would all of a sudden flock to support NKS.

I hope you can implement getProgramName() into MSF

kind regards

[MeldaProduction]

Hi, I'm afraid this won't happen, simply because we don't use the primitive ancient preset handling these synths are using. Basically there needs to be a predefined nonhierarchical list of predefined maximum number of presets. We use a tree of presets and currently there's over thousands of them, then there's the hierarchical system of instruments, which also have their presets,... At the end this is impossible I'm afraid, sorry.

[MeldaProduction]

For the record, we could certainly return a preset name, but that would be pointless without the preset index wouldn't it?

[astey]

I believe this would be a big improvement!
Other synth, such as massive and cypher2, don’t use midi „program change“ either and they work really well.
They don't use these banks with 127 slots like sylenth1 or reveal spire.

Other examples:
- Kilohearts phase plant transmits names as well
- Kontakt 6 transmits the preset name to the host of the instrument loaded into the first position.

I’m not a programmer unfortunately, so i can just give you examples where it works.

[Big Tick]

If you support getProgramName() to return the name of the current preset (no need for indexing) and send updateDisplay() when a new preset is loaded, then VIP can automatically import new presets as you browse through them.

[MeldaProduction]

Okey dokey !

[astey]

If you support getProgramName() to return the name of the current preset (no need for indexing) and send updateDisplay() when a new preset is loaded, then VIP can automatically import new presets as you browse through them.

Thanks MeldaProduction!
Thanks Big Tick!

[MeldaProduction]

[astey]

Works beautifully!

One question & improvement: would it be possible to transmit the preset name only?
Right now a string is transmitted with this pattern: "folder~subfolder~presetname"

The folder names aren't necessary and are applied by using tags within preset manager/daws.
The preset name alone would be perfect.
Additionaly, the strings are too long and get cut off, so I see the folder names, but just some letters of the preset name.

Cheers

[MeldaProduction]

Aaaaha, ok!