Latency "solved"

@DavideAru
I feel I’m in the same boat.
(BTW, my job has been and still is playing live and recording music for the last 30 years or so)

Got my QC in December and so far I’ve been compromising to get a giggable/recordable unit.

And so far my compromises have been :

  • avoiding Rows 3 & 4 (latency)
  • avoiding FXLoops (latency)
  • removing blocks if I need external pedals via FXLoop (latency)
  • having an extra iPad & forScore to call presets via USB for last minute setlist changes before a show (no drag/drop & swap/insert between on setlists)

Had the most horrible experience in January with a “do it all” preset that had 9.75ms latency (didn’t start to measure latencies at the time, I sincerely thought it could never happen with the power advertised)
It felt like I had smoked bags of w**d (which I don’t) and I spent the evening physically compensating and playing ahead of time (fucked up my brain)

Being the man I am, I wanted to have an explanation on that abnormal feeling (this is why I started measuring stuff)

And yes, I too am sensitive to latency.
Imagine playing with a drummer that has 10ms of latency !
Even if you don’t/can’t analyse the situation, you know something’s off !
It’s what I call sloggish or sloppy or lazy.

Sloggish or sloppy or lazy doesn’t get you called or recommended for gigs.

I’m still evaluating the pros and cons of the QC and I still can’t say for sure that it’s a keeper for me.

  • I love (I really do) that I can capture my gear and stack pedal and amp captures (only the QC does this with that quality of sound)
  • I hate all the other points mentioned above.

All the best…

2 Likes