Each effect can also take a bit of time to process the audio, and delay compensation keeps the tracks playing together, despite varying amounts of latency due to the various effects on the tracks. Mixcraft does have delay compensation, but that's mostly dealing with having effects on tracks and keeping everything in sync. Mixcraft has to wait for your sound device to process the audio and send it to Mixcraft. That’s why now i use samplitude for recording audio and midi and protools hd for plugins and instrument played by samplitude midi tracks.Latency is mostly determined by your sound device. If it so disable it ! because at 1024 samples you cannot play guitar rig in realtime…Ĭubase is to big ! samplitude is light powerfull and easy and quite for little computer. You maybe have bad suprise with asio guard because 23.220 millisecond is maybe 1024 samples latency ! If you want be more precise you have to hear your guitare through a real amps and switch the signal in the same time to the plugins. īut 512 samples is quite when you record guitar rig for example. I cannot make running plugins under 512 samples in cubase. įirst disable asio direct monitoring (because it disable vst plugins)ģ put a global value in record shift (higher than the plugins who do the bigiest latency)Ħ see the difference - the 512 samples of recording shift= track delay latencyħ adjust the difference in the option track delay of cubase.
You can maybe do the same with cubase alone. Now i can use all the existing plugins (vst/rtas/tdm/aax) measuring and compensate the latency of every plugins with samplitude adjusting them with time adjuter and i can record my guitare basse drums voices with plugins and without any latency in samplitude !!! When i use a tdm plugin i have only 130 samples latency then i put 382 samples in the time adjuster of protools 382+130=512. Why ? because every plugins have diferrent latency in protools. So i put 512 samples in the recording offset and 53 samples in the time adjuster plugins of protools. Then i see the latency of protools plugins.įor example guitar rig rtas at 128 samples buffer protools do 459 samples of latency.
Now i will explain you how i resolve the latency problems of plugins when you record in realtime with a vst or rtas on insert.įirst i record a click track in samplitude.Īfter i record this click track passing throught protools plugins into samplitude. So i use samplitude at 1024 sample asio direct monitoring and protools hd at 64/128 samples. to much latency for playing plugins in realtime. In protools hd i can make working maybe 10 big plugins at 64 samples buffersize.īut when i use protools alone a have latency and when i use samplitude or cubase alone …it only work at 1024 samples. In samplitude you have the same option “record shift” maned offset recording in samplitude.
I have an old computer lga 775 q圆850 8 go ssd sata 2 windows 7 圆4Īnd i’am working at 512 samples. Yes you need a big computer to run plugings at 64 samples without clic and pops in cubase…īut even at 64 samples you have 5.079+3.515 milisecond so at 44 khz you will have 370 samples of recording shift latency.