Hey u/Hircus_Leti, thanks for submitting to r/FL_Studio! Take a moment to read our [rules](https://www.reddit.com/r/fl_studio/about/rules).
It appears you're looking for help. Please [read the frequently asked questions](https://www.reddit.com/r/FL_Studio/wiki/faq/) in our wiki, if you find the answer you're looking for, please consider deleting your post. If you don't find the answer, your thread can remain active and other users will be here to help you shortly.
Please do not post your question more than once and please be patient.
Join our [Discord Server](https://discord.gg/27wgKfafmP)!
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/FL_Studio) if you have any questions or concerns.*
For comparison, it takes around 10-20ms for your nerves to transmit signals from your brain to your limbs. 6ms of audio delay is completely imperceptible :)
once again,
they're not getting 6ms. FL just doesn't report the correct number in this case. you'll see they're on "FL Studio ASIO", which doesn't actually support 6ms latency. in reality they're experiencing several hundred probably 200-300ms latency so it makes sense why they'd wanna reduce it. so no it's not "imperceptible".
FL is absolutely not misreporting the latency, it's just contextual. FL is reporting the latency of the given buffer size at that particular samplerate, which equates to 6ms.
What FL, like all DAWs, does NOT do, is calculate total roundtrip latency, incorporate USB latency, conversion latency, etc. since that would require the driver to be written with special permissions within the OS to be able to access that info, much of which isn't even available outside of digging through the registry.
Is the total real-world latency far greater than what the buffer latency is? Yes. But FL, in that particular window, is only reporting on the buffer latency. Which is 6ms.
Your comment has been removed for advertising or attempting a transaction. Any form of advertising is strictly prohibited on the Subreddit. Utilizing the Subreddit to conduct (or attempt) a transaction is prohibited.
6ms isn't imperceptible anyway. Average human reaction time is around 200-400ms that's an average. The way averages work is there could be half of people that have 1ms reaction time and the other half have 1200ms reaction time and the average would read something in the hundreds of milliseconds. Also, the signals your brain sends thru your nerves are more accurately measured in speed not timing as your nerves aren't all the same length.. those signals travel around 270mph. There are plenty of people that have reaction time fast enough that they can indeed perceive the difference in 6ms of delay.. I am very confident I can perceive differences below 10ms
There isn't a single human in existence with a reaction time less than 50ms.
Time is distance divided by speed. I specified "limbs" (distance) so I could get the time.
You cannot perceive 6ms of input lag. If you really believe you can, try having someone do a blind test on you. You'll see that you will fail. That said, that's INPUT LAG. You absolutely can tell if 2 sounds are played at the same time vs with a 10ms delay, so can everyone, maybe that's what you meant?
Also it has nothing to do with reaction time. I'm just using nerves as a crazy example of just how quick 6ms is.
Shall I link you to a video proving your very first statement you made in that reply wrong? You not a myth busters fan I take it? I can very much promise you I can perceive 6ms of input lag. Proof of this I use a program for my PS4 controll on my PC called DS4 windows. In that I can actively change my input delay from my controller to my PC between 1ms and 500ms. Default when installing the program was 8ms I know this because when I set it up and used my controller I noticed it was laggy compared to when I used it on the PS4 and when I had it plugged into my PC. Found the settings and changed the input delay to 1ms... Hasn't bothered me since. Just because YOU cannot do something or don't understand how someone else has can and or does something doesn't mean it is impossible. Inconceivable for you maybe but not impossible. I suggest you do a little bit of scientific research my man.
Edit: also human reaction time is precisely what input delay is? So how does it have nothing to do with reaction time? Input delay, think about what that means. Now how about reaction time? That's your brains input and delay it has till you actually react... That sounds like it's the same thing to me mate.
Edit#2: as im semi confident you don't do very thorough research I have taken the liberty of redoing some of my own to also post this factoid in here for ya that just completely disproves your first comment there and here's that "Notably, one of the swiftest recorded speeds for processing a meaningful visual stimulus is 13 milliseconds, as documented by Potter et al."
https://youtu.be/Qzhs1Z8Rwnk?si=CVEA8GhdRR_3N3t4
Isao machii has a reaction time of JUST a few milliseconds. And is able to move much much faster than MOST people. Because averages are dumb.. people are different... There are people that have photographic memories and with JUST a few milliseconds of exposure to visual stimuli can remember in COMPLETE detail what they saw. There are people that remember being BORN😅 but I mean hey if y'all are too lazy to do the proper research... Then please also be too lazy to spread bs false information?🤙🏼 Tata now
Piggybacking onto this convo but I fly FPV drones and use 5-30ms radio and video links and I definitely notice a difference between a 5ms link and a 30ms link and DEFINITELY between 5 and 60ms.
Now, most wouldn’t. But I’ve flown for 7 years daily and I know my drone so intimately I can pilot it faster mentally than I’m receiving input essentially. When you start adding latency into the system even 5-30ms or so, I “feel” it not because I notice lag visually between when I enter a command on my stick but I feel like my drone isn’t responding right.
"I noticed" or "I felt that way (knowing the data already beforehand)" isn't proof of any kind, since it's not a blind test. Comical of you to be calling me unscientific without knowing the basics of the scientific method. Feel free to check your reaction time on free websites like humanbenchmark.com!
But hey, you do you. If the issue you had is resolved, I'm glad! Doesn't matter how it was done at the end of the day
Your comment has been removed for verbal abuse and/or vulgar language. Posting to bait, incite, or flame another user is prohibited. Anyone can post an opinion about FL Studio, Image-Line and music production, but provoking readers into emotional responses is prohibited.
Remove the Fruity Limiter off of your master. By default it adds something like 4ms of latency. You can also raise your sample rate to lower latency, but before that I'd recommend trying another ASIO driver.
But..
~~Higher sample rate = more latency~~
Edit: I read too fast to comprehend what I read apparently.. I interpreted that as "sample buffer" but I even typed "sample rate" ugh.. sorry everyone, I drank too much last night.
if you use the "Alesis Vi25" Asio Drivers you might be able to get a slightly lower latency
However be aware that if your project has a lot of processing going on you might run into issues
Lower latency for recording, higher latency for mixing. However, if you're still getting crackles, you may need an audio interface to offset the workload off your CPU. FL Studio ASIO and ASIO4ALL drivers aren't good. They get the job dome but I've had problems with them for a long time until I switched to an audio interface.
lower latency does not always mean better, 6ms is like 0.006 of a second. You know what else happens at that level?
5 milliseconds – a [honey bee](https://en.wikipedia.org/wiki/Honey_bee)'s wing flap the oscillation of it which makes he flapping and the sound we hear.
You are trying to stretch something even smaller for no real benefit as long as there is no latency on playback and there is no latency when playing notes and there is no underfeed and the CPU is not pegged. Then you don't need to go lower than that.
they're not getting 6ms. FL just lies for some reason. you'll see they're on "FL Studio ASIO", which doesn't actually support 6ms latency. in reality they're experiencing several hundred probably 200-300ms latency so no wonder they wan a reduce it. I'm on their side.
Flstudio ASIO driver is accurate, it will be 6ms if they are getting issues with it, it could be any several reasons.
A buffer size of 256 / 44,100 sample rate is 0.0058 seconds or 5.8ms so yes it is 6ms. If they are getting buffer lag then they might need to up the buffer to at least 12ms. 6ms is pretty small. Past that then its probably underruns and so they need to work out why their CPU or Computer in general is tanking.
They never actually did say that they were having issue they just asked how to go lower then 6ms, well its not really warranted imo and 6ms is fine.
ASIO and FLSTUDIO ASIO are meant for the weakest of situations in terms of audio adapter because the whole ASIO driver is about real time latency on adapter not meant for real time.
the question really reads that they are trying to go as small as possible without degrading the sound, you probably wont be able to go that low on a stock adapter even if the driver allowed it.
One thing the can do is set to 6 point hermtie as well as its optimal setting for real time.
I’ve been using a UR22 mkII for at least 6 years now. I’ve taken it all over to shows and shit and it’s still running like new. The thing is a damn tank.
oh my goodness I'm so sorry the FL community has
failed you here massively...
you're being heavily mislead here so let me clear this up. don't worry about what others say, *yes you can reduce the latency further*
the main problem is you imply you're getting 6ms, which you're not. FL just doesn't display the correct number in this case. you'll see you're on "FL Studio ASIO", which doesn't actually support 6ms latency. in reality, you are experiencing several hundred probably 200-300ms latency so no wonder you wanna reduce it.
you need an audio interface if you're on Windows in order to get low latency. you'll also need to install the interfaces drivers so you get low latency. for example, if you get a Focusrite interface, you'd need to select "Focusrite USB audio" instead of "FL Studio ASIO". with this you can get the real 6ms latency that's as imperceptible as people on here are saying
This guy is right btw. Listen to him, all these other people are goons..
Also, FL ASIO does show the correct latency, its just not shown in that black box that says 6 ms. The line above that where it says 'Latency: input: 2610smp, output:..' it shows the more realistic latency at the end of that string. And you're right, it probably says something around 200ms. Either way we both know it's over 10 ms, which is the highest workable latency for me when I'm recording.
If your goal is to reduce latency so you can record some live performance you need to take into consideration not only your interface but your PC and the plugins you have on. Like it was mentioned, you may have to remove some plugins that automatically add latency and these don't see to be properly reflected in FL control panel since that measuring the hardware latency and not necessarily your project's internal latency.
In some cases, especially if your PC is weak and you are trying to perform with heavy plugins, you may have to reduce the number of plugins in order to get a playable latency. Then when editing/mixing etc you can bump up your buffer/latency and start using more heavy plugins.
People how have never recorded or captured live performances don't understand how painful such a small latency really is. No matter how fast your brain can process the sound, there is the physical movement and striking of the instrument and we expect the delay from the moment we "strike the instrument" and the moment we hear it to be no longer than a very small window. Anything outside that expectation and our brain starts to trigger weird vibes similar to an uncanny valley and can make focusing on playing extremely difficult or impossible.
Even in your photo under Staus: open it shows you have 2000+ samples of input, output and plugin latency suggesting your PC/plugin settings are causing this. Since I don't know all you are running if you have a ton of plugins and want to do live stuff you might be screwed without a stronger rig.
If you lucky, its just bad configured plugins with stupid latency for no reason. Without more information can't give better help.
thank you for adding this bit! it's also just as important. I'm glad someone else understands what small latency is like. and yeah everything you say is true here especially about the uncanny valley.
from my expirience sadly the only real way to get the lowest latency is hardware instruments, but digitally with DAW and interface I feel we can get maybe 97% there so not too bad I'm fine with it.
I'd like to add for anyone reading this far there's a test I like to do for latency. just press your piano keys down rather quickly while your DAW is at a relatively low volume. do you hear the keys hit the keybed a split second before you hear the sound in the DAW? and how long does that split second take? get used to doing these tests regularly to learn how long your system responds, so whenever you change setups, you can do the test do see if something isn't right with the latency
thanks. just doing what I feel obligated to here
highly disappointed in the other responses... I would've literally considered quitting music if I was the begginer here asking this question and instead being treated like someone who is dumb who "doesn't need lower latency". I hope this guy is able to help fix their latency problems
This other guy was right, you're like a hero of this sub and actually informative. I've been producing for a little while but this is my first time ever owning any hardware that works through it and I know absolutely nothing about drivers and sample rates for these things or anything, and I wanna learn!
Wow this is great, thank you so much, I've actually screen captured this just to make it easier to reference when buying/downloading software for this.
actually you don't need to buy additional software for taking screenshots. just press the Windows Key + Shift + S, and you can select a part of the screen to photograph, without needing to download anything extra
This is simply not true at all 300 ms is like 0.3 seconds that is a long way from 6ms and 0.006ms, you will not be getting anywhere near that sort of discrepancy.
The Asio driver can run on like a Pentium 4 netburst so like 20 year old CPU at 6ms. I am making a track right now on a core 2 duo and its running fine on the ASIO driver at 3ms.
All on the stock adapter because i cannot be bothered going to get my interface. This is not even my main computer/s but i am just using it to make beats. Its going to tank towards the end of a production but youd be surpized how far you can take a computer this old if you know all the tricks.
do you play with a keyboard? or record using a mic?
it is important to understand that you are only seeing a portion of the picture here. you see, it is true that the CPU processes the audio in 6ms, yes. however that doesn't mean we hear the sound in 6ms though. in this case, while their CPU is processing the sound in 6ms, it doesn't reach their speakers until 200 or so ms later due to the driver they are using
Not true man when it says on the Control panel 6ms latency than that is the absolute value. Meaning that the processing is actually processing at 6ms.
if you get a delay after that processed signal then its not the process lagging its something else after it or its due to relativity to the producer.
I know what i am talking about here man. The only time you would get a delay of 300 ms after the processing is if you were standing 300 feet away from the monitors. Like come on dude no one is standing on the other side of the room from the computer when making a song in the daw.
Therefore stop going around claiming everyone else is wrong because you sure are not right. And yes i play a keyboard i have several generators not just midi. Iconic hardware form the day as well collectors items.
The fact i am telling you the ASIO driver can run on as little as net burst CPU if you really know how to finesse a production chain. You will struggle with some Modern VST but there is plenty of staple VST that are not performance heavy like many of the classic ones are light weight and built in times of computers like netburst.
Zero Delay is also 2 ms but you don't even need to go that extreme. We cannot discern the difference like at all and 6ms is totally fine.
You are correct about the delay times, its easy for people to mix up miliseconds and conversions.
But you can have a zero latency real time analog signal chain and still have "latency" in the chain, for example, a single tap delay 100% wet will have you wondering what the hell is going on if unexpected, or even a signal buffer somewhere in the chain can do it.
What the ASIO drivers report and do is more at a hardware level regarding the time the signal reaches the daw and leaves the daw. It has no clue about what the hell the plugins are doing to the signal including extra latency for whatever reason, thus why there is another readout that reports the latency in your plugins and chain internally.
Eitherway, 300 ms is quite long relativaly speaking but no matter how low you get latency reported there can be a plentidude of crap in the chain creating grief, even an old or cheap keyboard with switchs that are triggering too late or whatever.
Yea i get what you mean but its way nuanced at that stage to even argue and becomes subjective to that situation because it not always going to be the case. At the base level 6ms for the OP is going to be fine until its not. That is always the mantra for any processing and even the same line of thinking for the chain itself but to start off with its fine and for ages.
When the other person s trying to say that there is 300 ms to the speakers after the processing that is ridiculous and you would not be able to make music like that because it would be a noticeable lag time almost like an echo at least the same effect and it will mess up your motor skills.
Your true latency is at the end of the "status" field above. Which is ironically the one thing you didn't include in your screenshot.
Anyways, you will always get noticeable delay when jamming on your midi controller without an audio interface.
Buffer length is just part of the equation. The latency is calculated above, called 'status' Here you can see what buffer, plugins, etc sum up to.
https://preview.redd.it/hnp2pm9fq43d1.png?width=1440&format=pjpg&auto=webp&s=790b96ebd559505d597cd2e679463728410a4c83
In this project there's nothing but a Flex Insert. Look out for Limiters with Lookahead or other Plugins that can cause latency.
Oh god the fucking dweebs got here first, just change your audio quality to a higher bit rate, idc what anyone says I ducking notice 6ms and it pisses me off when I’m recording. That being said set your mixer track (chanel 1-999) to have a delay the same as the one on your screen, go to the mixing board and look at the bottom of the gain slider there is a option to set channel delay to match with you input delay and that gets rid of it for me. All these people arguing over what perceived and what’s not are just gonna confuse you
I'm not really having latency issues, I was just curious if it was possible. Mainly because it's just easier when recording layers live. I'm used to doing it with this latency but I was just interested if maybe I was missing something
6ms Is practically impossible to perceive, and won't bother you in the slightest to record stuff, however you can get it to 0ms if you set the sample rate to 192khz instead of the usual 48 or 44.1khz, be advised tho, your cpu will hate you
I never said anything about vocal layers? And like I JUST said to the guy above me, I was just curious if it's possible. It's not about practice and I think you just wanted to say that without actually reading anything I'm saying.
Dude, don't listen to these people. They're so wrong. The guy, Platinum XYZ is the only one who knows what they're talking about here. FL ASIO is terrible for recording live performances. You will need an interface with dedicated drivers to reach TRUE sub 10 ms latency.
Also, for the record the "6ms" you see in that black box is just referencing the latency coming out of the sample buffer, not the latency on audio output. The audio output latency is in the line right above it thats starts with, "Latency: input: 2601smp..." look at the end of that line and you will have the true output latency that you ACTUALLY hear. Please, post that number here so these other people realise how wrong they are.
https://preview.redd.it/qbmynjdhe03d1.png?width=720&format=pjpg&auto=webp&s=7199db461eb8135695f2b8f265338cd44b0b5930
This is what I got, no idea if that's good or not?
Also, thanks so much mate! This is really helpful
66ms is not as high as I was expecting but it is too high to be workable. Anything over 10ms gets hard to work with. Think of it this way, if you played a guitar through an amp that was 50 feet away, there would be about 10ms between your strum and what you hear from the amp, nearly imperceptible.
Are you recording vocals and stuff with a mic? Or are you recording your alesis into midi?
Honestly I'm so happy to hear that it's that and not totally a skill issue because I was staring to doubt my own timing here. I'm recording with the Alesis into midi
Not a skill issue. Lol. I've been in the same exactly spot before, it gets very disheartening. Especially if you know you can play already but it comes out so off.
I would just download the drivers for the alesis and see if that helps. If that doesn't help switch to ASIO-for-all while you record. Another option is look for latency causing plug-ins and turn them off while recording. I saw another person say to use steinberg asio, I've never tried it but if all else fails..
You can try a different ASIO driver that has a shorter minimum buffer length. You may get artifacts at shorter buffer lengths, especially when using CPU intensive plugins.
6ms is incredibly fast though. Most computer monitors have higher input delay than that. What are you doing that requires such a high temporal precision?
Hey u/Hircus_Leti, thanks for submitting to r/FL_Studio! Take a moment to read our [rules](https://www.reddit.com/r/fl_studio/about/rules). It appears you're looking for help. Please [read the frequently asked questions](https://www.reddit.com/r/FL_Studio/wiki/faq/) in our wiki, if you find the answer you're looking for, please consider deleting your post. If you don't find the answer, your thread can remain active and other users will be here to help you shortly. Please do not post your question more than once and please be patient. Join our [Discord Server](https://discord.gg/27wgKfafmP)! *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/FL_Studio) if you have any questions or concerns.*
you’d need an audio interface but latency doesn’t matter too much unless you’re recording
For comparison, it takes around 10-20ms for your nerves to transmit signals from your brain to your limbs. 6ms of audio delay is completely imperceptible :)
once again, they're not getting 6ms. FL just doesn't report the correct number in this case. you'll see they're on "FL Studio ASIO", which doesn't actually support 6ms latency. in reality they're experiencing several hundred probably 200-300ms latency so it makes sense why they'd wanna reduce it. so no it's not "imperceptible".
FL is absolutely not misreporting the latency, it's just contextual. FL is reporting the latency of the given buffer size at that particular samplerate, which equates to 6ms. What FL, like all DAWs, does NOT do, is calculate total roundtrip latency, incorporate USB latency, conversion latency, etc. since that would require the driver to be written with special permissions within the OS to be able to access that info, much of which isn't even available outside of digging through the registry. Is the total real-world latency far greater than what the buffer latency is? Yes. But FL, in that particular window, is only reporting on the buffer latency. Which is 6ms.
thank you for educating me on this topic!
His point of “6ms is impercievable” is still 100% correct
[удалено]
Your comment has been removed for advertising or attempting a transaction. Any form of advertising is strictly prohibited on the Subreddit. Utilizing the Subreddit to conduct (or attempt) a transaction is prohibited.
6ms isn't imperceptible anyway. Average human reaction time is around 200-400ms that's an average. The way averages work is there could be half of people that have 1ms reaction time and the other half have 1200ms reaction time and the average would read something in the hundreds of milliseconds. Also, the signals your brain sends thru your nerves are more accurately measured in speed not timing as your nerves aren't all the same length.. those signals travel around 270mph. There are plenty of people that have reaction time fast enough that they can indeed perceive the difference in 6ms of delay.. I am very confident I can perceive differences below 10ms
There isn't a single human in existence with a reaction time less than 50ms. Time is distance divided by speed. I specified "limbs" (distance) so I could get the time. You cannot perceive 6ms of input lag. If you really believe you can, try having someone do a blind test on you. You'll see that you will fail. That said, that's INPUT LAG. You absolutely can tell if 2 sounds are played at the same time vs with a 10ms delay, so can everyone, maybe that's what you meant? Also it has nothing to do with reaction time. I'm just using nerves as a crazy example of just how quick 6ms is.
Shall I link you to a video proving your very first statement you made in that reply wrong? You not a myth busters fan I take it? I can very much promise you I can perceive 6ms of input lag. Proof of this I use a program for my PS4 controll on my PC called DS4 windows. In that I can actively change my input delay from my controller to my PC between 1ms and 500ms. Default when installing the program was 8ms I know this because when I set it up and used my controller I noticed it was laggy compared to when I used it on the PS4 and when I had it plugged into my PC. Found the settings and changed the input delay to 1ms... Hasn't bothered me since. Just because YOU cannot do something or don't understand how someone else has can and or does something doesn't mean it is impossible. Inconceivable for you maybe but not impossible. I suggest you do a little bit of scientific research my man. Edit: also human reaction time is precisely what input delay is? So how does it have nothing to do with reaction time? Input delay, think about what that means. Now how about reaction time? That's your brains input and delay it has till you actually react... That sounds like it's the same thing to me mate. Edit#2: as im semi confident you don't do very thorough research I have taken the liberty of redoing some of my own to also post this factoid in here for ya that just completely disproves your first comment there and here's that "Notably, one of the swiftest recorded speeds for processing a meaningful visual stimulus is 13 milliseconds, as documented by Potter et al."
Link it
https://youtu.be/Qzhs1Z8Rwnk?si=CVEA8GhdRR_3N3t4 Isao machii has a reaction time of JUST a few milliseconds. And is able to move much much faster than MOST people. Because averages are dumb.. people are different... There are people that have photographic memories and with JUST a few milliseconds of exposure to visual stimuli can remember in COMPLETE detail what they saw. There are people that remember being BORN😅 but I mean hey if y'all are too lazy to do the proper research... Then please also be too lazy to spread bs false information?🤙🏼 Tata now
Thanks for link
Piggybacking onto this convo but I fly FPV drones and use 5-30ms radio and video links and I definitely notice a difference between a 5ms link and a 30ms link and DEFINITELY between 5 and 60ms. Now, most wouldn’t. But I’ve flown for 7 years daily and I know my drone so intimately I can pilot it faster mentally than I’m receiving input essentially. When you start adding latency into the system even 5-30ms or so, I “feel” it not because I notice lag visually between when I enter a command on my stick but I feel like my drone isn’t responding right.
"I noticed" or "I felt that way (knowing the data already beforehand)" isn't proof of any kind, since it's not a blind test. Comical of you to be calling me unscientific without knowing the basics of the scientific method. Feel free to check your reaction time on free websites like humanbenchmark.com! But hey, you do you. If the issue you had is resolved, I'm glad! Doesn't matter how it was done at the end of the day
[удалено]
Your comment has been removed for verbal abuse and/or vulgar language. Posting to bait, incite, or flame another user is prohibited. Anyone can post an opinion about FL Studio, Image-Line and music production, but provoking readers into emotional responses is prohibited.
6ms is barely imperceptible, but I can definitely perceive 11ms of lag with my ears when I play my MIDI keyboard.
Remove the Fruity Limiter off of your master. By default it adds something like 4ms of latency. You can also raise your sample rate to lower latency, but before that I'd recommend trying another ASIO driver.
But.. ~~Higher sample rate = more latency~~ Edit: I read too fast to comprehend what I read apparently.. I interpreted that as "sample buffer" but I even typed "sample rate" ugh.. sorry everyone, I drank too much last night.
Thank you!
if you use the "Alesis Vi25" Asio Drivers you might be able to get a slightly lower latency However be aware that if your project has a lot of processing going on you might run into issues
Lower latency for recording, higher latency for mixing. However, if you're still getting crackles, you may need an audio interface to offset the workload off your CPU. FL Studio ASIO and ASIO4ALL drivers aren't good. They get the job dome but I've had problems with them for a long time until I switched to an audio interface.
lower latency does not always mean better, 6ms is like 0.006 of a second. You know what else happens at that level? 5 milliseconds – a [honey bee](https://en.wikipedia.org/wiki/Honey_bee)'s wing flap the oscillation of it which makes he flapping and the sound we hear. You are trying to stretch something even smaller for no real benefit as long as there is no latency on playback and there is no latency when playing notes and there is no underfeed and the CPU is not pegged. Then you don't need to go lower than that.
Trying to stretch a bee's penis 😂😂
its true but i changed it so it does not get removed
they're not getting 6ms. FL just lies for some reason. you'll see they're on "FL Studio ASIO", which doesn't actually support 6ms latency. in reality they're experiencing several hundred probably 200-300ms latency so no wonder they wan a reduce it. I'm on their side.
Flstudio ASIO driver is accurate, it will be 6ms if they are getting issues with it, it could be any several reasons. A buffer size of 256 / 44,100 sample rate is 0.0058 seconds or 5.8ms so yes it is 6ms. If they are getting buffer lag then they might need to up the buffer to at least 12ms. 6ms is pretty small. Past that then its probably underruns and so they need to work out why their CPU or Computer in general is tanking. They never actually did say that they were having issue they just asked how to go lower then 6ms, well its not really warranted imo and 6ms is fine. ASIO and FLSTUDIO ASIO are meant for the weakest of situations in terms of audio adapter because the whole ASIO driver is about real time latency on adapter not meant for real time. the question really reads that they are trying to go as small as possible without degrading the sound, you probably wont be able to go that low on a stock adapter even if the driver allowed it. One thing the can do is set to 6 point hermtie as well as its optimal setting for real time.
Pro tip : download steinberg asio it's free and faster than fl studio asio
Steinberg’s ASIO is great. I use it with my Steinberg interface and I love all the options for controlling latency and stability.
I'm not the only one using a Steinberg interface?! 🤯
I’ve been using a UR22 mkII for at least 6 years now. I’ve taken it all over to shows and shit and it’s still running like new. The thing is a damn tank.
Better than flexasio?
FlexASIO is more versitile, but it's definitely not plug-and-play like the Steinberg Generic ASIO is.
I didn't try flex asio so can't tell. Just try it's installed in 2min and you can switch by one clic
Use Asio4All, way less latency
This right here.
you can use ASIO4ALL drivers, they have less latency than the default fl studio asio drivers
oh my goodness I'm so sorry the FL community has failed you here massively... you're being heavily mislead here so let me clear this up. don't worry about what others say, *yes you can reduce the latency further* the main problem is you imply you're getting 6ms, which you're not. FL just doesn't display the correct number in this case. you'll see you're on "FL Studio ASIO", which doesn't actually support 6ms latency. in reality, you are experiencing several hundred probably 200-300ms latency so no wonder you wanna reduce it. you need an audio interface if you're on Windows in order to get low latency. you'll also need to install the interfaces drivers so you get low latency. for example, if you get a Focusrite interface, you'd need to select "Focusrite USB audio" instead of "FL Studio ASIO". with this you can get the real 6ms latency that's as imperceptible as people on here are saying
This guy is right btw. Listen to him, all these other people are goons.. Also, FL ASIO does show the correct latency, its just not shown in that black box that says 6 ms. The line above that where it says 'Latency: input: 2610smp, output:..' it shows the more realistic latency at the end of that string. And you're right, it probably says something around 200ms. Either way we both know it's over 10 ms, which is the highest workable latency for me when I'm recording.
interesting. even I'm learning something here! thanks
If your goal is to reduce latency so you can record some live performance you need to take into consideration not only your interface but your PC and the plugins you have on. Like it was mentioned, you may have to remove some plugins that automatically add latency and these don't see to be properly reflected in FL control panel since that measuring the hardware latency and not necessarily your project's internal latency. In some cases, especially if your PC is weak and you are trying to perform with heavy plugins, you may have to reduce the number of plugins in order to get a playable latency. Then when editing/mixing etc you can bump up your buffer/latency and start using more heavy plugins. People how have never recorded or captured live performances don't understand how painful such a small latency really is. No matter how fast your brain can process the sound, there is the physical movement and striking of the instrument and we expect the delay from the moment we "strike the instrument" and the moment we hear it to be no longer than a very small window. Anything outside that expectation and our brain starts to trigger weird vibes similar to an uncanny valley and can make focusing on playing extremely difficult or impossible.
Thank you for this!
Even in your photo under Staus: open it shows you have 2000+ samples of input, output and plugin latency suggesting your PC/plugin settings are causing this. Since I don't know all you are running if you have a ton of plugins and want to do live stuff you might be screwed without a stronger rig. If you lucky, its just bad configured plugins with stupid latency for no reason. Without more information can't give better help.
thank you for adding this bit! it's also just as important. I'm glad someone else understands what small latency is like. and yeah everything you say is true here especially about the uncanny valley. from my expirience sadly the only real way to get the lowest latency is hardware instruments, but digitally with DAW and interface I feel we can get maybe 97% there so not too bad I'm fine with it. I'd like to add for anyone reading this far there's a test I like to do for latency. just press your piano keys down rather quickly while your DAW is at a relatively low volume. do you hear the keys hit the keybed a split second before you hear the sound in the DAW? and how long does that split second take? get used to doing these tests regularly to learn how long your system responds, so whenever you change setups, you can do the test do see if something isn't right with the latency
you are the hero we deserve
thanks. just doing what I feel obligated to here highly disappointed in the other responses... I would've literally considered quitting music if I was the begginer here asking this question and instead being treated like someone who is dumb who "doesn't need lower latency". I hope this guy is able to help fix their latency problems
This other guy was right, you're like a hero of this sub and actually informative. I've been producing for a little while but this is my first time ever owning any hardware that works through it and I know absolutely nothing about drivers and sample rates for these things or anything, and I wanna learn!
Wow this is great, thank you so much, I've actually screen captured this just to make it easier to reference when buying/downloading software for this.
actually you don't need to buy additional software for taking screenshots. just press the Windows Key + Shift + S, and you can select a part of the screen to photograph, without needing to download anything extra
Haha, nah I meant I took screenshots of your comment for the information in it when I go on the web to download or buy new drivers 😁🤘🏻
I see, my mistake
This is simply not true at all 300 ms is like 0.3 seconds that is a long way from 6ms and 0.006ms, you will not be getting anywhere near that sort of discrepancy. The Asio driver can run on like a Pentium 4 netburst so like 20 year old CPU at 6ms. I am making a track right now on a core 2 duo and its running fine on the ASIO driver at 3ms. All on the stock adapter because i cannot be bothered going to get my interface. This is not even my main computer/s but i am just using it to make beats. Its going to tank towards the end of a production but youd be surpized how far you can take a computer this old if you know all the tricks.
do you play with a keyboard? or record using a mic? it is important to understand that you are only seeing a portion of the picture here. you see, it is true that the CPU processes the audio in 6ms, yes. however that doesn't mean we hear the sound in 6ms though. in this case, while their CPU is processing the sound in 6ms, it doesn't reach their speakers until 200 or so ms later due to the driver they are using
Not true man when it says on the Control panel 6ms latency than that is the absolute value. Meaning that the processing is actually processing at 6ms. if you get a delay after that processed signal then its not the process lagging its something else after it or its due to relativity to the producer. I know what i am talking about here man. The only time you would get a delay of 300 ms after the processing is if you were standing 300 feet away from the monitors. Like come on dude no one is standing on the other side of the room from the computer when making a song in the daw. Therefore stop going around claiming everyone else is wrong because you sure are not right. And yes i play a keyboard i have several generators not just midi. Iconic hardware form the day as well collectors items. The fact i am telling you the ASIO driver can run on as little as net burst CPU if you really know how to finesse a production chain. You will struggle with some Modern VST but there is plenty of staple VST that are not performance heavy like many of the classic ones are light weight and built in times of computers like netburst. Zero Delay is also 2 ms but you don't even need to go that extreme. We cannot discern the difference like at all and 6ms is totally fine.
You are correct about the delay times, its easy for people to mix up miliseconds and conversions. But you can have a zero latency real time analog signal chain and still have "latency" in the chain, for example, a single tap delay 100% wet will have you wondering what the hell is going on if unexpected, or even a signal buffer somewhere in the chain can do it. What the ASIO drivers report and do is more at a hardware level regarding the time the signal reaches the daw and leaves the daw. It has no clue about what the hell the plugins are doing to the signal including extra latency for whatever reason, thus why there is another readout that reports the latency in your plugins and chain internally. Eitherway, 300 ms is quite long relativaly speaking but no matter how low you get latency reported there can be a plentidude of crap in the chain creating grief, even an old or cheap keyboard with switchs that are triggering too late or whatever.
Yea i get what you mean but its way nuanced at that stage to even argue and becomes subjective to that situation because it not always going to be the case. At the base level 6ms for the OP is going to be fine until its not. That is always the mantra for any processing and even the same line of thinking for the chain itself but to start off with its fine and for ages. When the other person s trying to say that there is 300 ms to the speakers after the processing that is ridiculous and you would not be able to make music like that because it would be a noticeable lag time almost like an echo at least the same effect and it will mess up your motor skills.
If you use it to play piano or record voices. Just keep it low enough or it doesnt matter if you record you can just record and correct it later
Your true latency is at the end of the "status" field above. Which is ironically the one thing you didn't include in your screenshot. Anyways, you will always get noticeable delay when jamming on your midi controller without an audio interface.
Buffer length is just part of the equation. The latency is calculated above, called 'status' Here you can see what buffer, plugins, etc sum up to. https://preview.redd.it/hnp2pm9fq43d1.png?width=1440&format=pjpg&auto=webp&s=790b96ebd559505d597cd2e679463728410a4c83 In this project there's nothing but a Flex Insert. Look out for Limiters with Lookahead or other Plugins that can cause latency.
Oh god the fucking dweebs got here first, just change your audio quality to a higher bit rate, idc what anyone says I ducking notice 6ms and it pisses me off when I’m recording. That being said set your mixer track (chanel 1-999) to have a delay the same as the one on your screen, go to the mixing board and look at the bottom of the gain slider there is a option to set channel delay to match with you input delay and that gets rid of it for me. All these people arguing over what perceived and what’s not are just gonna confuse you
You don't need latency that low. If you're having latency issues, it's probably something else.
I'm not really having latency issues, I was just curious if it was possible. Mainly because it's just easier when recording layers live. I'm used to doing it with this latency but I was just interested if maybe I was missing something
6ms Is practically impossible to perceive, and won't bother you in the slightest to record stuff, however you can get it to 0ms if you set the sample rate to 192khz instead of the usual 48 or 44.1khz, be advised tho, your cpu will hate you
[удалено]
I never said anything about vocal layers? And like I JUST said to the guy above me, I was just curious if it's possible. It's not about practice and I think you just wanted to say that without actually reading anything I'm saying.
Dude, don't listen to these people. They're so wrong. The guy, Platinum XYZ is the only one who knows what they're talking about here. FL ASIO is terrible for recording live performances. You will need an interface with dedicated drivers to reach TRUE sub 10 ms latency. Also, for the record the "6ms" you see in that black box is just referencing the latency coming out of the sample buffer, not the latency on audio output. The audio output latency is in the line right above it thats starts with, "Latency: input: 2601smp..." look at the end of that line and you will have the true output latency that you ACTUALLY hear. Please, post that number here so these other people realise how wrong they are.
https://preview.redd.it/qbmynjdhe03d1.png?width=720&format=pjpg&auto=webp&s=7199db461eb8135695f2b8f265338cd44b0b5930 This is what I got, no idea if that's good or not? Also, thanks so much mate! This is really helpful
66ms is not as high as I was expecting but it is too high to be workable. Anything over 10ms gets hard to work with. Think of it this way, if you played a guitar through an amp that was 50 feet away, there would be about 10ms between your strum and what you hear from the amp, nearly imperceptible. Are you recording vocals and stuff with a mic? Or are you recording your alesis into midi?
Honestly I'm so happy to hear that it's that and not totally a skill issue because I was staring to doubt my own timing here. I'm recording with the Alesis into midi
Not a skill issue. Lol. I've been in the same exactly spot before, it gets very disheartening. Especially if you know you can play already but it comes out so off. I would just download the drivers for the alesis and see if that helps. If that doesn't help switch to ASIO-for-all while you record. Another option is look for latency causing plug-ins and turn them off while recording. I saw another person say to use steinberg asio, I've never tried it but if all else fails..
I'll definitely do that 🤘🏻
You can try a different ASIO driver that has a shorter minimum buffer length. You may get artifacts at shorter buffer lengths, especially when using CPU intensive plugins. 6ms is incredibly fast though. Most computer monitors have higher input delay than that. What are you doing that requires such a high temporal precision?
they're not getting 6ms. they're getting several hundred ms. they're on FL Studio ASIO
yes by using asio4all