Maybe because the change from High to Normal wouldn't be visible on the grid.
Personally I don't like it when settings are changed "under the hood", I want to know and see what's happening.
Also, that change from High to Normal is an intermediate solution. If Normal doesn't suffice, a second action would be needed to deal with the CPU overload.
It would get too complex. I think it's a good thing to leave it to the user to change the Verb settings.
I am with Yek on this one - I would not like the Ax8 to 'decide' anything on its own.
Don't need to. Just make a global setting that keeps the current behavior.
By the way, the AX8 is ALREADY 'deciding' to shut down the reverb on its own, which is already quite annoying...
it's either that or stop your entire signal. your CPU choices are making the decision if your CPU is close, reduce the Reverb settings yourself before you get to the gig.By the way, the AX8 is ALREADY 'deciding' to shut down the reverb on its own, which is already quite annoying...
it's either that or stop your entire signal. your CPU choices are making the decision if your CPU is close, reduce the Reverb settings yourself before you get to the gig.
can you upload that preset here? if you are in the 87% range, once the AX8 starts actually processing the audio (when you start playing guitar), the CPU will raise 2-3%. this is normal. that audio processing might be pushing it up a bit.More or less. Currently I am facing an issue in one preset that I have (nor sure if it is expected or it is a bug) that when I turn the drive "on" it works for like 1-2min then suddenly the CPU goes up and it shuts down the Verb. And that happens "while" I am playing.
I can proactively choose stuff to be low resolution, but, that happens just while I am using the drive
can you upload that preset here? if you are in the 87% range, once the AX8 starts actually processing the audio (when you start playing guitar), the CPU will raise 2-3%. this is normal. that audio processing might be pushing it up a bit.
if you can export and upload that preset, we can help figure this out if you'd like.
i'll try it out, but i'm just gonna guess this is the thing if your Reverb Echo Density can come down from 8 to 6, or 6 to 4 etc (i haven't seen the preset yet) it probably will take care of it, and probably won't notice any difference in the audio.The CPU usage is around 87%
i'll try it out, but i'm just gonna guess this is the thing if your Reverb Echo Density can come down from 8 to 6, or 6 to 4 etc (i haven't seen the preset yet) it probably will take care of it, and probably won't notice any difference in the audio.
cool. i wouldn't put "fixed" in quotes though, because that is the way to solve a too high CPU issue - reduce CPU.Yes, you are right. Changed the Echo Density from 8 to 6 and it "fixed" it.
But... again... I still think that a "automatic resolution reduction" is a cool feature. I strongly believe is better then just shut down out of nowhere
cool. i wouldn't put "fixed" in quotes though, because that is the way to solve a too high CPU issue - reduce CPU.
though i too am in the camp of "don't change my settings automatically." a disabled block results from a very specific issue. having settings change and not knowing what they are would lead many people to insanity, including myself