FL Studio TUTORIAL | Every Latency Issues Fixed!

[@lelnoob4301]

Saved Mah Life broo! Was looking for this simple thing for hours and you just solved it in 5mins!

[@toavnwub]

You're welcome bro :D

[@NicolasStephensen]

YOU HAVE SAVED MY LIFE!!!! Thank you man!!!❤❤❤

[@timvanloon3628]

Ur the goat bro thankyou sooo much, also amazing video quality very nicely done!!

[@toavnwub]

thank you :D

[@arthurmaximillian]

thanks mate, helped me with a lot of stress!

[@McGrizz]

doesnt work with soothe :(

[@toavnwub]

I assumed this worked on every vst and since i don't use soothe a lot i didn't know ... Something you can try is to use the latest version of fl and if it still doesn't work then you don't have any other option than to bounce every thing in audio

[@McGrizz]

@@toavnwub i think it doesnt work if you use a midi as an input for sidechaining and wahetevr you put on a channel thats routed to that sidechain it make it delayed

[@ninjehdzn]

seriously? so you are saying the biggest headache I've ever had with FL that almost got me to switch to Bitwig is hidden in a submenu and its not even activated by default? I hate image-line but I love you dude

[@toavnwub]

haha xD it might be on by default or i don't know but ngl bitwig is a solid choice! also thanks :)

[@kayaradiofm]

THANK YOUUUU

[@toavnwub]

you're welcome :))

[@iamquietfire]

Thanks for the tutorial. I kinda liked the shifted version tho; reminded me of melodic riddim.

[@toavnwub]

i mean yeah it is cool when it's like that but it gets bad when you do the same for every element xD might as well enable the settings 1st then manually shifting everything, that would make more sense.

[@andewprod]

Thanks so much, its more simpler than I thought. I actually struggled a lot with that in earlier FL versions some years ago already and I never found the complete answer. Would have been useful in 2017 hahah.

[@toavnwub]

no problem :) and yeah i agree although i wasn't really that advanced back in 2017 but definitely would've been useful

[@mqbaka]

But how?? How do you know all this stuff ??

[@DETERMINOLOGY]

I see talks of fixes for this. But no one really talks about the typical delay of input notes when recording. If you watch any you tube video most people will "ALWAYS" quantize notes right after they record. Im sure its not their pc nor the hardware. FL as a software has this issue since they first started and no other daw has this problem as you record the notes go directly on grid no need to quantize

[@toavnwub]

I can kinda understand your point, but isn't that just a buffer thing? you can just lower your buffer size for less latency while recording and also preferably use the asio driver that comes with your audio interface. but again, i don't do a lot of recording so maybe there are things that i'm missing

[@DETERMINOLOGY]

@@toavnwub Ive tried all of that but its still a issue. Thus while lowering the buffer size and changing the recording helps its not a full fix. Even if you watch many videos when people record if they don't do any edits they will have to quantize the notes. Any other daw i dont have to do that except FL and im sure some of these guys have better pc /gear setups then me and my setup isnt no slouch... This has always been a fl studio issue which is why when i use it i mostly draw in my notes for that reason. Logic, Reason, Ableton Live, Studio one or even garage band none of those DAWS have that issue and i never had to mess with the buffer size as they catch the notes on grid perfectly ( No quantize needed after playing) Just watch a few videos most people after they record something in fl they will quantize the notes. Thus its quick its not a major issue but its still one of those things FL could fix. If i was to hook up a midi keyboard or mpc and trying to hit some drum patterns in it that would make put me off with the program and i would look for another DAW

[@toavnwub]

@@DETERMINOLOGY i see, well i hope that'll get fixed in fl 21 since it sounds like the next "big" update

[@Hani_000]

What program used?

[@toavnwub]

i use fl studio

[@AaronPoulsen]

life saver!

[@gourabmusic]

Wow , thank you so much , i got my answers 💗

[@toavnwub]

np man :)

[@daw-20r11on]

wow!! thank you 👍

[@zaalimbeats]

Wow ! My Vocal Tracking Effect chain was creating latency issues.

[@toavnwub]

i feel that pain

[@zaalimbeats]

@TOavn and I found out that the options shown in the video were already enabled *pain intensifies*

[@toavnwub]

@@zaalimbeats it could be the plugin you used, or idk could be anything. When in doubt, always consolidate

[@zaalimbeats]

@@toavnwub yeah that's what I've been doing

[@djmcg83]

It`s helps thank You.

[@toavnwub]

you're welcome!

[@Jinglex]

That's so helpful! I always thought fl's latency just sucked xd

[@toavnwub]

looks like it doesn't anymore xD

[@markwoodson2020]

What about hardware induced lag?

[@toavnwub]

can you explain a bit more please?

[@andewprod]

@@toavnwub maybe he talks about latency of the soundcard for external gear, be it a mic, a guitar or a synth. My recommendation: reduce latency of your sound card, the less, the better but higher CPU needed. What I also use to do is just to use the "computer" and "imput" mix-knob that most soundcards have. That way you wont hear your instrument / voice fully processed but at least it doesnt have any latency at all.

[@sumbodee3]

DO NOT change the PPQ in the midst of your production. The PPQ you use at the start of mixing is the one you have to stick with and need to export with. .. It's gonna mess up your mix. Higher PPQ means higher resolution of the Grid, how many steps one cell has. so if you have something that has x empty steps from the left of a cell and y steps from the right, changing the PPQ will result in FL placing the piece on the wrong spot,, FL works with the steps of it's grid, not time. So you better not mess with the PPQ. 96 should be practical. just make sure its at 96 before you do anything

[@hund2955]

Well you can always set it higher. See if your CPU can handle hat PPQ change and if not change back to previous. As long as you do not change the positon of any note in piano-roll or pattern/ automation-node in the playlist you wont lose any data. But if you want to go save anyway just save your project as a new one and mess with the copy...

[@sumbodee3]

@@hund2955 I'm not talking about losing data, changing the PPQ can result in your notes being all over the place, not just notes in piano roll, also objects in playlist ,, because it is a different grid. you HAVE to work on the PPQ you started with,, So you're wrong, you see you don't have to change the position of anything,, changing the PPQ WILL change the postition automatically and will ruin it.

[@hund2955]

@@sumbodee3 actually it won't If you dont Change any Note after switching to a Higher ppq and Back. I know what you mean, but let me demonstrate: You have a ppq of 96 for example. Now you can place (theoreticaly) a Note on 96 steps between 2 quarter notes. Since ppq ist Short for Pulses per quaternote. If you now Change to a Higher ppq Like 192 you can place a Note on 192 different steps between 2 quarter notes. You have effectivly Doubled the Numbers of steps you can use. But all the old steps Form the 96 ppq are still there. The 96 ppq grid can Just use every secound step of the 192 ppq grid. AS Long as you do Not Change anything between now and the Point you Set the ppq Back to 96 No Note Placements will be Changed. Because they only Change if a Note is on a step that the new grid can't represent. But even then they will 'just' be cast to the next fitting step. So they dont End Up all over the place but sliglty Offset. Which ist Bad enough. So Not Decresing the ppq is generally good advice, since fl dont save the old positons. They are lost Without a Project Backup. Thats what the Warning Message means with losing Data. The Note Position Change is essentially loss of Note placment Data. Of course this can also happen to Playlist Clips, Automations anything that can snap to the Midi/Playlist Clips, as you pointed Out. But its ALLWAYS save to increase ppq. But youre CPU has handle Double the Pulses per secound, every Pulse FL collects all Data IT needs to Play the Sound, Like Soundcard audio Buffer values, Automation clip value at that Point, etc... So you can make Life hard for your PC very easaly. But you can Just Look If your PC can handle the Higher ppq setting If needed and If Not Change Back, ASLONG as you didn't made Changes. I get that never Change the ppq setting mid project is good advice for beginners, but Not for expirenced Users. Also it should be: do Not Decrese ppq mid Project. To be more upfront to beginners about how ppq works...

[@BochiDaru]

thanks, nice tutorial

[@toavnwub]

Ty for watching 🙏