Possible Virtual Capo bug


I save a preset that has a Virtual Capo Pitch block enabled with 0 Shift. When I boot up the Axe with that as my preset, I get crazy high latency (~80ms). If I shift it off zero and then back on, latency is back to normal. If I switch to another preset and than back, latency is normal.

"That's expected behavior. The "heads" are frozen when the shift is zero so depending upon where the heads are the latency can be noticeable."

This is a bummer. I thought I could just leave it on at 0 Shift in all my presets and just adjust the Shift when needed on the Performance page. Now it sounds like I need to have to use two separate Perform parameters, one to enable the block and another to shift it.
Top Bottom