Zebra automation parameter names

[Mans]

Hi Urs,

The way the automation parameters are exposed to Renoise is not very convenient. I've attached a picture. It would really be an improvement if the names could be "module: parameter" instead of just "parameter". So you'd get "ENV1: Sustain" and "ENV2: Sustain".

[Goratrix]

agree, it would be great to have the parameters named more clearly.

Fabfilter Twin 2 example:

[Urs]

Infrastructure is already there... just gotta add a tiny bit of code, and a text file.

RTAS version btw. does this already, but for I had to cut down the length of the parameter names dramatically.

[Mans]

Great!

[fas1piano]

that would be VERY cool, yes!

[red37]

Yes please!!!

[phlake]

MFM does this same kind of thing; hopefully your fix is easy to share between projects?

[phlake]

Any news on this issue? Was this addressed in Zebra 2.5? Will there be an update to MFM2?

[Urs]

Any news on this issue? Was this addressed in Zebra 2.5?

There should be a file "com.u-he.Zebra2.publicparams.txt" and one with an "xt" before .txt. The one with xt has a Module:Param naming scheme.

Rename com.u-he.Zebra2.publicparams.txt
to com.u-he.Zebra2.publicparams.txt.bak

Rename com.u-he.Zebra2.publicparams.xt.txt
to com.u-he.Zebra2.publicparams.txt

Let me know what you think... I mean, it's still going to be cryptic due to various restrictions of maximum lenth of parameter names. I guess I'll have to go VST3 for a massively improved situation...

Will there be an update to MFM2?

Yes, but it's a bit more complicated there as MFM isn't built as modular as Zebra. I have to see how far I can go with it in respect of parameter naming.

[phlake]

Okay. Thanks, Urs.