Latency SOS

Hey guys,

I’m in desperate need of help. I am a long-time pianist with little to no experience with keyboard playing, sound design, synthesizers, etc. I am starting to get involved with some cover bands so I purchased Gig Performer at a friend’s recommendation. Over the last couple of months I have put in countless hours creating patches and dialing in my sounds.

Problem is, I was just using my computer speakers the whole time. Today I wanted to test my entire setup before my first gig (in 5 days), so I hooked up my keyboard, laptop, interface, and amp and suddenly I had ridiculous latency. I know that’s probably obvious/inevitable but I am totally new to all this so I didn’t anticipate it. Rookie mistake I guess.

Anyway, I’ve tried lowering the buffer size as low as I could without pops and stuff, but it’s still really bad. I’ve updated my interface driver as well.

I assume the issue is that my computer isn’t powerful enough to handle lower buffer sizes?

Here’s my specs:

My interface is a Focusrite Scarlet Solo 2nd Gen.

If there is any way for me to salvage all the work I’ve put in, your input is greatly appreciated!

Could you also post a screenshot of your audio settings in GP?

And one of small settings screen from the focusrite applet in the systemtray at the bottom right

Edit: This one (the little red arrow at the bottom points to the focusrite applet):

Given that using the internal audio you did seem to have no problems, it is not my first suspect, but it is not very ‘beefy’. An important thing is to read and apply (where applicable) the suggestions in this guide:

For power plans look at this thread. Somewhere around reply 55 I’ve posted a small script that can make it somewhat easier when you’re system uses ‘modern standby’, in which case you see no powerplans like ‘ultimate’:

2 Likes

Please create a screenshot of the Audio Options window in Gig Performer.

1 Like

Capture

There lies the problem, instead of Windows Audio, please use ASIO and then select your Scarlet Solo (and not your integrated Realtek chip).

image

5 Likes

Btw: 16 is for most systems way too small and for most users just burning cpu cycles: aim for something in a range of 256 to 128 @ 48KHz.

2 Likes

Frank’s script saved me on my Lenovo Thinkpad P16 (Gen 2)!

Lowering your sample rate to 44.1 also helps

2 Likes

There’s a caveat to this. If a vst instrument is sampled in 48kHz there’s less strain on the cpu to use the same for the sample rate. I use a lot of Native Instrument plugins and they sample everything in 48. Back when I was using a system with limited resources my system became more stable and less cpu usage when I switched from 44.1 to 48.

1 Like

Wow that’s interesting, I had no idea. Maybe as an experiment I’ll try 48kHz to see what happens.

Hmm, I use tons of Kontakt libraries and I run at 44.1k … never noticed an issue. I don’t think that sample conversion is expensive

2 Likes

Same here.

I’m sure I wouldn’t notice a difference on any of my current machines but there was a time when being a “power user” with tons of instruments on a questionably slow machine definitely made a difference for me.

Thank you!!! It is working now.

4 Likes

Great! Enjoy Gig Performer :slight_smile:

2 Likes