AU parameter entry problem in Live

[olilarkin]

I have noticed that if you try to type values into ableton live's default parameter display for an AU iplug plugin, the value isn't set correctly. It works if you bring up the cocoa AU editor window and type it in. It seems OK in Logic's default gui, and you don't seem to be able to enter values for aus in reaper's display so i cant test there. It works in live if you drag the slider, only when you type is it a problem. Other non iplug aus are OK.

see attached.

the problem seems to be down to IPlugAU::IPlugAUEntry(). I think IPlugAU::SetParamProc() gets called from here but the value of the parameter is lost.

anyone got any ideas how to fix this?

I tried stepping through many times with the debugger, but still couldn't work it out!

thanks,

oli

[gwok]

dont know if this is relevant, though maybe it has something to do with having to create the options.text file with the
-ensurekeymessagesforplugins - message in the ableton appdata folder - or somewhere...

http://www.ableton.com/pages/faq/options_text

you prolly know bout all that anyway, though might help

[Tale]

Well spotted! The problem lies in IPlugAU::GetProperty(), case kAudioUnitProperty_ParameterValueFromString:

int v;
if (pParam->MapDisplayText(cStr.mCStr, &v)) {
pVFS->outValue = (AudioUnitParameterValue) v;
}

MapDisplayText() can only be used on parameters that actually have display texts. If you replace the code with the following code it should work:

if (pParam->GetNDisplayTexts())
{
int v;
if (pParam->MapDisplayText(cStr.mCStr, &v))
pVFS->outValue = (AudioUnitParameterValue) v;
}
else
{
double v = atof(cStr.mCStr);
if (pParam->DisplayIsNegated()) v = -v;
pVFS->outValue = (AudioUnitParameterValue) v;
}

EDIT: Although the above fix does work, it still goes wrong with some parameters / parameter types. I will have to investigate this some more another day.

[RRokkenAudio]

You guys putting these on the GIT? I haven't checked recently.

~RR.

[Tale]

I have been updating my Git repository almost weekly, so yeah, once I have properly fixed this I will.

[RRokkenAudio]

ahh!! Thanks guys, I appreciate your work. Wish I could contrib but well, you know the story ;)

~Rob.

[Tale]

I have updated my Git repository (http://www.taletn.com/WDL.git) with the above fix. I have also added support for generic UI text input for VST plug-ins using the effString2Parameter opcode.


EDIT: Although the above fix does work, it still goes wrong with some parameters / parameter types. I will have to investigate this some more another day.
Actually what still went wrong is related to this thread. I haven't fixed this (in fact I'm not yet sure if it needs fixing).

[olilarkin]

generic UI text input for VST plug-ins using the effString2Parameter opcode.

so does this mean that you can type the actual value you want instead of a value between 0.-1.?

oli

[Tale]

so does this mean that you can type the actual value you want instead of a value between 0.-1.?
Yes, it does.