You don't need to do anything as complicated as that. I use Logic, but I should imagine cubase has a similar function;
You want to give the midi tracks going to giga a negative delay - so notes play before the song position reaches them.
There are ways of finding out the exact latency though. Trigger the same sharp sound from both giga and cubase (on audio track), record the output from your mixer and measure the distance between the peaks in milsecs
I do this by ear because I find that things like strings usually need more neg delay than percussion.
Some libraries even have a small bit of silence at the start of the sample (as if we weren't battling with latency enough.) :mad
Patthoven, I thought the latency compensation was for plug ins and not for audio?
Latency compensation does in fact usually have to do not only with plugins, but also with making sure your new recorded tracks are not latent with respect with the existing tracks. So for example, say your system has 30ms of latency, then without latency compensation, every new track you record would be 30ms behind the existing tracks. The way latency compensation works (roughly) is that the system knows what the latency is and aligns the new tracks time-wise with the old tracks assuming this latency value.
Now I don't know what your problem actually is, but it's not related to latency compensiation, not likely. Of course I use hardware monitoring on an ultra-low-latency system to record so I'm not really well versed on latency problems (running Linux, I can get under 10ms of latency, and with M-Audio hardware I have zero latency monitoring so it's a non-issue).