[joma]

Hi have the same issue here!

Under Xp/32bits, i get the message: “The procedure entry point GetFinalPathNameByHandleW could not be located in dynamic link library Kernell32.dll

Came back to 5.3.159 wich launches fine!

[joma]

Hi,

Does any one have that K3Editor.bpanelz file somewhere?
I could not find it following the link given by Bomma72.
It will be nice to not start working from zero!

Thanks

[joma]

Hello Widdly,

I’m actually re-working your shruti panelz to suit my needs (on ctrlr rev 1655)!

it’s coming a bit late but for info.
I found that a controller is able to send correctly negative NRPN values if in the field “Expression to evaluate when calculating midi message value from modulator” we put the the following line:

gte (modulatorValue, 0, modulatorValue, 256 + modulatorValue)

bye

[joma]

Thanks Atom for your reply,

Not sure that we are writing about the same subject! Sorry, up to now i was not very clear and introduced a lot of confusion by writing wrong information! Even the the title of the topic is not well chosen!

In fact, Relative (+inc/dec vst param) or absolute is the reaper part of the story (the learn input from a midi controller) nothing to do with Ctrlr!

So Let’s try to be clear!

In fact, the input which gives me problems is not a midi input but the “vst parameters input”
As you now, Ctrlr offers (as every vst(i)) to the host(DAW) an access to his controllers/parameters. And if i’m right the range of these parameters is 0.00-1.00 (Vst sdk definition).

So About the amount of values in a Ctrl’s component, it seems that it can not be less than 54 if i want the parameter to be “vst controllable” by the host:

– On a uiSlider, we can set the minimum and maximum value and the Interval. So i tried to change the interval to 0.5 (instead of 1) to double the amount of values. But it had no effect. For now i have to use a min-max value range greater than 54 (eg: min 20-max 74).

– On a uiCombo as i wrote before the amount of values/lines in the “combo content” should be greater than 54!

[joma]

Hello Atom,

In fact, it seems that the midi input that CTRLR has which receives midi from the host (when ctrlr is used as a vst) is mapping the received cc window of 0-127 to a minimum of 56 (127 :2) modulator values or indexes.
if previously i have seen a limit of 13, it was because my midi controller was sending increments of 5 values (127/5 :2= 13).

So the effect of using less than 56 values in a modulator, is that the modulator doesn’t reply at all to midi input ccs coming from the host!

For now, i can work with the workaround mentioned previously, but it is not ideal!
it will be better if these limit of 56 is diminished to 2!
So if you have an occasion too look at these issue, it will be nice

Thanks and best regards

PS: In the coming days, i will try to make a small video to show a way of using CTRLR that you may not have thinked before 😉

[joma]

Hello,
the workaround i found for that is to double or triple the lines in the content box to get a least 13 lines:

for example:

LPF=0
BPF=1
HPF-2

will be replaced by:
LPF=0
LPF=0
LPF=0
LPF=0
BPF=1
BPF=1
BPF=1
BPF=1
HPF-2
HPF-2
HPF-2
HPF-2

[Author]

Posts