Glitchy audio when running streaming audio - buffer size 16 samples

[dhj]

@EskilS

That does seem to be the consensus, yes

The vast majority of our professional guitar users are perfectly happy with a buffer size of 128. They rarely go down even to 64

For example, check out one of our user’s youtube video (he was guitarist of the year in Guitar Magazine a few years ago) who is quite the shredder and perfectly happy with 128

Stop Worrying About Latency: Igor Paspalj Explains Latency Concerns

[Miguel]

We keyboard players are also fine with 256 samples… and we have to deal with a certain travel of the key as we play it, roughly 1 - 1,5cm before the actual sound is executed… (depending on each keyboard, evidently)

A guitar player has no travel at all, thus, the latency compared to a keyboard player is much less… 128 for a guitarist should be more than sufficient.

[EskilS]

In case someone else has the same issue and finds this thread; here’s an update on this now that I’ve played around some more.

Yes, buffer size definitely seems to have been the culprit here. I actually needed to go up to 512 samples before I stopped hearing glitches completely.

So what I ended up doing was taking the advice of a comment above and separating my GP into two instances - One for bass and guitar, with a low buffer setting (32 samples on my gig laptop, 16 samples on my home machine), and one for backing tracks and synths with a high buffer setting (512 samples on both machines).

For me this works really well. My “bass rig” is now completely detached from my setlist, which is actually preferrable now that I’ve set it up properly. I can now set up my bass rig as a regular rig, with a MIDI controller pedalboard and just jump between rackspace variations with that.

Meanwhile, my backing track rig utilises a proper setlist, with part actions taking care of selecting the correct audio files in all my streaming players, and variations taking care of any synth rig changes that I need to make for each song (splitting the keyboard, transposing, activating different synths, etc). Very handy. Sample size is much less of an issue with synths, presumably because there’s no processing of audio from the input happening.

Thanks everyone for your input!

[Marbles]

@EskilS

For me this works really well. My “bass rig” is now completely detached from my setlist, which is actually preferrable now that I’ve set it up properly.

In case you ever change your mind about that preferrability:

Best practice for managing multiple instances with shared setlists

Hi everyone, I’m currently using two instances of Gig Performer on the same machine, each connected to a different keyboard controller: • Instance 1 is for basic piano sounds (bottom keyboard) • Instance 2 is for synth sounds (top keyboard) These two instances are linked via OSC, and they share the same setlist for seamless patch changes. Recently, I wanted to add extra synth layers to the bottom keyboard, so I created a third instance for those sounds. However, I ran into a limitation: I c…

[Frank1119]

@EskilS

So what I ended up doing was taking the advice of a comment above and separating my GP into two instances - One for bass and guitar, with a low buffer setting (32 samples on my gig laptop, 16 samples on my home machine), and one for backing tracks and synths with a high buffer setting (512 samples on both machines).

Glad to hear that you figured a way to solve this.

For other people: Whether this setup is possible or not highly depends on the audio interface and its drivers. Some interfaces only support 1 buffer size at a time. In that case instances of GP running at different buffer sizes will probably have an issue.

[EskilS]

@Frank1119

For other people: Whether this setup is possible or not highly depends on the audio interface and its drivers. Some interfaces only support 1 buffer size at a time. In that case instances of GP running at different buffer sizes will probably have an issue.

Good input, thanks.

Seems to run fine on both my Apollo Solo and Scarlett 4i4. I haven’t tried it on my Arturia Minifuse yet, but that’s just a jam interface anyway, and not used live.