Mk2 Axe has more "NV" memory (non-volatile, aka storage) due to a change in the NV memory chips.Where will the new ir's be stored on the mk2 axe, will we lose some preset or user ir bank storage space?
You completely miss the point that you may be at a gig and need to build 80 presets between soundcheck and your first set.
Indeed. And that's usually the time to experiment with IRs.
The prefect time, indeed. 2048 IRs, at 10 seconds per IR, only require 5,7 hours to be tested
I fooled around with this a bit. It looks like muted cabs are omitted from the Excel file. True? Or am I missing something?Before applying the upgrade:
1) Use FracTool to list all the links between User CABs and User Presets in a Excel file
2) Highlight the CABS at User Bank 2 that are linked to a preset
3) Move them to Bank 1 and re-link the preset
Coming soon:
Use the Axe-Edit "Save Preset + CAB bundle" feature to save you presets together with the CABs
Thanks for the response. I do recall now 48kHz being the standard or limit. I also recall a few very funny threads on that very thing in the past.The hardware is locked at 48kHz, but IR length will be increased to 1330 ms
I got a dream this morning that 17.00 was released and Cliff managed to incorporate the double the number of upcoming Full res IR's into user bank 2 on the Mk1.
Was a nice dream i must say!
Dude, that's MY jam!Totally! I like to play a riff into the Looper and have it endlessly repeat as I scroll through IRs. The audience loves it!
Totally! I like to play a riff into the Looper and have it endlessly repeat as I scroll through IRs. The audience loves it!
Is an IR made with a distant room mic still considered far-field even though it has room reflections?I doubt it. The IRs used in this clip are room mic IRs. They have lots of reflections. Far-field IRs have (ideally) no reflections.
No because it has reflections. A far-field measurement is only the response of the transducer.Is an IR made with a distant room mic still considered far-field even though it has room reflections?
They'd have to maintain this dual identity moving forward for every FW release. I doubt this is feasible.I'm not sure how much extra work it would be,
But what if 2 separate firmwares were released (16.06HighRes) + (16.06NON) ,
The first having IR slots reduced for the high res , and the second just keeping up with regular firmware updates and not losing out on IR slots, than you'd have the choice ?