FL studio 20.1 - Latency with DELAY
-
@Fortune I thought the null test only works if both tracks are identical
-
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.
-
@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.
-
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 ;)
-
@Christoph-Hart Hehehehe :)
-
@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?
Dan Korneff - Producer / Mixer / Audio Nerd
-
@dustbro It seems latency report is somehow a redundant issue...
-
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?
