labcoats wrote:JAH wrote:labcoats wrote:
And despite the manual saying for fine control of plugin parameters hit shift. Doesnt work at my end. For example take one of the delays and the delay time goes up by multiples of 20ms. this is no use if you need your delay at 229 but can only get either 220 or 240. not really related, but they are related to the Qlinks I guess.
Delays don't necessarily work that way. I took a look at the Ren's stock Delays and Universal Audio's Delays. You can't dial or punch in any number you want. They are fixed at specific increments.
Also the data dial, Qlinks, and your mouse have different resolutions so you won't be able to set certain values depending on what method you are using.
As I said I dont get fine resolution regardless if I use the (shift) mouse or the Q links. Fine resolution is not increments of 20ms. Are you crazy
The Rens effects are the only ones I have which don't allow me fine resolution. I don't have a single other delay effect I cannot increment in 1ms multiples. I'm talking about using those effects inside the Ren. This is coding - nothing more, and I totally expect them to get around to fixing this. Producers have been fine tuning their delays in less than 1ms increments for decades. Wake up man!
You need to wake up, slow down, and read what I wrote.
For example....Universal Audio has a DM-1 Delay Modulation plugin. You can set delay from .14 ms to 125 ms. But you CANNOT set it to every value between these min/max values. The values are set a fixed increments when using your mouse.
Example:
1. Open Pro Tools
2. Insert 'Long Delay II' plugin (stock delay plugin)
3. Open the plugin GUI
4. Use your mouse to set the delay time
Results - You will notice as you use your mouse to drag the slider to adjust this param, you won't be able to choose any value. You will be able to choose 4.26, 8.53, 12.79, etc. Why can't you set it to 4 ms with a mouse? Why not 5 ms with a mouse? If you try to set it to 21ms, the closest you will get is 21.32ms.
Take a look at Maschine. If you use the same UAD delay effect, it won't attempt to display an intuitive value. Instead of displaying values between .14 ms to 125 ms...it simply shows from 0% to 100%. That is 101 values if your are counting. Now how many values can you count between .14 ms to 125 ms noting that there are decimals?
You did get 1 thing correct. It is coding. And I just displayed 3 different products for you to mull over with similar results.
Inputs devices (knobs, data dials, mouse, etc) just don't perform the way you expect them here.