
WEll,
in general, yes.
latency is THE cause of whats happening, whether its midi port input latency or just general CPU latency. thats the point of having really fast computers.
my tower is the slowest G5 ever built, but even with 4 gigs of ram, i can clip out CPU in a larger session. Thats why I always track vocals to a bounced 2 track.
if you have the whole session for the beat, and its spinnin wheels on 40 plug ins, your vocals are going to record late regardless, and get worse as you add layers.
But back to midi..
Which interface do you have again?
The way I see it theres two ways about it...
you can either run the whole session a consistent amount off grid, and ignore the nudge factor until it becomes critical... and then chop all of the fronts off at once and slide everything to grid...
or, you start narrowing down whats causing the latency....
long cable runs?
cpu latency?
stuff like that... if your locked on time code, and your machine is chasing your protools grid, then the latency can just be adjusted... as above.
or you can see of you can mess with your playback buffer, midi offset, and all of that,
ill play around.
poundaproblem wrote:"...dudes like me. Dudes who started YEARS ago and spent HOURS, DAYS, WEEKS, MONTHS, YEARS to learn our craft just so some little swaggot can buy an MPC, download a DAW and call himself a producer."