Waveform Pro just sprung a control surface mapping problem

[nealdc]

My Waveform Pro 13.5.8 has just developed a MIDI controller mapping/learn problem that I'm hoping someone can help with:

• Selecting Edit Control Mappings... for the controller (let's say it's a MidiMIX) works fine. Twiddle a pot, pick the parameter and it takes.

• Selecting the Automation menu, then Create Midi Controller Mappings... also works fine. Click on Click here to choose a controller, twiddle the pot and it takes.

• However... if I load pretty much any plugin (eg. Waveform basic Chorus) then try midi learn, as soon as I move the plugin parameter the midi learn window immediately says "Assignment made" without me having touched a control surface pot. Then Waveform no longer responds and the parameter itself starts to flicker as if it's being repeatedly moved from 0 to 127 and back very quickly.

One time I happened to try this with a parameter that was already assigned to a Mackie MCU fader. The fader started flicking between full off and full on and I had to force the Waveform window shut to get it back under control.

• Midi controller assignments all seemed to work fine up until a week or so ago.

• I have tried reinstalling Waveform. Same problem.

• I have tried the same with an MPD218. Same problem.

• I have checked the midi traffic using midiview - all looks good.

I am wondering if there is some sort of setting I have made which is maybe telling Waveform to interpret controller pot movements as either full on or full off, with nothing in between, and then Waveform is having to spend ages responding to all the possible values between 0 & 127.

Any ideas most welcome. Difficult second album being made even more difficult...