What happens if you add an AMP and CAB block?My elaborate preset:
View attachment 50774
No clue. Not enough interest to pursue. Just wanted to debunk the 38 ms latency stuff I read above. It did not match what my ears told me. If I have time I'll do another test and see.What happens if you add an AMP and CAB block?
I don't think you've "debunked" anything. Just made it more mysterious. End to end latency, with an amp and cab block, is most definitely not sub-10 ms like you measured.No clue. Not enough interest to pursue. Just wanted to debunk the 38 ms latency stuff I read above. It did not match what my ears told me. If I have time I'll do another test and see.
Exactly, especially his attention to detail is questionable. 38ms was never mentioned, only 29 from you & 35 from me which was a guess. Also, no one else has heard how it sounds on my system & there is no way it is anywhere near as low as 9.5, 8.2 or 5.2ms. @FractalAudio, is it possible for a corrupted system setting or something else to cause extra latency in the pitch block? I don't think it is a bad firmware install as the issue has been the same in all the betas & the release that had the new pitch block algorithm.I don't think you've "debunked" anything. Just made it more mysterious. End to end latency, with an amp and cab block, is most definitely not sub-10 ms like you measured.
What were your pitch block settings?
So about 20’ish ms is the expected latency here. That I confirmed with the boss. Physics prevent this from being any lower, really.Exactly, especially his attention to detail is questionable. 38ms was never mentioned, only 29 from you & 35 from me which was a guess. Also, no one else has heard how it sounds on my system & there is no way it is anywhere near as low as 9.5, 8.2 or 5.2ms. @FractalAudio, is it possible for a corrupted system setting or something else to cause extra latency in the pitch block? I don't think it is a bad firmware install as the issue has been the same in all the betas & the release that had the new pitch block algorithm.
Thanks Ian! Now I have something solid to go by. Now I just have to find a way to accurately measure the latency I am experiencing here. My gut feeling is it's more than 20ms but it would be nice to know for sure. It may be that this aspect of the pitch block is not for me but I do appreciate the effort Cliff puts into making the Axe better & better. Might as well ask the boss, @FractalAudio, what would be the best way to test to see what latency I am actually getting? Thanks!So about 20’ish ms is the expected latency here. That I confirmed with the boss. Physics prevent this from being any lower, really.
About. That means greater than depending on polyphony and tracking settings.Thanks Ian! Now I have something solid to go by. Now I just have to find a way to accurately measure the latency I am experiencing here. My gut feeling is it's more than 20ms but it would be nice to know for sure. It may be that this aspect of the pitch block is not for me but I do appreciate the effort Cliff puts into making the Axe better & better. Might as well ask the boss, @FractalAudio, what would be the best way to test to see what latency I am actually getting? Thanks!
I would have to agree with decreebass that the latency seems to change being worse when I first start playing & then varying as I play. Simple, easy strumming I can deal with it but intricate, syncopated funk rhythm playing, forget it. Comically bad as I get totally disoriented trying to stay with a click. I thought it was just my imagination about the latency varying but I'm glad to see I'm not the only one experiencing that.Definitely can confirm between 38 and 45ms latency. Again, this may be fine for some people. One weird thing, and I don't know if this is significant or maybe my ears just started to adjust, BUT (and I'll explain my method below) it seems that the latency gets better or worse - it doesn't STAY at 45ms, and it NEVER gets anywhere near under 20 (as iaresee confirmed with the boss, and as I was able to demonstrate to my own satisfaction), but I'd say it got as low as low-30s-ish. It seemed like when I initially create the preset, the latency is the worst, but then if I go back to it, it seems to get a tad bit better (low-30s), but goes back up (again, hovers in the 38-45ms) range.
Not sure if this is some kind of bug or not, but when I first installed FW1.19b and rebooted the AX3 I tried the pitch drop. The virtual capo wasnt implemented yet, but I tried the dual pitch. There was a huge latency. I was surprised because it was quite a bit longer than previous versions. I shut down the AXE3 and restarted. The huge latency was gone. Not sure what happened and am not able to replicate the behavior. Just wondering if this is what decreebass is hearing. Now, I cant really detect any latency, at least on a half step down. It definitely is no worse than "The Drop" pedal.
Hey all.
I just updated to the latest FW and my detuned patches sound terrible, with noticeably worse latency than before. I then changed the type to 'Virtual Capo' from the 'dual shift' I was previously using and... instant bliss! Insignificant latency and much, much more cool than it was before.
So, if you're having hassles with detuned patches, it's worth a tinker to make sure you're using an appropriate setting in the pitch block. The new Virtual Capo was the one that sorted it all out for me.
Thank you Fractal!
To rule out variables:
- Guitar in front input
- Reset the III (Setup > Utility > Reset)
- Create the most simple preset: IN > PITCH > AMP > CAB > OUT
- Reset each block
- Select Virtual Capo
- Test...
To rule out variables:
- Guitar in front input
- Reset the III (Setup > Utility > Reset)
- Create the most simple preset: IN > PITCH > AMP > CAB > OUT
- Reset each block
- Select Virtual Capo
- Test...
Hey Sukh,
So you had issues as well? I'm sure I tried switching from the dual shift to the virtual capo modes and still has no luck. I was getting quite a bit of latency like a sort of slap back delay effect. I think I might try and have another look over the weekend.