Wish Global Virtual Capo

Lumikut

Inspired
Vendor
  • Independent of preset
  • Ability to increment up or down using FC or, ideally an external switch or stand in switch
  • Some sort of visual feedback on the FC. For example, just like it tells you the preset and scene you're on...it could also show the + or - value for the virtual capo regardless of the preset or scene you're on. That way you always have a visual reference
 
I agree with the general idea here. This is why I still use my Drop pedal. The virtual capo is truly impressive, but in many cases it doesn’t make sense to make it part of the amp modeling/effects device preset. I view it as part of the instrument that feeds the AxeFX, independent of AxeFX presets.
 
Last edited:
+1

My current solution is to put a Virtual Capo Pitch block in most of my presets and I have it set as a Global Performance parameter, so I always have it on my Global Perform Page to see it and adjust. This is working pretty well, but I wish I could limit the range: https://forum.fractalaudio.com/threads/modifier-options-for-perform-controls.166713/

Edit: yeah, this didn't end up being the solution either. See these threads:
https://forum.fractalaudio.com/thre...led-state-and-other-bugs.169253/#post-2033961
https://forum.fractalaudio.com/threads/global-virtual-capo.167103/
 
Last edited:
I like it, but wouldn't that mean that you'd have the CPU hit from having a Capo block "in" every preset? (remember that CPU is used whether or not a block is active).

Probably wouldn't matter that much on the III but would significantly affect the FM3.
 
I like it, but wouldn't that mean that you'd have the CPU hit from having a Capo block "in" every preset?

Only when the global capo was enabled. But I think that's kinda the idea. I don't really think this is as useful on the FM3 considering it's got the old capo algorithm which isn't nearly as responsive/useful as the AxeFX's
 
Only when the global capo was enabled. But I think that's kinda the idea. I don't really think this is as useful on the FM3 considering it's got the old capo algorithm which isn't nearly as responsive/useful as the AxeFX's
Maybe it would be different if it was a global setting, but as I said in my post, blocks use CPU whether or not they're active. A global capo would still be a pitch block; it would just come before the grid.
 
Back
Top Bottom