JazzMac251
Inspired
I've done the reading on the whole "spillover" issue. It breaks my heart, but it is what it is. What I don't understand is how the delay blocks process X/Y changes. It seems like you can't NOT have spillover.
I've been tasked with reproducing an artist's original music live, and doing so requires me to do the whole "textural guitarist" thing, i.e. TONS of delays and reverbs. First, I discover that this incredible, top-of-the-line piece of gear lacks the spillover capability present in just about every medium-tier delay box out there. Well, you can have spillover, but if your "landing" preset doesn't have essentially the exact same settings as your "starting" preset, you're not going to like the results.
Now I'm finding out that basically the same is true of X/Y states too. To put it in simple terms, I need X to be 1/8 notes, Y to be 1/16th notes. Due to the high mix and feedback levels (textural guitar), swapping between the two states turns the tails of the previous delay into a warbly, unusable mess of unprofessional garbage. It seems like there's no real fix for this, either.
I can understand working within the limitations of the system. I get that a complex device like the AxeFX is always going to have idiosyncrasies based on functional limitations of the hardware. But, after reading through years of customer complaints about this type of issue, it's hard not to feel a little irate about this. This is pretty standard functionality present on most half-decent delay boxes these days, and it's absolutely essential to providing a professional-quality performance as a guitarist. Doubly true if you do the textural thing. Don't get me wrong, I absolutely love my Axe2, but, the truth of the matter is, if the heavy-fx thing was my main bag, I would be selling this thing in a split second. This is not usable.
I guess I just have to make an absurd amount of 1-delay-block-only presets to cover the various sounds on each song, use the second delay block solely to keep tail-continuity between patch changes, and hope to God I don't run into any situation where I trigger patches out of order. Fantastic...
People have been crying about this for YEARS!! Have the unit continually take samples of the last X repeats, load them into a buffer within memory, then dump the buffer to the audio output during patch/X-Y changes. Use the architecture already in place for the Hold function. Store it in unused Looper memory. I don't know...just do SOMETHING...
I've been tasked with reproducing an artist's original music live, and doing so requires me to do the whole "textural guitarist" thing, i.e. TONS of delays and reverbs. First, I discover that this incredible, top-of-the-line piece of gear lacks the spillover capability present in just about every medium-tier delay box out there. Well, you can have spillover, but if your "landing" preset doesn't have essentially the exact same settings as your "starting" preset, you're not going to like the results.
Now I'm finding out that basically the same is true of X/Y states too. To put it in simple terms, I need X to be 1/8 notes, Y to be 1/16th notes. Due to the high mix and feedback levels (textural guitar), swapping between the two states turns the tails of the previous delay into a warbly, unusable mess of unprofessional garbage. It seems like there's no real fix for this, either.
I can understand working within the limitations of the system. I get that a complex device like the AxeFX is always going to have idiosyncrasies based on functional limitations of the hardware. But, after reading through years of customer complaints about this type of issue, it's hard not to feel a little irate about this. This is pretty standard functionality present on most half-decent delay boxes these days, and it's absolutely essential to providing a professional-quality performance as a guitarist. Doubly true if you do the textural thing. Don't get me wrong, I absolutely love my Axe2, but, the truth of the matter is, if the heavy-fx thing was my main bag, I would be selling this thing in a split second. This is not usable.
I guess I just have to make an absurd amount of 1-delay-block-only presets to cover the various sounds on each song, use the second delay block solely to keep tail-continuity between patch changes, and hope to God I don't run into any situation where I trigger patches out of order. Fantastic...
People have been crying about this for YEARS!! Have the unit continually take samples of the last X repeats, load them into a buffer within memory, then dump the buffer to the audio output during patch/X-Y changes. Use the architecture already in place for the Hold function. Store it in unused Looper memory. I don't know...just do SOMETHING...