• We would like to remind our members that this is a privately owned, run and supported forum. You are here at the invitation and discretion of the owners. As such, rules and standards of conduct will be applied that help keep this forum functioning as the owners desire. These include, but are not limited to, removing content and even access to the forum.

    Please give yourself a refresher on the forum rules you agreed to follow when you signed up.

Is it normal...

Tone_Loc

Member
...for the reverb block to disengage when you access the tuner?

I setup a patch that was on the cusp of CPU usage (around 80%) and was fully functional however the reverb disengaged when I engaged the tuner.

I've also noticed the reverb block disengages at different CPU % values. Is that normal behavior also? It would be good if there was a set % value that we could work too.
 

Smittefar

Fractal Fanatic
The problem could be that the CPU usage actually depends on if and what you are playing. I have never seen anything happening just by engaging the tuner.
 
J

joe rogers

Guest
...for the reverb block to disengage when you access the tuner?

I setup a patch that was on the cusp of CPU usage (around 80%) and was fully functional however the reverb disengaged when I engaged the tuner.

I've also noticed the reverb block disengages at different CPU % values. Is that normal behavior also? It would be good if there was a set % value that we could work too.
What firmware are you running? It is possible with a some presets that the tuner will cause your CPU level to jump up above 90%. If this occurs, the unit starts to disable blocks to bring the usage down. However, if you are using the current firmware (V2.02), as soon as you exit the tuner, the reverb SHOULD return. If for some reason it is not, do something to drop the runtime CPU usage a couple of points.
 
Top Bottom