JiveTurkey
Fractal Fanatic
The true dummy option is to buy a GT1000 where every block in the entire device is in the chain at all times.
Correct.Doesn't the "economy" setting on the cab block only apply to the preamp (and only if you use it in the first place)?
IR length can also be thought of as an economy settingDoesn't the "economy" setting on the cab block only apply to the preamp (and only if you use it in the first place)?
So could "using no more than 1 IR" or "not turning on room mics", but they're not designated as such, so they aren't, IMHO.IR length can also be thought of as an economy setting

Jeez you people can be dense sometimes.So could "using no more than 1 IR" or "not turning on room mics", but they're not designated as such, so they aren't, IMHO.
Also, as per your argument, "using the least CPU intensive model/settings in any block" could also be thought of as an economy setting for each block, but that's what the OP already does; And he basically wants CPU-usage-less null-filters with block-specific mock-up settings, if I understood correctly.![]()
But people who expect Axe III level features out of an FM3 aren't delusional?Jeez you people can be dense sometimes.
There’s literally an option called “economy”, which directly addresses the issue with cpu hungry reverbs. All we’re asking is to apply that same idea to other cpu hungry blocks, especially after an update that overhauls an entire block and changes the workflow for lots of users.
I’m sure it’s not just as simple as adding an economy button to all the compressors. The coding may not be trivial, but it seems like it’s in the realm of possibility and worth asking about.
Now maybe this will all change when the final release comes out, but the people suggesting “just buy more hardware! Problem solved!” really need a reality check
But it really is.
The problem you're trying to solve is having enough processing power to have all the blocks you want to use in a single preset.
I guess this is the wrong place to try and find a solution for a real world problem.
Though my guess is that if Cliff has created Global Blocks for Axe Fx III, I might not be the only one with such needs.
As mentioned before it's not about CPU limitations, in the sense that I expect to use many FX's at a time.Here's the thing: You're butting up against CPU limitations. This isn't new, nor is it exclusive to your particular situation. Cliff could rewrite code for a month to make your wish come true, but then somebody else will come along right behind you and take it right back up to the redline again. So it's a constant battle, and more often than not the best solution is to find a way to get what you need within the confines of the hardware and firmware in its current state. Because no matter what, there will ALWAYS be somebody who wants more, and they will come up with a list of reasons why it should happen.

Again, it IS. Especially in regards to this wish.As mentioned before it's not about CPU limitations, in the sense that I expect to use many FX's at a time.
Yes, I have renamed this thread, and have +1 on the other global blocks wish thread.Yes, Global Blocks could help in your desired use case by spreading things out across multiple presets.
In that case your efforts are probably better spent to add your voice to that wish, although personally I don't expect that Fractal will add Global Blocks at this point.
Another option would be to just use the blocks library to manage any updates across multiple presets.
^THIS^Here's the thing: You're butting up against CPU limitations. This isn't new, nor is it exclusive to your particular situation. Cliff could rewrite code for a month to make your wish come true, but then somebody else will come along right behind you and take it right back up to the redline again. So it's a constant battle, and more often than not the best solution is to find a way to get what you need within the confines of the hardware and firmware in its current state. Because no matter what, there will ALWAYS be somebody who wants more, and they will come up with a list of reasons why it should happen.
[101] We could potentially do two amp blocks but at reduced quality and I don't want to do that. Part of the problem with other modelers is that they don't oversample enough (and use single-precision in places where you need double-precision). Then you get complaints of artifacts and ear fatigue and all the other things associated with inadequate sample rate and word length. The vast majority of users only use one amp block so we wanted to make something with one very high quality "Ares" amp block.
There are many similar statements in the Wiki where he could sacrifice the sound but won't.[24] […] I ALWAYS insist on quality over quantity. That's what differentiates our products. It takes a LOT of horsepower to do it right.
) as this would allow me to use presets, while still keeping consistency.