scriptingchagzuki wrote: Sun Dec 27, 2020 4:39 pm I'm wondering how I can emulate something like the random cycle / cycle modes that one has within a keygroup either at layer or program level, i.e. for each note to trigger either a different keygroup or layer.
UVI Falcon - v4 = 2026 released - rumors, ads, praise, kindergarden, auto-sampling and off-topic inside!
-
- KVRAF
- 2481 posts since 28 Mar, 2005
-
- KVRAF
- 2481 posts since 28 Mar, 2005
use the double click browser, not the tree view one as in that case, rationale is that sample are to be loaded inside keygroupsKraznet wrote: Sun Dec 27, 2020 5:02 pm I sent a query to UVI support but I thought I would ask here as well. When auditioning loops in the browser, in my case World Suite 2 percussion loops, there doesn't seem to be away to preview the loop at the bpm tempo of the DAW. In order to hear the loop in context you have to first drag it into an instrument slot in order to hear it at the correct tempo which isn't very intuitive.For example I use Spectrasonics Stylus RMX and you can quickly audition loops during playback and they will sync automatically and once you've found a suitable loop you can drag it into a instrument slot.I've researched this subject and haven't found any info about this so far. So I'm presuming it's not possible. I'm sure not the only one who wants to quickly audition loops at the hosts tempo?
-
- KVRAF
- 3399 posts since 26 Mar, 2002 from london
Another forum member messaged me to recommend using layer rules, which I did and it achieved just what I had in mind; very handy indeed.otristan wrote: Mon Jan 04, 2021 9:14 amscriptingchagzuki wrote: Sun Dec 27, 2020 4:39 pm I'm wondering how I can emulate something like the random cycle / cycle modes that one has within a keygroup either at layer or program level, i.e. for each note to trigger either a different keygroup or layer.
Every day takes figuring out all over again how to f#ckin’ live.
-
- KVRAF
- 2623 posts since 20 Oct, 2014
Hi,
I would like to request a bunch of improvements to the Falcon's filter modules. And more actual filter algorithms! Before you tell me, that there are already plenty of it inside Falcon, yes this is true. But there are not a lot filter type/coloration variants inside. For instance I am trying to build a bunch real style-conform synthwave basses in Falcon. The results are quite good, but still not as a Jupiter or Prophet sounding and near to "yes, that's it!". I am trying then to "fix/workaround" the result with a keyfollowing digital EQ, but I think that won't fix the issue really.
For example, if you look at Zebra, which filters sound quite a bunch better to my ears, or better say the coloration range suits a lot of needs much better, you will have also filters with multiple resonance spikes and so, plus a Diva filter, if you go with Dark Zebra. I wish there were a lot more color variants for the LP filter in Falcon. It's not enough to have LP12,LP24,LP36 etc.
The analog filter module could get those filter variants. Currently it is too basic, at least for my taste. Normally there are plenty of analog filter types and orders, too. This seems to be a "general LP18 or something analog filter".
Also repeating the same filter with same modulation isn't a good approach in workflow either. It will lead it a lot of multiple work and is poorly managable. The filter itself should provide such a order parameter. E.g. three parameters, algorithm, type, order.
Then I observed some detail, which might be Falcon (architecture) specific: Shouldn't a keygroup filter's keyfollow also respect the coarse tune of each single oscillator? Or at least optional? Is the filter applied to the sum of all oscs, or on each osc individually?
Could you rethink this a bit maybe?
Also regarding the drunk modulator, it seems to me that it lacks of some important parameters, e.g. the "maximum range".
A general graphical visualization of any modulation value would help a lot, too! Some kind of X/Y plotter or so.
Thanks a lot for consideration! Falcon really is a lot fun to use, I love it.
P.S.
- The digital filter's gain should be usable for any filter type, also LP. So you can align the output volume with other parallel filters better. Since it is much louder than the other filter modules. Maybe all filters could have a gain parameter?
- You know what is coming now: Please add undo/redo :=)
- Panning per keygroup
- I want to copy/paste/duplicate a layer in the tree view!
- I would like to be able to drag FXs from the keygroup to the layer (and vice versa), at least if the Fx type is allowed on both.
- Not sure, if this is easily possible, but wouldn't the analyzer view in the digital EQ improved a lot, of it would actually "compensate" for key follow? So if you set keyfollow to 100% that the position of the fundamental would be the same then always? Then you might see changes a lot better! It could fade out the frequency meter as soon as keyfollow > 0.
- What if you could make a instance copy of a layer / an layer-alias, so if I setup a single osc with filters and later want to add the same but one octave down, I would simply alias the layer, and then transpose/pan the alias...
I would like to request a bunch of improvements to the Falcon's filter modules. And more actual filter algorithms! Before you tell me, that there are already plenty of it inside Falcon, yes this is true. But there are not a lot filter type/coloration variants inside. For instance I am trying to build a bunch real style-conform synthwave basses in Falcon. The results are quite good, but still not as a Jupiter or Prophet sounding and near to "yes, that's it!". I am trying then to "fix/workaround" the result with a keyfollowing digital EQ, but I think that won't fix the issue really.
For example, if you look at Zebra, which filters sound quite a bunch better to my ears, or better say the coloration range suits a lot of needs much better, you will have also filters with multiple resonance spikes and so, plus a Diva filter, if you go with Dark Zebra. I wish there were a lot more color variants for the LP filter in Falcon. It's not enough to have LP12,LP24,LP36 etc.
The analog filter module could get those filter variants. Currently it is too basic, at least for my taste. Normally there are plenty of analog filter types and orders, too. This seems to be a "general LP18 or something analog filter".
Also repeating the same filter with same modulation isn't a good approach in workflow either. It will lead it a lot of multiple work and is poorly managable. The filter itself should provide such a order parameter. E.g. three parameters, algorithm, type, order.
Then I observed some detail, which might be Falcon (architecture) specific: Shouldn't a keygroup filter's keyfollow also respect the coarse tune of each single oscillator? Or at least optional? Is the filter applied to the sum of all oscs, or on each osc individually?
Could you rethink this a bit maybe?
Also regarding the drunk modulator, it seems to me that it lacks of some important parameters, e.g. the "maximum range".
A general graphical visualization of any modulation value would help a lot, too! Some kind of X/Y plotter or so.
Thanks a lot for consideration! Falcon really is a lot fun to use, I love it.
P.S.
- The digital filter's gain should be usable for any filter type, also LP. So you can align the output volume with other parallel filters better. Since it is much louder than the other filter modules. Maybe all filters could have a gain parameter?
- You know what is coming now: Please add undo/redo :=)
- Panning per keygroup
- I want to copy/paste/duplicate a layer in the tree view!
- I would like to be able to drag FXs from the keygroup to the layer (and vice versa), at least if the Fx type is allowed on both.
- Not sure, if this is easily possible, but wouldn't the analyzer view in the digital EQ improved a lot, of it would actually "compensate" for key follow? So if you set keyfollow to 100% that the position of the fundamental would be the same then always? Then you might see changes a lot better! It could fade out the frequency meter as soon as keyfollow > 0.
- What if you could make a instance copy of a layer / an layer-alias, so if I setup a single osc with filters and later want to add the same but one octave down, I would simply alias the layer, and then transpose/pan the alias...
Last edited by Hanz Meyzer on Sat Jan 09, 2021 11:22 am, edited 1 time in total.
- KVRist
- 260 posts since 30 Aug, 2011 from Melbourne, Australia
I really love crafting sounds with Falcon, but I agree all of these features are basic utilities and are sorely needed.Hanz Meyzer wrote: Sat Jan 09, 2021 9:14 am
- You know what is coming now: Please add undo/redo :=)
- Panning per keygroup
- I want to copy/paste/duplicate a layer!
- I would like to be able to drag FXs from the keygroup to the layer (and vice versa), at least if the Fx type is allowed on both.
- What if you could make a instance copy of a layer / an layer-alias, so if I setup a single osc with filters and later want to add the same but one octave down, I would simply alias the layer, and then transpose/pan the alias...![]()
A composer is a guy who goes around forcing his will on unsuspecting air molecules, often with the assistance of unsuspecting musicians. - FZ
-
- KVRAF
- 2481 posts since 28 Mar, 2005
You can already do that. Just select a single keygroup. Or you mean per oscillator ?
You can already do that in left panel List View
-
- KVRAF
- 2481 posts since 28 Mar, 2005
sum of all oscs.Hanz Meyzer wrote: Sat Jan 09, 2021 9:14 am Then I observed some detail, which might be Falcon (architecture) specific: Shouldn't a keygroup filter's keyfollow also respect the coarse tune of each single oscillator? Or at least optional? Is the filter applied to the sum of all oscs, or on each osc individually?
- KVRAF
- 24405 posts since 7 Jan, 2009 from Croatia
You can, in List view. Press the wrench in the layer list.
-
- KVRAF
- 2623 posts since 20 Oct, 2014
Thanks! Yes I actually meant panning per OSC, via the "oscillators" panel. Which is kinda the keygroup? At least you also can apply those parameters to a single OSC only, too. Only panning is missing here.
Btw. how do I rename a keygroup?
EDIT: Aha in the list view
Ok, from now on, if I don't find something, I will take a look into list view.
Btw. how do I rename a keygroup?
EDIT: Aha in the list view
- KVRAF
- 1841 posts since 3 Jan, 2019 from Holland
Ah cool info, i was having that issue too.ChamomileShark wrote: Wed Dec 02, 2020 3:54 pm Just for info.
Nearly a month ago I contacted UVI re an odd issue. I couldn't do a "save as" for new programs. It worked one day, the next it stopped. A few others found the same.
Anyway, if you've had this the good news is that UVI have found the issue and it is likely to be fixed in an update next week.
My workaround is to duplicate programs in Windows, rename the old version, then use "save program" to save the new under the old name.
But happy that they're working on a fix.
The loudness war is over, loudness has won
- KVRAF
- 24405 posts since 7 Jan, 2009 from Croatia
Incorrect. VST2 can work just fine on M1 (ask FabFilter).maximoog wrote: Sat Jan 09, 2021 12:09 pm Finally VST3, VST2 is no longer supported on the new Apple devices.
-
- KVRAF
- 2623 posts since 20 Oct, 2014
Some other questions:
- I added a macro to a DAHDSR decay value. But no matter whether I set the macro to bipolar or not, the macro value will be just substracted from the decay value... Shouldn't it be centered around set decay value in bipolar mode?
- I would like to macro control the curve of the decay, too. Is that possible?
- Can I macro control the filter on/off state? I would like to make a macro control to select the filter type (4 overall), but only activating one at a time.
- I would like to control the filter env amount by velocity and a macro at the same time. Possible?
- I added a macro to a DAHDSR decay value. But no matter whether I set the macro to bipolar or not, the macro value will be just substracted from the decay value... Shouldn't it be centered around set decay value in bipolar mode?
- I would like to macro control the curve of the decay, too. Is that possible?
- Can I macro control the filter on/off state? I would like to make a macro control to select the filter type (4 overall), but only activating one at a time.
- I would like to control the filter env amount by velocity and a macro at the same time. Possible?
-
- KVRAF
- 2481 posts since 28 Mar, 2005
DAHDSR time are modulated in a multiplicative fashion hence your issue.Hanz Meyzer wrote: Sat Jan 09, 2021 1:03 pm Some other questions:
- I added a macro to a DAHDSR decay value. But no matter whether I set the macro to bipolar or not, the macro value will be just substracted from the decay value... Shouldn't it be centered around set decay value in bipolar mode?
nop. but you can use the scripting to do that.Hanz Meyzer wrote: Sat Jan 09, 2021 1:03 pm - I would like to macro control the curve of the decay, too. Is that possible?
use scriptingHanz Meyzer wrote: Sat Jan 09, 2021 1:03 pm - Can I macro control the filter on/off state? I would like to make a macro control to select the filter type (4 overall), but only activating one at a time.
you can have multiple sub modulation, but only one is displayed/editable by default.Hanz Meyzer wrote: Sat Jan 09, 2021 1:03 pm - I would like to control the filter env amount by velocity and a macro at the same time. Possible?
You can right click the ratio slider of the modulation though and handle it manually
-
- KVRer
- 15 posts since 6 Jan, 2010
Yes. Right-click the on/off button of the Filter, select Add Modulation, Program/New Macro.
Then choose 'On/Off style' of the Macro.
You can also use that same Macro to switch another Filter off:
Right-click the on/off button of the new Filter, select Add Modulation, Program/[name of Macro you just created]. Then right click again, choose Edit Modulations, and click the Invert icon.
Quite a loooong weekdionenoid wrote: Sat Jan 09, 2021 12:10 pm Nearly a month ago I contacted UVI re an odd issue. I couldn't do a "save as" for new programs. It worked one day, the next it stopped. A few others found the same.
Anyway, if you've had this the good news is that UVI have found the issue and it is likely to be fixed in an update next week.
(edit: original post was from Dec 2nd 2020)
