uiSlider Invert Modulator Value From MIDI Value

[lfo2vco]

I have a uiSlider Modulator that sends a 0-127 control, this works fine. However the MIDI message it receives seems to be completely inverted, this sends the dial to the exact opposite position to where it should be.

What would be the best way to correct this, something to do with ‘midiValue’ maybe?

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[atom]

Can you tell me exactly what gets received, paste the data from the MIDI Monitor for 0,32,64,127 values.

[Hecticcc]

I use this for converting to opposite values, works with decimals & hex as input.

function invertNumber(input)

local range = 127
local output = range + (input*-1)

return (output)
end

Then just call it whenever you need it somewhere.

My weekly radioshow @ Belgium's best local radio station - - - - - -
Updates and news about the Emu eos sampler panel

[lfo2vco]

Hi Atom, as requested the data from the MIDI monitor is

7f,5f,3f,00

So the 3P is definitely sending inverted data for this byte.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[atom]

Then in the reverse expression just do 127 – midiValue, you’ll get the reverse values, but i don’t understand how it goes in a normal fashin in the direction of the synth and just the synth replies in an inverted form.

[lfo2vco]

I put “midiValue – 127” in the reverse expression, but still the problem persists.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[atom]

not midiValue – 127 (assuming that the synth sends 23, then the expression will be 23 – 127 = -104)

you want the expression to evaluate to a set of values your modulator has, so it’s 127 – modulator value, when the synth send 127 the expression will be 0, when it send 27 the expression will be 100 and so on.

you need to find the expression that suits your needs.

[lfo2vco]

Syntax and stuff has got the better of me again. I didn’t realise you could put the – in front of the value (because all the examples I’d seen had it behind). But I now understand a little more of the maths the expression is performing.

I have tried 127 – modulatorValue, 127 – midiValue, swapped them around, doubled them, halved them… nothing seems to work.

I also gave Hecticcc’s method a go… no luck

It makes absolutely no sense.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[atom]

Can you send/attach the panel and paste a dump of the data, when twisting the knob from 0 to max. I’ll see what i can do.

[lfo2vco]

Files attached as requested, I appreciate your time and effort Atom.

Attachments:

You must be logged in to view attached files.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[Hecticcc]

The values your device sends are not linear. It sends 1,3,4,6,8… instead of incrementing by 1.

You will need to figure out a formula for it or make a script that translates these values.

My weekly radioshow @ Belgium's best local radio station - - - - - -
Updates and news about the Emu eos sampler panel

[lfo2vco]

Hecticcc wrote:

The values your device sends are not linear. It sends 1,3,4,6,8… instead of incrementing by 1.

You will need to figure out a formula for it or make a script that translates these values.

The values are me twisting the knob as Atom requested. Just like the avatar to the left : )

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[atom]

That’s not an issue i think, a bigger issue is a bug i found yesterday about 2am and i had to delete the nightly build. I’ll try to fix it today and update then.

[Hecticcc]

lfo2vco wrote:

Hecticcc wrote:

The values your device sends are not linear. It sends 1,3,4,6,8… instead of incrementing by 1.

You will need to figure out a formula for it or make a script that translates these values.

The values are me twisting the knob as Atom requested. Just like the avatar to the left : )

Lol, self-facepalm time 😀

My weekly radioshow @ Belgium's best local radio station - - - - - -
Updates and news about the Emu eos sampler panel

[atom]

As far as i can tell you don’t need to do anything, i need to fix my bug and the default expression will work, there is no additional logic needed here. Just give me some time to fix my side.

[lfo2vco]

atom wrote:

As far as i can tell you don’t need to do anything, i need to fix my bug and the default expression will work, there is no additional logic needed here. Just give me some time to fix my side.

Cool, I look forward to giving the new version a go. I’m being dragged away from my synths and computer (kicking & screaming) for a long weekend. I’ll touch base a soon as I get back. Many thanks.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Hi Atom, I downloaded the latest nightly build (Ctrlr_1539.dmg) for Mac OSX and still the inverted modulator persists. Did you have time to try a fix this time around?

I understand you have a life outside Ctrlr, so I’m not hassling you regarding this. Cheers.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[atom]

I haven’t forgot, i found some bugs i generated myself in the latest nightly, i’ll try to fix what i can and post a build in a few hours.

[atom]

One thing i noticed you can’t (shouldnt) use

127 - modulatorValue

in the reverse expression, at least not in your case you should use

127 - midiValue

at the moment of receiving the MIDI message your modulator value can be anything, you are setting it, so setting the new value based on the OLD value is just not a wise thing to do (unless you know what you are doing)

[lfo2vco]

Ooops! good spot, corrected many thanks.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[Author]

Posts