Fake VS Real Value Parameters


(RANSOM) #1

As previously was mentioned (and finally approved) by devs, native compressors have “fake” parameter values compared to all other free or paid VST compressors and this thing confused a lot of people.

The same thing i see with doofers now. I made a simple doofer for cutting low and high freqs, but if you look at the screenshot u’ll see that “subcut” value (11.3? wtf is this suppose to mean?) in doofer have nothing to do what values displayed in hp filter (0.15khz which stands for 150hz)…and the same thing goes with the hicut.

5322 Screen Shot 2014-10-20 at 13.59.08 (2).png

I see no reason for that doofer/container thing then, if i need to open/maximize devices to see REAL values of filters/delays/whatever and fix them inside.

This thing somehow needs to be fixed, done proper.


Why Renoise decided to be less powerful than it can be?
List of feature suggestions for Renoise
(Denim) #2

1+
I find this annoying as well, would be great to have real values showing in the doofers.


(ballacr75) #3

I think that the problem is that with a single rotary of doofer you can modulate more than one parameter,… in this case what show?


(RANSOM) #4

I think that the problem is that with a single rotary of doofer you can modulate more than one parameter,… in this case what show?

different values for different parameters (frequencies, percentage), this solution need small amount of doofer gui alternation.


(Zer0 Fly) #5

To build it right up from the ground: renoise could need to get “special handling” of certain parameter types in general, enabling users to act more directed expecially when automating parameters. I talk of special modes for things like amplification, frequencies, delay values, note ranges and such. Together with more predictable (or documented at least) range mappings (now I just see linear, and uncertain exponetial range mappings, only way to be sure is to use formula device & map it yourself). DSP would need to react precisely to those special parameters, right now many things seem hit & miss somehow, or need to be extracted by scripts to get precise values. For external plugins maybe a tool to define such parameter ranges correctly, maybe with manual work that would need to be done once per parameter.

The hydra/doofer/etc stuff could then just use parameter description of a chosen linked parameter, maybe even passing through chains.

If this happened, we could finally launch laser guided missiles instead of raw shotgun ammunition with a single bullet that never hits where you’d expect it to.


(RANSOM) #6

To build it right up from the ground: renoise could need to get “special handling” of certain parameter types in general, enabling users to act more directed expecially when automating parameters. I talk of special modes for things like amplification, frequencies, delay values, note ranges and such. Together with more predictable (or documented at least) range mappings (now I just see linear, and uncertain exponetial range mappings, only way to be sure is to use formula device & map it yourself). DSP would need to react precisely to those special parameters, right now many things seem hit & miss somehow, or need to be extracted by scripts to get precise values. For external plugins maybe a tool to define such parameter ranges correctly, maybe with manual work that would need to be done once per parameter.

The hydra/doofer/etc stuff could then just use parameter description of a chosen linked parameter, maybe even passing through chains.

If this happened, we could finally launch laser guided missiles instead of raw shotgun ammunition with a single bullet that never hits where you’d expect it to.

Lol, absolutely indeed. WE WANT REAL VALUES!


(danoise) #7

REAL VALUES!

It could be done when you are mapping to a single parameter, but how do you then represent a knob which has been assigned to two different parameters?

The Lua API has two functions which allow you to translate a value into a string and vice versa, maybe this is the way to go?

So, assigning to single parameter could perhaps create those functions for you automatically,but you would be able to modify them as you desire… I’m thinking about a knob that goes all the way to 11 :badteeth:


(ffx) #8

Hey atarix your color scheme looks quite good, can I have it?


(RANSOM) #9

Hey atarix your color scheme looks quite good, can I have it?

http://forum.renoise.com/index.php/files/file/73-live9-atarix/


(Zer0 Fly) #10

It’s not just about displaying “real values”, what I mean is about how those different types of values are handled. Like, say, make an lfo of value range +/- 1.0, reroute via a log frequency mapper, and have a filter cutoff exactly cyle +/- one octave around a frequency, that might be given as frequency parameter, or as a note value (and that maybe makes a keytracker happy). And for a doofer that controls params, choose from a list of options of representation given by one of the linked params or defined yourself. This.

Hey, those 4 fancy curved mappings in the meta devices, I mean linear is obvious, but is there anywhere a description of the real formulas that are used to remap the linear values?