KVR Audio

c_voltage · Post by **c_voltage** » Wed Oct 05, 2016 7:07 pm

otristan wrote:FWIW, in order to reduce IRCAM stretch CPU usage, it's best to have 44.1khz sample and samplerate and run at a big buffer size.

Yes, this condition are there is. (44100, 512) Tried up buffer even to maximum, almost without changes.
Although, must admit that there is some moments (what happens especially with short samples) when suddenly cpu load decreases significantly (even on zero speed) and i can even to trigg couple voices at maximum envelope release, without cpu overload. Untill i change something else in stretch settings, then everything returns. Do not understand dependencies yet.

Well, if many users say that they had all good, then I do not know, may be really a problem is strictly on my side, but, I often compare the cpu load results from different hungry plugins from couple of other users (from other forum) who have quite powerfull machines, and our results could be different of course, but usually in such a ratio - If the CPU load has been a problem for my - then they also noticed an appreciably load. But such, that there all perfect , but here overload - I almost never seen.

topaz · Post by **topaz** » Wed Oct 05, 2016 8:19 pm

Why ? It would make distinguishing different modules so much better.

otristan wrote:
topaz wrote:Bump for option to color ( distinguish ) modules please
Our UI designer would burn us alive if we ask him something like this

Oberheim 8000 · Post by **Oberheim 8000** » Thu Oct 06, 2016 8:12 pm

What about make user option for choose own color for each module, oscilator section, keygroup, layer and program? If color for keygroup will be chosen, all modules under colored keygroup will be same color. Same for layer and program, but layer colorize only uncolored modules and colored modules (with diferent color as layer) will have rectangle around module with layer color etc... Designers need nothing to do.

topaz · Post by **topaz** » Thu Oct 06, 2016 8:23 pm

I guess some people like a bit of color in their life and some like UVI like grey.

Oberheim 8000 wrote:What about make user option for choose own color for each module, oscilator section, keygroup, layer and program? If color for keygroup will be chosen, all modules under colored keygroup will be same color. Same for layer and program, but layer colorize only uncolored modules and colored modules (with diferent color as layer) will have rectangle around module with layer color etc... Designers need nothing to do.

newuser2014 · Post by **newuser2014** » Thu Oct 06, 2016 10:15 pm

Tutorial by Attack Magazine "Pluck Organ with UVI Falcon"
https://www.attackmagazine.com/techniqu ... vi-falcon/

RobGee · Post by **RobGee** » Fri Oct 07, 2016 9:39 am

otristan wrote:
EvilDragon wrote:
otristan wrote:Falcon can indeed introduce latency with some FX.
Convolution reverb it not one of those though but this is indeed the case in limiter and oversampled FX like the xpander filter or waveshaper.
Why isn't this latency then reported to the host dynamically so PDC can be carried out?
This is not as easy as it sounds.

Loving the 1.2 update, awesome work!

I didn't realise this about PDC until yesterday, it's not easily noticeable but it is there. How far are you with implementing reporting of the latency?

FabFilter and Cytomic and many others report this dynamically for their plugins. I'm not a programmer or developer but it can't be that hard to implement if everyone is doing it?

I haven't been using Falcon for long, I think it's an amazing instrument from what I've seen but this has taken the shine off for me, especially as the xpander filter is one of my favourites within Falcon. Hopefully it is fixed soon.

otristan · Post by **otristan** » Fri Oct 07, 2016 9:50 am

PDC for an instrument and an FX are really different.
How can you have PDC on live input ?
I'm not even sure DAW supports latency for V.I as it means shifting the MIDI not the audio.

EvilDragon · Post by **EvilDragon** » Fri Oct 07, 2016 10:29 am

I suppose if you set Xpander filter to 1x (no) oversampling, then it doesn't introduce latency?

(Also, would be nice to know the difference between algo I and II?)

RobGee · Post by **RobGee** » Fri Oct 07, 2016 12:37 pm

otristan wrote:PDC for an instrument and an FX are really different.
How can you have PDC on live input ?
I'm not even sure DAW supports latency for V.I as it means shifting the MIDI not the audio.

Thanks for the reply.

Oh okay I didn't know it was different to implement for effects vs instruments, I thought it was just reported to the host which then delays everything else accordingly.

So any synth/sampler with oversampled filters and effects is going to be a little out of sync? That can't be right? I've just looked at the plugin information in Cubase and there is a listing for latency on instruments (U-he Diva and Zebra have 16 samples of latency).

Anyway awesome job with the update and Falcon in general, if you do manage to sort this it would be great.

kokotte · Post by **kokotte** » Fri Oct 07, 2016 12:58 pm

i have a wish/ fr:
see the mod amount for the 8 eq like in the other modules( filter, osc...) ( i can manage it in the tree view)
thanks in advance, and once again, you make a good job On the last update!

otristan · Post by **otristan** » Fri Oct 07, 2016 12:59 pm

First of all, I'm not sure all DAW handle this.
Plus in case of Falcon, you can have multiple parts that have different latency depending on which FX they have
so it would means taking the worst case and handling in each part an eventual compensation if it different from the one reported.
As I said, far from trivial, like it is in a simple FX.
So clearly, don't hold your breath.

loachm · Post by **loachm** » Fri Oct 07, 2016 1:11 pm

...apologies for my maybe stupid question - is there a demo version available in the meantime? Can't find any...

_TIP_ · Post by **_TIP_** » Sat Oct 08, 2016 3:28 am

otristan wrote:First of all, I'm not sure all DAW handle this.
Plus in case of Falcon, you can have multiple parts that have different latency depending on which FX they have
so it would means taking the worst case and handling in each part an eventual compensation if it different from the one reported.
As I said, far from trivial, like it is in a simple FX.
So clearly, don't hold your breath.

First of all, thanks again for the update

Otristan, i personally think you should fix that PDC problem and maybe have it as an option in the settings tab. It's 2016, almost 2017 and all serious DAW's can handle PDC... No offence here but you are selling a $350 plugin that doesn't even have that basic feature, it doesn't even have UNDO

. Instead of adding more fx and filter types (i appreciate it by the way you did) try to do the basics first... It's killing my workflow by not having the UNDO function and also I have to render every single Falcon midi file to audio and then move it slightly to the left, so it would sync with the rest of my project...
No hard feelings here, keep up the good work...

trusampler · Post by **trusampler** » Sat Oct 08, 2016 4:19 am

@ Amused+ Otristan - thank you for checking and pointing out that it may have something to do with the samples. I checked again ,and it's working fine, had to convert it,all good now, thank you.

Charlie Firpo · Post by **Charlie Firpo** » Sat Oct 08, 2016 7:53 am

About this pdc issue, is this a problem only while working with other plugins? Let's say that i do a whole song with only Falcon, will there be different latencys all over the tracks? I just tried 2 tracks, different channels (one with fx) with the same drum patch and did not notice any problem. Sounded tight as a rock. The only thing that caused a bit latency was the limiter, but i almost never use this on single tracks. And by the way, thank you Uvi for this wonderful plugin! I love it!

UVI Falcon - v4 = 2026 released - rumors, ads, praise, kindergarden, auto-sampling and off-topic inside!