Couple questions

Official support for: bigtickaudio.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hello,

i was wondering if there's a way to modify on the fly adsr values for the sound i'm playing, without changing envelope to every oscillator. I mostly find this feature a few other synths/romplers have very handy when browsing lot of patches which have a different attack than i would like. As example, lot of presets, both native or third parties have long attack values, which i would like to change fastly when browsing.

Is this possible in any way? Also is there any chance to lock something (keep values stable) while browsing?

Thanks in advance
Luca
Dream Audio Tools - Sample libraries http://www.dreamaudiotools.com
Archisounds - Music Website http://www.archisounds.net

Post

The ADSR values in the envelope box are global; they effect every envelope by a different ratio depending on what each individual evelope value (time) is. However, each envelope (volume, pitch, filter, phase, WS,...) has an independent "Amount" value. If that value is set to "0", changing the ADSR values will have no effect; this is handy for not changing the Global Pitch rate often used for vibrato. Any Amount value in between 99-1 could be though of as a percentage; a setting of 50 would mean that envelope will change 50% of one set at 100.

In practical terms: set the Amount value to "0" to prevent an envelope from changing. To make a quick compress/expand slider find a User Slider that you'd like to use and clear it. Then R-click on the slider so the matrix appears. Assign the parameter General > Attack to the first slot, General > Decay to the second slot and General > Release to the third slot; "OK". Name the Slide someting like "ADR Time" and have fun.

If you stretch the affected envelopes by 200% then a slider setting of "50" should give you your origional values and you can stretch or shrink at will. Okay, so the slider set to "0" gives you too quick an attack? R-click on the slider to open the matrix and set the Min Value to maybe "15" so there is a subtle attack (providing there was already an attack programmed). The sound was percussive and you want to add an attack? You will have to move the envelope point beyond a time value beyond 0.00 to hear a change. If you move the point to 4.50 the your assigned slider setting is "100" (if 100 is the max value assigned in the matrix) will give you 4.50 and a slider value of "0" (if 0 is the min value assigned in the matrix)should give you the original percussive attack.

Just a few minutes of experimenting and it is easy to figure out.

I'm not sure what you mean by keeping values stable while browsing...?

Post

Thanks a lot Daniel for the detailed explaination. I tried assigning attack to an user slider and it does the trick very well. My only problem is that this setting gets lost when i change patch, so, unless i find a way to lock the slider (see have it automatically assigned to attack, always) its a bit of a long process when i just want to browse between patches and just see how changing attacks and releases (mostly) affects the result. Is there any way to apply that lock?

thats what i mostly mean for locking feature, the ability to keep an assigment (as example) or an effect while browsing patches.

Thanks again
Luca
Dream Audio Tools - Sample libraries http://www.dreamaudiotools.com
Archisounds - Music Website http://www.archisounds.net

Post

Actually that could be a really cool feature - to be able to save slider settings separately from a patch. I know they might not be totally relevant to a different patch, but that's how happy accidents happen, yes?
Is there some clever way of using the text export/import feature to achieve this? (Daniel, you're the expert at this sort of stuff) Or is it something you've considered, Tick?
Thanks for the latest update, btw. Rhino continues to amaze...
Hear my music |
myLatestAlbum
so do I neither

Post

Folks,

Maybe it's the right time and place for me to explain something about Rhino parameters: not all of them are created equal ! Some of them are regular vst parameters, that can be automated by the host, but others are not. Examples of the latter are individual envelope segment data, tuning scale, waveshaping curves, filter and effect types, ... Fortunately, the *global* attack/decay/sustain/release parameters are regular VST parameters, which means that they can be assigned to a user slider, but also, to an external midi controller, and at the moment I think this would be your best option: just program 4 knobs on your midi controller to control the global A/D/S/R, and this will be locked across presets!

What you are going to find, though, is that most current presets don't react too well to global A/D/S/R - simply because they were designed before this feature was implemented. As Daniel described, it is not too hard to tweak a preset to respond to A/D/S/R in a musical way, but we didn't go back and fix all 1000 of them. Maybe we will, but it might take ages.

About happy accidents - I guess what you want is a randomizer. This could be an interesting feature for 2.07. Damn... I need more time to work on new stuff :)

'Tick

Post

Big Tick wrote: ... About happy accidents - I guess what you want is a randomizer. This could be an interesting feature for 2.07. Damn... I need more time to work on new stuff :) ...

'Tick
that would be ver' nice to have ...

in the mean time , though , rhino responds to the randomiser in 'minihost' , and i would assume
in something like 'chainer' , as well ...

lower values seem to work more , errmm ... musically ...


and , thanks , for the update ...
Image

Post

Thanks for the explanation, 'Tick. A randomizer would indeed be cool. In the meantime, is there an easy way to work out which parameters are automatable by assigning MIDI knobs (or automation envelopes/curves etc), and which require Rhino's own sliders? Aside from the ones you just mentioned, of course ;)
Hear my music |
myLatestAlbum
so do I neither

Post

+1 For a 'Randomizer'.
'Fastest Filter in the West'

Post

mikusan wrote:Thanks for the explanation, 'Tick. A randomizer would indeed be cool. In the meantime, is there an easy way to work out which parameters are automatable by assigning MIDI knobs (or automation envelopes/curves etc), and which require Rhino's own sliders? Aside from the ones you just mentioned, of course ;)
These parameters are:
- the 6 user sliders
- and the parameters than can be assigned to them

You can see a complete list of the latter in the user slider editor popup window (right-click on any user slider).

'Tick

Post

Thanks for the info - that's given me some real food for thought (strokes chin and gazes off into space...)
:)
Hear my music |
myLatestAlbum
so do I neither

Post Reply

Return to “Big Tick”