I have watched this video, and didn't get anywhere in the bigger picture... but I did learn that there are individual track delays before playing OTHER tracks, which might be useful to know later on if I'm troubleshooting issues....... are there like services offered that could review my settings and ensure minimal latency? I'm thinking maybe my laptop just has a really poor sound card.
I don’t know tbh. The main thing what is important is that the track with the biggest latency is making your latency. So if you have ten tracks and each 10ms latency but one with 200ma latency, your project is slowed down by that 200ms.
What I would do is to test things. Build either a project from scratch and experiment with settings and see which things cause it. Or the other way around take a slow project and start removing things gradually. Then nail it down where you notice it.
hi ois fit ? habe mir ein audio interface von behringer gekauft der input geht bei mir nur ab720 samples kratzfrei also 15 ms delay merkt man nicht aber bei dir sind es 32 samples wie geht das hast du ein apple pc ? mit meinem windows pc ist nicht langsam 10 th generation intel ...gehen mit oder ohne audio interface immer nur 720 samples ? hast du n plan woran das liegt ? an windows ? habe mal gehört das bei apple der sound anders angebunden ist. was würdest du empfehlen mac oder pc ? :) grüße aus münche
Hi, ja ich hab einen Mac M1 vielleicht liegt es daran, da ist das Audio tatsächlich anders geregelt. Ich muss dir aber leider sagen ich kenne mich nicht besonders gut mit Windows aus: aber ich glaube man braucht da ASIO4ALL Treiber o.ä. aber wahrscheinlich kann dir das hier jemand mit Windows besser beantworten. Der Punkt in dem Video ist aber eh, dass die Buffer Size nur die halbe Miete ist und die ganze Delay Compensation eigentlich den Löwenanteil oft ausmacht - deswegen das Bsp. mit dem Pro-Qs. Ich glaube alles kommt mit vor und Nachteilen z.B. Windows ist oft kompatibler. Meinen Mac bekomme ich nur mit vielen Umwegen an den Virus angeschlossen und gefühlt macht Mac ziemlich viele Updates, bei denen danach nichts mehr funktioniert weil sie die Hersteller außen vor lassen. Aber ansonsten mag ich Mac sehr gerne wegen des Workflows.
@@Psiger nice danke den asio 4 all hab ich wegen bitwig installiert habe ned gewusst wie ich den in abelton nutzen kann habe ihn jetzt eingerichtet die latenz ist auf 3,25 ms gesunken danke dafür aber wenn ich auch einen externen synth also audio in anmache habe ich 3,9 ms mehr latenz lol :) aber es war vorher auch nicht wirklich spürbar aber die 3,25 ms sind schon schön direkt echt guter hinweis mit dem asio . :) wieder was gelernt :) die treiberfehlerkompensation kann man vernachlässigen oder merke da nichts ? grüße
@@SuckeroftheYear Ich hab mal gesehen, dass jemand ein Video gemacht hat in dem er das getestet hatte und soweit ich ich erinnere meinte der auch er stellt es einfach möglichst niedrig ein. Ich habe aber selber noch nicht viel daran rumprobiert.
Did i missed anything from video? With 32 sample buffer size, I got a fresh project tracking 3-4 from my guitar, midi drum and bass. So i added synth/electrnc drum, etc. its fine, till add more tracking guitar then it started a latency..i tried to figured out but didnt find good result. So i experiment to delete all my synth or midi as much i could, and saved for new project. Means i leave guitar +midi drum+bass there and for purpose tracking guitar revision. But the latency is still there
It should be the track which has the most latency which is the culprit. In my production, I tend to bounce down stuff to audio once I don't touch it much more. But I always keep the midi version in the project folder in case I want to get sth back.
@@Psiger guess i shud keep use amp simulator which are more cpu usage friendly for tracking. And then Maybe Flatten it, but keep the DI, Then reamp with desired vsts sim, in mxing. For midi part i'll consider your tips for new workflow
A little trick is to not monitor the recording the track. If you want to hear what's going on set up a second track and use that one for monitoring. And you can try with external instrument and add latency in there
This makes no sense I have the top of the line computer and the input latency is all messed up. Says I have over 70ms of input latency but its only using 1% of my cpu
Not sure what's happening? But I guess you have a small buffer size already. But anyway for me the biggest change is once I remove all the plugins which add latency and are not included in that calculation in the settings.
Ableton EQ8 with oversampling enabled will *probably* tax the CPU more than Pro Q3 in zero latency. In any case, both EQ8 and Pro Q3 in zero latency mode are so low in CPU that the difference is negligible. The pro of using EQ8 is that it's a native plug in. The pro of using Pro Q3 is that it has an awful lot more features than EQ8. The dynamic bands in Pro Q3 alone, can save you having to open other plug ins to control what you cannot, with EQ8. So in the long run, Pro Q3 will save you CPU.
I didn't measure it and I know there is a video from Dan Worrall in which he states the ProQ3 is more efficient, but since I replaced all the ProQs in my projects I see it running more fluidly. Which also makes sense for me as most stock plugins is heavily optimized for the DAW. Did you test it somehow? I did just now a simple quick test. If I place 20 blank Eq8 in one track and 20 ProQs the CPU meter is higher on the ProQs. I guess it intensifies once you add EQ points - but I didn't test that now. I totally agree that the UI and functionality is way better on the ProQ.
@@Psiger just added 20 x EQ8 (no oversampling, just a high pass filter) instances in my template and CPU peaked at 18% Did the same with Pro Q3 (zero latency, just a high pass filter) and CPU meter peaked at 12% So on my MacMini M1 running MacOS 11.7.6 and Ableton Live 11.3.4, Pro Q3 is clearly more efficient according to Live's CPU meter on the top right.
@@nectariosm Interesting as I also have a Mac mini (M1, 2020) 12.4 Abl 11.2. Actually, it should react the same :D cannot really explain that difference, maybe something in the Ableton settings is diff.. Anyway, seems to be a good advice to check that things out on each system.
The vsts with good graphics such as the Q3 will cause latency cause it's consuming the graphic driver space. Whereas to KILL the latency, I export the whole project into a wav or mp3, then I lay the wav file or the MP3 file on a new fresh project, commit to the melody or whatever I'm working on irrespective of how heavy the vst is, save the instrument and midi clip. Then open the real nightmare project with bad bad latency and drop the midi clip followed by the saved instrument from the finder or Ableton explorer. Takes heck of a time but works! Good video!
weird my input buffer size says zero and cant change values my output buffer size is at 1680 giving me andoutput latencety of 76ms when i go any lower i start getting distortion . im v got a decent PC and my cpu usage is low like under 10% . i have no idea how to get my latencey down
really helpful, thank you! A breakout session where you can get a fresh moment on the set is such a good idea. love the accent, too
I totally love it. It was a massive improvement in my workflow 😃
I totally love it. It was a massive improvement in my workflow 😃
Is there a simple article somewhere instead of crumbling through 15min of video?
If you find one feel free to link 🔗 it.
I love you ! I used these export tips only when creating midi sequences and sounds I like.
Thank you. I couldn't even hit a single note on time during my live streams now I got back control 😅
@@Psiger 🤙🤙🤙🤪🤪🤪
I have watched this video, and didn't get anywhere in the bigger picture... but I did learn that there are individual track delays before playing OTHER tracks, which might be useful to know later on if I'm troubleshooting issues....... are there like services offered that could review my settings and ensure minimal latency? I'm thinking maybe my laptop just has a really poor sound card.
I don’t know tbh. The main thing what is important is that the track with the biggest latency is making your latency. So if you have ten tracks and each 10ms latency but one with 200ma latency, your project is slowed down by that 200ms.
What I would do is to test things. Build either a project from scratch and experiment with settings and see which things cause it. Or the other way around take a slow project and start removing things gradually. Then nail it down where you notice it.
hi ois fit ? habe mir ein audio interface von behringer gekauft der input geht bei mir nur ab720 samples kratzfrei also 15 ms delay merkt man nicht aber bei dir sind es 32 samples wie geht das hast du ein apple pc ? mit meinem windows pc ist nicht langsam 10 th generation intel ...gehen mit oder ohne audio interface immer nur 720 samples ? hast du n plan woran das liegt ? an windows ? habe mal gehört das bei apple der sound anders angebunden ist. was würdest du empfehlen mac oder pc ? :) grüße aus münche
Hi, ja ich hab einen Mac M1 vielleicht liegt es daran, da ist das Audio tatsächlich anders geregelt. Ich muss dir aber leider sagen ich kenne mich nicht besonders gut mit Windows aus: aber ich glaube man braucht da ASIO4ALL Treiber o.ä. aber wahrscheinlich kann dir das hier jemand mit Windows besser beantworten. Der Punkt in dem Video ist aber eh, dass die Buffer Size nur die halbe Miete ist und die ganze Delay Compensation eigentlich den Löwenanteil oft ausmacht - deswegen das Bsp. mit dem Pro-Qs.
Ich glaube alles kommt mit vor und Nachteilen z.B. Windows ist oft kompatibler. Meinen Mac bekomme ich nur mit vielen Umwegen an den Virus angeschlossen und gefühlt macht Mac ziemlich viele Updates, bei denen danach nichts mehr funktioniert weil sie die Hersteller außen vor lassen. Aber ansonsten mag ich Mac sehr gerne wegen des Workflows.
@@Psiger nice danke den asio 4 all hab ich wegen bitwig installiert habe ned gewusst wie ich den in abelton nutzen kann habe ihn jetzt eingerichtet die latenz ist auf 3,25 ms gesunken danke dafür aber wenn ich auch einen externen synth also audio in anmache habe ich 3,9 ms mehr latenz lol :) aber es war vorher auch nicht wirklich spürbar aber die 3,25 ms sind schon schön direkt echt guter hinweis mit dem asio . :) wieder was gelernt :) die treiberfehlerkompensation kann man vernachlässigen oder merke da nichts ? grüße
@@SuckeroftheYear Ich hab mal gesehen, dass jemand ein Video gemacht hat in dem er das getestet hatte und soweit ich ich erinnere meinte der auch er stellt es einfach möglichst niedrig ein. Ich habe aber selber noch nicht viel daran rumprobiert.
@@Psiger ich merk da nix egal ob ganz oben oder ganz unten egal is eh sogut wie keine latenz bei der eingabe :)
Did i missed anything from video? With 32 sample buffer size, I got a fresh project tracking 3-4 from my guitar, midi drum and bass. So i added synth/electrnc drum, etc. its fine, till add more tracking guitar then it started a latency..i tried to figured out but didnt find good result. So i experiment to delete all my synth or midi as much i could, and saved for new project. Means i leave guitar +midi drum+bass there and for purpose tracking guitar revision. But the latency is still there
It should be the track which has the most latency which is the culprit. In my production, I tend to bounce down stuff to audio once I don't touch it much more. But I always keep the midi version in the project folder in case I want to get sth back.
@@Psiger guess i shud keep use amp simulator which are more cpu usage friendly for tracking. And then Maybe Flatten it, but keep the DI, Then reamp with desired vsts sim, in mxing.
For midi part i'll consider your tips for new workflow
I dont habe problem with latency when hearing, i habe problems qhen recording, the midi note recird later than the audio signal
A little trick is to not monitor the recording the track. If you want to hear what's going on set up a second track and use that one for monitoring. And you can try with external instrument and add latency in there
This makes no sense I have the top of the line computer and the input latency is all messed up. Says I have over 70ms of input latency but its only using 1% of my cpu
Not sure what's happening? But I guess you have a small buffer size already. But anyway for me the biggest change is once I remove all the plugins which add latency and are not included in that calculation in the settings.
Ableton EQ8 with oversampling enabled will *probably* tax the CPU more than Pro Q3 in zero latency.
In any case, both EQ8 and Pro Q3 in zero latency mode are so low in CPU that the difference is negligible.
The pro of using EQ8 is that it's a native plug in.
The pro of using Pro Q3 is that it has an awful lot more features than EQ8. The dynamic bands in Pro Q3 alone, can save you having to open other plug ins to control what you cannot, with EQ8.
So in the long run, Pro Q3 will save you CPU.
I didn't measure it and I know there is a video from Dan Worrall in which he states the ProQ3 is more efficient, but since I replaced all the ProQs in my projects I see it running more fluidly. Which also makes sense for me as most stock plugins is heavily optimized for the DAW.
Did you test it somehow? I did just now a simple quick test. If I place 20 blank Eq8 in one track and 20 ProQs the CPU meter is higher on the ProQs. I guess it intensifies once you add EQ points - but I didn't test that now.
I totally agree that the UI and functionality is way better on the ProQ.
@@Psiger just added 20 x EQ8 (no oversampling, just a high pass filter) instances in my template and CPU peaked at 18%
Did the same with Pro Q3 (zero latency, just a high pass filter) and CPU meter peaked at 12%
So on my MacMini M1 running MacOS 11.7.6 and Ableton Live 11.3.4, Pro Q3 is clearly more efficient according to Live's CPU meter on the top right.
@@nectariosm Interesting as I also have a Mac mini (M1, 2020) 12.4 Abl 11.2. Actually, it should react the same :D cannot really explain that difference, maybe something in the Ableton settings is diff.. Anyway, seems to be a good advice to check that things out on each system.
The vsts with good graphics such as the Q3 will cause latency cause it's consuming the graphic driver space. Whereas to KILL the latency, I export the whole project into a wav or mp3, then I lay the wav file or the MP3 file on a new fresh project, commit to the melody or whatever I'm working on irrespective of how heavy the vst is, save the instrument and midi clip. Then open the real nightmare project with bad bad latency and drop the midi clip followed by the saved instrument from the finder or Ableton explorer. Takes heck of a time but works! Good video!
weird my input buffer size says zero and cant change values my output buffer size is at 1680 giving me andoutput latencety of 76ms when i go any lower i start getting distortion . im v got a decent PC and my cpu usage is low like under 10% . i have no idea how to get my latencey down
Hmm 🤔 to be honest I don't know maybe your Soundcard?
Don't use Ableton for PC, it's shit.
Sound 100%
Soundcard
Seconds begin at 0 not 1
Sorry quite a while ago this video to which timestamp are you referring to?
@@Psiger 7:05 hehe