FL studio 20.1 - Latency with DELAY

[d.healey]

@Fortune But won't the HISE made plugin affect the sound anyway because it's an audio effect?

[Fortune]

@d-healey Yes of course an audio effect adds tone to the sound, but we are checking if there is delay or not, between treated and untreated audio.

In order to do that, we are duplicating the same track, inverting the phase of the second track without any fx plugin. So both two tracks should delete each other (even one track slot has our Hise made fx plugin).

You can check this video:

Till 7 - 8 years ago you wouldn't make these tests but Nowadays almost all of the users test the quality of their plugins before they buy or use. Null Test & Plugin Doctor software ways are good to go for checking the quality of the plugins ;)

The must check list of a fx plugin:

• Phasing issue (delay compensation)
• Aliasing (it can be done with Oversampling - I see that Hise has it on Shape FX. It is good. Other "Saturation" unit is trash because it causes aliasing problem. Don't use "the saturation" unit on your plugins. Use "Shape FX - in saturation mode wiith oversampling" instead of it.)
• General issues (crackle - glitch, slow operating performance, loading time performance...etc)
• And of course Sound quality

If your plugin fails just one of these tests, then everybody will put a label to your plugin in black list or "Shitty". And everybody know before buy it from forums or community all around the world ;)

[d.healey]

@Fortune I thought the null test only works if both tracks are identical

[Christoph Hart]

I would argue that the statement „if a plugin is aliasing, nobody will buy it“ is FUD - it‘s a fact that many well known and famous plugins don‘t care about aliasing and it‘s just some weird nerds that discovered how to use sine sweeps moaning on Gearslutz.

[Fortune]

@Christoph-Hart said in FL studio 20.1 - Latency with DELAY:

I would argue that the statement „if a plugin is aliasing, nobody will buy it“ is FUD - it‘s a fact that many well known and famous plugins don‘t care about aliasing and it‘s just some weird nerds that discovered how to use sine sweeps moaning on Gearslutz.

Yeah I totally agree with you. However, people who want to buy a plugin, just search the user reviews or comments. Generally GearSlutz / KvR ...etc forums are the places that most of the users will look.

After reading some comments of some audio nerds; A person who doesn't even know about what the "Aliasing" is; just can decide that "This plugin has a low quality". Most of the forum users are not honest about their OWN thoughts. Most of them follow each other.

Because of that Nerdy moans, the plugin manufacturer will have a loss on sales drastically.

it‘s a fact that many well known and famous plugins don‘t care about aliasing.

Actually no, the well known manufacturers (Universal Audio, Waves, Softube, iZotope, Fab Filter, Acoustica Audio, Plugin Alliance, PSP, Slate Digital, Boz Digital, McDSP, Soundtoys, Audified....tons of etc) know this truth and they care about these rules very well.

[Christoph Hart]

Yeah in that case just make a fake user account and say that you think the aliasing makes it sound „warm“ and you‘ve got yourself a few more sales ;)

[Fortune]

@Christoph-Hart Hehehehe :)

[Dan Korneff]

@Christoph-Hart I'm looking for a way to deal with latency compensation in FL.

If I don't use setLatencySamples, FL will automatically detect and compensate for the latency of an FX plugin, but other hosts (cubase, PT, etc...) will have latency.

If I use setLatencySamples to set a specific amount of compensation, FL studio appears to have a fixed offset (I think 4096) samples when you process a file. (appears to not change depending on sample rate or buffer size).

I know you have expressed a strong bitterness with FL, but would you be able to suggest a way to deal with this?

[ustk]

@dustbro It seems latency report is somehow a redundant issue...

[A Former User]

Sorry it is an old topic but,

Yes I can confirm that, setLatencySamples works perfectly in all of the daws except FL Studio.

Weirdly, when I don't use setLatencySamples, FL studio matches the delay compensation perfectly

So what is the difference that only FL studio doesn't take setLatencySamples correctly? Have anyone solved that?