Page 1 of 1

fader scales not equal in lemur and cubase

Posted: 06 Jul 2013 18:33
by ahcvankampen
Hi,
I just noticed that that fader scale in cubase 7.0 (max 6db) does not correspond to the maximum fader scale in Lemur (which is 1). It corresponds to 0.93. Am i missing something here?
antoine

Re: fader scales not equal in lemur and cubase

Posted: 08 Jul 2013 07:17
by Softcore
Not sure what the question is.

The fader of Lemur has an internal range of 0 to 1 which is then translated into midi messages of a range from 0 to 127. After that, the CC midi message with value 0 (Lemur internal 0) is naturally connected to the controlled fader value "minimum" (whatever that is) and then CC midi message with value 127 (Lemur internal value 1) is naturally connected to the controlled fader value "maximum" (whatever that is).

What exactly is not happening from the above?

Re: fader scales not equal in lemur and cubase

Posted: 04 Jan 2015 11:34
by wurlitzer
Hi,
I have the same problem.
I created a fader. If I set the fader value to 0.81 I get 0db in total mix.
Is it possible to set a formula in the value field, so that lemur shows the same value as total mix?

Thank you so much

Re: fader scales not equal in lemur and cubase

Posted: 04 Jan 2015 15:55
by Phil999
it is sometimes not easy to replicate a fader. What I often do is set a value in the DAW (0dB, +6dB, -3dB, -12dB, etc.) and put a small line and value for each at the fader's position in Lemur (the DAW must be able to send data). Then the Lemur fader may not look the same as in the DAW, but the values next to the fader remain correct.

Re: fader scales not equal in lemur and cubase

Posted: 05 Jan 2015 21:09
by Softcore
Sample the dB readout in your software for many "positions" of the fader. For a midi accurate solution, you need to sample 128 values (midi positions of fader 0-127)

Create a vector, lets call it "dbvals" and fill it with the sampled values.

use dbvals[fader.x*amountofsamples] to display as dB readout

Example:
https://forum.liine.net/viewtopic.php?f ... =10#p10643

Re: fader scales not equal in lemur and cubase

Posted: 06 Jan 2015 15:44
by wurlitzer
Softcore wrote:Sample the dB readout in your software for many "positions" of the fader. For a midi accurate solution, you need to sample 128 values (midi positions of fader 0-127)
It seems, there is regimentation in the field lenght for a vector....

Re: fader scales not equal in lemur and cubase

Posted: 08 Jan 2015 08:05
by Softcore
Can you send-post the "sampled" dB values here? Im sure I can come up with a working example! ;)

Re: fader scales not equal in lemur and cubase

Posted: 12 Jun 2017 03:09
by th_ldu
Hi everyone,

it's an old post but I turn it on again.
I looked for a solution to fix the scales of the Lemur's monitors on those of Cubase but it doesn't works. I also try the Softcore's example without success.
The best solution I have found is based on the following equation:
20*(log(x*127/108))*6/3.241
but the result isn't good because the range seems to go from -200dB to +6dB. And Cubase's faders are in a range going from -121dB (-inf) to +6dB.
So if someone (with much more math skill than me) has an idea on how to convert on the right range I would be really thankful.

For information, here are the correspondences of Lemur monitor data from 0 to 1 for the Cubase's fader (dB).
0.00000 = -121 dB (-inf)
0.00787 = -80 dB
0.02362 = -60 dB
0.14175 = -30 dB
0.25197 = -20 dB
0.33858 = -15 dB
0.44882 = -10 dB
0.59055 = -5 dB
0.78740 = 0.0 dB
0.81102 = +1 dB
0.84252 = +2 dB
0.90551 = +4 dB
0.99213 = +6 dB
1.00000 = +6.02 dB