Yesterday I used GP5 for the first time on two live vocals using waves plugins, Gig Performer performed flawlessly using 128 samples. Although the singers were perfectly happy with the latency (I don’t even think they actually know what latency is), I will try a lower buffer rate to see how stable my laptop will be.
Yesterday, the vocal monitor needed to be placed about 7 feet away and I could hear the latency.
Other musicians were amazed to lean about GP5’s power, flexibility and features!
I wonder if you are aware that every added distance of one foot from a speaker will add about 1ms of latency?
So you are going to get that 7ms latency even if you could cut the computer latency to 0!
Yes, I was aware of that. Some singers, don’t mind a very small latency, others pick up on it straight away and hate it.
I have a singer from a big band that loves mingling with the crowd. He can often be 20 feet from the nearest speaker (FOH)! Somehow, he compensates fo that and sings in time. I have so far refused to use plugins on his vocals. Need to find out what is the smallest buffer that I can safely use with my i7 intel based laptop.
Then he should use IEMs
He has one but he doesn’t want to give a good trial, because he finds too difficult (scared of) to control his own monitoring through the Mixing Station App that I suggested.
There is also another vocalist which does use and love her IEM but doesn’t want to use the app, instead she is always asking me to change the Big Band’s balance. 
Sorry - you need to train them!
Oh believe me when I say that I have tried to for the last 3 years! 
I have just carried out a short test from my laptop lowering the samples from 128 to the minimum displayed of 8 spls running Reaper’s recording into GP5 and it worked fine for about 4 minutes, while monitoring the task window. After this short period, the dropouts started, quite intensive, and continued for about 30 seconds, then everything played fine fo another 4 minutes. This repeated almost an a regular basis.
During the dropouts I noticed that there was a change in the GPU window in task manager from 5% to 33% but I never used the mouse or any other keys to change to different screen/application.
Not sure why they GPU spike 
I have now set it at 32 spls and will continue to monitor.
Max memory used, 5.2gb
WiFi disabled
No other applications running (started by me).
8 samples buffer is killer
Like I said, it worked only in short bursts of appox. 4 minutes on, then 30 second off.
Now problem running at 32 spls. Now I will try it at 16 samples. 
Why do,you need such ultra low latency?
I don’t NEED extremely low latency but it’s good to know the computer’s limits to avoid surprises.
Currently I use low latency plugins (64 samples) and 0 sample plugins 48000Hz sample rate.
Human beings just cannot detect delays that small. You’re over-stressing your computer for absolutely no good reason.
Heck, most of our professional guitar players are using 192 at 44100 with absolutely no issues. Some go down to 128 but anything lower than that is, frankly, silly.
Yes, you are right but if I know that the laptop can safely handles 32 samples I can then if I wish run it at 64 samples on some occasions, if needed.
Yesterday I would have ran it at 64 samples in order to shave a few milliseconds to compensate for the monitor’s longer distance than normal setup.
I have played my guitar with 256 samples in the past and although I can hear and feel the difference in playing I can adapt.
Some people have the hearing of a bat and have let me know they where uncomfortable playing with 128 samples. 
The irony is that most pipe organ players deal with latency on the order of seconds (not milliseconds) and have no problem.
I would generally tend to question the ability of anybody who can’t handle 2.9 ms (that’s 128 at 44.1k) 
Continuing the test at 16 samples, in over 25 minutes the laptop has experienced 5 short dropouts of about 5 seconds on each occasion, but strangely no issues has yet been reported by LatencyMon.
I would ask them if they seriously notice a difference at 64 samples with regard to 128 and would increase to 256 instead without telling them… but I am a bad guy, I know… 
How was the cpu usage shown in gig performer?
Keep in mind, that when you are using patch persist and you switch rackspaces you can get audio glitches when both in sum exceed 100% or even when it is near 100%.
