Forum Replies Created
-
Thank you Simon and Tom. I look forward to the growth of this community and the sharing of knowledge.
Welcome to the forum and sorry for the registration hassle which we finally resolved it seems.
If it’s not a tempo-synced delay it would be better to use the DAHDSR envelope assigned to keygroup gain and set the initial delay as needed.
Your welcome Mr. ScreenDream I think the uneditablity is intentional…possibly?
Yes, actually I should add a note about this in the FAQ section. Right now there is a small time span where users can edit their posts, after that editing is disabled. We might change this in the future though or increase the time span (I can’t remember how long it is atm).
Just set the key follow parameter for pitch to zero. 100% = chromatic tuning.
Let’s see how it evolves over the next few weeks, after one year of one-Flacon-thread-does-it-all-on-KVR I enjoy having dedicated forums even if they are still mostly empty now.
For the coarse tune, you can use the Pitch knob instead. Regarding start slice, you indeed need to patch the sample multiple time.
Great to see you here, Olivier – so we do have some (unofficial) UVI support after all – yipieee 🙂
That’s the reason why only a small selection of effects is available on keygroup level. But things like e.g. the waveshaper sound very different when applied per note or for the sum, so I often use that on keygroup level and also add polyphonic modulation to it.
I just checked again, a multi envelope in legato mode assigned to grain position does what you’re asking for, but your initial request to actually switch between different samples would require them to be triggered by the same key, so it’s somewhat a contradiction. You can play the same sample in legato mode so that it will only re-trigger when playing non-legato.
Why don’t you just map the sample to the same key in two keygroups, assign the modulation wheel or even a Macro switch to osc gain, one of them inverted and then use the wheel/switch/controller to crossfade/switch between the two. Using non-retriggering LFOs or multi envelopes assigned to grain position in the granular oscillator is the closest to what you want to achieve but once triggered they never reset until the release phase of the ADSR is over.
- This reply was modified 7 years, 7 months ago by Sampleconstruct.
Related to this topic is a tutorial about individual editing/tuning of oscillators within a keygroup.
Tutorial – Independent Oscillator Tuning Inside One Keygroup
- This reply was modified 7 years, 7 months ago by Sampleconstruct.
Well if it’s a dummy keygroup or a dummy oscillator doesn’t matter, same principle.
If you want to upload/share stuff, please use your own server/webspace/whatever for it, we don’t want to supply a database for user content, otherwise my server will get bloated over the next few years. The options are plenty nowadays.
- This reply was modified 7 years, 7 months ago by Sampleconstruct.
So I took this a step further. I wanted to accomplish this across layers. I do not know how to share modulators across layers (yet) so I used the example above to create a second layer set up as the first. I then created an aux on the program level with my desired effect and set it 100 wet. I then assigned the retrigering envelopes I had set up within the layers (multi envelope in this case) to the slider of the “send to aux 1” by right clicking the slider. Again, edit modulation, invert, set legato. like most things in Falcon, I’m sure there are other ways to accomplish this and this technique probably has further implications here in sound design.
Well if you put the ADSR/multi envelope on program level, you can share it between layers.
I thought you wanted to save single oscillator templates, you can do that. You can’t save kegroups. As I don’t know what you’re trying to achieve, you asked for copying oscillators from one keygroup to another and I gave the answer. Save the osc, in the the target keygroup either duplicate the existing osc or add a new one and in that new one just load the oscillator preset you saved before.
Well, once you get used to the hierarchy you know what is possible and what isn’t so it becomes a non-issue.
And don’t forget to unlock the oscillators if you want to edit them individually.
Oh interesting. I had never done it that way. I would just drag an oscillator over the keyboard, and then do it again – which creates two keygroups. I guess mono means it can only play one keygroup at a time… but multiple oscillators are allowed in a single keygroup as you pointed out. Thanks! So, let’s say I have two keygroups, and I want to move an oscillator from one keygroup into another. Is that possible? Tree view shows the oscillators, but doesn’t have any cut / paste functions, or drag and drop. List view has cut / paste, but doesn’t show the oscillators.
Save the oscillator into your user library and then select it in the other keygroup -> create node -> choose anything -> then access your user library.
One can only move keygroups to a new layer in the keygroup editor or copy/duplicate oscillators inside a keygroup via alt+drag.
It works, here is a quick and dirty test patch, when you release the key, the wet parameter of the dual delay quickly fades in, when you play, the signal is dry.
http://falcontinuum.com/wp-content/uploads/2016/09/Delay-Gater.uvip_.zip
Actually I was writing nonsense, for test purposes I just setup a patch with 2 oscillators in one keygroup in a layer which is set to Mono Retrigger and both oscillators play just fine.
Here is a quick and dirty test video using 3 oscillators in one keygroup in a Mono Retrigger layer, so it works just fine.
Actually I was writing nonsense, for test purposes I just setup a patch with 2 oscillators in one keygroup in a layer which is set to Mono Retrigger and both oscillators play just fine.